atom feed20 messages in org.freebsd.freebsd-stableRe: Continuing ahc problems - also ca...
FromSent OnAttachments
Martin KraemerJul 20, 2001 1:50 am 
Matt DillonJul 25, 2001 10:11 am 
Martin KraemerJul 27, 2001 9:51 am 
Brandon D. ValentineJul 27, 2001 10:24 am 
Justin T. GibbsJul 27, 2001 11:58 am 
Martin KraemerJul 30, 2001 1:27 am 
Martin KraemerJul 30, 2001 5:30 am 
Justin T. GibbsJul 30, 2001 7:21 am 
Martin KraemerJul 30, 2001 8:33 am.dmesg, .pciconf, .messages
Martin KraemerJul 30, 2001 8:52 am 
Matt DillonJul 30, 2001 9:46 am 
Chad R. LarsonJul 30, 2001 9:59 am 
Cy Schubert - ITSD Open Systems GroupJul 30, 2001 11:10 am 
Martin KraemerJul 30, 2001 1:28 pm 
Mike HardingJul 30, 2001 9:14 pm 
Martin KraemerJul 30, 2001 11:44 pm 
Michael Sperber [Mr. Preprocessor]Jul 31, 2001 5:00 am.dmesg
Arno J. KlaassenJul 31, 2001 9:48 am 
Justin T. GibbsJul 31, 2001 1:00 pm 
Michael Sperber [Mr. Preprocessor]Aug 2, 2001 9:57 am 
Subject:Re: Continuing ahc problems - also cause fxp failure
From:Martin Kraemer (Mart@fujitsu-siemens.com)
Date:Jul 20, 2001 1:50:53 am
List:org.freebsd.freebsd-stable

Hi Matt, Vladislav,

Sorry for bothering you with this, but you seemed to be the most knowledgeable people about this -- I upgraded from 4.2-STABLE to 4.3-STABLE this week (also cvsup'ed the latter to include fixes, and made world and a kernel with i4b). Since going to 4.3, I see the same messages as you did, first with the on-board aic7880, now with a 2940uw card. Upgrading its bios from 1.23/1.34.3 to 22.0 did not change anything. The bug is unrelated to the disk drive, it appears on da0 as well as on da1. Repeat: I *never* noticed these messages with the 4.2-STABLE kernel (the source of which was from the original 4.2-STABLE CD-ROM).

The original thread starting in may (see http://www.mail-archive.com/freebsd-stable@freebsd.org/msg30014.html) seemed to have died; now I wonder if your problems really went away, and what you actually did (except upgrading the adaptec bios). Do you know whether anybody actually looked at the code, to see what may have triggered this bug in 4.2-STABLE-late and 4.3? Is there possibly a fix in -CURRENT? Who else should I ask?

I only subscribed to freebsd-stable@ today, but I did not find more traces about others suffering from this problem (using google).

Martin Jul 19 18:54:28 deejai2 /kernel: (da1:ahc1:0:1:0): SCB 0xe - timed out while
idle, SEQADDR == 0x177 Jul 19 18:54:30 deejai2 /kernel: STACK == 0x17f, 0x189, 0x0, 0xe Jul 19 18:54:30 deejai2 /kernel: SXFRCTL0 == 0x80 Jul 19 18:54:30 deejai2 /kernel: ahc1: Dumping Card State at SEQADDR 0x177 Jul 19 18:54:31 deejai2 /kernel: SCSISEQ = 0x12, SBLKCTL = 0x2, SSTAT0 0x5 Jul 19 18:54:31 deejai2 /kernel: SCB count = 140 Jul 19 18:54:32 deejai2 /kernel: Kernel NEXTQSCB = 111 Jul 19 18:54:32 deejai2 /kernel: Card NEXTQSCB = 14 Jul 19 18:54:32 deejai2 /kernel: QINFIFO entries: 14 125 2 22 122 83 64 98 Jul 19 18:54:32 deejai2 /kernel: Waiting Queue entries: Jul 19 18:54:32 deejai2 /kernel: Disconnected Queue entries: Jul 19 18:54:32 deejai2 /kernel: QOUTFIFO entries: Jul 19 18:54:32 deejai2 /kernel: Sequencer Free SCB List: 11 3 12 6 9 4 5 0 2 13
15 14 1 8 7 Jul 19 18:54:32 deejai2 /kernel: Pending list: 98 64 83 122 22 2 125 14 Jul 19 18:54:32 deejai2 /kernel: Kernel Free SCB list: 128 115 20 38 109 11 32
27 107 76 85 108 47 95 35 58 129 60 70 101 96 87 19 66 102 112 10 81 61 59 46 23
65 114 63 50 78 82 30 62 54 86 31 43 8 15 48 25 56 127 113 21 12 105 72 121 28
100 49 103 106 51 6 90 41 84 29 119 74 68 13 17 135 94 5 52 104 123 42 9 24 75
39 73 88 77 53 55 40 97 4 92 33 79 37 18 67 126 16 44 57 0 71 26 1 110 124 36 69
93 117 7 118 34 120 45 3 91 89 80 116 136 137 138 139 99 134 133 132 131 130 Jul 19 18:54:32 deejai2 /kernel: Untagged Q(1): 14 Jul 19 18:54:32 deejai2 /kernel: sg[0] - Addr 0x34b2000 : Length 1024 Jul 19 18:54:32 deejai2 /kernel: (da1:ahc1:0:1:0): SCB 14: Immediate reset.
Flags = 0x6040 Jul 19 18:54:32 deejai2 /kernel: (da1:ahc1:0:1:0): no longer in timeout, status
= 34b Jul 19 18:54:32 deejai2 /kernel: ahc1: Issued Channel A Bus Reset. 8 SCBs
aborted

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