linux-kernel - Re: BUG: kernel oops in 2.6.23.14 - unable to handle kernel paging request

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2375c9f90909160202p59fe30a2neb20b7000cf270cb@mail.gmail.com>
Date:	Wed, 16 Sep 2009 17:02:20 +0800
From:	Américo Wang <xiyou.wangcong@...il.com>
To:	Vinubalaji Gopal <vinubalaji@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: BUG: kernel oops in 2.6.23.14 - unable to handle kernel paging 
	request

On Wed, Sep 16, 2009 at 4:01 PM, Vinubalaji Gopal <vinubalaji@...il.com> wrote:
> Hi all,
>
> I got the following kernel oops message on kernel version 2.6.23. Have
> been searching the list archives, bug database and googling different
> terms related to this oops message, but can't find anything. Any idea
> on what could be causing this - a hardware failure or a bug in the
> kernel? This is happening very rarely and is hard to reproduce :(.
> This kernel is a patched kernel with ipsets and bootsplash.


Does the original kernel have the same problem? If yes, could
you please try 2.6.31?

>
> Thanks in advance.
>
> BUG: unable to handle kernel paging request at virtual address 000c0000
>  printing eip:
> c01723b0
> *pde = 00000000
> Oops: 0000 [#347]
> SMP
> Modules linked in:
> CPU:    0
> EIP:    0060:[<c01723b0>]       Tainted: G      B D VLI
> EIFLAGS: 000010206   (2.6.23)
> EIP is at __kill_fasync+0x10/0x60
> eax: 000c0000   ebx: 000c0000   ecx: 00020001   edx: 0000001d
> esi: 0000001d   edi: 00020001   ebp: 0000000c   esp: d36ebdd4
> ds: 007b   es: 007b   fs: 00d8   gs: 033   ss: 0068
> Process bounce (pid: 29145, ti=d36ea000 task=c2f37aa0 task.ti=d36ea000)
> Stack: 00000000 d5e0c740 000c0000 ccc7792c c0674045 000c0000 d5e11580 c067730f
>       00000000 ccc77900 d3a58600 c072b22a d36ebe1c 00000000 d5e11580 d5e113c0
>       d36ebe78 d36ebe98 00000000 000071d9 00000194 00000194 00000000 00000000
> Call Trace:
>  [<c0674045>] sock_value_async+0x55/0x80
>  [<c067730f>] sock_def_readable+0x5f/0x80
>  [<c072b22a>] unix_stream_sendmsg+0x1ea/0x320
>  [<c0673b3d>] do_sock_write+0x9d/0xb0
>  [<c-673ba4>] sock_aio_write+0x54/0x70
>  [<c01477d5>] find_lock_page+0x25/0x90
>  [<c0166660>] do_sync_write+0xc0/0x100
>  [<c0133700>] autoremove_wake_function+0x0/0x50
>  [<c0114d29>] do_page_fault+0x1b/0x630
>  [<c01667d9>] vfs_write+0x139/0x150
>  [<c01668b7>] sys_write+047/080
>  [<c0102b3e>] syscall_call+0x7/0xb
>  =======================
> Code: 04 a1 04 fe a5 c0 89 fa e0 be 12 ff ff eb bf b6 00 00 00 00 8d
> bf 00 00 00 00 57 89 cf 56 09 d6 53 03 ec 04 05 c0 74 24 <81> 3b 01 46
> 00 00 75 31 0b 43 0c 83 c0 28 83 fe 17 74 1d 8b 53
> EIP: [<c01723b0>] __kill_fasync+0x10/0x60 SS:ESP 0068:d36ebdd4

Interesting call trace...

It says you are writing to a Unix datagram socket, seems this happens
in softirq context? Mind to try script/markup_oops.pl?

If you have a debug kernel, what does `addr2line -e vmlinux 0xc01723b0`
say?

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/