On Tue, Oct 04, 2005 at 09:09:40AM -0700, Daniel Walker wrote:
> On Tue, 2005-10-04 at 20:46 +0530, Dinakar Guniguntala wrote:
> >
> > 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();
>
Nope doesnt help. I booted with this code change and I get the
same message.
I saw that the code change is in #ifdef CONFIG_HIGH_RES_TIMERS.
I have already disabled CONFIG_HIGH_RES_TIMERS as Thomas Gleixner
suggested
-Dinakar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
