mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: "K.R. Foley" <kr@cybsft.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	Esben Nielsen <simlo@phys.au.dk>,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	Jan Altenberg <tb10alj@tglx.de>
Subject: Re: 2.6.16-rc6-rt3
Date: Mon, 20 Mar 2006 09:48:45 +0100	[thread overview]
Message-ID: <1142844525.4668.1.camel@frecb000686> (raw)
In-Reply-To: <441B756A.9060309@cybsft.com>

On Fri, 2006-03-17 at 20:50 -0600, K.R. Foley wrote:
> Ingo Molnar wrote:
> > * K.R. Foley <kr@cybsft.com> wrote:
> > 
> >> OK. Tried rt9 with a clean build and still no joy. I've attached the 
> >> log which looks like it could be a similar problem?
> > 
> > seems to be a different one:
> > 
> >> input: ImPS/2 Generic Wheel Mouse as /class/input/input1
> >> Freeing unused kernel memory: 284k freed
> >> Could not allocate 8 bytes percpu data
> >> sd_mod: Unknown symbol scsi_print_sense_hdr
> > 
> > could you increase PERCPU_ENOUGH_ROOM in include/linux/percpu.h? (to 
> > e.g. 65536)
> > 
> > 	Ingo
> > 
> 
> Perhaps I misunderstood what you wanted me to do before. Just for grins
> I doubled the PERCPU_ENOUGH_ROOM to 131072 and have successfully booted
> twice now.
> 

  FYI, I bumped it to 196608 to play it safe, maybe 131072 could
be enough, never tried though.


-- 
-----------------------------------------------------

  Sébastien Dugué                BULL/FREC:B1-247
  phone: (+33) 476 29 77 70      Bullcom: 229-7770

  mailto:sebastien.dugue@bull.net

  Linux POSIX AIO: http://www.bullopensource.org/posix
                   http://sourceforge.net/projects/paiol

-----------------------------------------------------


  parent reply	other threads:[~2006-03-20  8:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14  8:46 2.6.16-rc6-rt3 Ingo Molnar
2006-03-14 13:36 ` 2.6.16-rc6-rt3 K.R. Foley
2006-03-14 14:13   ` 2.6.16-rc6-rt3 Steven Rostedt
2006-03-14 14:29     ` 2.6.16-rc6-rt3 K.R. Foley
2006-03-14 14:24   ` 2.6.16-rc6-rt3 Ingo Molnar
2006-03-14 14:31     ` 2.6.16-rc6-rt3 K.R. Foley
2006-03-14 16:37     ` 2.6.16-rc6-rt3 K.R. Foley
2006-03-17  9:23       ` 2.6.16-rc6-rt3 Ingo Molnar
     [not found]         ` <6bffcb0e0603170532r664142a4w@mail.gmail.com>
2006-03-17 13:50           ` 2.6.16-rc6-rt3 Ingo Molnar
2006-03-17 15:44             ` 2.6.16-rc6-rt3 Michal Piotrowski
2006-03-17 16:30         ` 2.6.16-rc6-rt3 K.R. Foley
2006-03-17 20:31           ` 2.6.16-rc6-rt3 Ingo Molnar
2006-03-17 20:44             ` 2.6.16-rc6-rt3 K.R. Foley
2006-03-18  2:50             ` 2.6.16-rc6-rt3 K.R. Foley
2006-03-18  8:56               ` 2.6.16-rc6-rt3 Ingo Molnar
2006-03-20  8:48               ` Sébastien Dugué [this message]
2006-03-14 14:11 ` 2.6.16-rc6-rt3 Michal Piotrowski
2006-03-14 21:24 ` 2.6.16-rc6-rt3 Clark Williams
2006-03-15 11:45 ` 2.6.16-rc6-rt4 Ingo Molnar
2006-03-15 13:17   ` 2.6.16-rc6-rt4 Michal Piotrowski
2006-03-15 15:09     ` 2.6.16-rc6-rt4 Ingo Molnar

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=1142844525.4668.1.camel@frecb000686 \
    --to=sebastien.dugue@bull.net \
    --cc=kr@cybsft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=simlo@phys.au.dk \
    --cc=tb10alj@tglx.de \
    --cc=tglx@linutronix.de \
    /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

Powered by JetHome