Re: 100% repeatable way to send firewire out to lunch permanently on 2.6.8.1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 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.
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux