[234] in linux-scsi channel archive
Re: A few cleanups to 1.2.9, and a request for help.
daemon@ATHENA.MIT.EDU (Steven N. Hirsch)
Tue Jun 6 18:11:43 1995
Date: Tue, 6 Jun 1995 17:21:13 -0400 (EDT)
From: "Steven N. Hirsch" <hirsch@emba.uvm.edu>
To: John Newnham <jnewnham@broncho.ct.monash.edu.au>
Cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <9506061126.AA25083@broncho.ct.monash.edu.au>
On Tue, 6 Jun 1995, John Newnham wrote:
> [ Executive summary: found some buglets, but still got a
> scsi timeout that is fixed by defining DEBUG in sd.c,
> seagate controller, XT-4380S hard disk, what can I do? ]
>
> Hello *,
>
> Two spelling bugs in scsi.c: "problemes" rather than
> "problems", and "to" instead of "too" on the same line;
>
> A printk() enabled by DEBUG_DELAY appears to be missing an
> argument;
>
> The line which is #ifdef notyet (near TEXEL borken support)))
> has too many close parentheses;
>
> "on" should be "one" in the comment at the top of sd.c:rw_intr().
>
> None of these affect functionality in any way, so they are
> perfect candidates for fixing in the 1.2 release ;-).
>
>
I haven't run into any compilation problems with the most recent
pre-release..
> Now for my problems. I have a 486-DX33 ISA system with 16Mb
> BUT, under load the drive times out, the kernel tries to abort,
> that times out, then the kernel tries to do a reset and ends
> up panicing (sp?). With 1.2.4 this was very easy to do (often
> just the daemons in rc.M would do it), under 1.2.9 it is harder
> to do, but still predictable: cat doom.wad >>/dev/null will
> get it every time.
>
>
> The path of the crash is repeatable, the trace is always:
> scsi_done
> seagate_st0x_queue_command
> seagate_st0x_queue_command
> scsi_request_sense
> scsi_done <- hmm...
> scsi_reset
> scsi_times_out
> scan_scsis <- huh?
> scsi_main_timeout
>
> with printks "command timed out", "abort timed out - resetting"
> "Danger Will Robinson", "disk error", "I/O error"
> "kernel NULL ptr dereference" ... register dump, not syncing.
>
> If anybody can help me with this (or point me at some patches
> that may fix it), I would much appreciate it. I can supply
> actual EIP values, stack contents etc. if needed.
>
I have a Maxtor XT-4170S and have seen symptoms almost identical to the
ones that you describe! I suspect that the Maxtor SCSI drives have
problems with 10 meg/sec synchronous SCSI operation. When I backed down
to 5.7, the symptoms pretty much vanished. A drive of that vintage
probably can't stream data much faster than that anyway.
- Steve
____________________________________________________________________________
|Steven N. Hirsch "Anything worth doing is worth |
|University of Vermont overdoing.." - Hunter S. Thompson|
|Computer Science / EE |
----------------------------------------------------------------------------
