[2015] in linux-scsi channel archive
SCSI and VFAT Problem
daemon@ATHENA.MIT.EDU (Ingo Rohloff)
Sun Jun 15 19:14:36 1997
From: Ingo Rohloff <rohloff@informatik.tu-muenchen.de>
To: linux-scsi@vger.rutgers.edu
Date: Mon, 16 Jun 1997 01:08:28 +0200 (MEST)
Hi,
A friend of mine got some problems with his
Adaptec 2940 UW (BIOS V 1.23)
HD: Atlas Quantum 34300 UW
Kernel Version: 2.0.30 (and 2.0.29)
Almost every time you try to do a "ls" on a
VFAT mounted partition the following happens:
(from /var/log/messages:)
Jun 15 22:48:07 TheShades kernel: scsi0: Queue full.
Jun 15 22:48:22 TheShades kernel: scsi : aborting command due to timeout :
pid 4987, scsi0, channel 0, id 0, lun 0 Read (6) 04 09 75 01 00
Jun 15 22:48:22 TheShades kernel: aic7xxx: (abort) Aborting scb 1, TCL 0/0/0
Jun 15 22:48:22 TheShades kernel: scsi : aborting command due to timeout :
pid 4988, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 60 35 c4 00 00 02
00
Jun 15 22:48:22 TheShades kernel: aic7xxx: (abort) Aborting scb 0, TCL 0/0/0
Jun 15 22:48:37 TheShades kernel: scsi : aborting command due to timeout :
pid 4987, scsi0, channel 0, id 0, lun 0 Read (6) 04 09 75 01 00
Jun 15 22:48:37 TheShades kernel: aic7xxx: (abort) Aborting scb 1, TCL 0/0/0
Jun 15 22:48:37 TheShades kernel: SCSI host 0 abort (pid 4987) timed out -
resetting
Jun 15 22:48:37 TheShades kernel: SCSI bus is being reset for host 0 channel
0.
Jun 15 22:48:37 TheShades kernel: aic7xxx: (reset) target/channel 0/0
Jun 15 22:48:37 TheShades kernel: aic7xxx: (abort_reset) scb state 0x1,
Data-In phase, SCSISIGI = 0x44
Jun 15 22:48:37 TheShades kernel: aic7xxx: (abort_scb) asserted ATN - bus
device reset in message buffer.
Jun 15 22:48:37 TheShades kernel: scsi : aborting command due to timeout :
pid 4988, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 60 35 c4 00 00 02
00
Jun 15 22:48:37 TheShades kernel: aic7xxx: (abort) Aborting scb 0, TCL 0/0/0
Jun 15 22:48:37 TheShades kernel: SCSI host 0 abort (pid 4988) timed out -
resetting
Jun 15 22:48:37 TheShades kernel: SCSI bus is being reset for host 0 channel
0.
Jun 15 22:48:37 TheShades kernel: aic7xxx: (reset) target/channel 0/0
Jun 15 22:48:37 TheShades kernel: aic7xxx: (abort_reset) scb state 0x1,
Data-In phase, SCSISIGI = 0x54
Jun 15 22:48:37 TheShades kernel: aic7xxx: (abort_scb) asserted ATN - bus
device reset in message buffer.
Jun 15 22:48:39 TheShades kernel: SCSI host 0 channel 0 reset (pid 4987)
timed out - trying harder
Jun 15 22:48:39 TheShades kernel: SCSI bus is being reset for host 0 channel
0.
Jun 15 22:48:39 TheShades kernel: aic7xxx: (reset) target/channel 0/0
Jun 15 22:48:39 TheShades kernel: aic7xxx: (reset_device) target/channel
-1/A, active_scb 1
Jun 15 22:48:39 TheShades kernel: aic7xxx: (match_scb) comparing
target/channel -1/A to scb 0/A
Jun 15 22:48:53 TheShades kernel: aic7xxx: (reset_device) aborting SCB 1,
TCL=0/0/0
Jun 15 22:48:53 TheShades kernel: aic7xxx: (match_scb) comparing
target/channel -1/A to scb 0/A
Jun 15 22:48:53 TheShades kernel: aic7xxx: (reset_device) aborting SCB 0,
TCL=0/0/0
Jun 15 22:48:53 TheShades kernel: aic7xxx: (match_scb) comparing
target/channel -1/A to scb 0/A
Jun 15 22:48:53 TheShades kernel: aic7xxx: (match_scb) comparing
target/channel -1/A to scb 0/A
Jun 15 22:48:53 TheShades kernel: aic7xxx: (reset_channel) Resetting current
channel A
Jun 15 22:48:53 TheShades kernel: aic7xxx: (reset_channel) Channel reset,
sequencer restarted
Jun 15 22:48:53 TheShades kernel: aic7xxx: (done_aborted_scbs) Aborting scb
0, TCL=0/0/0
Jun 15 22:48:53 TheShades kernel: aic7xxx: (done_aborted_scbs) Aborting scb
1, TCL=0/0/0
Jun 15 22:48:53 TheShades kernel: scsi0: Received MSG_WDTR, Target 0,
channel A needwdtr(0xfff9).
Jun 15 22:48:53 TheShades kernel: scsi0: Target 0, channel A, using 16 bit
transfers.
Jun 15 22:48:53 TheShades kernel: scsi0: Target 0, channel A, now
synchronous at 10.0MHz, offset 8.
Some times the whole bunch of messages is repeated (some times even more
than once).
This problem is only encountered on VFAT mounted partiotions, as
far as we know.
Copying files works well (as far as checked), only ls produces this
strange errors (not always but almost always).
Any suggestions ?
so long
Ingo
-------------------------------------------------------
Ingo Rohloff tel 089/9102606
rohloff@informatik.tu-muenchen.de
-------------------------------------------------------
