From owner-freebsd-current@FreeBSD.ORG Tue Apr 12 20:13:12 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 E03AD106566C; Tue, 12 Apr 2011 20:13:11 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 477658FC08; Tue, 12 Apr 2011 20:13:10 +0000 (UTC) Received: by fxm11 with SMTP id 11so16831fxm.13 for ; Tue, 12 Apr 2011 13:13:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=KaKSfzWM0TctN0LmMQXqabTUHgBNTuzEEAdP1gz9OKE=; b=Txvsi+CVUhD2rnxTHXD4bSQG5L6zG6zTORre7KO0gwoyrv1sRKWr9zlZwMG5Ohw/4M Faa+obCZtc14nCtifaAc+4BOTnOtpaygrdOE7fO/h0nBxQGq4XtetLhP9KrkyuSJ7GqA fs+eTJ9Mg0PTsPj3FzmEBfIQY4fTLL22k2B6I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=n74J4BLgE3vO2ZfT7vurvQiZGnLTPfPOXKCuGRTOIWV0gdVrAlLg9/wX09MxIKjyfM rM8KAgRxX4GoubkW+NIzUInrlb2/3LBY3erc7yEeFr97LOaT9bWaStnXgLBwjzHUnaWi xhlOiBJt18h247qIOR8dq5ECBx5cpQLQIuJj0= Received: by 10.223.159.14 with SMTP id h14mr816577fax.20.1302639190103; Tue, 12 Apr 2011 13:13:10 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id k5sm2105603faa.39.2011.04.12.13.13.08 (version=SSLv3 cipher=OTHER); Tue, 12 Apr 2011 13:13:09 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DA4B247.6010901@FreeBSD.org> Date: Tue, 12 Apr 2011 23:12:55 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: David Naylor References: <4DA3EE8F.8050306@FreeBSD.org> <201104122132.23809.naylor.b.david@gmail.com> In-Reply-To: <201104122132.23809.naylor.b.david@gmail.com> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current Subject: Re: [regression] unable to boot: no GEOM devices found. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 12 Apr 2011 20:13:12 -0000 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. -- Alexander Motin