From: Nathan Conrad <conrad@bungled.net>
To: Andrew Morton <akpm@digeo.com>
Cc: green@namesys.com, davej@codemonkey.org.uk, linux-kernel@vger.kernel.org
Subject: Re: ext3 / reiserfs data corruption, 2.5-bk; NULL pointer dereference bug
Date: Thu, 12 Jun 2003 01:20:59 -0400 [thread overview]
Message-ID: <20030612052059.GA2366@bungled.net> (raw)
In-Reply-To: <20030610135935.5db1abb7.akpm@digeo.com>
[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]
I just saw another one of these NULL pointer dereference oops on my
laptop:
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
c01665f3
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[__d_lookup+99/256] Not tainted
EFLAGS: 00210282
EIP is at __d_lookup+0x63/0x100
eax: 00000000 ebx: c06ef980 ecx: 00000010 edx: dfe80000
esi: dfe8da40 edi: 00000000 ebp: df85be70 esp: db047ec8
ds: 007b es: 007b ss: 0068
Process gcc (pid: 4738, threadinfo=db046000 task=c22198c0)
Stack: dcfcc014 c012a225 00000000 00000000 dfe8da40 db047f48 00000000 dcfcc001
0029e101 00000003 dcfcc001 db047f90 dfff4fc0 db047f3c c015cf80 dfd50e00
db047f44 c015cb64 dcfcc001 dcfcc005 db047f3c db047f44 c015d129 db047f90
Call Trace:
[in_group_p+37/48] in_group_p+0x25/0x30
[do_lookup+48/176] do_lookup+0x30/0xb0
[permission+84/112] permission+0x54/0x70
[link_path_walk+297/2000] link_path_walk+0x129/0x7d0
[__user_walk+73/96] __user_walk+0x49/0x60
[sys_access+129/320] sys_access+0x81/0x140
[syscall_call+7/11] syscall_call+0x7/0xb
Code: 0f 18 00 90 8b 74 24 10 8d 5d 90 39 73 78 75 17 8b 7b 58 89
I ran memtest86 for about 14 hours and it passed all of its tests. I
enabled the memory debugging options (under the kernel hacking
section) and I did not notice any errors displayed by it in my syslog.
I'm not sure what else to try... The backtrace is signifigantly
different that the last one...
On Tue, Jun 10, 2003 at 01:59:35PM -0700, Andrew Morton wrote:
> Nathan Conrad <conrad@bungled.net> wrote:
> >
> > Unable to handle kernel NULL pointer dereference at virtual address 00000000
> > printing eip:
> > c016781a
> > *pde = 00000000
> > Oops: 0000 [#1]
> > CPU: 0
> > EIP: 0060:[find_inode_fast+26/96] Not tainted
>
> Something scribbled on your inode hash chains. Please make sure that
> you're building the kernel with all the memory debug options enabled, and
> run memtest86 on that machine for 12 hourws or so.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-12 5:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 19:35 ext3 / reiserfs data corruption, 2.5-bk Dave Jones
2003-06-10 8:43 ` Oleg Drokin
2003-06-10 9:20 ` Dave Jones
2003-06-10 21:44 ` Nathan Conrad
2003-06-10 18:11 ` Bartlomiej Zolnierkiewicz
2003-06-10 22:18 ` Nathan Conrad
2003-06-10 20:59 ` Andrew Morton
2003-06-12 5:20 ` Nathan Conrad [this message]
2003-06-10 22:49 ` Dave Jones
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=20030612052059.GA2366@bungled.net \
--to=conrad@bungled.net \
--cc=akpm@digeo.com \
--cc=davej@codemonkey.org.uk \
--cc=green@namesys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox