public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: Andre Noll <maan@systemlinux.org>, linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: 2.6.19-rc5: Bad page state in process 'swapper'
Date: Fri, 10 Nov 2006 17:35:29 +0100	[thread overview]
Message-ID: <200611101735.29828.ak@suse.de> (raw)
In-Reply-To: <20061110161005.GF29040@skl-net.de>

On Friday 10 November 2006 17:10, Andre Noll wrote:
> On 14:36, Andre Noll wrote:
> 
> > > Does it help when you apply 
> > > 
> > > ftp://ftp.firstfloor.org/pub/ak/x86_64/quilt/patches/e820-small-entries ? 
> > 
> > OK I will try this. Can't promise if I will be able to do so today, as I
> > have to wait until the currently running jobs are finished.
> 
> I could check it already today: Your patch doesn't help unfortunately,
> i.e. I get the same "Bad page state in process 'swapper'" messages also
> with this patch. Again, nothing containing "e820" in the log.

If you apply the following debug patch you should get a shorter log.
Can you post it please?

-Andi

Index: linux/mm/page_alloc.c
===================================================================
--- linux.orig/mm/page_alloc.c
+++ linux/mm/page_alloc.c
@@ -188,6 +188,11 @@ static inline int bad_range(struct zone 
 
 static void bad_page(struct page *page)
 {
+	static int flag;
+	if (flag)
+		return;
+	flag = 1;
+
 	printk(KERN_EMERG "Bad page state in process '%s'\n"
 		KERN_EMERG "page:%p flags:0x%0*lx mapping:%p mapcount:%d count:%d\n"
 		KERN_EMERG "Trying to fix it up, but a reboot is needed\n"

  reply	other threads:[~2006-11-10 16:35 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
2006-11-10 13:36   ` Andre Noll
2006-11-10 16:10     ` Andre Noll
2006-11-10 16:35       ` Andi Kleen [this message]
2006-11-10 17:26         ` [discuss] " 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=200611101735.29828.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