From owner-freebsd-current@FreeBSD.ORG Tue Apr 12 21:09:14 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 31AE9106568E for ; Tue, 12 Apr 2011 21:09:14 +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 AF2388FC1D for ; Tue, 12 Apr 2011 21:09:13 +0000 (UTC) Received: by fxm11 with SMTP id 11so60854fxm.13 for ; Tue, 12 Apr 2011 14:09:12 -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=oSK5SGThSGLAWvkh3XxqqJCcPj4Tr0z+FFa4xhFwlcU=; b=lnkOL32DklqP+SI4bLMzJG1nRim6x2mLsYquLS2SNrPWi5EwN5HYI8pzguhPFqAP0n CY+oDjiPTWULVFBw7q6/Q/DWefkRF7/d/gqhQPNb3c4w+JUdK67CDiS0tkkwcMoAxJdm RD8E4685lQINc6CMXVXHy3A6tXYm11p02/hPM= 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=oGZc0T/jdYznTQ5AxlD50I6E8c9Ye8YzUA+FkuJRdhPNSmwiAh9rGl+r/6PSGAcxEL H+QDJ9t8Rc/wSnpyxIWDT65YZFZT0VIPRV+zA5MxBmrI8Ot0vQMXTWDPFoEV/ww34Bjy CKop4e3DD/DA9qAFGYsSnUY2/SSvsakG4tP3w= Received: by 10.223.83.130 with SMTP id f2mr1772503fal.80.1302642552777; Tue, 12 Apr 2011 14:09:12 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id k5sm2116714faa.39.2011.04.12.14.09.11 (version=SSLv3 cipher=OTHER); Tue, 12 Apr 2011 14:09:12 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DA4BF6A.7010806@FreeBSD.org> Date: Wed, 13 Apr 2011 00:08:58 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: pyunyh@gmail.com References: <4DA3EE8F.8050306@FreeBSD.org> <201104122132.23809.naylor.b.david@gmail.com> <4DA4B247.6010901@FreeBSD.org> <20110412210354.GC1421@michelle.cdnetworks.com> In-Reply-To: <20110412210354.GC1421@michelle.cdnetworks.com> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 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:09:14 -0000 YongHyeon PYUN wrote: > 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? ata(4) doesn't uses MSI by default and I doubt this controller supports them any way. But if I am not mixing something, there were very strange situations with MSI on that chipset, when enabling them one one device caused interrupt problems on another. > I think jhb's patch fixed one MSI issue of all MCP chipset. I am not telling it is wrong. It could just trigger something. -- Alexander Motin