From: Olaf Hering <olh@suse.de>
To: Dan Hollis <goemon@anime.net>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
bcollins@debian.org, linux1394-devel@lists.sourceforge.net
Subject: Re: 100% repeatable way to send firewire out to lunch permanently on 2.6.8.1
Date: Sun, 31 Jul 2005 21:16:58 +0200 [thread overview]
Message-ID: <20050731191658.GC19681@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0507310739320.13193-100000@sasami.anime.net>
On Sun, Jul 31, Dan Hollis wrote:
> On Sun, 24 Oct 2004, Olaf Hering wrote:
> > On Sun, Oct 24, 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.
> > How should sbp2_remove_device get rid of the device? It calls
> > scsi_remove_host, which calls scsi_remove_device, which sets the mode to
> > SDEV_CANCEL, then calls to device_del. sr_do_ioctl expects SDEV_OFFLINE.
>
> Has there been any progress on this issue? I just got my _entire scsi
> subsystem_ sent out to lunch because a firewire device lost power.
I cant help you with that, sr_mod is likely still broken with MRW
capable drives. But sbp2 is still the culprit, incomplete error
handling.
next prev parent reply other threads:[~2005-07-31 19:17 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
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 [this message]
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=20050731191658.GC19681@suse.de \
--to=olh@suse.de \
--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 \
/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).