Date: Sat, 20 Sep 2003 15:27:33 -0400 (EDT) From: Bryan Liesner <bleez@comcast.net> To: Lars Eggert <larse@ISI.EDU> Cc: current@freebsd.org Subject: Re: ATAng no good for me Message-ID: <20030920152154.S1008@gravy.homeunix.net> In-Reply-To: <3F6CA6B0.6090004@isi.edu> References: <Pine.GSO.4.10.10309201447120.18207-100000@pcnet5.pcnet.com> <3F6CA6B0.6090004@isi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 20 Sep 2003, Lars Eggert wrote: > Daniel Eischen wrote: > > On Sat, 20 Sep 2003, Soren Schmidt wrote: > >>It seems Daniel Eischen wrote: > >> > >>>On a kernel built just a few hours ago, it hangs on boot > >>>right after: > >>> > >>>acd0: CDROM <CD-532E-B> at ata0-master PIO4 > >> > >>Get atapicam out and see if that helps.. > > > > No, using latest sources, with or without atapicam, does > > not solve the problem. It still hangs. > > As a datapoint, I experienced the hang with atapicam, too. Removing it > helped in my case. I experienced the hang with atapicam, and removing it helps. These symptoms happened immediately after the commit of ata-queue.c v1.5. Reverting back to 1.4 removed the issue altogether. I tried to get a verbose boot message using ata-queue 1.5 and 1.6, but got way, way too many spurious interrupt messages to have anything useful to share... -Bryan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030920152154.S1008>