From: pinotj@club-internet.fr
To: torvalds@osdl.org, nathans@sgi.com
Cc: manfred@colorfullife.com, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [Oops] i386 mm/slab.c (cache_flusharray)
Date: Thu, 4 Dec 2003 19:27:41 CET [thread overview]
Message-ID: <mnet1.1070562461.26292.pinotj@club-internet.fr> (raw)
OK, I tried again the patch on "small kernel" test11 with CONFIG_DEBUG_PAGEALLOC only. Here are the first results. I will do more tests later because it seems weird. This time I have very different behavior for XFS and Ext3.
I got an oops at boot time, when system try to mount root filesystem (XFS).
But when I tried on a root Ext3, I got no problem at all. I even compiled 2 kernel straight without any problems. It seems to be the first time a test11 works flawless on my system.
Of course, XFS and Ext3 were respectively enabled in the kernels.
I hope I didn't make any mistake, I will confirm tomorrow.
Jerome Pinot
The XFS oops (I was too lazy to write down all the backtraces, all about xfs_* things, I can send if needed):
---
kernel BUG at include/linux/mm.h:267!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<c01aa5ac>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000 ebx: cef3d000 ecx: cef3c000 edx: c1254e28
esi: 00310020 edi: 00000001 ebp: c12f3b18 esp: c12f3b0c
ds: 007b es: 007b ss: 0068
Stack: 00000100 00000000 ceee0000 c12f3b28 c01aaf90 c0253d40 cef3d000 c12f3b7c
c019669b cef3d000 00000100 00000000 00000100 00000000 00000a02 00000000
00000100 00000000 cef3d000 00000100 00000000 00000a02 00000000 00000802
Call Trace:
[<c01aaf90>] pagebuf_free+0x24/0x30
[<c019669b>] xlog_find_verify_cycle+0x18b/0x1e0
Code: 0f 0b 0b 01 d6 cb 1f c0 eb 8e ff 73 54 eb b3 90 53 e8 0e 11
>>EIP; c01aa5ac <_pagebuf_free_object+108/134> <=====
>>ebx; cef3d000 <_end+ece0e4c/3fda1e4c>
>>ecx; cef3c000 <_end+ecdfe4c/3fda1e4c>
>>edx; c1254e28 <_end+ff8c74/3fda1e4c>
>>ebp; c12f3b18 <_end+1097964/3fda1e4c>
>>esp; c12f3b0c <_end+1097958/3fda1e4c>
Trace; c01aaf90 <pagebuf_free+24/30>
Trace; c019669b <xlog_find_verify_cycle+18b/1e0>
Code; c01aa5ac <_pagebuf_free_object+108/134>
00000000 <_EIP>:
Code; c01aa5ac <_pagebuf_free_object+108/134> <=====
0: 0f 0b ud2a <=====
Code; c01aa5ae <_pagebuf_free_object+10a/134>
2: 0b 01 or (%ecx),%eax
Code; c01aa5b0 <_pagebuf_free_object+10c/134>
4: d6 (bad)
Code; c01aa5b1 <_pagebuf_free_object+10d/134>
5: cb lret
Code; c01aa5b2 <_pagebuf_free_object+10e/134>
6: 1f pop %ds
Code; c01aa5b3 <_pagebuf_free_object+10f/134>
7: c0 eb 8e shr $0x8e,%bl
Code; c01aa5b6 <_pagebuf_free_object+112/134>
a: ff 73 54 pushl 0x54(%ebx)
Code; c01aa5b9 <_pagebuf_free_object+115/134>
d: eb b3 jmp ffffffc2 <_EIP+0xffffffc2>
Code; c01aa5bb <_pagebuf_free_object+117/134>
f: 90 nop
Code; c01aa5bc <_pagebuf_free_object+118/134>
10: 53 push %ebx
Code; c01aa5bd <_pagebuf_free_object+119/134>
11: e8 0e 11 00 00 call 1124 <_EIP+0x1124>
<0>Kernel panic: Attempted to kill the idle task!
---
next reply other threads:[~2003-12-04 18:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 18:27 pinotj [this message]
2003-12-04 18:49 ` [Oops] i386 mm/slab.c (cache_flusharray) Linus Torvalds
2003-12-04 19:09 ` Linus Torvalds
2003-12-04 21:21 ` Nathan Scott
2003-12-05 7:14 ` Christoph Hellwig
2003-12-05 9:34 ` Nathan Scott
2003-12-05 14:22 ` Christoph Hellwig
2003-12-05 3:00 ` Nathan Scott
2003-12-05 6:40 ` Linus Torvalds
2003-12-04 19:19 ` Manfred Spraul
2003-12-04 21:26 ` Nathan Scott
-- strict thread matches above, loose matches on Subject: below --
2003-12-09 0:57 pinotj
2003-12-09 2:03 ` Nathan Scott
2003-12-09 7:21 ` Christoph Hellwig
2003-12-09 23:58 ` Nathan Scott
2003-12-12 19:00 ` Christoph Hellwig
2003-12-12 20:07 ` Manfred Spraul
2003-12-03 23:06 pinotj
2003-12-03 23:26 ` Linus Torvalds
2003-11-29 17:41 pinotj
2003-12-02 0:36 ` Linus Torvalds
2003-12-02 1:37 ` Nathan Scott
2003-12-02 6:44 ` Nathan Scott
2003-12-02 18:05 ` Mike Fedyk
2003-12-02 20:05 ` Nathan Scott
2003-11-27 18:42 pinotj
2003-11-27 18:55 ` Manfred Spraul
2003-12-02 1:03 ` Mike Fedyk
2003-11-25 17:30 pinotj
2003-11-25 22:51 ` Linus Torvalds
2003-11-27 18:07 ` Manfred Spraul
2003-11-22 7:47 Re: " pinotj
2003-11-22 10:55 ` Manfred Spraul
2003-11-21 18:12 pinotj
2003-11-21 18:58 ` Manfred Spraul
2003-11-20 1:50 pinotj
2003-11-20 2:09 ` Andrew Morton
2003-11-19 18:19 pinotj
2003-11-20 1:07 ` Andrew Morton
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=mnet1.1070562461.26292.pinotj@club-internet.fr \
--to=pinotj@club-internet.fr \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=nathans@sgi.com \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).