Re: Firewire disk/tape access stopped working after recent CAM commit

2012-01-24 Thread Kenneth D. Merry
On Tue, Jan 24, 2012 at 00:03:56 -0600, Richard Todd wrote: On Mon, Jan 23, 2012 at 11:16:05AM -0700, Kenneth D. Merry wrote: If you can, please try the attached patch and see if it has any impact on the problem. There is a bug in that commit in that we shouldn't be invalidating all LUNs

Re: Firewire disk/tape access stopped working after recent CAM commit

2012-01-23 Thread Kenneth D. Merry
On Sun, Jan 22, 2012 at 20:52:38 -0600, Richard Todd wrote: Hi. I tried upgrading my amd64 10-CURRENT box to the most recent -CURRENT code and found that the new kernel couldn't find my two disks and tape drive that are on a Firewire bus. All the USB and AHCI-attached hardware still showed

Re: Firewire disk/tape access stopped working after recent CAM commit

2012-01-23 Thread Richard Todd
On Mon, Jan 23, 2012 at 11:16:05AM -0700, Kenneth D. Merry wrote: If you can, please try the attached patch and see if it has any impact on the problem. There is a bug in that commit in that we shouldn't be invalidating all LUNs on a target when we get a status of CAM_DEV_NOT_THERE. Just

Firewire disk/tape access stopped working after recent CAM commit

2012-01-22 Thread Richard Todd
Hi. I tried upgrading my amd64 10-CURRENT box to the most recent -CURRENT code and found that the new kernel couldn't find my two disks and tape drive that are on a Firewire bus. All the USB and AHCI-attached hardware still showed up okay, it's just the Firewire stuff that failed to show up