From: Andrew Morton <akpm@osdl.org>
To: Mikael Pettersson <mikpe@user.it.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc3: Bad page state at prep_new_page
Date: Fri, 29 Apr 2005 04:54:47 -0700 [thread overview]
Message-ID: <20050429045447.44649c8e.akpm@osdl.org> (raw)
In-Reply-To: <17006.3525.908807.563680@alkaid.it.uu.se>
Mikael Pettersson <mikpe@user.it.uu.se> wrote:
>
> My trusty network server (440BX PentiumIII box serving NFS and News)
> just threw the following at me:
>
> Bad page state at prep_new_page (in process 'python', page c10984e0)
> flags:0x20021008 mapping:00000000 mapcount:0 count:0
> Backtrace:
> [<c0137555>] bad_page+0x75/0xb0
> [<c01378aa>] prep_new_page+0x2a/0x70
> [<c0137e60>] buffered_rmqueue+0xc0/0x1c0
> [<c01380f0>] __alloc_pages+0xc0/0x400
> [<c01425a9>] do_anonymous_page+0x79/0x150
> [<c0142870>] do_no_page+0x1f0/0x360
> [<c0142c2d>] handle_mm_fault+0x13d/0x170
> [<c0110c92>] do_page_fault+0x2a2/0x6bf
> [<c0111d12>] recalc_task_prio+0xc2/0x170
> [<c026b49b>] schedule+0x31b/0x5c0
> [<c01109f0>] do_page_fault+0x0/0x6bf
> [<c0102dbf>] error_code+0x4f/0x54
> Trying to fix it up, but a reboot is needed
>
> It's running 2.6.12-rc3 since last Friday, but had been running
> 2.6.12-rc2 for weeks before that w/o problems. 2.4 kernels and
> most recent 2.6 kernels have always been rock solid on it.
>
PG_swapcache is set. It wasn't set when this page was returned to the page
allocator.
> This is the first time this box has had a problem like this.
> While I can't rule out bad memory (I'll memtest86 it when I
> get a chance to), I'm inclined to suspect a 2.6 kernel bug.
Could be a bug, but it'd be a damn unusual one. I wouldn't rule out a
bitflip.
next prev parent reply other threads:[~2005-04-29 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 9:45 Mikael Pettersson
2005-04-29 11:54 ` Andrew Morton [this message]
2005-05-04 11:09 ` Mikael Pettersson
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=20050429045447.44649c8e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@user.it.uu.se \
/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