From: Grant Coady <gcoady.lk@gmail.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: linux-kernel@vger.kernel.org, Marcelo Tosatti <marcelo@kvack.org>,
Grant Coady <grant_lkml@dodo.com.au>,
Jari Ruusu <jariruusu@users.sourceforge.net>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [ANNOUNCE] Linux-2.4.32-hf32.5
Date: Fri, 26 May 2006 23:28:51 +1000 [thread overview]
Message-ID: <vvvd72p7mv2j9fet19evm807e0flonnugh@4ax.com> (raw)
In-Reply-To: <20060526121623.GA14474@w.ods.org>
On Fri, 26 May 2006 14:16:23 +0200, Willy Tarreau <willy@w.ods.org> wrote:
>Could you please pass it through ksymoops so that we get an idea about the
>function causing this ? What was the last version not causing it ? hf32.4 ?
Yes, hf32.4 okay, see: <http://bugsplatter.mine.nu/test/linux-2.4/>
>This looks like a structure member gets accessed while a pointer is NULL,
>if you always get 0x88... I would be it could come from
>2.4.32-ext3-link-unlink-race-1, but that would be strange.
Good guess! The previous version comment stripped .configs are
linked by machine name from the summary page above.
Localtime 23:28 so it will be overnight delay before I reply to
queries for further info ;)
grant@sempro:~$ ksymoops -v ~/linux/linux-2.4.32-hf32.5/vmlinux -m /boot/System.map-2.4.32-hf32.5 oops
ksymoops 2.4.11 on i686 2.6.16.17a. Options used
-v /home/grant/linux/linux-2.4.32-hf32.5/vmlinux (specified)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.6.16.17a/ (default)
-m /boot/System.map-2.4.32-hf32.5 (specified)
Error (regular_file): read_ksyms stat /proc/ksyms failed
ksymoops: No such file or directory
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Unable to handle kernel NULL pointer dereference at virtual address 00000088 printing eip:
c013ee43
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<c013ee43>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000088 ebx: c19bb5c0 ecx: 00000088 edx: f7bf0005
esi: f7e3c508 edi: c19bb5c0 ebp: f7e3c480 esp: f7e6bf18
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 1, stackpage=f7e6b000)
Stack: c19bb5c0 00000000 c19bb5c0 f7bf0000 f7e6bf3c c19bb5c0 c013f056 f7e3c480
c19bb5c0 c19bb440 c19ac140 f7bf0005 00000004 01c0d8cc 00000010 00000000
c013e727 00000803 c02a18f6 c0105000 0008e000 c0302bfb c02a18f6 f7bf0000
Call Trace: [<c013f056>] [<c013e727>] [<c0105000>] [<c013e890>] [<c01051f3>]
[<c0105085>] [<c010568b>] [<c0105070>]
Code: ff 08 0f 88 8f 16 00 00 8b 5f 08 85 db 74 0c 8b 47 0c 39 68
>>EIP; c013ee43 <vfs_unlink+33/190> <=====
Trace; c013f056 <sys_unlink+b6/120>
Trace; c013e727 <vfs_mknod+c7/120>
Trace; c0105000 <_stext+0/0>
Trace; c013e890 <sys_mknod+110/180>
Trace; c01051f3 <prepare_namespace+73/140>
Trace; c0105085 <init+15/110>
Trace; c010568b <arch_kernel_thread+2b/40>
Trace; c0105070 <init+0/110>
Code; c013ee43 <vfs_unlink+33/190>
00000000 <_EIP>:
Code; c013ee43 <vfs_unlink+33/190> <=====
0: ff 08 decl (%eax) <=====
Code; c013ee45 <vfs_unlink+35/190>
2: 0f 88 8f 16 00 00 js 1697 <_EIP+0x1697>
Code; c013ee4b <vfs_unlink+3b/190>
8: 8b 5f 08 mov 0x8(%edi),%ebx
Code; c013ee4e <vfs_unlink+3e/190>
b: 85 db test %ebx,%ebx
Code; c013ee50 <vfs_unlink+40/190>
d: 74 0c je 1b <_EIP+0x1b>
Code; c013ee52 <vfs_unlink+42/190>
f: 8b 47 0c mov 0xc(%edi),%eax
Code; c013ee55 <vfs_unlink+45/190>
12: 39 68 00 cmp %ebp,0x0(%eax)
<0>Kernel panic: Attempted to kill init!
1 error issued. Results may not be reliable.
Thanks,
Grant.
next prev parent reply other threads:[~2006-05-26 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 13:10 [ANNOUNCE] Linux-2.4.32-hf32.4 Willy Tarreau
2006-05-25 13:34 ` [ANNOUNCE] Linux-2.4.32-hf32.5 Willy TARREAU
2006-05-26 11:09 ` Grant Coady
2006-05-26 12:16 ` Willy Tarreau
2006-05-26 13:28 ` Grant Coady [this message]
2006-05-26 14:07 ` Willy Tarreau
2006-05-26 18:27 ` Marcelo Tosatti
2006-05-26 19:29 ` Grant Coady
2006-05-26 19:43 ` Willy Tarreau
2006-05-26 18:38 ` Grant Coady
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=vvvd72p7mv2j9fet19evm807e0flonnugh@4ax.com \
--to=gcoady.lk@gmail.com \
--cc=chrisw@sous-sol.org \
--cc=grant_lkml@dodo.com.au \
--cc=jariruusu@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.org \
--cc=willy@w.ods.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®