Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Jul 1998 17:51:08 -0400 (EDT)
From:      "Robert G. Brown" <rgb@phy.duke.edu>
To:        Doug Ledford <dledford@dialnet.net>
Cc:        "Patrick W. Bryant" <daspwb@Queequeg.Gsu.EDU>, aic7xxx Mailing List <AIC7xxx@FreeBSD.ORG>
Subject:   Re: 5.1.0-pre2-to-pre3
Message-ID:  <Pine.LNX.3.96.980717172749.242B-100000@ganesh.phy.duke.edu>
In-Reply-To: <35AF984B.66D71D82@dialnet.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Phase II.  I separated the driver out into a module and loaded it by
hand from a diskless boot.  I loaded it with verbose:0x1ffff, and
(after a bunch of stuff presumably saying that it downloaded the
sequence code scrolled off in zero time) I get:

(scsi0:-1:-1:-1) Data Parity Error during PCI address or PCI writephase
(scsi0:-1:-1:-1) Received a PCI Target Abort

It appears to come out in a burst of a page or two, a pause for 5-10
seconds, and burst of another page or two (presumably after a reset
attempt?).

If I add the panic_on_abort line, I get the following:

aic7xxx: <Adaptec AIC-7860 Ultra SCSI host adapter> at PCI 6/0
aic7xxx: Initial PCI_COMMAND value was 0x117
aic7xxx: Initial DEVCONFIG value was 0x1100
aic7xxx: <Adaptec AIC-7890/1 Ultra2 SCSI host adapter> at PCI 4/0
aic7xxx: Initial PCI_COMMAND value was 0x1117
aic7xxx: Initial DEVCONFIG value was 0x540
(scsi0:-1:-1:-1) Data Parity Error during PCI address or PCI writephase
(scsi0:-1:-1:-1) Received a PCI Target Abort
aic7xxx driver version 5.1.0pre3
Controller type:
   Adaptec AIC-7890/1 Ultra2 SCSI host adapter
p>flags=0x10804501, p->chip=0x406, p->features=0xf6, sequencer is paused
SIMODE0=0x0, SIMODE1=0x406, SSTAT0=0x0, SSTAT1=0x0, INSTAT=0x0
SCSISIGI=0x0, SXFRCTL0=0x88, SXFRCTL1=0x27, SCSISEQ=0x0, SEQCTL=0x90
SCSIRATE=0x0, SCSIOFFSET=0, SEQADDR=0x1, LASTPHASE=P_MESGIN
QINFIFO: (TAG)
Current SCB: (SCBPTR/TAG/CONTROL) 0/255/0x0
WAITING_SCBS: (SCBPTR/TAG/CONTROL
DISCONNECTED_SCBS: (SCBPTR/TAG/CONTROL)

and after a moment I get:

IRQ DEADLOCK DETECTED BY CPU 0

after the system times out.  I don't think that this really means that
I'm getting a real IRQ deadlock -- this message pops up in SMP kernels
if one doesn't return from an interrupt after a certain amount of
time...

Hope this helps.

   rgb



Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.3.96.980717172749.242B-100000>