From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux1394-devel@lists.sourceforge.net
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Olaf Hering <olh@suse.de>, Dan Hollis <goemon@anime.net>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
bcollins@debian.org
Subject: Re: 100% repeatable way to send firewire out to lunch permanently on 2.6.8.1
Date: Sun, 24 Oct 2004 12:22:50 -0500 [thread overview]
Message-ID: <200410241222.50426.dtor_core@ameritech.net> (raw)
In-Reply-To: <1098631356.10824.33.camel@mulgrave>
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.
--
Dmitry
next prev parent reply other threads:[~2004-10-24 17:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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 22:57 ` [PATCH] ieee1394/sbp2: fix for hot-unplug Stefan Richter
2005-07-31 23:14 ` 100% repeatable way to send firewire out to lunch permanently on 2.6.8.1 Stefan Richter
2004-10-31 21:05 ` Herbert Schmid
[not found] <200410241930.47104.chrivers@iversen-net.dk>
2004-10-24 18:12 ` Stefan Richter
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=200410241222.50426.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=James.Bottomley@SteelEye.com \
--cc=bcollins@debian.org \
--cc=goemon@anime.net \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=olh@suse.de \
/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).