From: Thomas Gleixner <tglx@linutronix.de>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.21-git4 BUG: soft lockup detected on CPU#1!
Date: Thu, 03 May 2007 00:43:55 +0200 [thread overview]
Message-ID: <1178145835.2340.31.camel@localhost.localdomain> (raw)
In-Reply-To: <6bffcb0e0705021449i5ce6061eg6b684d08348b2d74@mail.gmail.com>
On Wed, 2007-05-02 at 23:49 +0200, Michal Piotrowski wrote:
> On 02/05/07, Thomas Gleixner <tglx@linutronix.de> wrote:
> > On Wed, 2007-05-02 at 23:42 +0200, Michal Piotrowski wrote:
> > > Hi Thomas,
> > >
> > > I hit this soft lockup
> > >
> > > [ 5401.599275] BUG: soft lockup detected on CPU#1!
> > > [ 5401.603809] [<c0105039>] show_trace_log_lvl+0x1a/0x2f
> > > [ 5401.608980] [<c0105720>] show_trace+0x12/0x14
> > > [ 5401.613456] [<c01057d2>] dump_stack+0x16/0x18
> > > [ 5401.617934] [<c01518e8>] softlockup_tick+0xa7/0xb9
> > > [ 5401.622841] [<c012a0b5>] run_local_timers+0x12/0x14
> > > [ 5401.627829] [<c012a482>] update_process_times+0x3e/0x63
> > > [ 5401.633164] [<c013a028>] tick_sched_timer+0x5d/0xa1
> > > [ 5401.638160] [<c01366fb>] hrtimer_interrupt+0x127/0x1b4
> > > [ 5401.643415] [<c0114c66>] smp_apic_timer_interrupt+0x72/0x84
> > > [ 5401.649097] [<c0104b2b>] apic_timer_interrupt+0x33/0x38
> > > [ 5401.654437] =======================
> > > [ 5401.658055] Clocksource tsc unstable (delta = 9372000804 ns)
> > > [ 5401.664061] Time: acpi_pm clocksource has been installed.
> >
> > Hmm. Looks like TSC going awry and the softlockup hits before the tsc
> > watchdog logic kicks in.
> >
> > Was the system stable afterwards ?
>
> It works.
Ok. So it's more annoyance than a problem.
Nevertheless, I keep it in my list of things to look at.
tglx
prev parent reply other threads:[~2007-05-02 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 21:42 Michal Piotrowski
2007-05-02 21:49 ` Thomas Gleixner
2007-05-02 21:49 ` Michal Piotrowski
2007-05-02 22:43 ` Thomas Gleixner [this message]
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=1178145835.2340.31.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/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
all inboxes | Powered by JetHome®