Messages in this thread Patch in this message |  | | | Subject | Re: 2.6.14-rc3-rt2 | | From | Daniel Walker <> | | Date | Tue, 04 Oct 2005 09:09:40 -0700 |
| |
On Tue, 2005-10-04 at 20:46 +0530, Dinakar Guniguntala wrote: > On Tue, Oct 04, 2005 at 04:27:18PM +0200, Ingo Molnar wrote: > > > > > Hmm Ingo, > > > > > > Looks like -rt6 got rid of all the _nort defines, but it's still used > > > throughout the kernel. > > > > yeah, -rt7 should fix this. > > > > > I get a lot of these with -rt7 (One every minute) > > BUG: auditd:3596, possible softlockup detected on CPU#3! > [<c0144c48>] softlockup_detected+0x39/0x46 (8) > [<c0144d26>] softlockup_tick+0xd1/0xd3 (20) > [<c0111252>] smp_apic_timer_ipi_interrupt+0x4d/0x56 (24) > [<c010396c>] apic_timer_ipi_interrupt+0x1c/0x24 (12) > [<c0102e7f>] sysenter_past_esp+0x24/0x75 (44)
Woops, forgot to CC LKML ..
Index: linux-2.6.13/arch/i386/kernel/apic.c =================================================================== --- linux-2.6.13.orig/arch/i386/kernel/apic.c +++ linux-2.6.13/arch/i386/kernel/apic.c @@ -1153,6 +1153,16 @@ fastcall notrace void smp_apic_timer_ipi #if 0 profile_tick(CPU_PROFILING, regs); #endif + + /* + * If the task is currently running in user mode, don't + * detect soft lockups. If CONFIG_DETECT_SOFTLOCKUP is not + * configured, this should be optimized out. + */ + if (user_mode(regs)) + touch_light_softlockup_watchdog(); + + update_process_times(user_mode_vm(regs)); irq_exit();
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |