BUG: scheduling while atomic: hald-addon-stor/

Bug #77866 reported by Carlos Martín Nieto
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
High
Ben Collins

Bug Description

Binary package hint: linux-image-2.6.20-3-generic

I get this trace once in a while:

[ 6684.539355] BUG: scheduling while atomic: hald-addon-stor/0x20000000/4773
[ 6684.539360]
[ 6684.539361] Call Trace:
[ 6684.539379] [<ffffffff802653ed>] __sched_text_start+0x5d/0x821
[ 6684.539389] [<ffffffff8022f7d3>] __wake_up+0x43/0x70
[ 6684.539407] [<ffffffff8028e13c>] __cond_resched+0x1c/0x50
[ 6684.539412] [<ffffffff80265cd9>] cond_resched+0x29/0x40
[ 6684.539417] [<ffffffff80267d16>] __reacquire_kernel_lock+0x26/0x47
[ 6684.539424] [<ffffffff80265c5e>] thread_return+0xad/0xff
[ 6684.539452] [<ffffffff88143780>] :scsi_mod:scsi_done+0x0/0x20
[ 6684.539466] [<ffffffff8028e13c>] __cond_resched+0x1c/0x50
[ 6684.539470] [<ffffffff80265cd9>] cond_resched+0x29/0x40
[ 6684.539475] [<ffffffff80265d27>] wait_for_completion+0x17/0xf0
[ 6684.539484] [<ffffffff80334818>] blk_execute_rq_nowait+0x88/0xb0
[ 6684.539491] [<ffffffff803348ff>] blk_execute_rq+0xbf/0x110
[ 6684.539534] [<ffffffff88149c1d>] :scsi_mod:scsi_execute+0xed/0x120
[ 6684.539556] [<ffffffff88149cd8>] :scsi_mod:scsi_execute_req+0x88/0x110
[ 6684.539573] [<ffffffff881c823d>] :sr_mod:sr_media_change+0x10d/0x260
[ 6684.539590] [<ffffffff881bd093>] :cdrom:media_changed+0x53/0xa0
[ 6684.539598] [<ffffffff802ed987>] check_disk_change+0x27/0x90
[ 6684.539608] [<ffffffff881c1cfe>] :cdrom:cdrom_open+0x9de/0xa60
[ 6684.539615] [<ffffffff8020ceaf>] dput+0x2f/0x170
[ 6684.539622] [<ffffffff80209d1b>] __link_path_walk+0xc6b/0xdc0
[ 6684.539638] [<ffffffff8022e164>] mntput_no_expire+0x24/0xb0
[ 6684.539644] [<ffffffff8020e740>] link_path_walk+0xd0/0xf0
[ 6684.539651] [<ffffffff8025e1df>] hrtimer_nanosleep+0x6f/0x150
[ 6684.539663] [<ffffffff8025b292>] kobject_get+0x12/0x20
[ 6684.539669] [<ffffffff80336a38>] get_disk+0x48/0x80
[ 6684.539675] [<ffffffff8025ea5c>] exact_lock+0xc/0x20
[ 6684.539688] [<ffffffff881c84cb>] :sr_mod:sr_block_open+0xab/0xd0
[ 6684.539692] [<ffffffff802ee6a0>] blkdev_open+0x0/0x80
[ 6684.539698] [<ffffffff802ee6a0>] blkdev_open+0x0/0x80
[ 6684.539702] [<ffffffff802ee12b>] do_open+0xbb/0x300
[ 6684.539707] [<ffffffff80211d90>] may_open+0x70/0x260
[ 6684.539714] [<ffffffff802ee6a0>] blkdev_open+0x0/0x80
[ 6684.539719] [<ffffffff802ee6dc>] blkdev_open+0x3c/0x80
[ 6684.539727] [<ffffffff8021f1cc>] __dentry_open+0xfc/0x1f0
[ 6684.539737] [<ffffffff80228b1d>] do_filp_open+0x2d/0x40
[ 6684.539743] [<ffffffff8025e1df>] hrtimer_nanosleep+0x6f/0x150
[ 6684.539763] [<ffffffff8021a02a>] do_sys_open+0x5a/0x100
[ 6684.539772] [<ffffffff8026111e>] system_call+0x7e/0x83
[ 6684.539787]

Revision history for this message
Nafallo Bjälevik (nafallo) wrote :

Same here.

Changed in linux-source-2.6.20:
status: Unconfirmed → Confirmed
Revision history for this message
Ben Collins (ben-collins) wrote :

This is a known upstream bug. Patch is available, just waiting for it to trickle down into the mainline kernel.

Please keep checking newer Ubuntu kernel versions and respond with whether it fixes the problem or not.

Thanks

Changed in linux-source-2.6.20:
assignee: nobody → ben-collins
importance: Undecided → High
status: Confirmed → In Progress
Revision history for this message
Ben Collins (ben-collins) wrote :

Should be fixed in 2.6.20-4

Changed in linux-source-2.6.20:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.