From owner-freebsd-current@FreeBSD.ORG Tue Apr 12 21:34:09 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF07E106564A for ; Tue, 12 Apr 2011 21:34:08 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9A0258FC0A for ; Tue, 12 Apr 2011 21:34:08 +0000 (UTC) Received: by iyj12 with SMTP id 12so8655346iyj.13 for ; Tue, 12 Apr 2011 14:34:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:date:to:cc:subject:message-id:reply-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=j/gog2zCbGBBbbOArEcWHtBDi9h+3/XDLbKkbZWT3xE=; b=qxyfQK1upa18mZtqmq0H5Z2roRQ8OrzlnQl/6zmIyu+Rk9d2mXVe9BGjXqpw7FWgVi bWLM/M+RIanZR0ShWZtlgQv/KJ5EM3NSDr5iaDUtl8D4pbD+nKDJLUeSvgBKI/nOSUeF rHhNUV0XxLloiUCZmE0vE+9QRDmkT3HuvlBDU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=OnbT22NHiHtZB4oXksVDwe3YrIGF8MtFswgvmqxRdOp2QLlLEfVBqywgsEeY5zvReQ yaMQsEkIoESM05il5Tu3reD/HblN6G/UJqPJBT88FW0XhRvbLEWIVEAFNfY43hwG21zx DqAL6gFh317R3WGDVxbJY3lLPgrb02p/Ou+sQ= Received: by 10.42.96.135 with SMTP id j7mr11272842icn.245.1302642255154; Tue, 12 Apr 2011 14:04:15 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id i26sm4068567iby.7.2011.04.12.14.04.05 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2011 14:04:07 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 12 Apr 2011 14:03:54 -0700 From: YongHyeon PYUN Date: Tue, 12 Apr 2011 14:03:54 -0700 To: Alexander Motin Message-ID: <20110412210354.GC1421@michelle.cdnetworks.com> References: <4DA3EE8F.8050306@FreeBSD.org> <201104122132.23809.naylor.b.david@gmail.com> <4DA4B247.6010901@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DA4B247.6010901@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD-Current , David Naylor Subject: Re: [regression] unable to boot: no GEOM devices found. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2011 21:34:09 -0000 On Tue, Apr 12, 2011 at 11:12:55PM +0300, Alexander Motin wrote: > David Naylor wrote: > > On Tuesday 12 April 2011 08:17:51 Alexander Motin wrote: > >> David Naylor wrote: > >>> I am running -current and since a few days ago (at least 2011/04/11) I am > >>> unable to boot. > >>> > >>> The boot process stops when it looks to find a bootable device. The > >>> prompt (when pressing '?') does not display any device and yielding one > >>> second (or more) to the kernel (by pressing '.') does not improve the > >>> situation. > >>> > >>> A known working date is 2011/02/20. > >>> > >>> I am running amd64 on a nVidia MCP51 chipset. > >> MCP51... again... > >> > >>> I am willing to help any way I can. > >> You could start from capturing and showing verbose dmesg. Full or at > >> least in parts related to disks. > > > > I captured the dmesg output for both the old (working) kernel and the new > > (bad) kernel. See attached for the difference between the two. If you need > > the full dmesg please let me know. > > > > One thing I found is that the old kernel would not boot if I simply rebooted > > from the bad kernel. I had to do a hard power off before the old kernel would > > work again. Is some device state surviving between reboots? > > +ata2: reiniting channel .. > +ata2: SATA connect time=0ms status=00000113 > +ata2: reset tp1 mask=01 ostat0=58 ostat1=00 > +ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 > +ata2: reset tp2 stat0=50 stat1=00 devices=0x1 > +ata2: reinit done .. > +unknown: FAILURE - ATA_IDENTIFY timed out LBA=0 > > As soon as all devices detected but not responding to commands, I would > suppose that there is something wrong with ATA interrupts. There is a > long chain of interrupt problems in this chipset. I have already tried > to debug one case where ATA wasn't generating interrupts at all. > Unfortunately, without success -- requests were executing, but not > generating interrupts, it wasn't looked like ATA driver problem. > > What's about possible candidate to revision triggering your problem, I > would look on this message: > +pcib0: Enabling MSI window for HyperTransport slave at pci0:0:9:0 > > At least it is recent (SVN revs 219737,219740 on 2011-03-18 by jhb) and > it is interrupt related. > Does the driver disable MSI for MCP51? I think jhb's patch fixed one MSI issue of all MCP chipset.