From: Mikael Pettersson <mikpe@csd.uu.se>
To: alan@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: 2.2.18pre15 oops in find_buffer()
Date: Mon, 30 Oct 2000 18:15:52 +0100 (MET) [thread overview]
Message-ID: <200010301715.SAA16699@harpo.it.uu.se> (raw)
Is there any known bug in 2.2.18pre15 that could cause the
following oops in fs/buffer.c:find_buffer() ?
=== snip ===
ksymoops 0.7c on i586 2.2.18pre15. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.2.18pre15/ (default)
-m /boot/System.map-2.2.18pre15 (specified)
Unable to handle kernel paging request at virtual address 80000000
current->tss.cr3 = 01a29000, %cr3 = 01a29000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c0125ef6>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: 80000000 ebx: 00000004 ecx: 00006ec2 edx: 80000000
esi: 0000000a edi: 00000305 ebp: 000a4fc1 esp: c350de4c
ds: 0018 es: 0018 ss: 0018
Process fgrep (pid: 13207, process nr: 39, stackpage=c350d000)
Stack: 00000000 00000400 00006ec2 c0125f2f 00000305 000a4fc1 00001000 c0126c2c
00000305 000a4fc1 00001000 0000287a c246e3cc 00000000 c350deec 00000305
00000000 c114a7e0 c114a900 00000000 000a4fc1 c0139c2a c114a900 00002879
Call Trace: [<c0125f2f>] [<c0126c2c>] [<c0139c2a>] [<c0126f12>] [<c011c99a>] [<c011cd29>] [<c011d0b7>]
[<c011d00c>] [<c0124a9e>] [<c0109eb4>]
Code: 8b 12 39 68 04 75 f3 8b 4c 24 20 39 48 08 75 ea 66 39 78 0c
>>EIP; c0125ef6 <find_buffer+6a/8c> <=====
Trace; c0125f2f <get_hash_table+17/24>
Trace; c0126c2c <brw_page+128/334>
Trace; c0139c2a <ext2_bmap+66/80>
Trace; c0126f12 <generic_readpage+86/94>
Trace; c011c99a <try_to_read_ahead+ee/104>
Trace; c011cd29 <do_generic_file_read+299/57c>
Trace; c011d0b7 <generic_file_read+5b/74>
Trace; c011d00c <file_read_actor+0/50>
Trace; c0124a9e <sys_read+ae/c4>
Trace; c0109eb4 <system_call+34/40>
Code; c0125ef6 <find_buffer+6a/8c>
00000000 <_EIP>:
Code; c0125ef6 <find_buffer+6a/8c> <=====
0: 8b 12 mov (%edx),%edx <=====
Code; c0125ef8 <find_buffer+6c/8c>
2: 39 68 04 cmp %ebp,0x4(%eax)
Code; c0125efb <find_buffer+6f/8c>
5: 75 f3 jne fffffffa <_EIP+0xfffffffa> c0125ef0 <find_buffer+64/8c>
Code; c0125efd <find_buffer+71/8c>
7: 8b 4c 24 20 mov 0x20(%esp,1),%ecx
Code; c0125f01 <find_buffer+75/8c>
b: 39 48 08 cmp %ecx,0x8(%eax)
Code; c0125f04 <find_buffer+78/8c>
e: 75 ea jne fffffffa <_EIP+0xfffffffa> c0125ef0 <find_buffer+64/8c>
Code; c0125f06 <find_buffer+7a/8c>
10: 66 39 78 0c cmp %di,0xc(%eax)
=== snip ===
The instruction that failed is the "next = tmp->b_next" statement in
fs/buffer.c:find_buffer(). From the edx register, we see that "tmp"
(struct buffer_head *) got the value 0x80000000, an invalid pointer.
This happended after 16 days uptime with 2.2.18pre15. Any attempt to
read() a large file would die with the above oops.
memtest86 finds nothing wrong with the memory modules.
The machine seems fine after a reboot and upgrade to 2.2.18pre18.
/Mikael
-
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/
next reply other threads:[~2000-10-30 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 17:15 Mikael Pettersson [this message]
2000-10-30 17:50 ` adrian
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=200010301715.SAA16699@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=alan@lxorguk.ukuu.org.uk \
--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®