From: Steven Cole <elenstev@mesatop.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Andrew Morton <akpm@zip.com.au>, linux-mm@kvack.org
Subject: Re: 2.5.41-mm1 oops on boot (EIP at kmem_cache_alloc)
Date: 09 Oct 2002 10:25:14 -0600 [thread overview]
Message-ID: <1034180714.32404.200.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <3DA4543B.A2E5C5B1@digeo.com>
On Wed, 2002-10-09 at 10:07, Andrew Morton wrote:
> Steven Cole wrote:
> >
> > Greetings,
> >
> > I got an oops when booting 2.5.41-mm1 on my dual p3.
>
> Manfred sent through an update - don't know if it will
> fix this though:
>
>
[patch snipped]
Yep, that worked. Thanks. I also got the same debug message
for mm/slab.c:1374 which I reported for 2.5.41-bk2, plus the usual
set of "bad: scheduling while atomic!" messages on boot up.
Steven
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
prev parent reply other threads:[~2002-10-09 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 15:33 Steven Cole
2002-10-09 16:07 ` Andrew Morton
2002-10-09 16:25 ` Steven Cole [this message]
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=1034180714.32404.200.camel@spc9.esa.lanl.gov \
--to=elenstev@mesatop.com \
--cc=akpm@digeo.com \
--cc=akpm@zip.com.au \
--cc=linux-mm@kvack.org \
/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