Re: 2.6.22-rc3 : "BUG: scheduling while atomic: swapper/0x00000100/0"

public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed

From: Boaz Harrosh <bharrosh@panasas.com>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>,
	"Benjamin Pineau" <benjamin_pineau@zouh.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.22-rc3 : "BUG: scheduling while atomic: swapper/0x00000100/0"
Date: Mon, 04 Jun 2007 18:21:10 +0300	[thread overview]
Message-ID: <46642DE6.4010705@panasas.com> (raw)
In-Reply-To: <20070604144101.GB3363@atjola.homenet>

[-- 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:

     prev parent reply	other threads:[~2007-06-04 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

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=46642DE6.4010705@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=B.Steinbrink@gmx.de \
    --cc=benjamin_pineau@zouh.org \
    --cc=linux-kernel@vger.kernel.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