Re: [ANNOUNCE] 3.2.52-rt73
From: Pavel Vasilyev
Date: Thu Nov 21 2013 - 15:44:53 EST
Fine, killed 3.12 now decided to finish 3.2.x. Good job guys!
Not configuration, not hardware, not software has not been updated or changed.
BUG: scheduling while atomic: irq/74-sata_nv/57/0x00000002
Modules linked in: cls_u32 sch_sfq sch_htb
Pid: 57, comm: irq/74-sata_nv Tainted: G O 3.2.52-rt73 #10
Call Trace:
[<ffffffff814bdef4>] ? __schedule+0x314/0x344
[<ffffffff81081b77>] ? task_blocks_on_rt_mutex+0x1e7/0x280
[<ffffffff814be741>] ? schedule+0x21/0xa0
[<ffffffff814c0d88>] ? rt_spin_lock_slowlock+0x128/0x280
[<ffffffff81204d01>] ? blk_update_request+0x11/0x450
[<ffffffff812a6976>] ? add_timer_randomness+0x86/0x1e0
[<ffffffff81206eac>] ? blk_end_request+0x9c/0xc0
[<ffffffff812c629a>] ? scsi_io_completion+0x9a/0x770
[<ffffffff8120d4ab>] ? blk_done_softirq+0x6b/0x80
[<ffffffff8104a805>] ? __do_softirq_common+0xa5/0x1d0
[<ffffffff81094ec0>] ? irq_thread_fn+0x50/0x50
[<ffffffff8104ad77>] ? local_bh_enable+0x127/0x150
[<ffffffff81094f08>] ? irq_forced_thread_fn+0x48/0x70
[<ffffffff81094d80>] ? irq_thread+0x150/0x240
[<ffffffff81094c30>] ? disable_irq_nosync+0x60/0x60
[<ffffffff81067150>] ? kthread+0x80/0x90
[<ffffffff814c3174>] ? kernel_thread_helper+0x4/0x10
[<ffffffff810670d0>] ? kthread_bind+0x80/0x80
[<ffffffff814c3170>] ? gs_change+0xb/0xb
BUG: scheduling while atomic: ksoftirqd/3/27/0x00000002
Pid: 3, comm: ksoftirqd/0 Tainted: G O 3.2.52-rt73 #10
...
BUG: scheduling while atomic: ksoftirqd/0/3/0x00000002
Pid: 27, comm: ksoftirqd/3 Tainted: G O 3.2.52-rt73 #10
....
BUG: scheduling while atomic: ksoftirqd/0/3/0x00000002
Pid: 27, comm: ksoftirqd/3 Tainted: G O 3.2.52-rt73 #10
--
Pavel.
Attachment:
signature.asc
Description: OpenPGP digital signature