From doka@doka.kiev.sovam.com Tue Mar 30 11:40:01 1999
Return-Path: <doka@doka.kiev.sovam.com>
Received: from doka.kiev.sovam.com (doka.kiev.sovam.com [194.186.143.15])
	by hub.freebsd.org (Postfix) with ESMTP id 7576214C3A
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 30 Mar 1999 11:39:57 -0800 (PST)
	(envelope-from doka@doka.kiev.sovam.com)
Received: from doka by doka.kiev.sovam.com with local (Exim 2.12 #1)
	id 10S4MO-00007U-00
	for FreeBSD-gnats-submit@freebsd.org; Tue, 30 Mar 1999 22:39:40 +0300
Message-Id: <E10S4MO-00007U-00@doka.kiev.sovam.com>
Date: Tue, 30 Mar 1999 22:39:40 +0300
From: Vladimir Litovka <doka@doka.kiev.sovam.com>
Reply-To: doka@doka.kiev.sovam.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: aic7895 code failed
X-Send-Pr-Version: 3.2

>Number:         10876
>Category:       kern
>Synopsis:       aic7895 code failed
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 30 11:40:00 PST 1999
>Closed-Date:    Wed Mar 31 04:15:14 PST 1999
>Last-Modified:  Wed Mar 31 04:15:52 PST 1999
>Originator:     Vladimir Litovka
>Release:        FreeBSD 3.1-19990328-STABLE i386
>Organization:
Sovam Teleport Kiev
>Environment:

	Motherboard SuperMicro P6DGS with aic7895 on-board, 3x9Gb IBM DDRS
	HDDs

>Description:

	While booting kernel detects SCSI controller successfully, but
	later panics with such messages on console:

	(probe0:ahc0:0:1:7): parity error during Data-In phase
	SEQADDR == 0x111 (may be 0x110 and 0x112)
	SCSIRATE == 0x88
	[ ... ]
	(probe2:ahc0:0:2:7): parity error during Data-In phase
	SEQADDR == 0x112 (may be 0x110 and 0x111)
	SCSIRATE == 0x88
	[ ... ]
	(probe1:ahc0:0:1:7): parity error during Data-In phase
	SEQADDR == 0x110 (may be 0x111 and 0x112)
	SCSIRATE == 0x88

	At the same time on the 2nd console appear such message:

	Fatal trap 12
	fault virtual address = 0x8
	fault code = supervisor read, page not present
	instruction pointer = 0x8:0xf015fae1
	stack pointer = 0x10:0xf60efac8
	frame pointer = 0x10:0xf60efad4
	code segment = base 0x0, limit 0xfffff, type 0x16
			DPL 0, pres 1, def32 1, gran 1
	processor eflags = interrupt enabled, resume, IOPL = 0
	current process = 1 (sysinstall)
	interrupt mask =
	trap number = 12

>How-To-Repeat:

	Boot from distribution floppies (kernfs.flp and mfsroot.flp)

>Fix:

	Don't know, but need it ASAP! :-)

>Release-Note:
>Audit-Trail:

From: "Justin T. Gibbs" <gibbs@plutotech.com>
To: doka@doka.kiev.sovam.com
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/10876: aic7895 code failed 
Date: Tue, 30 Mar 1999 13:23:29 -0700

 >>Description:
 >
 >	While booting kernel detects SCSI controller successfully, but
 >	later panics with such messages on console:
 >
 >	(probe0:ahc0:0:1:7): parity error during Data-In phase
 >	SEQADDR == 0x111 (may be 0x110 and 0x112)
 >	SCSIRATE == 0x88
 
 There is something wrong with your cabling or termination that is
 causing parity errors to be reported.  This is not a driver bug.
 
 >	Fatal trap 12
 >	fault virtual address = 0x8
 >	fault code = supervisor read, page not present
 >	instruction pointer = 0x8:0xf015fae1
 
 Taking the kernel from the 19990328-STABLE snapshot off of kern.flp:
 nm kernel | sort
 ...
 f015f654 t gcc2_compiled.
 f015f794 T dscheck
 f015fa80 T dsclose
 f015fad4 T dsgone
 f015fb3c T dsioctl
 f01600cc t dsiodone
 
 This is in the middle of dsgone().  Perhaps Bruce (bde@FreeBSD.org)
 can help you out here.  My guess is that if you fix your parity
 problem, the diskslice code will be less confused.
 
 --
 Justin
 
 
 
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Wed Mar 31 04:15:14 PST 1999 
State-Changed-Why:  
Originator notes this turned out to be a cabling problem. 
>Unformatted:
