From: Udo van den Heuvel <udovdh@xs4all.nl>
To: RT <linux-rt-users@vger.kernel.org>
Subject: Re: 2.6.33.1-rt11 BUG: sleeping function called from invalid context at kernel/rtmutex.c:684
Date: Sun, 04 Apr 2010 11:17:56 +0200 [thread overview]
Message-ID: <4BB85944.8000304@xs4all.nl> (raw)
In-Reply-To: <4BB8587F.40307@xs4all.nl>
Hello,
On 2010-04-04 11:14, Udo van den Heuvel wrote:
> I see a load of these after booting into 2.6.33.1-rt11:
>
> BUG: sleeping function called from invalid context at kernel/rtmutex.c:684
> pcnt: 1 0 in_atomic(): 1, irqs_disabled(): 0, pid: 1507, name: md1_raid5
> Pid: 1507, comm: md1_raid5 Not tainted 2.6.33.1-rt11 #1
> Call Trace:
> [<ffffffff8138fb8c>] ? rt_spin_lock+0x2c/0x70
> [<ffffffff812becc4>] ? __raid_run_ops+0x304/0xc60
> [<ffffffff812c0ccd>] ? handle_stripe+0x6bd/0x1a70
> [<ffffffff8104b460>] ? mod_timer+0x150/0x200
> [<ffffffff812c23f6>] ? raid5d+0x376/0x4f0
> [<ffffffff8138e5bd>] ? schedule_timeout+0x22d/0x2b0
> [<ffffffff8138fb8c>] ? rt_spin_lock+0x2c/0x70
> [<ffffffff812cd0f3>] ? md_thread+0x53/0x120
> [<ffffffff810573a0>] ? autoremove_wake_function+0x0/0x30
> [<ffffffff812cd0a0>] ? md_thread+0x0/0x120
> [<ffffffff81057016>] ? kthread+0x96/0xa0
> [<ffffffff81037908>] ? finish_task_switch+0x58/0xd0
> [<ffffffff810032d4>] ? kernel_thread_helper+0x4/0x10
> [<ffffffff81056f80>] ? kthread+0x0/0xa0
> [<ffffffff810032d0>] ? kernel_thread_helper+0x0/0x10
>
I also see this one happing in 2.6.33.1-rt1 in between a number of the
BUGs I mentioned up on this page:
#
BUG: scheduling while atomic: md1_raid5/0x00000001/1507, CPU#2
#
Modules linked in: radeon ttm drm_kms_helper drm fb i2c_algo_bit
cfbcopyarea cfbimgblt cfbfillrect nfsd nfs_acl exportfs eeprom it87
hwmon_vid lockd sunrpc cpufreq_ondemand powernow_k8 ipt_REJECT
nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables
nf_conntrack_netbios_ns ip6t_REJECT xt_tcpudp nf_conntrack_ipv6 xt_state
nf_conntrack ip6table_filter ip6_tables x_tables ipv6 microcode
binfmt_misc ext4 jbd2 crc16 snd_hda_codec_realtek snd_ice1712
snd_ice17xx_ak4xxx snd_ak4xxx_adda snd_cs8427 snd_ac97_codec ac97_bus
snd_i2c snd_mpu401_uart snd_hda_intel snd_hda_codec snd_seq snd_rawmidi
snd_pcm snd_seq_device snd_timer i2c_nforce2 ppdev snd ehci_hcd
parport_pc ohci1394 ohci_hcd parport ieee1394 sg snd_page_alloc evdev
k10temp button floppy [last unloaded: scsi_wait_scan]
#
Pid: 1507, comm: md1_raid5 Not tainted 2.6.33.1-rt11 #1
#
Call Trace:
#
[<ffffffff8138da5a>] ? __schedule+0x38a/0x920
#
[<ffffffff8138fb8c>] ? rt_spin_lock+0x2c/0x70
#
[<ffffffff8138fe30>] ? _raw_spin_unlock+0x10/0x40
#
[<ffffffff8106a54f>] ? task_blocks_on_rt_mutex+0x17f/0x1e0
#
[<ffffffff8138e110>] ? schedule+0x10/0x20
#
[<ffffffff8138f22f>] ? rt_spin_lock_slowlock+0x1ef/0x2c0
#
[<ffffffff812bcf38>] ? release_stripe+0x28/0x50
#
[<ffffffff81196d4e>] ? async_xor+0x13e/0x170
#
[<ffffffff812bee4a>] ? __raid_run_ops+0x48a/0xc60
#
[<ffffffff812bd140>] ? ops_complete_reconstruct+0x0/0xa0
#
[<ffffffff812c0ccd>] ? handle_stripe+0x6bd/0x1a70
#
[<ffffffff812c23f6>] ? raid5d+0x376/0x4f0
#
[<ffffffff812cd0f3>] ? md_thread+0x53/0x120
#
[<ffffffff810573a0>] ? autoremove_wake_function+0x0/0x30
#
[<ffffffff812cd0a0>] ? md_thread+0x0/0x120
#
[<ffffffff81057016>] ? kthread+0x96/0xa0
#
[<ffffffff81037908>] ? finish_task_switch+0x58/0xd0
#
[<ffffffff810032d4>] ? kernel_thread_helper+0x4/0x10
#
[<ffffffff81056f80>] ? kthread+0x0/0xa0
#
[<ffffffff810032d0>] ? kernel_thread_helper+0x0/0x10
Udo
next prev parent reply other threads:[~2010-04-04 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 9:14 2.6.33.1-rt11 BUG: sleeping function called from invalid context at kernel/rtmutex.c:684 Udo van den Heuvel
2010-04-04 9:17 ` Udo van den Heuvel [this message]
2010-04-06 8:07 ` Thomas Gleixner
2010-04-06 13:34 ` Udo van den Heuvel
2010-04-06 13:43 ` Luis Claudio R. Goncalves
2010-04-06 14:01 ` Udo van den Heuvel
2010-04-06 14:39 ` Thomas Gleixner
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=4BB85944.8000304@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=linux-rt-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.