From: "Rainer Mager" <rmager@vgkk.com>
To: "Marcelo Tosatti" <marcelo@conectiva.com.br>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Oops with 4GB memory setting in 2.4.0 stable
Date: Tue, 16 Jan 2001 08:45:25 +0900 [thread overview]
Message-ID: <NEBBJBCAFMMNIHGDLFKGKENHCMAA.rmager@vgkk.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101151946400.834-100000@freak.distro.conectiva>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
I knew that, I was just testing you all. ;-)
\e hides his head in shame
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Marcelo Tosatti
> Sent: Tuesday, January 16, 2001 6:47 AM
> To: Rainer Mager
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: Oops with 4GB memory setting in 2.4.0 stable
>
>
>
>
> On Tue, 16 Jan 2001, Rainer Mager wrote:
>
> > Attached is my oops.txt and the result sent through
> ksymoops. The results
> > don't look particularly useful to me so perhaps I'm doing
> something wrong.
> > PLEASE tell me if I should parse this differently. Likewise, if there is
> > anything else I can do to help debug this, please tell me.
>
> It seems you forgot to attach oops.txt.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
[-- Attachment #2: oops.parsed --]
[-- Type: application/octet-stream, Size: 2090 bytes --]
ksymoops 0.7c on i686 2.4.0. Options used
-v /boot/vmlinux-2.4.0-bigmem (specified)
-K (specified)
-L (specified)
-o /lib/modules/2.4.0/ (default)
-m /boot/System.map-2.4.0-bigmem (specified)
No modules in ksyms, skipping objects
Unable to handle kernel NULL pointer dereference at virtual address 00000000
f889e044
*pde = 00000000
Oops: 0002
CPU: 1
EIP: 0010:[<f889e044>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000 ebx: d5762800 ecx: 00000400 edx: c19665fc
esi: d55be120 edi: 00000000 ebp: d5764260 esp: d5505f1c
ds: 0018 es: 0018 ss: 0018
Process ls (pid: 865, stackpage=d5505000)
Stack: d5762800 d55be120 d5764260 d5764260 d55be120 00000000 f889d966 d55be120
d5762800 d5504000 d5764260 fffffffe fffffffb d5762800 d5764260 d55be120
00000000 d5764260 bffffa40 00000006 c0140c10 d5764260 d5505fb0 c0140e7c
Call Trace: [<f889d966>] [<c0140c10>] [<c0140e7c>] [<c0140f9e>] [<c0140e7c>] [<c0108f4b>]
Code: f3 ab e9 8b 00 00 00 90 8d 74 26 00 8b 44 24 14 c7 00 00 00
>>EIP; f889e044 <END_OF_CODE+385bfe34/????> <=====
Trace; f889d966 <END_OF_CODE+385bf756/????>
Trace; c0140c10 <vfs_readdir+90/ec>
Trace; c0140e7c <filldir+0/d8>
Trace; c0140f9e <sys_getdents+4a/98>
Trace; c0140e7c <filldir+0/d8>
Trace; c0108f4b <system_call+33/38>
Code; f889e044 <END_OF_CODE+385bfe34/????>
00000000 <_EIP>:
Code; f889e044 <END_OF_CODE+385bfe34/????> <=====
0: f3 ab repz stos %eax,%es:(%edi) <=====
Code; f889e046 <END_OF_CODE+385bfe36/????>
2: e9 8b 00 00 00 jmp 92 <_EIP+0x92> f889e0d6 <END_OF_CODE+385bfec6/????>
Code; f889e04b <END_OF_CODE+385bfe3b/????>
7: 90 nop
Code; f889e04c <END_OF_CODE+385bfe3c/????>
8: 8d 74 26 00 lea 0x0(%esi,1),%esi
Code; f889e050 <END_OF_CODE+385bfe40/????>
c: 8b 44 24 14 mov 0x14(%esp,1),%eax
Code; f889e054 <END_OF_CODE+385bfe44/????>
10: c7 00 00 00 00 00 movl $0x0,(%eax)
[-- Attachment #3: oops.txt --]
[-- Type: text/plain, Size: 810 bytes --]
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
f889e044
*pde = 00000000
Oops: 0002
CPU: 1
EIP: 0010:[<f889e044>]
EFLAGS: 00010246
eax: 00000000 ebx: d5762800 ecx: 00000400 edx: c19665fc
esi: d55be120 edi: 00000000 ebp: d5764260 esp: d5505f1c
ds: 0018 es: 0018 ss: 0018
Process ls (pid: 865, stackpage=d5505000)
Stack: d5762800 d55be120 d5764260 d5764260 d55be120 00000000 f889d966 d55be120
d5762800 d5504000 d5764260 fffffffe fffffffb d5762800 d5764260 d55be120
00000000 d5764260 bffffa40 00000006 c0140c10 d5764260 d5505fb0 c0140e7c
Call Trace: [<f889d966>] [<c0140c10>] [<c0140e7c>] [<c0140f9e>] [<c0140e7c>] [<c0108f4b>]
Code: f3 ab e9 8b 00 00 00 90 8d 74 26 00 8b 44 24 14 c7 00 00 00
Segmentation fault
next prev parent reply other threads:[~2001-01-15 23:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 22:47 FS corruption on 2.4.0-ac8 Jure Pecar
2001-01-15 21:11 ` Marcelo Tosatti
2001-01-16 1:00 ` Neil Brown
2001-01-15 23:31 ` Oops with 4GB memory setting in 2.4.0 stable Rainer Mager
2001-01-15 21:47 ` Marcelo Tosatti
2001-01-15 23:45 ` Rainer Mager [this message]
2001-01-15 22:09 ` Marcelo Tosatti
2001-01-16 0:21 ` Rainer Mager
2001-01-15 22:37 ` Marcelo Tosatti
2001-01-16 2:03 ` Keith Owens
2001-01-16 8:40 ` Urban Widmark
2001-01-17 23:59 ` Rainer Mager
2001-01-18 0:30 ` Urban Widmark
2001-01-16 0:29 ` FS corruption on 2.4.0-ac8 Andreas Dilger
2001-01-16 13:33 Oops with 4GB memory setting in 2.4.0 stable Petr Vandrovec
2001-01-16 20:17 ` Urban Widmark
2001-01-16 22:29 Petr Vandrovec
2001-01-16 22:38 ` Urban Widmark
2001-01-16 22:42 ` Rainer Mager
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=NEBBJBCAFMMNIHGDLFKGKENHCMAA.rmager@vgkk.com \
--to=rmager@vgkk.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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
all inboxes | Powered by JetHome®