Date: Thu, 5 Apr 2012 10:40:32 +0200 From: David Naylor <naylor.b.david@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: Alexander Motin <mav@freebsd.org>, FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: [regression] unable to boot: no GEOM devices found. Message-ID: <201204051040.35808.naylor.b.david@gmail.com> In-Reply-To: <201203281437.35746.jhb@freebsd.org> References: <mailpost.1302585106.8448174.20731.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw> <201105092024.41588.naylor.b.david@gmail.com> <201203281437.35746.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart13473285.JGPzsrg3Au Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Wednesday, 28 March 2012 20:37:35 John Baldwin wrote: > On Monday, May 09, 2011 2:24:37 pm David Naylor wrote: > > On Friday 15 April 2011 23:29:55 David Naylor wrote: > > > On Friday 15 April 2011 18:28:06 John Baldwin wrote: > > > > On Wednesday, April 13, 2011 1:07:06 pm David Naylor wrote: > > > > > On Tuesday 12 April 2011 22:12:55 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. > > > > > > >>>=20 > > > > > > >>> The boot process stops when it looks to find a bootable > > > > > > >>> device. The prompt (when pressing '?') does not display any > > > > > > >>> device and yielding > > > >=20 > > > > one > > > >=20 > > > > > > >>> 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 > > > > > > +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 > > > > > > 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. > > > > > >=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) and it is interrupt related. > > > > >=20 > > > > > I reverted those two revs and everything works again. > > > >=20 > > > > Hmm, can you provide a full boot verbose dmesg? Alternatively, can > > > > you see if the device at pci0:0:9:0 is a PCI-PCI bridge? > > >=20 > > > I can provide a verbose dmesg if the following is not enough: > > >=20 > > > none17@pci0:0:9:0: class=3D0x050000 card=3D0x50011458 chip=3D0x0= 27010de > > > rev=3D0xa2 hdr=3D0x00 > > >=20 > > > vendor =3D 'NVIDIA Corporation' > > > device =3D 'MCP51 Host Bridge' > > > class =3D memory > > > subclass =3D RAM > > >=20 > > > I see two PCI-PCI bridges at pci0:0:3:0 and pci0:0:16:0. I've attach= ed > > > the full `pciconf -lv` output. > >=20 > > FYI, this issue is still present on current (~24 hours old). Reverting > > the above mentioned revisions still fixes the problem. >=20 > I finally had an idea about a way to solve this (at least when using ACPI) > that doesn't involve a whole bunch of quirks, etc. Please try > http://www.FreeBSD.org/~jhb/patches/hostb_htmsi.patch I am no longer able to test on that machine. Booting of a USB stick doesn'= t=20 work, the kernel says: WARNING WITNESS ENABLED then the computer restarts. = =20 This is with -current after you committed the patch and with stable-9. =20 I have verified that the USB stick does boot off other computers. =20 --nextPart13473285.JGPzsrg3Au Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEABECAAYFAk99WoMACgkQUaaFgP9pFrLYCwCfRrWwNiyicx5z9R69oiQqa2PW qBIAn3a1zCxjCut8YAF+gMlB5ANzIXNS =ETbg -----END PGP SIGNATURE----- --nextPart13473285.JGPzsrg3Au--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201204051040.35808.naylor.b.david>