* 2.6.22-rc3 : "BUG: scheduling while atomic: swapper/0x00000100/0"
@ 2007-06-04 13:55 Benjamin Pineau
2007-06-04 14:39 ` Björn Steinbrink
0 siblings, 1 reply; 4+ messages in thread
From: Benjamin Pineau @ 2007-06-04 13:55 UTC (permalink / raw)
To: linux-kernel
Hi,
The stock 2.6.22-rc3 (with no alien modules or patchs) on my i386 desktops
fired this message in loop like a mad (thousands of times/second) until
reboot, for no evident reason (I mean, I don't know what I did to get this,
from an end-user perspective : I was just editing text on vim and surfing
the web with firefox).
The same kernel worked for several days without exposing surch a problem
and this never occured with the olders kernels I used (2.6.17, 2.6.21).
Beside the log presure, the only symptom I noted is that reboot didn't work:
it killed X and probably most userland, but got silently stuck on the console,
without actually restarting the machine. Then, on the console, everytime I
typed a key, 2 new "BUG: scheduling ..." lines appeared. Typing ctrl-alt-del
finaly forced it to physically reboot.
I've got more details in dmesg. Sample (full dmesg plus more
at http://oshima.zouh.org/~ben/2.6.23-rc3_bug_details.txt):
[333259.145874] =======================
[333259.145894] BUG: scheduling while atomic: swapper/0x00000100/0
[333259.145906] [<c03f254c>] schedule+0x4dc/0x860
[333259.145915] [<c0141c76>] getnstimeofday+0x36/0xd0
[333259.145932] [<c013fcc6>] ktime_get_ts+0x16/0x50
[333259.145941] [<c013a358>] rcu_pending+0x38/0x50
[333259.145949] [<c013a3a2>] rcu_needs_cpu+0x32/0x40
[333259.145964] [<c01022d0>] mwait_idle+0x0/0x20
[333259.145974] [<c010245c>] cpu_idle+0x9c/0xe0
[333259.145985] [<c0558a7f>] start_kernel+0x31f/0x3b0
[333259.145994] [<c05581f0>] unknown_bootoption+0x0/0x260
[333259.146007] =======================
[334129.061709] BUG: scheduling while atomic: swapper/0x00000100/0
[334129.061735] [<c03f254c>] schedule+0x4dc/0x860
[334129.061760] [<c013f96b>] enqueue_hrtimer+0x6b/0x110
[334129.061773] [<c0140245>] hrtimer_start+0xc5/0x130
[334129.061785] [<c01459e1>] tick_nohz_restart_sched_tick+0xf1/0x140
[334129.061796] [<c01022d0>] mwait_idle+0x0/0x20
[334129.061806] [<c010245c>] cpu_idle+0x9c/0xe0
[334129.061817] [<c0558a7f>] start_kernel+0x31f/0x3b0
[334129.061827] [<c05581f0>] unknown_bootoption+0x0/0x260
[333259.148510] =======================
Since I see the word "time" there : note I have NO_HZ, HIGH_RES_TIMERS,
TIMER_STATS and HPET (but according to /proc/timer_list, hpet is not active),
but no IRQ_BALANCE.
And for the boot options (?), /proc/cmdline is :
root=UUID=349f275c-a633-4d1d-8ab7-b3a75d67dc51 ro locale=fr_FR
lspci -vv, lspci -vn, /proc/config.gz, /proc/timer_list, lsmod,
/proc/interrupts, /proc/vmstat, ps auxf, and dmesg (with and
without the bug's logs) outputs at
http://oshima.zouh.org/~ben/2.6.23-rc3_bug_details.txt
Thank you.
Benjamin Pineau
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 2.6.22-rc3 : "BUG: scheduling while atomic: swapper/0x00000100/0"
2007-06-04 13:55 2.6.22-rc3 : "BUG: scheduling while atomic: swapper/0x00000100/0" Benjamin Pineau
@ 2007-06-04 14:39 ` Björn Steinbrink
2007-06-04 14:41 ` Björn Steinbrink
0 siblings, 1 reply; 4+ messages in thread
From: Björn Steinbrink @ 2007-06-04 14:39 UTC (permalink / raw)
To: Benjamin Pineau; +Cc: linux-kernel
On 2007.06.04 15:55:14 +0200, Benjamin Pineau wrote:
> Hi,
> The stock 2.6.22-rc3 (with no alien modules or patchs) on my i386 desktops
> fired this message in loop like a mad (thousands of times/second) until
> reboot, for no evident reason (I mean, I don't know what I did to get this,
> >from an end-user perspective : I was just editing text on vim and surfing
> the web with firefox).
>
> The same kernel worked for several days without exposing surch a problem
> and this never occured with the olders kernels I used (2.6.17, 2.6.21).
>
> Beside the log presure, the only symptom I noted is that reboot didn't work:
> it killed X and probably most userland, but got silently stuck on the console,
> without actually restarting the machine. Then, on the console, everytime I
> typed a key, 2 new "BUG: scheduling ..." lines appeared. Typing ctrl-alt-del
> finaly forced it to physically reboot.
>
> I've got more details in dmesg. Sample (full dmesg plus more
> at http://oshima.zouh.org/~ben/2.6.23-rc3_bug_details.txt):
>
> [333259.145874] =======================
> [333259.145894] BUG: scheduling while atomic: swapper/0x00000100/0
> [333259.145906] [<c03f254c>] schedule+0x4dc/0x860
> [333259.145915] [<c0141c76>] getnstimeofday+0x36/0xd0
> [333259.145932] [<c013fcc6>] ktime_get_ts+0x16/0x50
> [333259.145941] [<c013a358>] rcu_pending+0x38/0x50
> [333259.145949] [<c013a3a2>] rcu_needs_cpu+0x32/0x40
> [333259.145964] [<c01022d0>] mwait_idle+0x0/0x20
> [333259.145974] [<c010245c>] cpu_idle+0x9c/0xe0
> [333259.145985] [<c0558a7f>] start_kernel+0x31f/0x3b0
> [333259.145994] [<c05581f0>] unknown_bootoption+0x0/0x260
> [333259.146007] =======================
> [334129.061709] BUG: scheduling while atomic: swapper/0x00000100/0
> [334129.061735] [<c03f254c>] schedule+0x4dc/0x860
> [334129.061760] [<c013f96b>] enqueue_hrtimer+0x6b/0x110
> [334129.061773] [<c0140245>] hrtimer_start+0xc5/0x130
> [334129.061785] [<c01459e1>] tick_nohz_restart_sched_tick+0xf1/0x140
> [334129.061796] [<c01022d0>] mwait_idle+0x0/0x20
> [334129.061806] [<c010245c>] cpu_idle+0x9c/0xe0
> [334129.061817] [<c0558a7f>] start_kernel+0x31f/0x3b0
> [334129.061827] [<c05581f0>] unknown_bootoption+0x0/0x260
> [333259.148510] =======================
>
> Since I see the word "time" there : note I have NO_HZ, HIGH_RES_TIMERS,
> TIMER_STATS and HPET (but according to /proc/timer_list, hpet is not active),
> but no IRQ_BALANCE.
> And for the boot options (?), /proc/cmdline is :
> root=UUID=349f275c-a633-4d1d-8ab7-b3a75d67dc51 ro locale=fr_FR
>
> lspci -vv, lspci -vn, /proc/config.gz, /proc/timer_list, lsmod,
> /proc/interrupts, /proc/vmstat, ps auxf, and dmesg (with and
> without the bug's logs) outputs at
> http://oshima.zouh.org/~ben/2.6.23-rc3_bug_details.txt
To save somebody else from guessing, that's HIRoshima, i.e. the correct
URL is http://hiroshima.zouh.org/~ben/2.6.23-rc3_bug_details.txt
;-)
Björn
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 2.6.22-rc3 : "BUG: scheduling while atomic: swapper/0x00000100/0"
2007-06-04 14:39 ` Björn Steinbrink
@ 2007-06-04 14:41 ` Björn Steinbrink
2007-06-04 15:21 ` Boaz Harrosh
0 siblings, 1 reply; 4+ messages in thread
From: Björn Steinbrink @ 2007-06-04 14:41 UTC (permalink / raw)
To: Benjamin Pineau, linux-kernel
On 2007.06.04 16:39:25 +0200, Björn Steinbrink wrote:
> On 2007.06.04 15:55:14 +0200, Benjamin Pineau wrote:
> > lspci -vv, lspci -vn, /proc/config.gz, /proc/timer_list, lsmod,
> > /proc/interrupts, /proc/vmstat, ps auxf, and dmesg (with and
> > without the bug's logs) outputs at
> > http://oshima.zouh.org/~ben/2.6.23-rc3_bug_details.txt
>
> To save somebody else from guessing, that's HIRoshima, i.e. the correct
> URL is http://hiroshima.zouh.org/~ben/2.6.23-rc3_bug_details.txt
Hmpf, about a second later the original URL also started to work...
Confused,
Björn
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 2.6.22-rc3 : "BUG: scheduling while atomic: swapper/0x00000100/0"
2007-06-04 14:41 ` Björn Steinbrink
@ 2007-06-04 15:21 ` Boaz Harrosh
0 siblings, 0 replies; 4+ messages in thread
From: Boaz Harrosh @ 2007-06-04 15:21 UTC (permalink / raw)
To: Björn Steinbrink, Benjamin Pineau, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]
Björn Steinbrink wrote:
> On 2007.06.04 16:39:25 +0200, Björn Steinbrink wrote:
>> On 2007.06.04 15:55:14 +0200, Benjamin Pineau wrote:
>>> lspci -vv, lspci -vn, /proc/config.gz, /proc/timer_list, lsmod,
>>> /proc/interrupts, /proc/vmstat, ps auxf, and dmesg (with and
>>> without the bug's logs) outputs at
>>> http://oshima.zouh.org/~ben/2.6.23-rc3_bug_details.txt
>> To save somebody else from guessing, that's HIRoshima, i.e. the correct
>> URL is http://hiroshima.zouh.org/~ben/2.6.23-rc3_bug_details.txt
>
> Hmpf, about a second later the original URL also started to work...
>
> Confused,
> Björn
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
I get something reproducible when using a setup that worked up until 2.6.22-rc2.
I did not report it because the authors of the projects involved do not like that I
use the particular setup that I do.
The setup is using iSCSI Initiator from kernel with iscsi enterprise Target (IET)
which is an out-of-tree kernel module. Both run on the same machine.
(The iet project do not like that I run on the same machine with the Initiator, and
they are probably right, just that it worked perfectly well up to 2.6.21, The first
2.6.22 patches broke the iet over files, and now I have above brakege also when
using iet-over-block-io)
Do I need to bisect this over my setup?
Some dmesg prints:
[-- Attachment #2: dmsg-scheduling-while-atomic.txt --]
[-- Type: text/plain, Size: 11366 bytes --]
Jun 4 15:41:12 bh-testlin2 kernel: BUG: sleeping function called from invalid context at include2/asm/semaphore.h:105
Jun 4 15:41:12 bh-testlin2 kernel: in_atomic():1, irqs_disabled():0
Jun 4 15:41:12 bh-testlin2 kernel:
Jun 4 15:41:12 bh-testlin2 kernel: Call Trace:
Jun 4 15:41:12 bh-testlin2 kernel: [<ffffffff802216e1>] __might_sleep+0xb5/0xb7
Jun 4 15:41:12 bh-testlin2 kernel: [<ffffffff881d3943>] :iscsi_trgt:target_lock+0x4f/0x68
Jun 4 15:41:12 bh-testlin2 kernel: [<ffffffff881d1333>] :iscsi_trgt:istd+0xa5/0xc3f
Jun 4 15:41:12 bh-testlin2 kernel: [<ffffffff80223e04>] __wake_up_common+0x42/0x61
Jun 4 15:41:12 bh-testlin2 kernel: [<ffffffff881d128e>] :iscsi_trgt:istd+0x0/0xc3f
Jun 4 15:41:12 bh-testlin2 kernel: [<ffffffff80239f4c>] kthread+0x3d/0x63
Jun 4 15:41:12 bh-testlin2 kernel: [<ffffffff8020a0b8>] child_rip+0xa/0x12
Jun 4 15:41:12 bh-testlin2 kernel: [<ffffffff80239f0f>] kthread+0x0/0x63
Jun 4 15:41:12 bh-testlin2 kernel: [<ffffffff8020a0ae>] child_rip+0x0/0x12
Jun 4 15:41:12 bh-testlin2 kernel:
Jun 4 15:41:12 bh-testlin2 kernel: BUG: scheduling while atomic: istd1/0x00000018/3561
Jun 4 15:41:12 bh-testlin2 kernel:
Jun 4 15:41:12 bh-testlin2 kernel: Call Trace:
Jun 4 15:41:13 bh-testlin2 kernel: [<ffffffff803e34ef>] __sched_text_start+0x5f/0x7ce
Jun 4 15:41:13 bh-testlin2 kernel: [<ffffffff80223e58>] __wake_up+0x35/0x4b
Jun 4 15:41:13 bh-testlin2 kernel: [<ffffffff8037aa78>] release_sock+0x10/0xae
Jun 4 15:41:13 bh-testlin2 kernel: [<ffffffff803e57b0>] _spin_unlock_bh+0x6/0x11
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803a7187>] tcp_ioctl+0x131/0x13a
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803a7190>] tcp_sendpage+0x0/0x66b
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff881d12fc>] :iscsi_trgt:istd+0x6e/0xc3f
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80223e04>] __wake_up_common+0x42/0x61
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff881d128e>] :iscsi_trgt:istd+0x0/0xc3f
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80239f4c>] kthread+0x3d/0x63
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff8020a0b8>] child_rip+0xa/0x12
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80239f0f>] kthread+0x0/0x63
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff8020a0ae>] child_rip+0x0/0x12
Jun 4 15:41:14 bh-testlin2 kernel:
Jun 4 15:41:14 bh-testlin2 kernel: >] __sched_text_start+0x5f/0x7ce
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff881ceaae>] :iscsi_trgt:iscsi_cmnd_remove+0x157/0x177
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803e57b0>] _spin_unlock_bh+0x6/0x11
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803a7190>] tcp_sendpage+0x0/0x66b
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff881d12fc>] :iscsi_trgt:istd+0x6e/0xc3f
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80223e04>] __wake_up_common+0x42/0x61
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff881d128e>] :iscsi_trgt:istd+0x0/0xc3f
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80239f4c>] kthread+0x3d/0x63
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff8020a0b8>] child_rip+0xa/0x12
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80239f0f>] kthread+0x0/0x63
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff8020a0ae>] child_rip+0x0/0x12
Jun 4 15:41:14 bh-testlin2 kernel: BUG: scheduling while atomic: swapper/0x00000083/0
Jun 4 15:41:14 bh-testlin2 kernel:
Jun 4 15:41:14 bh-testlin2 kernel: Call Trace:
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803e34ef>] __sched_text_start+0x5f/0x7ce
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff802079ce>] default_idle+0x0/0x3d
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80207b81>] cpu_idle+0x6e/0x70
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80500772>] start_kernel+0x29c/0x2a5
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80500151>] _sinittext+0x151/0x158
Jun 4 15:41:14 bh-testlin2 kernel:
Jun 4 15:41:14 bh-testlin2 kernel: BUG: scheduling while atomic: istd1/0x00000100/3561
Jun 4 15:41:14 bh-testlin2 kernel:
Jun 4 15:41:14 bh-testlin2 kernel: Call Trace:
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803e34ef>] __sched_text_start+0x5f/0x7ce
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80223e58>] __wake_up+0x35/0x4b
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff8037aa78>] release_sock+0x10/0xae
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803e57b0>] _spin_unlock_bh+0x6/0x11
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803a7187>] tcp_ioctl+0x131/0x13a
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803a7190>] tcp_sendpage+0x0/0x66b
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff881d12fc>] :iscsi_trgt:istd+0x6e/0xc3f
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80223e04>] __wake_up_common+0x42/0x61
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff881d128e>] :iscsi_trgt:istd+0x0/0xc3f
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80239f4c>] kthread+0x3d/0x63
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff8020a0b8>] child_rip+0xa/0x12
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80239f0f>] kthread+0x0/0x63
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff8020a0ae>] child_rip+0x0/0x12
Jun 4 15:41:14 bh-testlin2 kernel:
Jun 4 15:41:14 bh-testlin2 kernel: BUG: scheduling while atomic: swapper/0x00000083/0
Jun 4 15:41:14 bh-testlin2 kernel:
Jun 4 15:41:14 bh-testlin2 kernel: Call Trace:
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803e34ef>] __sched_text_start+0x5f/0x7ce
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff802079ce>] default_idle+0x0/0x3d
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80207b81>] cpu_idle+0x6e/0x70
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80500772>] start_kernel+0x29c/0x2a5
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80500151>] _sinittext+0x151/0x158
Jun 4 15:41:14 bh-testlin2 kernel:
Jun 4 15:41:14 bh-testlin2 kernel: BUG: scheduling while atomic: istd1/0x00000100/3561
Jun 4 15:41:14 bh-testlin2 kernel:
Jun 4 15:41:14 bh-testlin2 kernel: Call Trace:
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803e34ef>] __sched_text_start+0x5f/0x7ce
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff881ceaae>] :iscsi_trgt:iscsi_cmnd_remove+0x157/0x177
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803e57b0>] _spin_unlock_bh+0x6/0x11
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803a7190>] tcp_sendpage+0x0/0x66b
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff881d12fc>] :iscsi_trgt:istd+0x6e/0xc3f
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80223e04>] __wake_up_common+0x42/0x61
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff881d128e>] :iscsi_trgt:istd+0x0/0xc3f
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80239f4c>] kthread+0x3d/0x63
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff8020a0b8>] child_rip+0xa/0x12
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80239f0f>] kthread+0x0/0x63
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff8020a0ae>] child_rip+0x0/0x12
Jun 4 15:41:14 bh-testlin2 kernel:
Jun 4 15:41:14 bh-testlin2 kernel: BUG: scheduling while atomic: swapper/0x00000084/0
Jun 4 15:41:14 bh-testlin2 kernel:
Jun 4 15:41:14 bh-testlin2 kernel: Call Trace:
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803e34ef>] __sched_text_start+0x5f/0x7ce
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff802079ce>] default_idle+0x0/0x3d
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80207b81>] cpu_idle+0x6e/0x70
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80500772>] start_kernel+0x29c/0x2a5
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80500151>] _sinittext+0x151/0x158
Jun 4 15:41:14 bh-testlin2 kernel:
Jun 4 15:41:14 bh-testlin2 kernel: BUG: scheduling while atomic: istd1/0x00000100/3561
Jun 4 15:41:14 bh-testlin2 kernel:
Jun 4 15:41:14 bh-testlin2 kernel: Call Trace:
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803e34ef>] __sched_text_start+0x5f/0x7ce
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff80223e58>] __wake_up+0x35/0x4b
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff8037aa78>] release_sock+0x10/0xae
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803e57b0>] _spin_unlock_bh+0x6/0x11
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803a7187>] tcp_ioctl+0x131/0x13a
Jun 4 15:41:14 bh-testlin2 kernel: [<ffffffff803a7190>] tcp_sendpage+0x0/0x66b
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff881d12fc>] :iscsi_trgt:istd+0x6e/0xc3f
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff80223e04>] __wake_up_common+0x42/0x61
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff881d128e>] :iscsi_trgt:istd+0x0/0xc3f
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff80239f4c>] kthread+0x3d/0x63
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff8020a0b8>] child_rip+0xa/0x12
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff80239f0f>] kthread+0x0/0x63
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff8020a0ae>] child_rip+0x0/0x12
Jun 4 15:41:15 bh-testlin2 kernel:
Jun 4 15:41:15 bh-testlin2 kernel: BUG: scheduling while atomic: swapper/0x00000084/0
Jun 4 15:41:15 bh-testlin2 kernel:
Jun 4 15:41:15 bh-testlin2 kernel: Call Trace:
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff803e34ef>] __sched_text_start+0x5f/0x7ce
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff802079ce>] default_idle+0x0/0x3d
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff80207b81>] cpu_idle+0x6e/0x70
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff80500772>] start_kernel+0x29c/0x2a5
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff80500151>] _sinittext+0x151/0x158
Jun 4 15:41:15 bh-testlin2 kernel:
Jun 4 15:41:15 bh-testlin2 kernel: BUG: scheduling while atomic: istd1/0x00000100/3561
Jun 4 15:41:15 bh-testlin2 kernel:
Jun 4 15:41:15 bh-testlin2 kernel: Call Trace:
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff803e34ef>] __sched_text_start+0x5f/0x7ce
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff881ceaae>] :iscsi_trgt:iscsi_cmnd_remove+0x157/0x177
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff803e57b0>] _spin_unlock_bh+0x6/0x11
Jun 4 15:41:15 bh-testlin2 kernel: /0x00000100/3561
Jun 4 15:41:15 bh-testlin2 kernel:
Jun 4 15:41:15 bh-testlin2 kernel: Call Trace:
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff803e34ef>] __sched_text_start+0x5f/0x7ce
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff881ceaae>] :iscsi_trgt:iscsi_cmnd_remove+0x157/0x177
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff803e57b0>] _spin_unlock_bh+0x6/0x11
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff881d12fc>] :iscsi_trgt:istd+0x6e/0xc3f
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff80223e04>] __wake_up_common+0x42/0x61
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff881d128e>] :iscsi_trgt:istd+0x0/0xc3f
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff80239f4c>] kthread+0x3d/0x63
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff8020a0b8>] child_rip+0xa/0x12
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff80239f0f>] kthread+0x0/0x63
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff8020a0ae>] child_rip+0x0/0x12
Jun 4 15:41:15 bh-testlin2 kernel:
Jun 4 15:41:15 bh-testlin2 kernel: BUG: scheduling while atomic: swapper/0x000000b5/0
Jun 4 15:41:15 bh-testlin2 kernel:
Jun 4 15:41:15 bh-testlin2 kernel: Call Trace:
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff803e34ef>] __sched_text_start+0x5f/0x7ce
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff802079ce>] default_idle+0x0/0x3d
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff80207b81>] cpu_idle+0x6e/0x70
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff80500772>] start_kernel+0x29c/0x2a5
Jun 4 15:41:15 bh-testlin2 kernel: [<ffffffff80500151>] _sinittext+0x151/0x158
Jun 4 15:41:15 bh-testlin2 kernel:
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-06-04 15:21 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-06-04 13:55 2.6.22-rc3 : "BUG: scheduling while atomic: swapper/0x00000100/0" Benjamin Pineau
2007-06-04 14:39 ` Björn Steinbrink
2007-06-04 14:41 ` Björn Steinbrink
2007-06-04 15:21 ` Boaz Harrosh
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox