Bug 574910

Summary: BUG: scheduling while atomic: swapper/0/0x10000002
Product: [openSUSE] openSUSE 11.2 Reporter: Juergen Weigert <jw>
Component: KernelAssignee: E-mail List <kernel-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: lchiquitto
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 357354    

Description Juergen Weigert 2010-01-28 21:13:37 UTC
Rebooting after some online updates 
I have these disturbing messages in the logs:


[    0.004330] using mwait in idle threads.
[    0.004339] Performance Events: no PMU driver, software events only.
[    0.004346] Checking 'hlt' instruction... OK.
[    0.008793] Unpacking initramfs...
[    0.016039] BUG: scheduling while atomic: swapper/0/0x10000002
[    0.016048] Modules linked in:
[    0.016053] Pid: 0, comm: swapper Not tainted 2.6.32-3-desktop #1
[    0.016056] Call Trace:
[    0.016074]  [<c02067eb>] try_stack_unwind+0x14b/0x170
[    0.016081]  [<c02056df>] dump_trace+0x3f/0xf0
[    0.016087]  [<c020648b>] show_trace_log_lvl+0x4b/0x60
[    0.016092]  [<c02064b8>] show_trace+0x18/0x20
[    0.016099]  [<c062b415>] dump_stack+0x6d/0x72
[    0.016105]  [<c062c08f>] schedule+0x76f/0x790
[    0.016112]  [<c02389a6>] __cond_resched+0x16/0x30
[    0.016118]  [<c062c1c5>] _cond_resched+0x25/0x30
[    0.016125]  [<c02b6298>] generic_perform_write+0x138/0x1d0
[    0.016132]  [<c02b6956>] generic_file_buffered_write+0x66/0xe0
[    0.016139]  [<c02b8390>] __generic_file_aio_write+0x200/0x500
[    0.016145]  [<c02b86ee>] generic_file_aio_write+0x5e/0xc0
[    0.016152]  [<c02f60d5>] do_sync_write+0xd5/0x120
[    0.016158]  [<c02f63c0>] vfs_write+0xa0/0x190
[    0.016164]  [<c02f6e93>] sys_write+0x53/0xe0
[    0.016171]  [<c091ae7b>] do_copy+0x93/0xc6
[    0.016177]  [<c091a8b6>] flush_buffer+0x74/0x98
[    0.016185]  [<c093970e>] gunzip+0x383/0x42a
[    0.016191]  [<c091acef>] unpack_to_rootfs+0x274/0x36d
[    0.016197]  [<c091b66e>] populate_rootfs+0x4b/0x69
[    0.016202]  [<c091997c>] start_kernel+0x2e4/0x2f8
[    0.025308] BUG: scheduling while atomic: swapper/0/0x10000002
[    0.025318] Modules linked in:
[    0.025323] Pid: 0, comm: swapper Not tainted 2.6.32-3-desktop #1
[    0.025326] Call Trace:
[    0.025342]  [<c02067eb>] try_stack_unwind+0x14b/0x170
[    0.025349]  [<c02056df>] dump_trace+0x3f/0xf0
[    0.025355]  [<c020648b>] show_trace_log_lvl+0x4b/0x60
[    0.025361]  [<c02064b8>] show_trace+0x18/0x20
[    0.025368]  [<c062b415>] dump_stack+0x6d/0x72
[    0.025374]  [<c062c08f>] schedule+0x76f/0x790
[    0.025380]  [<c02389a6>] __cond_resched+0x16/0x30
[    0.025386]  [<c062c1c5>] _cond_resched+0x25/0x30
...
repeats a number of times, then it continues
...
[    0.193268]  [<c02b6298>] generic_perform_write+0x138/0x1d0
[    0.193275]  [<c02b6956>] generic_file_buffered_write+0x66/0xe0
[    0.193281]  [<c02b8390>] __generic_file_aio_write+0x200/0x500
[    0.193287]  [<c02b86ee>] generic_file_aio_write+0x5e/0xc0
[    0.193294]  [<c02f60d5>] do_sync_write+0xd5/0x120
[    0.193300]  [<c02f63c0>] vfs_write+0xa0/0x190
[    0.193305]  [<c02f6e93>] sys_write+0x53/0xe0
[    0.193312]  [<c091ae17>] do_copy+0x2f/0xc6
[    0.193317]  [<c091a8b6>] flush_buffer+0x74/0x98
[    0.193324]  [<c093970e>] gunzip+0x383/0x42a
[    0.193330]  [<c091acef>] unpack_to_rootfs+0x274/0x36d
[    0.193336]  [<c091b66e>] populate_rootfs+0x4b/0x69
[    0.193341]  [<c091997c>] start_kernel+0x2e4/0x2f8
[    0.199207] Freeing initrd memory: 7381k freed
[    0.203624] ACPI: Core revision 20090903
[    0.235253] Mapping cpu 0 to node 0
[    0.235444] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.246018] CPU0: Intel(R) Core(TM) Duo CPU      L2400  @ 1.66GHz stepping 0c
[    0.251991] Booting processor 1 APIC 0x1 ip 0x6000
[    0.001999] Initializing CPU#1
Comment 1 Leonardo Chiquitto 2010-01-29 00:03:04 UTC
This is a duplicate of bug #568120.

*** This bug has been marked as a duplicate of bug 568120 ***