Date: Sat, 2 Oct 2010 00:18:38 -0500 From: Brandon Gooch <jamesbrandongooch@gmail.com> To: David Wolfskill <david@catwhisker.org>, Brandon Gooch <jamesbrandongooch@gmail.com>, current@freebsd.org Subject: Re: Hang near end of kernel probes since r213267 (likely earlier) Message-ID: <AANLkTimh%2BmgHF=txOYKv6bSfg0w4tun01iz7A71Ly5so@mail.gmail.com> In-Reply-To: <20101002033859.GK1535@albert.catwhisker.org> References: <20101001212038.GE1535@albert.catwhisker.org> <20101001233001.GG1535@albert.catwhisker.org> <20101002013344.GI1535@albert.catwhisker.org> <AANLkTiny8TxsT0jObNqF7Jnkp-wrPBSecp_Y3%2BnKazNg@mail.gmail.com> <20101002033859.GK1535@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 1, 2010 at 10:38 PM, David Wolfskill <david@catwhisker.org> wro= te: > On Fri, Oct 01, 2010 at 08:56:13PM -0500, Brandon Gooch wrote: >> ... >> > Any ideas on what mught be causing CURRENT to hang -- sometimes >> > -- given that it appears to involve the Modular Bay (or the specific >> > device that is in the bay during the hang)? >> > >> >> If you haven't already, it may be worth trying 'options ATA_CAM' in >> your kernel config. > > Well, I hadn't, so I tried it. =A0And since I had read the note: > > # ATA_CAM: =A0 =A0 =A0 =A0 =A0 =A0 =A0Turn ata(4) subsystem controller dr= ivers into cam(4) > # =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 interface modules. This dep= recates all ata(4) > # =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 peripheral device drivers (= atadisk, ataraid, atapicd, > # =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 atapifd, atapist, atapicam)= and all user-level APIs. > # =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 cam(4) drivers and APIs wil= l be connected instead. > > I had an idea that /etc/fstab would need a global edit (though I > didn't know what device would be used). > > Attempting a single-user mode boot clarified that for me: > > =A0 =A0 =A0 =A0:s/ad4/ada0/ > > Fortunately, I'm in the habit of keeping more than one bootable slice > around, so I was able to accomplish that. > > And -- probably more important for this discussion -- I was unable to > re-create the failing condition: the machine booted Just Fine every > time I tried it, whether the CD/DVD drive was inserted or not. > > Now, this seems a bit more like a circumvention or diagnostic aid > (to me) than an actual solution -- or am I misunderstanding? > > Thanks for the suggestion, though! > The ATA_CAM option allows the use of the new CAM ATA infrastructure, replacing the legacy operation of the ATA devices. The following may be enlightening: http://lists.freebsd.org/pipermail/freebsd-current/2009-December/013956.htm= l I've been using it now on all of my newer machines; it's well worth the slight changes to your setups considering what you stand to gain. I definitely would not consider it a work-around, unless you absolutely require legacy operation of some device. -Brandon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimh%2BmgHF=txOYKv6bSfg0w4tun01iz7A71Ly5so>