lkml.org 
[lkml]   [2000]   [Aug]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.4.0-test4&6 scsi tape problem [not fixed :-/]
On Thu, 31 Aug 2000, G. Saraber wrote:

> "Richard B. Johnson" wrote:
> >
> > On Wed, 30 Aug 2000, G. Saraber wrote:
> >
> > > Thanks for the excellent guide on how to pinpoint the problem ...
> > >
> > > guess what :-) I decided before I send in another bugreport i'll upgrade
> > > to test7 so the developers dont have to dig through 'old' kernel
> > > versions ..
> > > anyway, the problem went away, they must have fixed it :-)
>
> ok,

[SNIPPED...]
Looks like your SCSI tape drive is getting hung and has grabbed the
bus <forever>.

Finally, the SCSI driver makes the last-ditch effort by aborting
everything and resetting the bus.


> Aug 31 00:57:20 ahr kernel: SCSI bus is being reset for host 0 channel
> 0.
> Aug 31 00:57:20 ahr kernel: (scsi0:0:5:0) Synchronous at 10.0 Mbyte/sec,
> offset 15.
> Aug 31 00:57:20 ahr kernel: (scsi0:0:3:0) Synchronous at 80.0 Mbyte/sec,
> offset 31.
> Aug 31 00:57:20 ahr kernel: (scsi0:0:4:0) Synchronous at 80.0 Mbyte/sec,
> offset 31.
> Aug 31 00:57:25 ahr kernel: st0: Error with sense data: Info fld=0x40,
> Current st09:00: sns = f0 6
> Aug 31 00:57:25 ahr kernel: ASC=29 ASCQ= 0

Now you have a device not-ready.

> Aug 31 00:57:25 ahr kernel: Raw sense data:0xf0 0x00 0x06 0x00 0x00 0x00
> 0x40 0x12 0x00 0x00 0x00 0x00 0x29 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> 0x00 0x00 0x00 0x00 0x00 0x00
> Aug 31 00:57:25 ahr kernel: st0: Error with sense data: Info fld=0x1,
> Current st09:00: sns = f0 2
> Aug 31 00:57:25 ahr kernel: ASC= 4 ASCQ= 1

And the device is now becoming ready.

> Aug 31 00:57:25 ahr kernel: Raw sense data:0xf0 0x00 0x02 0x00 0x00 0x00
> 0x01 0x12 0x00 0x00 0x00 0x00 0x04 0x01 0x00 0x00 0x00 0x00 0x00 0x00
> 0x00 0x00 0x00 0x00 0x00 0x00
> Aug 31 00:57:25 ahr kernel: st0: Error on write filemark.
>

Maybe your drive can't handle the synchronous speed? Maybe it's too
hot? Maybe anything. The kernel code __seems__ to be trying its
hardest to handle a problem with the drive. The new kernel may
be slightly faster in its transfer-rate, triggering a latent problem
with the drive. I'd first try backing off on the sync-speed (through
the SCSI BIOS).


Cheers,
Dick Johnson

Penguin : Linux version 2.2.15 on an i686 machine (797.90 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.


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

\
 
 \ /
  Last update: 2005-03-22 12:38    [W:0.033 / U:23.048 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site