Prev: ppp: use big tty mutex
Next: linux-next: manual merge of the driver-core tree with the sh tree
From: James Morris on 31 Mar 2010 01:00
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).

Also, the help text for the item makes little sense to a non-expert in
this area:


" ---help---
Use early_res directly instead of bootmem before slab is ready.
- allocator (buddy) [generic]
- early allocator (bootmem) [generic]
- very early allocator (reserve_early*()) [x86]
- very very early allocator (early brk model) [x86]
So reduce one layer between early allocator to final allocator."

I had no idea what all this meant, so trusted the default=y and then spent
several hours wondering why everything was breaking, and would likley not
have figured it out in linear time without a suggestion from Dave Airlie.


- James
--
James Morris
<jmorris(a)namei.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: H. Peter Anvin on 31 Mar 2010 02:40
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)?

-hpa

--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: James Morris on 31 Mar 2010 02:50
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.

--
James Morris
<jmorris(a)namei.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Stefan Richter on 31 Mar 2010 07:00
James Morris wrote:
> Also, the help text for the item makes little sense to a non-expert in
> this area:

I too noticed this absolutely catastrophic "help" text but forgot to
send a bug report.

Either this option can be explained and the text fixed, or it cannot be
explained and shouldn't be an option in the first place.
--
Stefan Richter
-=====-==-=- --== =====
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Yinghai Lu on 31 Mar 2010 12:30
On 03/30/2010 11:47 PM, James Morris 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.

please send out bootlog if possible.

BTW please try
git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-2.6-yinghai.git

Thanks

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 |  Next  |  Last
Pages: 1 2 3 4 5 6 7
Prev: ppp: use big tty mutex
Next: linux-next: manual merge of the driver-core tree with the sh tree