All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Antti Salmela <asalmela@iki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel BUG at mm/vmscan.c:428 (2.6.17-rc4-git2, Dualcore AMD x86-64)
Date: Mon, 15 May 2006 18:42:45 +1000	[thread overview]
Message-ID: <44683F05.5050709@yahoo.com.au> (raw)
In-Reply-To: <20060515082508.GA6950@asalmela.iki.fi>

Antti Salmela wrote:
> My Dualcore AMD x86-64 desktop has been a little bit unstable as long as I
> remember, but at last I had enough willpower to enable netconsole to see
> if anything was reported after a lockup. For some reason these
> BUG messages made now their way to local log file too.
> 
> May 15 06:51:43 enigma kernel: ----------- [cut here ] --------- [please bite here ] ---------
> May 15 06:51:43 enigma kernel: Kernel BUG at mm/vmscan.c:428
> May 15 06:51:43 enigma kernel: invalid opcode: 0000 [1] PREEMPT SMP 

Thanks for reporting.

Either you have an active page on the inactive list, or your hardware has
flipped a bit in page->flags. I was going to say the latter is more likely,
however -- AFAIKS, the first oops should cause that page to be lost from the
LRU list, so the second oops shouldn't happen if the flip a single bad bit,
and should be pretty unlikely if it is a random error.

Still, anything explainable by a single bit flip is worth running memtest86+
overnight for.

Nick

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-05-15  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15  8:25 Kernel BUG at mm/vmscan.c:428 (2.6.17-rc4-git2, Dualcore AMD x86-64) Antti Salmela
2006-05-15  8:42 ` Nick Piggin [this message]
2006-05-15 13:59   ` Antti Salmela
2006-05-16 10:09     ` Nick Piggin

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=44683F05.5050709@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=asalmela@iki.fi \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.