From: Douglas Gilbert <dougg@torque.net>
To: linux-kernel@vger.kernel.org
Cc: xhejtman@mail.muni.cz
Subject: Re: 2.5.54: ide-scsi still buggy?
Date: Thu, 09 Jan 2003 09:26:28 +1100 [thread overview]
Message-ID: <3E1CA594.60407@torque.net> (raw)
Lukas Hejtmanek wrote:
> On Tue, Jan 07, 2003 at 09:17:46PM -0500, Zwane Mwaikambo wrote:
> > > It freezes kernel (sysrq do nothing) after lines:
> > > scsi0 : SCSI host adapter emulation for IDE ATAPI devices
> > > Vendor: TEAC Model: CD-W512EB Rev: 2
> > > Type: CD-ROM ANSI SCSI revision: 02
> > > scsi scan: host 0 channel 0 id 0 lun 0 identifier too long,
> > > length 60, max 50. \
> > > Device might be improperly identified.
> > > while attaching it to /dev/hde works ok. Why?
> >
> > This has been observed to cause an oops on some boxes and nothing
> > on mine,
> > try this patch from Andries
>
> Acctualy this patch caused only I do not see "scsi scan:
> host 0 channel 0 id
> 0 lun 0 identifier too long, length 60, max 50. Device might
> be improperly identified."
>
> how ever after above message kernel causes hard hw lockup.
> IDE activity LED is turned on but nothing else works. (nor
> sysrq)
>
> I believe that code that report this message causes hw lockup.
> sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
There are several different patches to ide-scsi in Linus's
snapshots that will most likely appear in lk 2.5.55 .
See:
http://www.kernel.org/pub/linux/kernel/v2.5/snapshots/
with patch-2.5.54-bk6 being the most recent. See the associated
log for a listing of the ide-scsi changes.
It would be interesting to hear if that snapshot fixes your
ide-scsi problem.
Doug Gilbert
next reply other threads:[~2003-01-08 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 22:26 Douglas Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-08 1:40 2.5.54: ide-scsi still buggy? Lukas Hejtmanek
2003-01-08 2:17 ` Zwane Mwaikambo
2003-01-08 20:25 ` Lukas Hejtmanek
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=3E1CA594.60407@torque.net \
--to=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=xhejtman@mail.muni.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.