linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-scsi@vger.kernel.org
Cc: linux1394-devel@lists.sourceforge.net
Subject: Re: 100% repeatable way to send firewire out to lunch permanently on 2.6.8.1
Date: Sun, 24 Oct 2004 20:12:56 +0200	[thread overview]
Message-ID: <a08d7dec1a72c641aa8fc62d940ebbda@localhost> (raw)
In-Reply-To: <200410241930.47104.chrivers@iversen-net.dk>

Christian Iversen wrote to linux1394-devel:
> On Sunday 24 October 2004 19:22, Dmitry Torokhov wrote:
>> On Sunday 24 October 2004 10:22 am, James Bottomley wrote:
>>> The trace doesn't show any error handler activity at all.  Are there no
>>> messages in the log about offlining the device?  If not, it sounds like
>>> there's a problem somewhere in the firewire system.
>> 
>> The thing is that the hang is happening only with CD/DVD devices (sr_mod)
>> and not with hard drives (sd_mod) and as far as I can tell SBP2 does not
>> differentiate betweeh an HD and a CD so I think there is something going
>> on in sr_mod code.
> 
> I can't see the start of the thread, but I have a very similar problem with 
> external CD-ROMs in usb-2.0 cases. Whenever I unplug them, they kill the 
> entire system (usb subsystem at first, then the whole kernel locks up).
...
> This is tested on 3 different controllers, 2 different motherboards and 3
> different kernels. 2.6.7-2.6.9 all have this problem. 2.6.5-rc3 works like
> a charm, and I haven't tested 2.6.6.

I have 2 different SBP-2 CD-RW drives, 3 different SBP-2 harddrives, and
use an USB memory stick occasionally. After the last kernel update (from
2.6.6-rc3 to 2.6.8.1) I noticed problems with device removals concerning
/dev/scd? for the first time. I did not use the drives very extensively
under the former kernel so I am not sure whether that worked fine. One
thing is however certain: There is no hassle with sd devices.

There were some more reports about the CD/DVD removal problems with
recent 2.6 kernels on linux1394-user/-devel, but nothing similar about
harddisks.
-- 
Stefan Richter
-=====-=-=-- =-=- ==---
http://arcgraph.de/sr/


       reply	other threads:[~2004-10-24 18:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200410241930.47104.chrivers@iversen-net.dk>
2004-10-24 18:12 ` Stefan Richter [this message]
     [not found] <Pine.LNX.4.44.0409050434540.8779-100000@sasami.anime.net>
2004-10-24 14:42 ` 100% repeatable way to send firewire out to lunch permanently on 2.6.8.1 Olaf Hering
2004-10-24 14:53   ` James Bottomley
2004-10-24 15:00     ` Olaf Hering
2004-10-24 15:22       ` James Bottomley
2004-10-24 17:22         ` Dmitry Torokhov
2004-10-24 18:02         ` Olaf Hering
2004-10-24 19:29         ` Olaf Hering
2005-07-31 14:43           ` Dan Hollis
2005-07-31 17:31             ` Stefan Richter
2005-07-31 17:54               ` Stefan Richter
2005-07-31 17:59                 ` Christoph Hellwig
2005-07-31 18:08                   ` Stefan Richter
2005-07-31 19:16             ` Olaf Hering
2005-07-31 23:14               ` Stefan Richter
2004-10-31 21:05   ` Herbert Schmid

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=a08d7dec1a72c641aa8fc62d940ebbda@localhost \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).