From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Mark Hindley <mark@hindley.uklinux.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS: 2.6.9
Date: Thu, 11 Nov 2004 19:35:09 +1100 [thread overview]
Message-ID: <4193243D.3000201@yahoo.com.au> (raw)
In-Reply-To: <20041111072734.GA1671@titan.home.hindley.uklinux.net>
Mark Hindley wrote:
> On Wed, Nov 10, 2004 at 07:28:44PM +1100, Nick Piggin wrote:
>
>
>> a9 40 00 00 00 test $0x40,%eax
>> 74 08 je 33 <_EIP+0x33>
>> 0f 0b ud2a
>>
>>So eax (20001045) is page->flags, which is
>>PG_locked | PG_referenced | PG_active | PG_private, I think.
>>
>>You might have flipped a bit. Can you run memtest86 on the system overnight?
>>
>
>
> Ran for 12 hours overnight. Extended tests, no errors.
>
OK, it's just that it's a pretty common path in the kernel, and if
there was a bug there you'd be very unlucky to be the only one
hitting it. Still, it's possible. Probably the best thing to do is
report it if it happens again.
Oh, what sort of system is it? CPU, how much RAM, etc?
Sorry I can't be of more help.
next prev parent reply other threads:[~2004-11-11 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 7:48 OOPS: 2.6.9 Mark Hindley
2004-11-10 8:28 ` Nick Piggin
2004-11-11 7:27 ` Mark Hindley
2004-11-11 8:35 ` Nick Piggin [this message]
2004-11-11 10:18 ` Arjan van de Ven
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=4193243D.3000201@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@hindley.uklinux.net \
/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