linux-kernel - Re: 2.6.18-rc2-mm1 timer int 0 doesn't work

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 28 Jul 2006 18:24:50 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Paul Fulghum <paulkf@...rogate.com>
Cc:	ak@....de, linux-kernel@...r.kernel.org, mingo@...e.hu,
	ebiederm@...ssion.com
Subject: Re: 2.6.18-rc2-mm1 timer int 0 doesn't work

On Fri, 28 Jul 2006 20:16:32 -0500
Paul Fulghum <paulkf@...rogate.com> 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.

I assume you have a large NR_CPUS?  Decreasing it should help.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/