linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Holger Kiehl <Holger.Kiehl@dwd.de>
To: <linux-kernel@vger.kernel.org>
Subject: AIC7xxx errors in 2.2.19 but not in 2.2.18
Date: Fri, 14 Sep 2001 11:34:46 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.30.0109141121010.27057-100000@talentix.dwd.de> (raw)

Hello

I am getting SCSI errors with an onboard Adaptec AIC-7890/1 Ultra2, but
only under very heavy disk load and only under kernel 2.2.19. These errors
do not appear under 2.2.18.

The system I have is a dual PIII-450 with 6 disks attached to the controller.
All disks are put together in SW-Raid5 array with one configured as hot
spare.

The errors under 2.2.19 look as follows:

 scsi : aborting command due to timeout : pid 52414, scsi0, channel 0, id 0, lun 0 Read (10) 00 00 ba f3 76 00 00 18 00
 scsi : aborting command due to timeout : pid 52416, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 ba f4 0e 00 00 80 00
 (scsi0:0:1:0) SCSISIGI 0x4, SEQADDR 0x77, SSTAT0 0x0, SSTAT1 0x2
 (scsi0:0:1:0) SG_CACHEPTR 0x8, SSTAT2 0x40, STCNT 0x5fc
 scsi : aborting command due to timeout : pid 52417, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 ba f4 8e 00 00 80 00
 scsi : aborting command due to timeout : pid 52419, scsi0, channel 0, id 2, lun 0 Write (10) 00 00 ba f4 0e 00 00 80 00
 scsi : aborting command due to timeout : pid 52420, scsi0, channel 0, id 2, lun 0 Write (10) 00 00 ba f4 8e 00 00 80 00
 scsi : aborting command due to timeout : pid 52422, scsi0, channel 0, id 3, lun 0 Write (10) 00 00 ba f4 0e 00 00 80 00
 scsi : aborting command due to timeout : pid 52423, scsi0, channel 0, id 3, lun 0 Write (10) 00 00 ba f4 8e 00 00 80 00
 scsi : aborting command due to timeout : pid 52425, scsi0, channel 0, id 4, lun 0 Write (10) 00 00 1c ed 06 00 00 08 00
 scsi : aborting command due to timeout : pid 52426, scsi0, channel 0, id 4, lun 0 Write (10) 00 00 ba f3 8e 00 00 80 00
 scsi : aborting command due to timeout : pid 52427, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 ba f3 8e 00 00 80 00
 scsi : aborting command due to timeout : pid 52428, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 ba f5 0e 00 00 80 00
 scsi : aborting command due to timeout : pid 52429, scsi0, channel 0, id 3, lun 0 Write (10) 00 00 ba f5 0e 00 00 80 00
 scsi : aborting command due to timeout : pid 52430, scsi0, channel 0, id 2, lun 0 Write (10) 00 00 ba f5 0e 00 00 80 00
 scsi : aborting command due to timeout : pid 52431, scsi0, channel 0, id 4, lun 0 Write (10) 00 00 ba f4 0e 00 00 80 00
 scsi : aborting command due to timeout : pid 52432, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 ba f4 0e 00 00 80 00
 SCSI host 0 abort (pid 52416) timed out - resetting
 SCSI bus is being reset for host 0 channel 0.

 wait_on_bh, CPU 1:
 irq:  0 [0 0]
 bh:   1 [1 0]
 <[c010aead]> <[c0199ffc]> <[c019ab9b]> <[c01a3860]> <6>(scsi0:0:4:0) Synchronous at 80.0 Mbyte/sec, offset 31.
 (scsi0:0:2:0) Synchronous at 80.0 Mbyte/sec, offset 63.
 (scsi0:0:3:0) Synchronous at 80.0 Mbyte/sec, offset 31.
 (scsi0:0:1:0) Synchronous at 80.0 Mbyte/sec, offset 31.
 (scsi0:0:0:0) Synchronous at 80.0 Mbyte/sec, offset 31.
 scsi : aborting command due to timeout : pid 53513, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 bb 4c f6 00 00 80 00
 (scsi0:0:1:0) SCSISIGI 0x4, SEQADDR 0x62, SSTAT0 0x0, SSTAT1 0x2
 (scsi0:0:1:0) SG_CACHEPTR 0x3c, SSTAT2 0x40, STCNT 0x3fc
 scsi : aborting command due to timeout : pid 53514, scsi0, channel 0, id 2, lun 0 Write (10) 00 00 bb 4a f6 00 00 80 00
 scsi : aborting command due to timeout : pid 53515, scsi0, channel 0, id 3, lun 0 Write (10) 00 00 bb 4c f6 00 00 80 00
 scsi : aborting command due to timeout : pid 53516, scsi0, channel 0, id 4, lun 0 Write (10) 00 00 bb 4a f6 00 00 80 00
 scsi : aborting command due to timeout : pid 53517, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 bb 4d 76 00 00 40 00
 scsi : aborting command due to timeout : pid 53518, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 bb 4d 76 00 00 40 00
 scsi : aborting command due to timeout : pid 53519, scsi0, channel 0, id 3, lun 0 Write (10) 00 00 bb 4d 76 00 00 40 00
 scsi : aborting command due to timeout : pid 53520, scsi0, channel 0, id 2, lun 0 Write (10) 00 00 ba fb 86 00 00 08 00
 scsi : aborting command due to timeout : pid 53521, scsi0, channel 0, id 4, lun 0 Write (10) 00 00 ba fb 86 00 00 08 00
 scsi : aborting command due to timeout : pid 53522, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 bb 4d be 00 00 30 00
 scsi : aborting command due to timeout : pid 53523, scsi0, channel 0, id 1, lun 0 Write (10) 00 00 bb 4d be 00 00 30 00
 scsi : aborting command due to timeout : pid 53524, scsi0, channel 0, id 3, lun 0 Write (10) 00 00 bb 4d be 00 00 30 00
 scsi : aborting command due to timeout : pid 53525, scsi0, channel 0, id 4, lun 0 Write (10) 00 00 bb 4b 76 00 00 80 00
 scsi : aborting command due to timeout : pid 53526, scsi0, channel 0, id 2, lun 0 Write (10) 00 00 bb 4b 76 00 00 80 00
 scsi : aborting command due to timeout : pid 53527, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 bb 4b f6 00 00 80 00
 SCSI host 0 abort (pid 53513) timed out - resetting
 SCSI bus is being reset for host 0 channel 0.
 (scsi0:0:4:0) Synchronous at 80.0 Mbyte/sec, offset 31.
 (scsi0:0:3:0) Synchronous at 80.0 Mbyte/sec, offset 31.
 (scsi0:0:2:0) Synchronous at 80.0 Mbyte/sec, offset 63.
 (scsi0:0:1:0) Synchronous at 80.0 Mbyte/sec, offset 31.
 (scsi0:0:0:0) Synchronous at 80.0 Mbyte/sec, offset 31.

>From Alan's changelog I see that there where changes in the AIC7xxx code.
Any idea what is wrong here?

Thanks,
Holger


             reply	other threads:[~2001-09-14  9:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-14  9:34 Holger Kiehl [this message]
2001-09-14 13:11 ` AIC7xxx errors in 2.2.19 but not in 2.2.18 Frank Schneider
2001-09-14 13:37   ` Andreas Steinmetz
2001-09-15 15:37     ` Doug Ledford
2001-09-15 15:42       ` Andreas Steinmetz
2001-09-14 13:46   ` Holger Kiehl
2001-09-14 17:12     ` Mike Fedyk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.30.0109141121010.27057-100000@talentix.dwd.de \
    --to=holger.kiehl@dwd.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).