Re: 18rc1 soft lockup

[john stultz]

On Thu, 2006-07-13 at 18:07 -0400, Dave Jones wrote:
> On Tue, Jul 11, 2006 at 03:16:58PM -0400, Dave Jones wrote:
>  > On Tue, Jul 11, 2006 at 12:13:47PM -0700, john stultz wrote:
>  >  > On Tue, 2006-07-11 at 15:03 -0400, Dave Jones wrote:
>  >  > > Just saw this during boot of a HT P4 box.
>  >  > > 
>  >  > > BUG: soft lockup detected on CPU#0!
>  >  > >  [<c04051af>] show_trace_log_lvl+0x54/0xfd
>  >  > >  [<c0405766>] show_trace+0xd/0x10
>  >  > >  [<c0405885>] dump_stack+0x19/0x1b
>  >  > >  [<c0450ec7>] softlockup_tick+0xa5/0xb9
>  >  > >  [<c042d496>] run_local_timers+0x12/0x14
>  >  > >  [<c042d81b>] update_process_times+0x3c/0x61
>  >  > >  [<c04179e0>] smp_apic_timer_interrupt+0x6d/0x75
>  >  > >  [<c0404ada>] apic_timer_interrupt+0x2a/0x30
>  >  > 
>  >  > That's clocksource_adjust/lost tick bug. Roman's fix landed in Linus'
>  >  > -git yesterday.
>  > 
>  > Ah, that was actually a .18rc1-git3 tree. I notice a git4 just appeared,
>  > I'll try and reproduce with that.
> 
> Just when I thought it had gotten fixed..
> 2.6.18rc1-git6 this time on x86-64..
> 
> BUG: soft lockup detected on CPU#3!
> 
> Call Trace:
>  [<ffffffff80270865>] show_trace+0xaa/0x23d
>  [<ffffffff80270a0d>] dump_stack+0x15/0x17
>  [<ffffffff802c44e6>] softlockup_tick+0xd5/0xea
>  [<ffffffff80250bea>] run_local_timers+0x13/0x15
>  [<ffffffff8029cc1d>] update_process_times+0x4c/0x79
>  [<ffffffff8027bfeb>] smp_local_timer_interrupt+0x2b/0x50
>  [<ffffffff8027c766>] smp_apic_timer_interrupt+0x58/0x62
>  [<ffffffff802628ae>] apic_timer_interrupt+0x6a/0x70

Hmmm.. grumble. Was this on bootup, or after some time period?

I'm looking into it.

thanks for the report
-john

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/