Date: Fri, 15 Apr 2011 12:28:06 -0400 From: John Baldwin <jhb@freebsd.org> To: David Naylor <naylor.b.david@gmail.com> Cc: Alexander Motin <mav@freebsd.org>, FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: [regression] unable to boot: no GEOM devices found. Message-ID: <201104151228.06105.jhb@freebsd.org> In-Reply-To: <201104131907.12368.naylor.b.david@gmail.com> References: <mailpost.1302585106.8448174.20731.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw> <4DA4B247.6010901@FreeBSD.org> <201104131907.12368.naylor.b.david@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > > >>> > > >>> 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... > > > > +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. > > I reverted those two revs and everything works again. 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? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201104151228.06105.jhb>