public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] instrument ide-scsi in 2.5.68
Date: Thu, 08 May 2003 10:00:58 +1000	[thread overview]
Message-ID: <3EB99E3A.9060005@torque.net> (raw)
In-Reply-To: <20030507142057.760f426b.rddunlap@osdl.org>

Randy.Dunlap wrote:
> | Hi Doug-
> 
> | On Wed, 07 May 2003 23:21:43 +1000 Douglas Gilbert <dougg@torque.net> wrote:
> | 
> | | Randy.Dunlap wrote:
> | | > On Tue, 06 May 2003 18:38:39 +1000 Douglas Gilbert <dougg@torque.net> wrote:
> | | > 
> | | > | > Are there any docs on SCSI logging?
> | | 
> | | Do your failures only occur in an SMP environment?
> | 
> | I'll try 2.5.69 plus your patch ver. 2.
> 
> 2.5.69 + your ide-scsi ver. 2 patch, booted with "nosmp":
> 
>   hangs/locks up during boot sequence, immediately after this:
> 
> end_request: I/O error, dev hdc, sector 0
> scsi0 : SCSI host adapter emulation for IDE ATAPI devices
> ide-scsi: hdd: que 1, cmd = [ 12 0 0 0 24 0 ]
> ide-scsi: abort called for cmd serial #1
> ide-scsi: abort ignored
> ide-scsi: reset called for 1
> ide-scsi: device reset partially ignored
> ide-scsi: hdd: que 1, cmd = [ 0 0 0 0 0 0 ]
> ide-scsi: abort called for cmd serial #1
> ide-scsi: abort ignored
> scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 0 lun 0
> 
> 
> same kernel without "nosmp", so it's dual-proc P4:
> 
>   I ran cdrecord, got to an error, cdrecord had a segfault.
> 
> Not much help I'm sorry to say.
> 
> Complete logs are here:
>   http://www.xenotime.net/linux/capt-2569-nosmp-locked.txt

Randy,
The "nosmp" failed on the very first SCSI command sent
to the device (36 byte INQUIRY during scan). Looks
like the 'rq->flags' were cleared (corruption) and
the end_request was routed through ide_end_request().

Good to see the scsi error handling took the device
offline. Did the device lock up or the whole machine?

> and
>   http://www.xenotime.net/linux/capt-2569-isc-dual-segv.txt

Got a bit further than last time but failed on the same
command, again with corrupted fields.

Perhaps you could send me your .config file so I can
set up my IDE subsystem the same way as yours.

Doug Gilbert



      reply	other threads:[~2003-05-07 23:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01 13:02 [PATCH] instrument ide-scsi in 2.5.68 Douglas Gilbert
2003-05-01 22:52 ` Randy.Dunlap
2003-05-01 22:57   ` Randy.Dunlap
2003-05-01 23:29   ` Douglas Gilbert
2003-05-01 23:44     ` Willem Riede
2003-05-02  0:38     ` Randy.Dunlap
2003-05-02  1:10       ` Douglas Gilbert
2003-05-02  8:40 ` Douglas Gilbert
2003-05-02 16:55   ` Randy.Dunlap
2003-05-03  9:03     ` Douglas Gilbert
2003-05-05  8:46       ` Mike Anderson
2003-05-05 16:57       ` Randy.Dunlap
2003-05-06  8:38         ` Douglas Gilbert
2003-05-06 14:39           ` Randy.Dunlap
2003-05-07 13:21             ` Douglas Gilbert
2003-05-07 18:16               ` Randy.Dunlap
2003-05-07 21:20                 ` Randy.Dunlap
2003-05-08  0:00                   ` Douglas Gilbert [this message]

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=3EB99E3A.9060005@torque.net \
    --to=dougg@torque.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rddunlap@osdl.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