From owner-freebsd-current@FreeBSD.ORG Sat Sep 20 12:27:36 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C65D616A4B3; Sat, 20 Sep 2003 12:27:36 -0700 (PDT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB98043FD7; Sat, 20 Sep 2003 12:27:35 -0700 (PDT) (envelope-from bleez@comcast.net) Received: from gravy.homeunix.net ([68.81.196.221]) by comcast.net (rwcrmhc12) with ESMTP id <2003092019273501400bjv6me>; Sat, 20 Sep 2003 19:27:35 +0000 Received: from gravy.homeunix.net (gravy.homeunix.net [192.168.1.2]) by gravy.homeunix.net (8.12.9/8.12.9) with ESMTP id h8KJRXTl001027; Sat, 20 Sep 2003 15:27:34 -0400 (EDT) (envelope-from bleez@comcast.net) Date: Sat, 20 Sep 2003 15:27:33 -0400 (EDT) From: Bryan Liesner To: Lars Eggert In-Reply-To: <3F6CA6B0.6090004@isi.edu> Message-ID: <20030920152154.S1008@gravy.homeunix.net> References: <3F6CA6B0.6090004@isi.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: deischen@freebsd.org cc: Soren Schmidt cc: current@freebsd.org Subject: Re: ATAng no good for me X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Sep 2003 19:27:36 -0000 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 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