Messages in this thread | | | Date | Wed, 31 Mar 2010 15:02:57 -0700 | From | Yinghai Lu <> | Subject | Re: Config NO_BOOTMEM breaks my amd64 box |
| |
On 03/31/2010 02:14 PM, Dave Airlie wrote: > On Thu, Apr 1, 2010 at 4:59 AM, Ingo Molnar <mingo@elte.hu> wrote: >> >> * James Morris <jmorris@namei.org> wrote: >> >>> On Tue, 30 Mar 2010, H. Peter Anvin wrote: >>> >>>> On 03/30/2010 09:49 PM, James Morris wrote: >>>>> >>>>> Please make NO_BOOTMEM default to n, at least for amd64, where I've found >>>>> that it leads to all kinds of strange, undebuggable boot hangs and errors >>>>> (with relatively current Fedora development userland). >>>> >>>> Have you tested it with the latest fixes that are now in Linus' tree (-rc3)? >>> >>> Yes, it was happening with -rc3. >> >> Could you please send the bootlog that Yinghai asked for, plus also one that >> you get with NO_BOOTMEM turned off (for comparison)? >> >> Also, when did you first hit this bug? This code has been upstream for almost >> a month, and it was in linux-next before that - so you should have hit this >> much sooner. A rough timeframe would suffice. I suppose you were booting >> upstream kernels during the merge window as well? >> >> We can flip the default around if there's no fix available based on the >> bootlogs. (Plus the help text should definitely be improved.) >> > > Are you testing this btw with initramfs/initrds? I suspect lots of testing > is being done by people on monolithic kernels, this is just a misc guess, > considering I couldn't boot from when this landed until rc3 with this option > on a basic 32-bit install on a dual-core 64-bit CPU, it suggested a > hole of some sort > in the test coverage.
so -rc3 is working your setup?
Yinghai
| |