SCSI timeouts AHA2940U

Rolf Fokkens (rolf@flits102-126.flits.rug.nl)
Sat, 12 Sep 1998 13:32:38 +0000


Until recently I believed my system was a stable system. I had no
problems at all. But then I did this:

vrec -w -t 260 -s 44100 -S -b 16 | cat | cat | cat | cat > test.wav

Meaning recording from the sound device at 44 kHz, stereo, 16 bits for
260 seconds.

The first time this was successfull, and the second time it was too. But
the third time it resulted in SCSI timeouts:

Aug 23 15:40:20 home01 kernel: scsi : aborting command due to timeout :
pid 5162
1, scsi0, channel 0, id 6, lun 0 UNKNOWN(0x42) 02 40 01 00 00 00 00 10
00
Aug 23 15:40:20 home01 kernel: SCSI host 0 channel 0 reset (pid 51618)
timed out
- trying harder
Aug 23 15:40:20 home01 kernel: SCSI bus is being reset for host 0
channel 0.
Aug 23 15:40:20 home01 kernel: SCSI host 0 abort (pid 51619) timed out -
resetti
ng
Aug 23 15:40:20 home01 kernel: SCSI bus is being reset for host 0
channel 0.
Aug 23 15:40:31 home01 kernel: Sound: Recording overrun
Aug 23 15:40:38 home01 last message repeated 311 times
Aug 23 15:41:13 home01 kernel: nd: Recording overrun
Aug 23 15:41:13 home01 kernel: Sound: Recording overrun
Aug 23 15:41:13 home01 last message repeated 63 times
Aug 23 15:41:13 home01 kernel: SCSI host 0 abort (pid 51752) timed out -
resetti
ng
Aug 23 15:41:13 home01 kernel: SCSI bus is being reset for host 0
channel 0.
Aug 23 15:41:13 home01 kernel: Sound: Recording overrun
Aug 23 15:41:13 home01 last message repeated 21 times
Aug 23 15:41:13 home01 kernel: SCSI host 0 channel 0 reset (pid 51752)
timed out
- trying harder
Aug 23 15:41:13 home01 kernel: SCSI bus is being reset for host 0
channel 0.

Since then I experimented with it, and it appears that that I can
reproduce this behaviour sometimes after calling the vrec thing once,
but allways after calling it three times.

I sent a message to this maillist assuming it had to do with my recently
installed second CPU. It appeared however that this didn't have anything
to do with it.

Most replies I received assured my that lots of people never had trouble
with their aha2940 at all.

Well, to be honest: untill I tried the vrec thing I never had any
trouble too. And as long as I don't use it my system is stable like all
the other stable ones. I wonder however if other people consider their
system stable after they try the vrec thing. If they still consider
their system stable afterwards it must some kind of hardware problem in
my PC, otherwise it might be a driver problem.

More details about my system:

DEC PC5500 dual PII
64MB memory
4GB IBM DCAS, 2 GB IBM DORS
on-board ES1887 sound chip
TELES isdn adapter (Hisax driver)
Ultraplex 32x SCSI CD-ROM

What I tried:

Non-ultra SCSI disk (seagate): There appeared to be no problem at all!
AHA2940UW: same problem
Disconnected CD-ROM: same problem
Removed 1 CPU: same problem
Instructed Adaptec BIOS to use lowest transfer rates: same problem
used shorter SCSI cable: same problem
disable automatic termination: same problem
copied 64mb swap file to another location: same problem sometimes
copied 4 x 640 MB (4CD-s) to non-ultra SCSI disk: no problem at all.

This problem seems to be ultra-scsi related, combined with sound.

Who's willing to stress-test his system the same way? The first attemts
may not result in problems, so retry this a few times.

Rolf Fokkens

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html