Andrew Morton <[email protected]> writes:
> On Fri, 28 Jul 2006 20:16:32 -0500
> Paul Fulghum <[email protected]> wrote:
>
>> On Fri, 2006-07-28 at 19:15 -0500, Paul Fulghum wrote:
>> > I'm doing a build on my home machine now to see if it
>> > happens there also.
>>
>> Well, the timer int 0 problem does not happen on my home machine.
>> However, it still crashes in early boot for a different reason.
>>
>> 2.6.18-rc2 works fine with same config.
>>
>> In this case the error is:
>>
>> No per-cpu room for modules
>
> yeah, sorry, that's a known problem which nobody appears to be doing
> anything about. The expansion of NR_IRQS gobbles all the percpu memory in
> the kstat structure.
Sorry I didn't realize it was so easy to trip over.
It's on my todo list for sometime in the next couple of days.
> I assume you have a large NR_CPUS? Decreasing it should help.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
