Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Mar 2001 12:48:06 -0800
From:      "Brett G. Lemoine" <bl@incyte.com>
To:        "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: ahc - Invalidating pack 
Message-ID:  <200103232048.MAA19814@blah.incyte.com>
In-Reply-To: Your message of "Fri, 23 Mar 2001 13:17:11 MST." <200103232017.f2NKHBs16971@aslan.scsiguy.com> 

next in thread | previous in thread | raw e-mail | index | archive | help

> >
> >Well, crap.  I'm still getting them with a kernel built from a
> >cvsup yesterday early afternoon.
> >
> >(da2:ahc1:0:6:0): SCB 0x3 - timed out while idle, SEQADDR == 0x8
> >STACK == 0x3, 0x110, 0x166, 0x0
> >SXFRCTL0 == 0x80
> >ahc1: Dumping Card State at SEQADDR 0x8
> >SCSISEQ = 0x12, SBLKCTL = 0x6, SSTAT0 0x0
> >SCB count = 20
> >Kernel NEXTQSCB = 4
> >Card NEXTQSCB = 4
> >QINFIFO entries:
> >Waiting Queue entries:
> >Disconnected Queue entries: 0:3
> >QOUTFIFO entries:
> >Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 
> 21
> > 2
> >2 23 24 25 26 27 28 29 30 31
> >Pending list: 3
> >Kernel Free SCB list: 14 15 16 17 18 19 0 1 2 5 6 7 8 9 13 12 11 10
> >Untagged Q(6): 3
> >sg[0] - Addr 0xca3a900 : Length 8
> >(da2:ahc1:0:6:0): Queuing a BDR SCB
> >(da2:ahc1:0:6:0): Bus Device Reset Message Sent
> >(da2:ahc1:0:6:0): no longer in timeout, status = 34b
> >ahc1: Bus Device Reset on A:6. 1 SCBs aborted
> >da2 at ahc1 bus 0 target 6 lun 0
> >da2: <iomega jaz 2GB E.17> Removable Direct Access SCSI-2 device
> >da2: 20.000MB/s transfers (20.000MHz, offset 15)
> >da2: 1911MB (3915600 512 byte sectors: 255H 63S/T 243C)
> 
> This looks like a device issue.  From what the controller can tell,
> the jaz drive never re-selects us after taking a command and disconnecting.

I had the same errors on my root drive (SEAGATE ST318404LW) too, I
just didn't get to capture it.

> >I'm also still getting the below messages anytime I try to use
> >the on-board ES1371 sound.
> 
> Noisy bus I suppose.
> 
> >What are the chances that these are unrelated?
> 
> You might be able to figure that out with a PCI bus analyzer and
> a SCSI bus analyzer.

Well those are two items I've never seen, much less owned or know how to
use.  Any suggestions on where I should go from here?  Any way to get
additional information that might better pin down where the fault lies?

I'm perfectly happy to jump through hoops to get this figured out, but
I don't know what other info that I can get would be most useful.

bl
--
//====== Brett G. Lemoine -=- <bl@incyte.com> ===============================\\
|| Info. Systems Architect |                                                 ||
||Core Unix System Services|              We have enough youth.              ||
||     Incyte Genomics     |          How about a fountain of SMART?         ||
||  Palo Alto, California  |                                                 ||
|+-------------------------+-------------------------------------------------+|
\\== PGP Key Fingerprint: 68 A1 2A 2D 82 CE E9 70  5B 80 D1 11 EC F3 FB 85 ==//

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103232048.MAA19814>