From: Michail Bachmann <mb@emeraldcity.de>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Christoph Lameter <cl@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel BUG at mm/page_alloc.c:775
Date: Fri, 29 Jan 2010 23:01:57 +0100 [thread overview]
Message-ID: <201001292302.04105.mb@emeraldcity.de> (raw)
In-Reply-To: <201001210110.18569.mb@emeraldcity.de>
[-- Attachment #1: Type: Text/Plain, Size: 994 bytes --]
> > On Tue, Jan 12, 2010 at 03:25:23PM -0600, Christoph Lameter wrote:
> > > On Sat, 9 Jan 2010, Michail Bachmann wrote:
> > > > [ 48.505381] kernel BUG at mm/page_alloc.c:775!
> > >
> > > Somehow nodes got mixed up or the lookup tables for pages / zones are
> > > not giving the right node numbers.
> >
> > Agreed. On this type of machine, I'm not sure how that could happen
> > short of struct page information being corrupted. The range should
> > always be aligned to a pageblock boundary and I cannot see how that
> > would cross a zone boundary on this machine.
> >
> > Does this machine pass memtest?
>
> I ran one pass with memtest86 without errors before posting this bug, but I
> can let it run "all tests" for a while just to be sure it is not caused by
> broken hw.
Please disregard this bug report. After running memtest for more than 10 hours
it found a memory error. The funny thing is, linux found it much faster...
Thanks for your time.
CU Micha
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-01-29 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 21:32 PROBLEM: kernel BUG at mm/page_alloc.c:775 Michail Bachmann
2010-01-12 21:25 ` Christoph Lameter
2010-01-18 12:03 ` Mel Gorman
2010-01-21 0:10 ` Michail Bachmann
2010-01-29 22:01 ` Michail Bachmann [this message]
2010-02-01 10:29 ` Mel Gorman
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=201001292302.04105.mb@emeraldcity.de \
--to=mb@emeraldcity.de \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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;
as well as URLs for NNTP newsgroup(s).