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, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] instrument ide-scsi in 2.5.68
Date: Fri, 02 May 2003 09:29:55 +1000	[thread overview]
Message-ID: <3EB1ADF3.5080008@torque.net> (raw)
In-Reply-To: <20030501155225.7df14e51.rddunlap@osdl.org>

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

The code uses Rusty's moduleparam.h and it worked
for me with scsi_debug. [It is some time since I checked
scsi_debug built-in.] Could you try "idescsi.debug=3"
(i.e. drop the hyphen). Failing that perhaps you could
build ide-scsi as a module.

> Anyway, it never gets thru the boot sequence (with or without this
> patch).  It hangs with these last messages:
> 
> scsi2 : SCSI host adapter emulation for IDE ATAPI devices
> ide-scsi: abort called for cmd serial #32
> hdd: lost interrupt
> ide-scsi: CoD != 0 in idescsi_pc_intr
> hdd: DMA disabled
> hdd: ATAPI reset complete
> hdd: irq timeout: status=0x80 { Busy }
> hdd: ATAPI reset complete
> hdd: irq timeout: status=0x80 { Busy }
> hdd: ATAPI reset complete
> hdd: irq timeout: status=0x80 { Busy }

It would be interesting to see what effect "suppress_reset=1"
has on this failure.

Doug Gilbert


  parent reply	other threads:[~2003-05-01 23:15 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 [this message]
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

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=3EB1ADF3.5080008@torque.net \
    --to=dougg@torque.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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