BUG: scheduling while atomic
I'm using 2.6.24-rc8 on a PPC 440 and getting this error. I've also seen another form of it when doing Telnet. In this case, I'm doing a copy of a file on an NFS mount. Any help would be appreciated. Thanks, John Linn # cp ftptest2 ftptest2_copied BUG: scheduling while atomic: cp/355/0x0efe Call Trace: [cfc89ec0] [c000725c] show_stack+0x4c/0x174 (unreliable) [cfc89ef0] [c0016880] __schedule_bug+0x54/0x68 [cfc89f10] [c01df464] schedule+0x50/0x300 [cfc89f40] [c0002374] recheck+0x0/0x24 BUG: scheduling while atomic: cp/355/0x0efe Call Trace: [cfc89c50] [c000725c] show_stack+0x4c/0x174 (unreliable) [cfc89c80] [c0016880] __schedule_bug+0x54/0x68 [cfc89ca0] [c01df464] schedule+0x50/0x300 [cfc89cd0] [c01df744] io_schedule+0x30/0x54 [cfc89cf0] [c003d79c] sync_page+0x44/0x58 [cfc89d00] [c01dfaf0] __wait_on_bit_lock+0x68/0xc8 [cfc89d20] [c003da28] __lock_page+0x64/0x78 [cfc89d60] [c00402d0] do_generic_mapping_read+0x218/0x418 [cfc89db0] [c00405fc] generic_file_aio_read+0x12c/0x1a8 [cfc89e00] [c00cba0c] nfs_file_read+0xf0/0x104 [cfc89e30] [c005b3d4] do_sync_read+0xb8/0x10c [cfc89ef0] [c005b840] vfs_read+0xc0/0x154 [cfc89f10] [c005c3bc] sys_read+0x4c/0x8c [cfc89f40] [c0001960] ret_from_syscall+0x0/0x3c BUG: scheduling while atomic: cp/355/0x0efe Call Trace: ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
22.1-rt8: BUG: scheduling while atomic: stress/0x00000002/739, CPU#0
Hi, First of all Im sorry to crosspost between linuxppc-dev and linuxppc-embedded. I am running linux-2.6.22.1-rt8 on mpc5200 and on running stress #./stress --cpu 8 --io 4 --vm 2 --vm-bytes 2M --timeout 300s I get the following stack.But this does not happen with non -rt kernel. LR = 0xff51fcc BUG: scheduling while atomic: stress/0x0002/739, CPU#0 Call Trace: [c04fbb80] [c0008650] show_stack+0x50/0x190 (unreliable) [c04fbbb0] [c0016fc0] __schedule_bug+0x38/0x48 [c04fbbc0] [c01d4f7c] __schedule+0x3dc/0x450 [c04fbbf0] [c01d56c8] schedule+0x54/0xf0 [c04fbc00] [c01d6390] rt_spin_lock_slowlock+0x100/0x224 [c04fbc60] [c0052198] get_zone_pcp+0x30/0x58 [c04fbc80] [c0053078] free_hot_cold_page+0x114/0x1fc [c04fbcb0] [c0056424] put_page+0x50/0x15c [c04fbcd0] [c0069854] free_page_and_swap_cache+0x44/0x80 [c04fbce0] [c005d760] unmap_vmas+0x2e0/0x788 [c04fbd70] [c006292c] exit_mmap+0x74/0x108 [c04fbda0] [c001adc0] mmput+0x54/0xf0 [c04fbdc0] [c001ecfc] exit_mm+0xc0/0x124 [c04fbde0] [c001ffd0] do_exit+0x164/0x8bc [c04fbe20] [c0020760] do_group_exit+0x38/0x90 [c04fbe40] [c002ba48] get_signal_to_deliver+0x2ac/0x3c0 [c04fbe70] [c000739c] do_signal+0x50/0x60c [c04fbf40] [c000fec0] do_user_signal+0x74/0xc4 --- Exception: c00 at 0xfeab1dc LR = 0xff51fcc I have also tested the same case on x86 and that does not throw up anything. Another observation is the fact is that this happens when --vm is > 1. So I am guessing its a very PowerPC specific problem. Maybe some part of the vm code for powerpc. This happens for all powerpc -rt kernels I have used. Link to stress is : http://weather.ou.edu/~apw/projects/stress/ A friend of mine has already posted this problem to the rt-preempt mailing list and I have posted this on the linuxppc-dev list as well. Any pointers suggestions as to where the problem could be is most welcome. Thanks in advance regards /prady -- htp://prady.livejournal.com ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
