Date: Wed, 16 Apr 2014 13:06:26 -0400 From: John Baldwin <jhb@freebsd.org> To: Claude Buisson <clbuisson@orange.fr> Cc: FreeBSD stable <freebsd-stable@freebsd.org> Subject: Re: Unable to mount the root fs on stable/8 r264339, GENERIC kernel, with MBR, FreeBSD slice, and UFS volume labels Message-ID: <201404161306.26721.jhb@freebsd.org> In-Reply-To: <534EA7AC.8060808@orange.fr> References: <alpine.BSF.2.00.1404111820160.9102@mail.fig.ol.no> <201404161038.55512.jhb@freebsd.org> <534EA7AC.8060808@orange.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, April 16, 2014 11:54:20 am Claude Buisson wrote: > On 04/16/2014 16:38, John Baldwin wrote: > > On Wednesday, April 16, 2014 5:41:44 am Claude Buisson wrote: > >> On 04/16/2014 10:09, Trond Endrest=F8l wrote: > >>> On Tue, 15 Apr 2014 19:44+0200, Trond Endrest=F8l wrote: > >>> > >>>> On Fri, 11 Apr 2014 18:38+0200, Trond Endrest=F8l wrote: > >>>> > >>>>> Hi, > >>>>> > >>>>> I have a couple of uncritical systems running stable/8 r258344. > >>>>> Hardware is Dell OptiPlex GX260, BIOS A09, which is the latest rev. > >>>>> > >>>>> The r264339 GENERIC kernel are unable to mount the root fs from the > >>>>> hard drive using MBR, FreeBSD slice, and UFS volume labels. > >>>>> > >>>>> r258344 obviously can. > >>>>> > >>>>> I even tried regular device names like /dev/ad0s1a in /etc/fstab, a= nd > >>>>> at the mountroot> prompt, i.e. ufs:/dev/ad0s1a. The kernel still > >>>>> cannot mount the root fs. > >>>>> > >>>>> The new kernel (r264339) does recognize the ad0 harddrive, and ad0 = is > >>>>> listed as one of the GEOM managed disk devices; acd0 being the other > >>>>> one. > >>>>> > >>>>> Do I need to load additional geom modules, or is it a genuine bug? > >>>>> > >>>>> I have recreated the same conditions on a spare GX260, yes, I have > >>>>> plenty of them. > >>>> > >>>> I believe I have identified r262226 as the offending commit. > >>>> > >>>> Maybe the flags integer is set to a bad value before the calls to > >>>> resource_list_alloc(). > >>>> > >>>> My spare system is currently recompiling r262221 of both world and > >>>> kernel, and I hope to confirm this assumption in a few hours. > >>> > >>> Confirmed. > >>> > >>>> If all goes well, I intend to move forward to the latest revision of > >>>> stable/8, back out the change done to sys/dev/pci/pci.c in r262226, > >>>> recompile world and kernel, install the kernel, and if successfully, > >>>> I'll install world as well. > >>> > >>> Confirmed, stable/8 r264519 with r262226 backed out does indeed work > >>> on a Dell OptiPlex GX260, BIOS A09. > >>> > >> > >> Just another data point related to r262226: > >> > >> Yesterday, I upgraded a stable/8 system from r260539 to r264426, which= could not > >> finish booting. In my case, it stopped just after detecting an agp car= d (and > >> could boot if agp was disabled by device.hints). > >> > >> Reverting r262226 gave me back a fully usable system. > >> > >> This system is also a Dell, but a (oldish) Dimension 4550 BIOS A08. > >> > >>> Any chance anyone would like to dig deeper into the matter? > >>> Should I file a PR? > >>> > >> > >> I think so, if jhb (cced) keep being interested in stable/8.. > >> > >> BTW, this morning I succeeded in booting a stable/10 snapshot r264194 = USB stick > >> on this machine. > > > > Can you get a verbose dmesg with and without the change? > > >=20 > If r262226 is not reverted, the only way to boot and have a verbose dmesg= is to=20 > disable agp. Is it OK ? Yes. Hmmmm. I may know what the problem is then. Can you kldload agp aft= er boot? =2D-=20 John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201404161306.26721.jhb>