LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* Kernel BUG at mm/slab.c:595
@ 2007-02-04 14:55 Yu-Chen Wu
2007-02-04 15:47 ` Arjan van de Ven
2007-02-05 12:14 ` Joerg Roedel
0 siblings, 2 replies; 3+ messages in thread
From: Yu-Chen Wu @ 2007-02-04 14:55 UTC (permalink / raw)
To: linux-kernel
Hi all,
I am developing my module, but meet a bug. Is the bug created by
me??
Kernel:2.6.18 on SUSE10.1 + Intel DualCore
Feb 5 00:57:39 VM-SUSE kernel: ----------- [cut here ] --------- [please
bite here ] ---------
Feb 5 00:57:39 VM-SUSE kernel: Kernel BUG at mm/slab.c:595
Feb 5 00:57:39 VM-SUSE kernel: invalid opcode: 0000 [1] SMP
Feb 5 00:57:39 VM-SUSE kernel: CPU 1
Feb 5 00:57:39 VM-SUSE kernel: Modules linked in: raid0 mymodule
acpi_cpufreq edd freq_table ipv6 button battery ac
loop d
Feb 5 00:57:39 VM-SUSE kernel: Pid: 3239, comm: read_helper_1 Tainted: GF
2.6.18-yuchen #1
Feb 5 00:57:39 VM-SUSE kernel: RIP: 0010:[<ffffffff8027d4a6>]
[<ffffffff8027d4a6>] kfree+0x5e/0x1bd
Feb 5 00:57:39 VM-SUSE kernel: RSP: 0018:ffff810036d19dd0 EFLAGS: 00010046
Feb 5 00:57:39 VM-SUSE kernel: RAX: 0000000000000000 RBX: 0000000000004000
RCX: 000000000000003f
Feb 5 00:57:39 VM-SUSE kernel: RDX: ffff810000771840 RSI: 0000000000040000
RDI: 00000000000082b8
Feb 5 00:57:39 VM-SUSE kernel: RBP: ffffffff882b8d78 R08: 00000000fffffffc
R09: ffff810036d19ba0
Feb 5 00:57:39 VM-SUSE kernel: R10: 0000000000000001 R11: 0000000000000000
R12: 0000000000000009
Feb 5 00:57:39 VM-SUSE kernel: R13: ffff8100364f74c8 R14: 0000000000000286
R15: 0000000000023000
Feb 5 00:57:39 VM-SUSE kernel: FS: 0000000000000000(0000)
GS:ffff81003fea1ac0(0000) knlGS:0000000000000000
Feb 5 00:57:39 VM-SUSE kernel: CS: 0010 DS: 0018 ES: 0018 CR0:
000000008005003b
Feb 5 00:57:39 VM-SUSE kernel: CR2: 00002afccd5f0795 CR3: 000000003ceaf000
CR4: 00000000000006e0
Feb 5 00:57:39 VM-SUSE kernel: Process read_helper_1 (pid: 3239, threadinfo
ffff810036d18000, task ffff8100017757a0)
Feb 5 00:57:39 VM-SUSE kernel: Stack: 0000000000000246 ffff81003aca7540
0000000000004000 ffff8100364f7400
Feb 5 00:57:39 VM-SUSE kernel: 0000000000000009 ffff8100364f74c8
ffff8100364f7528 ffffffff882b5b0b
Feb 5 00:57:39 VM-SUSE kernel: 0000000000000001 0000002700000020
0000000000626473 ffff8100017757a0
Feb 5 00:57:39 VM-SUSE kernel: Call Trace:
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff882b5b0b>]
:mymodule:helper_get_info+0x517/0x755
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff80242c84>]
keventd_create_kthread+0x0/0x61
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff882b623e>]
:mymodule:thread_func_th1+0x107/0x121
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff8024307c>]
autoremove_wake_function+0x0/0x2e
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff882b6137>]
:mymodule:thread_func_th1+0x0/0x121
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff80242f3b>] kthread+0xec/0x121
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff8020a55c>] child_rip+0xa/0x12
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff80242c84>]
keventd_create_kthread+0x0/0x61
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff80242e4f>] kthread+0x0/0x121
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff8020a552>] child_rip+0x0/0x12
Feb 5 00:57:39 VM-SUSE kernel:
Feb 5 00:57:39 VM-SUSE kernel:
Feb 5 00:57:39 VM-SUSE kernel: Code: 0f 0b 68 fd 46 40 80 c2 53 02 4c 8b 6a
28 65 8b 04 25 2c 00
Feb 5 00:57:39 VM-SUSE kernel: RIP [<ffffffff8027d4a6>] kfree+0x5e/0x1bd
Feb 5 00:57:39 VM-SUSE kernel: RSP <ffff810036d19dd0>
Feb 5 00:57:39 VM-SUSE kernel: <3>BUG: sleeping function called from
invalid context at kernel/rwsem.c:20
Feb 5 00:57:39 VM-SUSE kernel: in_atomic():0, irqs_disabled():1
Feb 5 00:57:39 VM-SUSE kernel:
Feb 5 00:57:39 VM-SUSE kernel: Call Trace:
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff80245819>] down_read+0x15/0x24
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff8023d099>]
blocking_notifier_call_chain+0x13/0x36
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff802331d0>] do_exit+0x20/0x8f4
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff8033f84e>]
do_unblank_screen+0x2c/0x139
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff8020ae9a>]
kernel_math_error+0x0/0x90
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff8020b441>]
do_invalid_op+0xad/0xb7
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff8027d4a6>] kfree+0x5e/0x1bd
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff802f1de3>] vsnprintf+0x314/0x595
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff8020a3a1>] error_exit+0x0/0x84
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff8027d4a6>] kfree+0x5e/0x1bd
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff882b5b0b>]
:mymodule:helper_get_info+0x517/0x755
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff80242c84>]
keventd_create_kthread+0x0/0x61
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff882b623e>]
:mymodule:thread_func_th1+0x107/0x121
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff8024307c>]
autoremove_wake_function+0x0/0x2e
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff882b6137>]
:mymodule:thread_func_th1+0x0/0x121
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff80242f3b>] kthread+0xec/0x121
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff8020a55c>] child_rip+0xa/0x12
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff80242c84>]
keventd_create_kthread+0x0/0x61
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff80242e4f>] kthread+0x0/0x121
Feb 5 00:57:39 VM-SUSE kernel: [<ffffffff8020a552>] child_rip+0x0/0x12
Feb 5 00:57:39 VM-SUSE kernel:
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Kernel BUG at mm/slab.c:595
2007-02-04 14:55 Kernel BUG at mm/slab.c:595 Yu-Chen Wu
@ 2007-02-04 15:47 ` Arjan van de Ven
2007-02-05 12:14 ` Joerg Roedel
1 sibling, 0 replies; 3+ messages in thread
From: Arjan van de Ven @ 2007-02-04 15:47 UTC (permalink / raw)
To: Yu-Chen Wu; +Cc: linux-kernel
On Sun, 2007-02-04 at 22:55 +0800, Yu-Chen Wu wrote:
> Hi all,
>
> I am developing my module, but meet a bug. Is the bug created by
> me??
very likely; your module is all over the backtrace...
if you post the module source somewhere I and others will take a look to
see if there's anything obviously wrong with it...
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Kernel BUG at mm/slab.c:595
2007-02-04 14:55 Kernel BUG at mm/slab.c:595 Yu-Chen Wu
2007-02-04 15:47 ` Arjan van de Ven
@ 2007-02-05 12:14 ` Joerg Roedel
1 sibling, 0 replies; 3+ messages in thread
From: Joerg Roedel @ 2007-02-05 12:14 UTC (permalink / raw)
To: Yu-Chen Wu; +Cc: linux-kernel
On Sun, Feb 04, 2007 at 10:55:19PM +0800, Yu-Chen Wu wrote:
> Hi all,
>
> I am developing my module, but meet a bug. Is the bug created by
> me??
>
> Kernel:2.6.18 on SUSE10.1 + Intel DualCore
>
Have you tried that with a vanilla kernel? There is a Debian
bugreport[1] with about a similar issue. But I didn't care about it yet
because it was never reported for vanilla kernels. Seeing your module
source will help anyway.
Joerg
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406477
--
Joerg Roedel
Operating System Research Center
AMD Saxony LLC & Co. KG
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-02-05 12:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-02-04 14:55 Kernel BUG at mm/slab.c:595 Yu-Chen Wu
2007-02-04 15:47 ` Arjan van de Ven
2007-02-05 12:14 ` Joerg Roedel
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).