From: Andi Kleen <ak@suse.de>
To: Andre Noll <maan@systemlinux.org>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc5: Bad page state in process 'swapper'
Date: Fri, 10 Nov 2006 13:40:56 +0100 [thread overview]
Message-ID: <200611101340.56161.ak@suse.de> (raw)
In-Reply-To: <20061110121151.GC29040@skl-net.de>
On Friday 10 November 2006 13:11, Andre Noll wrote:
> Hi
>
> just tried to boot 2.6.19-rc5 on a 2-way opteron 250 with 8G Ram:
Do you have the earliest kernel messages still in the log buffer (e820 map etc.)?
If yes can we see them.
Did any earlier kernel work?
What is your .config?
Does it help when you apply
ftp://ftp.firstfloor.org/pub/ak/x86_64/quilt/patches/e820-small-entries ?
-Andi
next prev parent reply other threads:[~2006-11-10 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 12:11 2.6.19-rc5: Bad page state in process 'swapper' Andre Noll
2006-11-10 12:24 ` Arjan van de Ven
2006-11-10 13:24 ` Andre Noll
2006-11-10 12:40 ` Andi Kleen [this message]
2006-11-10 13:36 ` Andre Noll
2006-11-10 16:10 ` Andre Noll
2006-11-10 16:35 ` [discuss] " Andi Kleen
2006-11-10 17:26 ` Andre Noll
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=200611101340.56161.ak@suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maan@systemlinux.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