On Fri, 2006-07-14 at 01:05 +0200, Roman Zippel wrote:
> Hi,
>
> On Thu, 13 Jul 2006, john stultz wrote:
>
> > > 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.
>
> I don't quite understand how this is clock related, soft lockup uses
> jiffies and there is nothing clock related in the trace???
Hmmm. Well, its easy to check:
Dave, could you comment out the "clocksource_adjust(...)" line in
kernel/timer.c::update_wall_time() just to check if its the same issue?
thanks
-john
-
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]
