BDR messages for Adaptec card

Tue Mar 9 22:53:54 PST 2004

Hi,

I enabled CAMDEBUG in the kernel and got the logs at the time the problem happens. I have trimmed down the logs considerably as it generated a huge file. If after looking at the logs someone can even explain me what the problem might be (without bothering for the solution) it would be a great help.

Thanks.

fc scsi <scsi_fc_group at yahoo.com> wrote: 

Hi,

I am getting the error messages mentioned below on my system using the following Adaptec card on FreeBSD 4.7:

========================================================================

ahc0: <Adaptec 29160B Ultra160 SCSI adapter> port 0xde00-0xdeff mem 0xfe9df000-0

xfe9dffff irq 3 at device 8.0 on pci1

aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

=========================================================================

Mar 2 03:02:37 /kernel: (da0:ahc0:0:0:0): SCB 0x8 - timed out

Mar 2 03:02:37 /kernel: ahc0: Dumping Card State while idle, at SEQADDR 0x8

Mar 2 03:02:37 /kernel: ACCUM = 0x0, SINDEX = 0x9, DINDEX = 0xe4, ARG_2 = 0x0

Mar 2 03:02:37 /kernel: HCNT = 0x0 SCBPTR = 0x0

Mar 2 03:02:37 /kernel: SCSISEQ = 0x12, SBLKCTL = 0xa

Mar 2 03:02:37 /kernel: DFCNTRL = 0x0, DFSTATUS = 0x89

Mar 2 03:02:37 /kernel: LASTPHASE = 0x1, SCSISIGI = 0x0, SXFRCTL0 = 0x80

Mar 2 03:02:37 /kernel: SSTAT0 = 0x0, SSTAT1 = 0x8

Mar 2 03:02:37 /kernel: SCSIPHASE = 0x0

Mar 2 03:02:37 /kernel: STACK == 0x3, 0x108, 0x160, 0x0

Mar 2 03:02:37 /kernel: SCB count = 20

Mar 2 03:02:37 /kernel: Kernel NEXTQSCB = 14

Mar 2 03:02:37 /kernel: Card NEXTQSCB = 14

Mar 2 03:02:37 /kernel: QINFIFO entries:

Mar 2 03:02:37 /kernel: Waiting Queue entries:

Mar 2 03:02:37 /kernel: Disconnected Queue entries: 1:8

Mar 2 03:02:37 /kernel: QOUTFIFO entries:

Mar 2 03:02:37 /kernel: Sequencer Free SCB List: 0 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Mar 2 03:02:37 /kernel: Sequencer SCB Info: 0(c 0x40, s 0x17, l 0, t 0xff) 1(c 0x44, s 0x7, l 0, t 0x8) 2(c 0x0, s 0xff, l 255, t 0xff) 3(c 0x0, s 0xff, l 255, t 0xff) 4(c 0x0, s 0xff, l 255, t 0xff) 5(c 0x0, s 0xff, l 255, t 0xff) 6(c 0x0, s 0xff, l 255, t 0xff) 7(c 0x0, s 0xff, l 255, t 0xff) 8(c 0x0, s 0xff, l 255, t 0xff) 9(c 0x0, s 0xff, l 255, t 0xff) 10(c 0x0, s 0xff, l 255, t 0xff) 11(c 0x0, s 0xff, l 255, t 0xff) 12(c 0x0, s 0xff, l 255, t 0xff) 13(c 0x0, s 0xff, l 255, t 0xff) 14(c 0x0, s 0xff, l 255, t 0xff) 15(c 0x0, s 0xff, l 255, t 0xff) 16(c 0x0, s 0xff, l 255, t 0xff) 17(c 0x0, s 0xff, l 255, t 0xff) 18(c 0x0, s 0xff, l 255, t 0xff) 19(c 0x0, s 0xff, l 255, t 0xff) 20(c 0x0, s 0xff, l 255, t 0xff) 21(c 0x0, s 0xff, l 255, t 0xff) 22(c 0x0, s 0xff, l 255, t 0xff) 23(c 0x0, s 0xff, l 255, t 0xff) 24(c 0x0, s 0xff, l 255, t 0xff) 25(c 0x0, s 0xff, l 255, t 0xff) 26(c 0x0, s 0xff, l 255, t 0xff) 27(c 0x0, s 0xff, l 255, t 0xff) 28(c 0x0, s 0xff, l 255, t 0xff) 29(
 c 0x0, s
 0xff, l 255, t 0xff) 30(c 0x0, s 0xff, l

Mar 2 03:02:37 /kernel: 0xff) 31(c 0x0, s 0xff, l 255, t 0xff)

Mar 2 03:02:37 /kernel: Pending list: 8(c 0x40, s 0x7, l 0)

Mar 2 03:02:37 /kernel: Kernel Free SCB list: 9 15 16 17 18 19 0 1 2 3 4 5 6 7 13 12 11 10

Mar 2 03:02:37 /kernel: Untagged Q(0): 8

Mar 2 03:02:37 /kernel: sg[0] - Addr 0x6514000 : Length 2048

Mar 2 03:02:37 /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB

Mar 2 03:02:37 /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent

Mar 2 03:02:37 /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 34b

Mar 2 03:02:37 /kernel: ahc0: Bus Device Reset on A:0. 1 SCBs aborted

==========================================================================

# camcontrol negotiate da0

Current Parameters:

(pass0:ahc0:0:0:0): sync parameter: 10

(pass0:ahc0:0:0:0): frequency: 40.000MHz

(pass0:ahc0:0:0:0): offset: 31

(pass0:ahc0:0:0:0): bus width: 16 bits

(pass0:ahc0:0:0:0): disconnection is enabled

(pass0:ahc0:0:0:0): tagged queueing is disabled

===========================================================================

This is happening mostly in case of heavy I/O. I am using the default driver which came with the 4.7 kernel. Just wanted to know if there is already a solution to this problem in form of any driver patch or any workarounds (any tunable parameters like timeouts, etc.) which can be useful in eliminating the above messages. 

Also, can somebody point me to the latest driver for FreeBSD 4.7 for the above card which I can download and try out. I tried searching on Adaptec's site but couldn't find one for FreeBSD for the above card:

(http://www.adaptec.com/worldwide/support/suppbyproduct.html?sess=no&language=English+US&cat=/Technology/SCSI+Host+Adapters&fromPage=driverindex)

Any information in this regard will be a great help.

Regards.

---------------------------------
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster.

---------------------------------
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: messages.BDR.camdebug-T-I-c
Type: application/octet-stream
Size: 26776 bytes
Desc: messages.BDR.camdebug-T-I-c
Url : http://lists.freebsd.org/pipermail/freebsd-scsi/attachments/20040309/5ac0ace2/messages.BDR.obj