On Wednesday 12 February 2014 02:43 AM, Kirill Tkhai wrote: > > > 06.01.2014, 07:56, "Allen Pais" <allen.pais@xxxxxxxxxx>: >> In the attempt of get PREEMPT_RT working on sparc64 using >> linux-stable-rt version 3.10.22-rt19+, the kernel crash >> with the following trace: >> >> [ 1487.027884] I7: <rt_mutex_setprio+0x3c/0x2c0> >> [ 1487.027885] Call Trace: >> [ 1487.027887] [00000000004967dc] rt_mutex_setprio+0x3c/0x2c0 >> [ 1487.027892] [00000000004afe20] task_blocks_on_rt_mutex+0x180/0x200 >> [ 1487.027895] [0000000000819114] rt_spin_lock_slowlock+0x94/0x300 >> [ 1487.027897] [0000000000817ebc] __schedule+0x39c/0x53c >> [ 1487.027899] [00000000008185fc] schedule+0x1c/0xc0 >> [ 1487.027908] [000000000048fff4] smpboot_thread_fn+0x154/0x2e0 >> [ 1487.027913] [000000000048753c] kthread+0x7c/0xa0 >> [ 1487.027920] [00000000004060c4] ret_from_syscall+0x1c/0x2c >> [ 1487.027922] [0000000000000000] (null) >> - spin_unlock_irqrestore(&mm->context.lock, flags); >> + raw_spin_unlock_irqrestore(&mm->context.lock, flags); >> } > > We also should do the same in update_mmu_cache_pmd(). > I have already done this. I should have updated the patch. the issue still persists though. - Allen -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
