public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Roman Zippel <zippel@linux-m68k.org>
Subject: Re: 18rc1 soft lockup
Date: Thu, 13 Jul 2006 15:15:43 -0700	[thread overview]
Message-ID: <1152828943.6845.107.camel@localhost> (raw)
In-Reply-To: <20060713220722.GA3371@redhat.com>

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


  reply	other threads:[~2006-07-13 22:15 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 [this message]
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
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=1152828943.6845.107.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