From owner-freebsd-current@FreeBSD.ORG Wed Apr 13 04:52:06 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 D7E15106564A; Wed, 13 Apr 2011 04:52:06 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 2EB348FC08; Wed, 13 Apr 2011 04:52:06 +0000 (UTC) Received: by wwc33 with SMTP id 33so236226wwc.31 for ; Tue, 12 Apr 2011 21:52:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:subject:date:user-agent:cc:references :in-reply-to:mime-version:content-type:content-transfer-encoding :message-id; bh=WD+GuTscdb+OrtcrKt47M3o5Qh+45fZEQTWk8CHbrxo=; b=cwHVZcDbrLYjt3LDyC/zYoQ/vqccBWssSXoa3f5S9jUHY8LjA0g2IwFvKVpjYNBWLn A/WgrAqmYaFb2JH8wh7pA96GuSYyqkZxrIUr0crkDd91TLzM2C0R8FBRB4Pikr9k1Luf HJMX4IanZr9YUfq+OcZ0qTdR3BBcJAERj4mVc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=G2reJT1pcbS3VJKw0G1onAgeTi2kMyLesl2PB7rgvFO4cNGcYDSb80ZP2qW5azNQp9 Il6xwA2VnlVa62j8e3XdXGzvPpDkbceLhEJKzRNTOHvUoaMwfG+dhzLBao/h/H1iMRda RnuyRrGO78QC2wyEOGsuTOMZxFOhu64FQgG7M= Received: by 10.227.168.138 with SMTP id u10mr1973380wby.186.1302670325234; Tue, 12 Apr 2011 21:52:05 -0700 (PDT) Received: from dragon.dg (41-135-148-75.dsl.mweb.co.za [41.135.148.75]) by mx.google.com with ESMTPS id b20sm84549wbb.33.2011.04.12.21.52.01 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2011 21:52:04 -0700 (PDT) From: David Naylor To: Garrett Cooper Date: Wed, 13 Apr 2011 06:51:41 +0200 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.6.1; amd64; ; ) References: <4DA4BF6A.7010806@FreeBSD.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1709355.o4kG2Z27Zl"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201104130651.45408.naylor.b.david@gmail.com> Cc: pyunyh@gmail.com, Alexander Motin , 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: Wed, 13 Apr 2011 04:52:06 -0000 --nextPart1709355.o4kG2Z27Zl Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Tuesday 12 April 2011 23:39:30 Garrett Cooper wrote: > On Tue, Apr 12, 2011 at 2:08 PM, Alexander Motin wrote: > > 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/1= 1) > >>>>>> I am unable to boot. > >>>>>>=20 > >>>>>> The boot process stops when it looks to find a bootable device. T= he > >>>>>> prompt (when pressing '?') does not display any device and yielding > >>>>>> one second (or more) to the kernel (by pressing '.') does not > >>>>>> improve the situation. > >>>>>>=20 > >>>>>> A known working date is 2011/02/20. > >>>>>>=20 > >>>>>> I am running amd64 on a nVidia MCP51 chipset. > >>>>>=20 > >>>>> MCP51... again... > >>>>>=20 > >>>>>> I am willing to help any way I can. > >>>>>=20 > >>>>> You could start from capturing and showing verbose dmesg. Full or at > >>>>> least in parts related to disks. > >>>>=20 > >>>> 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. > >>>>=20 > >>>> 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? > >>>=20 > >>> +ata2: reiniting channel .. > >>> +ata2: SATA connect time=3D0ms status=3D00000113 > >>> +ata2: reset tp1 mask=3D01 ostat0=3D58 ostat1=3D00 > >>> +ata2: stat0=3D0x50 err=3D0x01 lsb=3D0x00 msb=3D0x00 > >>> +ata2: reset tp2 stat0=3D50 stat1=3D00 devices=3D0x1 > >>> +ata2: reinit done .. > >>> +unknown: FAILURE - ATA_IDENTIFY timed out LBA=3D0 > >>>=20 > >>> As soon as all devices detected but not responding to commands, I wou= ld > >>> 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. > >>>=20 > >>> 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 > >>>=20 > >>> At least it is recent (SVN revs 219737,219740 on 2011-03-18 by jhb) a= nd > >>> it is interrupt related. > >>=20 > >> Does the driver disable MSI for MCP51? > >=20 > > 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. > >=20 > >> I think jhb's patch fixed one MSI issue of all MCP chipset. > >=20 > > I am not telling it is wrong. It could just trigger something. >=20 > Could the OP try disabling MSI[X] to see whether or not the issue > still occurs then? > -Garrett I added: hw.pci.enable_msi=3D0 hw.pci.enable_msix=3D0 to loader.conf but the problem persisted. =20 @mav: I will revert r219737 and r219740 and try again but this will be in += 10=20 hours... =20 Thanks --nextPart1709355.o4kG2Z27Zl Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iEYEABECAAYFAk2lK+EACgkQUaaFgP9pFrKtkwCcDMr2BtREyyB5Q4EF4F4s6M8P eQ8AnRf8/qPwSmW7kGWm2ve6otlr9+1Q =m91d -----END PGP SIGNATURE----- --nextPart1709355.o4kG2Z27Zl--