From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 19:00:53 2004 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 95CE316A4D2 for ; Sun, 11 Jul 2004 19:00:53 +0000 (GMT) Received: from hrothgar.unconceived.net (rrcs-se-24-73-170-14.biz.rr.com [24.73.170.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4457A43D45 for ; Sun, 11 Jul 2004 19:00:53 +0000 (GMT) (envelope-from jhandvil@tampabay.rr.com) Received: from localhost (localhost [IPv6:::1])i6BJCAkC007556; Sun, 11 Jul 2004 15:12:11 -0400 (EDT) (envelope-from jhandvil@tampabay.rr.com) From: jhandvil To: Bruce M Simpson Date: Sun, 11 Jul 2004 15:12:10 -0400 User-Agent: KMail/1.5.4 References: <200407082032.10210.jhandvil@tampabay.rr.com> <200407111043.21173.jhandvil@tampabay.rr.com> <20040711182957.GA769@empiric.dek.spc.org> In-Reply-To: <20040711182957.GA769@empiric.dek.spc.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200407111512.10333.jhandvil@tampabay.rr.com> cc: freebsd-current@freebsd.org cc: Ivan Voras Subject: Re: 5.2.1 p9 --> 5.2 current 20040708 upgrade ATA_IDENTIFY no interrupt X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jhandvil@tampabay.rr.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 19:00:53 -0000 On Sunday 11 July 2004 02:29 pm, Bruce M Simpson wrote: > On Sun, Jul 11, 2004 at 10:43:21AM -0400, jhandvil wrote: > > > > ata0-master: FAILURE - ATA_IDENTIFY no interrupt > > > > ata0-master: FAILURE - ATA_IDENTIFY no interrupt > > > > Mounting root from ufs:/dev/ad0s1a > > > > setrootbyname failed > > > > ffs_mountroot: can't find rootvp > > > > Root mount failed: 6 > > This is a very, very similar situation to what I've just observed on > several IBM ThinkPad T41 systems with the Panasonic UJDA755 CDRW module! > > Please post as much information about your hardware configuration as you > can; please also see my recent posts to -mobile for descriptions of how > to pull a backtrace in the situation where your machine faults and drops > into the debugger without the ability to 'call doadump'. > > I now strongly suspect we have a bug in ata(4). I will backtrack through > green@'s recent commits concerning atapicam as I think this may tell > part of the story (he identified some other issues and suggested fixes, > I have a hunch he is on a similar track). > > I'm in a debugging session now and will post further results of my findings > on -mobile. Excellent! I added a panic immediately after the error in ata_completed so that I can perform the backtrace. I will post the response to the group as soon as I rebuild the kernel and reboot. Thanks, Justin