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: Fri, 02 May 2003 11:10:15 +1000	[thread overview]
Message-ID: <3EB1C577.1050204@torque.net> (raw)
In-Reply-To: <20030501173806.4fb6a663.rddunlap@osdl.org>

Randy.Dunlap wrote:
> On Fri, 02 May 2003 09:29:55 +1000 Douglas Gilbert <dougg@torque.net> wrote:
> 
> | Randy.Dunlap wrote:
> | <snip/>
> | 
> | > Hi Doug,
> | > 
> | > I have ATAPI CD-ROM as hdc and CD-RW as hdd.  I boot with
> | > "hdd=icd-scsi ide-scsi.debug=3".  Is that right/OK so far?
> | > If not, what should it be?
> | 
> | Randy,
> | I thought so but it's not picking "ide-scsi.debug=3" up:
> | 
> |  > Kernel command line: auto BOOT_IMAGE=lin2568isc ro root=304
> |    >  devfs=nomount hdd=ide-scsi ide-scsi.debug=3 console=tty0
> |    >  console=ttyS0,38400n8 debug
> |  > ide_setup: hdd=ide-scsi
> |  > ide_setup: ide-scsi.debug=3 -- BAD OPTION
> 
> Yes, I noticed that.  So I changed it to "ide_scsi.debug=3" and got
> the same message.  So I changed it to "idescsi.debug=3" and still
> get error messages...??
> 
> Anyway, I set the sysfs file values to 3 and 1 (debug and suppress_reset)
> [since it boots now for some unknown reason] and tried to burn another
> CD.  Now I have just another coaster.  :)
> 
> The system is hung-up again, no keyboard, no messages on serial console.
> 
> In the future I should probably use ide-scsi as a module to see if the
> parameters work OK.  And I'll look into the parameters for built-in
> drivers too (on my long todo list).

Randy,
Thanks for trying this. It would be great to see which
command it is locking up on.

Since you see the problem at driver load time, perhaps
this is related to what Matthew Dharm has been seeing
with some USB devices. Namely when these devices get
a SCSI command that don't like (e.g. INQUIRY with the
EVPD bit set **) they lock up. If this is the case then
the ide-scsi driver may be needing that command filter
as well.


** Patrick Mansfield has submitted a patch (now in Linus's
bk snapshots) that removes the VPD=0x83 code from device
scans. Not sure if this is a forward step. Some user app
is going to come along and send that INQUIRY (vpd=0x83)
to all SCSI devices and lock up the "bad" ones ;-( That
user space app needs information to discriminate.

Doug Gilbert


  reply	other threads:[~2003-05-02  0:55 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 [this message]
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

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=3EB1C577.1050204@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