From: Frank van Maarseveen <fvm@altium.nl>
To: linux-kernel@vger.kernel.org
Subject: 2.4.17 Oops
Date: Thu, 14 Feb 2002 09:39:55 +0100 [thread overview]
Message-ID: <20020214093955.A28603@espoo.tasking.nl> (raw)
ksymoops 2.3.5 on i686 2.4.17-x67. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.17-x67/ (default)
-m /boot/System.map-2.4.17-x67 (specified)
Feb 14 09:35:01 espoo kernel: Unable to handle kernel paging request at virtual address 0000ffff
Feb 14 09:35:01 espoo kernel: c0140de0
Feb 14 09:35:01 espoo kernel: *pde = 00000000
Feb 14 09:35:01 espoo kernel: Oops: 0000
Feb 14 09:35:01 espoo kernel: CPU: 0
Feb 14 09:35:01 espoo kernel: EIP: 0010:[<c0140de0>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Feb 14 09:35:01 espoo kernel: EFLAGS: 00010207
Feb 14 09:35:01 espoo kernel: eax: c1471600 ebx: 0000ffef ecx: 0000000f edx: c1440000
Feb 14 09:35:01 espoo kernel: esi: 0028c69d edi: c9baff74 ebp: 0000ffff esp: c9baff10
Feb 14 09:35:01 espoo kernel: ds: 0018 es: 0018 ss: 0018
Feb 14 09:35:01 espoo kernel: Process distribute (pid: 28497, stackpage=c9baf000)
Feb 14 09:35:01 espoo kernel: Stack: 0028c69d ce252adc c9baff74 c9baffa4 c1471600 cd014014 0028c69d 00000003
Feb 14 09:35:01 espoo kernel: c0138d04 ce252adc c9baff74 0028c69d c013942a ce252adc c9baff74 00000000
Feb 14 09:35:01 espoo kernel: cd014000 00000000 c9baffa4 00000009 c9bae000 c9bae000 00000009 cd014017
Feb 14 09:35:01 espoo kernel: Call Trace: [<c0138d04>] [<c013942a>] [<c013969a>] [<c0139a51>] [<c0136869>]
Feb 14 09:35:01 espoo kernel: [<c0106db3>]
Feb 14 09:35:01 espoo kernel: Code: 8b 6d 00 8b 74 24 18 39 73 44 75 7c 8b 74 24 24 39 73 0c 75
>>EIP; c0140de0 <d_lookup+60/100> <=====
Trace; c0138d04 <cached_lookup+10/54>
Trace; c013942a <link_path_walk+522/778>
Trace; c013969a <path_walk+1a/1c>
Trace; c0139a51 <__user_walk+35/50>
Trace; c0136869 <sys_newstat+19/70>
Trace; c0106db3 <system_call+33/40>
Code; c0140de0 <d_lookup+60/100>
00000000 <_EIP>:
Code; c0140de0 <d_lookup+60/100> <=====
0: 8b 6d 00 movl 0x0(%ebp),%ebp <=====
Code; c0140de3 <d_lookup+63/100>
3: 8b 74 24 18 movl 0x18(%esp,1),%esi
Code; c0140de7 <d_lookup+67/100>
7: 39 73 44 cmpl %esi,0x44(%ebx)
Code; c0140dea <d_lookup+6a/100>
a: 75 7c jne 88 <_EIP+0x88> c0140e68 <d_lookup+e8/100>
Code; c0140dec <d_lookup+6c/100>
c: 8b 74 24 24 movl 0x24(%esp,1),%esi
Code; c0140df0 <d_lookup+70/100>
10: 39 73 0c cmpl %esi,0xc(%ebx)
Code; c0140df3 <d_lookup+73/100>
13: 75 00 jne 15 <_EIP+0x15> c0140df5 <d_lookup+75/100>
--
Frank
reply other threads:[~2002-02-14 8:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020214093955.A28603@espoo.tasking.nl \
--to=fvm@altium.nl \
--cc=frank.van.maarseveen@altium.nl \
--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
all inboxes | Powered by JetHome®