From: "Serge Noiraud" <serge.noiraud@bull.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PREEMPT_RT : 2.6.16-rt12 and boot : BUG ?
Date: Tue, 11 Apr 2006 18:15:25 +0200 [thread overview]
Message-ID: <200604111815.25494.Serge.Noiraud@bull.net> (raw)
In-Reply-To: <200604101446.13610.Serge.Noiraud@bull.net>
Hi,
It now works with all config parameters set to yes on 2.6.16-rt16.
however, PERCPU_ENOUGH_ROOM is set to 384KB.
I'm now trying to lower this value of PERCPU_ENOUGH_ROOM.
With 256K and 2.6.16-rt16 : doesn't work.
With 320K : OK
So I need to use 320K for PERCPU_ENOUGH_ROOM to boot correctly.
I have several questions :
Is there a problem in my config file ?
Will this memory freed at end of kernel loading ?
Why do we need such a size ?
What usage is this for ?
lundi 10 Avril 2006 14:46, Serge Noiraud wrote/a écrit :
> jeudi 6 Avril 2006 17:05, Serge Noiraud wrote/a écrit :
> > jeudi 6 Avril 2006 16:31, Ingo Molnar wrote/a écrit :
> > >
> > > * Serge Noiraud <serge.noiraud@bull.net> wrote:
> > >
> > > > input: ImPS/2 Generic Wheel Mouse as /class/input/input1
> > > > VFS: Mounted root (ext2 filesystem).
> > > > Fusion MPT base driver 3.03.07
> > > > Copyright (c) 1999-2005 LSI Logic Corporation
> > > > Could not allocate 8 bytes percpu data
> > > > mptscsih: Unknown symbol scsi_remove_host
> > >
> > > could you increase (double) PERCPU_ENOUGH_ROOM in
> > > include/linux/percpu.h, does that solve this problem? (and make sure you
> > > use -rt13, -rt12 had a couple of bugs)
> > Tested with rt12 and 192K : same problem
> > Tested with rt12 and 256K : same problem.
> > Tested with rt13 and 256K : same problem.
> > I'm currently compiling with CONFIG_KALLSYMS_ALL not set.
> Same thing.
>
> The boot succeed if I set CONFIG_CRITICAL_IRQSOFF_TIMING to no.
> If I set this parameter to yes, I get the scsi unresolved symbols.
> PERCPU_ENOUGH_ROOM is actually set to 256K.
> I'll try to set the original value.
it didn't work with CONFIG_CRITICAL_IRQSOFF_TIMING set to no and PERCPU_ENOUGH_ROOM = 128K.
>
> I don't see the relation between this parameter and the missing scsi symbols resolution.
> Timing problem ?
>
> > >
> > > Ingo
>
--
Serge Noiraud
next prev parent reply other threads:[~2006-04-11 16:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 12:16 PREEMPT_RT : 2.6.16-rt12 and boot : BUG ? Serge Noiraud
2006-04-06 14:31 ` Ingo Molnar
2006-04-06 15:05 ` Serge Noiraud
2006-04-10 12:46 ` Serge Noiraud
2006-04-11 16:15 ` Serge Noiraud [this message]
2006-04-12 1:58 ` Steven Rostedt
2006-04-12 6:25 ` Ingo Molnar
2006-04-12 7:23 ` Serge Noiraud
2006-04-12 7:30 ` Serge Noiraud
2006-04-12 6:17 ` Ingo Molnar
2006-04-06 14:33 ` Aurelien Degremont
2006-04-06 15:10 ` Serge Noiraud
2006-04-07 9:39 ` Aurelien Degremont
2006-04-06 12:40 Sébastien Dugué
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200604111815.25494.Serge.Noiraud@bull.net \
--to=serge.noiraud@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).