From: "Nick Piggin" <s3293115@student.anu.edu.au>
To: "Linux-Kernel" <linux-kernel@vger.kernel.org>
Subject: test9 oops (in block_read_full_page)
Date: Mon, 30 Oct 2000 02:43:25 +1100 [thread overview]
Message-ID: <029f01c041be$fab45d90$0200a8c0@W2K> (raw)
[-- Attachment #1: Type: text/plain, Size: 166 bytes --]
I apologise if this oops has already been fixed: it has happened twice but I
can't find the exact way to trigger it, I just want to make sure it is
reported ;)
Nick
[-- Attachment #2: oops --]
[-- Type: application/octet-stream, Size: 2257 bytes --]
Unable to handle kernel paging request at virtual address f8e400cc
c013020a
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c013020a>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010202
eax: f8e400c0 ebx: c3fdb3d0 ecx: c1a7c81f edx: c1033c48
esi: c1033c48 edi: c1a7c8bc ebp: 00000000 esp: c1b91ee4
ds: 0018 es: 0018 ss: 0018
Process bash (pid: 383, stackpage=c1b91000)
Stack: c3fdb3d0 c1033c48 c1a7c8bc 00000000 c02677c0 c012a44a 00000000 c0267a58
c1a7c8bc c1a7c81f c012a5b8 c0267a4c 00000000 00000001 00000001 00000000
00000000 c1a7c8bc c014e33f c1033c48 c014dca0 c0123275 c1531cc0 c1033c48
Call Trace: [<c012a44a>] [<c012a5b8>] [<c014e33f>] [<c014dca0>] [<c0123275>] [<c012355b>] [<c01234a0>]
[<c012db56>] [<c010a4d3>]
Code: 8b 68 0c 8b 44 24 4c 83 78 38 00 75 0b 55 51 50 e8 b1 fa ff
>>EIP; c013020a <block_read_full_page+4a/1f0> <=====
Trace; c012a44a <__alloc_pages_limit+8a/b0>
Trace; c012a5b8 <__alloc_pages+148/300>
Trace; c014e33f <ext2_readpage+f/20>
Trace; c014dca0 <ext2_get_block+0/490>
Trace; c0123275 <do_generic_file_read+2a5/4d0>
Trace; c012355b <generic_file_read+5b/80>
Trace; c01234a0 <file_read_actor+0/60>
Trace; c012db56 <sys_read+96/d0>
Trace; c010a4d3 <system_call+33/38>
Code; c013020a <block_read_full_page+4a/1f0>
00000000 <_EIP>:
Code; c013020a <block_read_full_page+4a/1f0> <=====
0: 8b 68 0c mov 0xc(%eax),%ebp <=====
Code; c013020d <block_read_full_page+4d/1f0>
3: 8b 44 24 4c mov 0x4c(%esp,1),%eax
Code; c0130211 <block_read_full_page+51/1f0>
7: 83 78 38 00 cmpl $0x0,0x38(%eax)
Code; c0130215 <block_read_full_page+55/1f0>
b: 75 0b jne 18 <_EIP+0x18> c0130222 <block_read_full_page+62/1f0>
Code; c0130217 <block_read_full_page+57/1f0>
d: 55 push %ebp
Code; c0130218 <block_read_full_page+58/1f0>
e: 51 push %ecx
Code; c0130219 <block_read_full_page+59/1f0>
f: 50 push %eax
Code; c013021a <block_read_full_page+5a/1f0>
10: e8 b1 fa ff 00 call fffac6 <_EIP+0xfffac6> c112fcd0 <_end+e539dc/4550d0c>
reply other threads:[~2000-10-29 15:47 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='029f01c041be$fab45d90$0200a8c0@W2K' \
--to=s3293115@student.anu.edu.au \
--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