Date: Tue, 24 Jan 2012 10:40:39 -0700 From: "Kenneth D. Merry" <ken@freebsd.org> To: Richard Todd <rmtodd@servalan.servalan.com> Cc: freebsd-current@freebsd.org Subject: Re: Firewire disk/tape access stopped working after recent CAM commit Message-ID: <20120124174039.GA87021@nargothrond.kdm.org> In-Reply-To: <20120124060356.GA4989@ichotolot.servalan.com> References: <20120123025238.GA17816@ichotolot.servalan.com> <20120123181605.GA52248@nargothrond.kdm.org> <20120124060356.GA4989@ichotolot.servalan.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 on a target when we get a status of > > CAM_DEV_NOT_THERE. > > Just applied the patch, built new kernel, and rebooted, and all the FW > drivees are showing up now. Thanks! Great! > > It may be that we need to do a more thorough audit of how various SIM > > drivers are using the CAM_DEV_NOT_THERE status. > > So I take it the layers for the different hardware (SCSI, FW, USB, > ATA/AHCI) are handling this status differently, so that's why this bug only > showed up on the Firewire buses but not on ATA/AHCI, USB, or (on my other > machine) SCSI buses? Yes. Some drivers report a selection timeout, some report that the device isn't there, and they may be using those status values in different situations. Ken -- Kenneth Merry ken@FreeBSD.ORG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120124174039.GA87021>