From: john stultz <johnstul@us.ibm.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 18rc1 soft lockup
Date: Thu, 13 Jul 2006 17:02:38 -0700 [thread overview]
Message-ID: <1152835358.6845.119.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0607140058400.12900@scrub.home>
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
next prev parent reply other threads:[~2006-07-14 0:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 19:03 18rc1 soft lockup Dave Jones
2006-07-11 19:13 ` john stultz
2006-07-11 19:16 ` Dave Jones
2006-07-13 22:07 ` Dave Jones
2006-07-13 22:15 ` john stultz
2006-07-13 22:28 ` Dave Jones
2006-07-14 9:22 ` Roman Zippel
2006-07-14 14:09 ` Dave Jones
2006-07-14 23:30 ` john stultz
2006-07-13 23:05 ` Roman Zippel
2006-07-14 0:02 ` john stultz [this message]
2006-07-14 0:12 ` Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1152835358.6845.119.camel@localhost \
--to=johnstul@us.ibm.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox