From: Andries Brouwer <aebr@win.tue.nl>
To: William Lee Irwin III <wli@holomorphy.com>,
James W McMechan <mcmechanjw@juno.com>,
linux-kernel@vger.kernel.org
Subject: Re: Oops with tmpfs on both 2.4.22 & 2.6.0-test11
Date: Mon, 1 Dec 2003 08:58:24 +0100 [thread overview]
Message-ID: <20031201075824.GA6068@win.tue.nl> (raw)
In-Reply-To: <20031201012126.GN8039@holomorphy.com>
On Sun, Nov 30, 2003 at 05:21:26PM -0800, William Lee Irwin III wrote:
> On Sun, Nov 30, 2003 at 01:17:46PM -0800, James W McMechan wrote:
> > Unable to handle kernel paging request at virtual address 00200200
> > c018a152
> > *pde = 00000000
> > Oops: 0002 [#1]
> > CPU: 0
> > EIP: 0060:[<c018a152>] Not tainted
>
> This is significantly different in nature from the 2.4 oops, since
> 2.4 hit NULL and this pointer is total garbage.
>
> Either it's a double bitflip or even worse is afoot.
This oops is completely understood. I was going to write to you
yesterday evening, but then saw that Oleg Drokin already had
written. Didnt you see his mail?
next prev parent reply other threads:[~2003-12-01 7:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 21:17 Oops with tmpfs on both 2.4.22 & 2.6.0-test11 James W McMechan
2003-12-01 1:21 ` William Lee Irwin III
2003-12-01 7:58 ` Andries Brouwer [this message]
2003-12-01 8:00 ` William Lee Irwin III
[not found] <20031207.140732.-1654081.3.mcmechanjw@juno.com>
2003-12-08 5:10 ` Maneesh Soni
-- strict thread matches above, loose matches on Subject: below --
2003-12-07 22:48 James McMechan
2003-12-03 11:06 James W McMechan
2003-12-03 12:02 ` Maneesh Soni
2003-12-01 2:59 James W McMechan
2003-12-01 11:37 ` Maneesh Soni
2003-12-01 2:06 James W McMechan
2003-12-01 4:51 ` William Lee Irwin III
2003-12-01 1:06 James W McMechan
2003-12-01 3:43 ` William Lee Irwin III
2003-11-30 17:34 James W McMechan
2003-11-30 20:06 ` William Lee Irwin III
2003-11-30 21:21 ` Oleg Drokin
2003-11-30 16:57 James W McMechan
2003-11-30 19:27 ` William Lee Irwin III
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=20031201075824.GA6068@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mcmechanjw@juno.com \
--cc=wli@holomorphy.com \
/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.