From: Borislav Petkov <bp@amd64.org>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Andrew Lutomirski <luto@mit.edu>, <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
x86 <x86@kernel.org>
Subject: Re: HPET (?) related hangs and breakage in 2.6.35,36
Date: Tue, 9 Nov 2010 16:38:05 +0100 [thread overview]
Message-ID: <20101109153805.GB3146@kryptos.osrc.amd.com> (raw)
In-Reply-To: <4CD966D8.4000602@ladisch.de>
On Tue, Nov 09, 2010 at 04:20:56PM +0100, Clemens Ladisch wrote:
> Andrew Lutomirski wrote:
> > After several minutes of uptime, my system freezes in a strange way.
> > All of userspace and some kernel services freeze hard (no mouse, no
> > typing, etc.) Caps-lock works intermittently, as does (I think)
> > pinging. The only debug output I've been able to get is this (typed
> > from a blurry photo because netconsole dies along with everything
> > else):
> >
> > [ 5478.244722] Clocksource tsc unstable (delta = 101399051316 ns)
> > [ 5478.367958] Switching to clocksource hpet
> > [ 5543.729698] BUG: soft lockup - CPU #1 stuck for 61s! [migration/1:6]
>
> Looks like this one:
> http://lkml.org/lkml/2010/10/26/126
I don't think so: the one at the URL above is 37-rc1 specific (issue
came in during the merge window) while Andrew's problem can be
reproduced with 35 and 36, reportedly.
Anyway, adding more people to Cc.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2010-11-09 15:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 13:46 Andrew Lutomirski
2010-11-09 15:20 ` Clemens Ladisch
2010-11-09 15:38 ` Borislav Petkov [this message]
2010-11-09 17:44 ` Andrew Lutomirski
2010-11-09 18:01 ` Borislav Petkov
2010-11-09 21:29 ` Andrew Lutomirski
2010-11-10 18:48 ` [FALSE ALARM] " Andrew Lutomirski
2010-11-10 18:50 ` Borislav Petkov
2010-11-10 19:02 ` Andrew Lutomirski
2010-11-10 20:52 ` Thomas Gleixner
2010-11-10 20:56 ` Andrew Lutomirski
2010-11-10 20:58 ` Thomas Gleixner
2010-11-11 11:06 ` Roedel, Joerg
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=20101109153805.GB3146@kryptos.osrc.amd.com \
--to=bp@amd64.org \
--cc=clemens@ladisch.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
Powered by JetHome