From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-kernel@vger.kernel.org
Subject: Hard lockups using 3.10.0
Date: Thu, 11 Jul 2013 11:38:37 +0200 [thread overview]
Message-ID: <8484013.LsABBJRIOx@devpool02> (raw)
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
Hi,
I'm running 3.10.0 (from openSUSE packages) on an "Intel(R) Core(TM) i7-2600
CPU @ 3.40GHz". I got a hard lockup on one of my CPUs twice, once with
backtrace (see attached image). Graphics is the builtin Intel, used with X 7.6
and KDE 4.10beta2 (basically current openSUSE 12.3+KDE).
I'm not aware that I had done anything special, just "normal" desktop and
development usage, but no heavy compile work at the moment the lockups
happened.
Any ideas?
Eike
[-- Attachment #2: lockup.jpg --]
[-- Type: image/jpeg, Size: 266338 bytes --]
next reply other threads:[~2013-07-11 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 9:38 Rolf Eike Beer [this message]
2013-07-11 10:07 ` Hard lockups using 3.10.0 Borislav Petkov
2013-07-11 10:16 ` Peter Zijlstra
2013-07-11 10:52 ` Peter Zijlstra
2013-07-11 17:50 ` Paul E. McKenney
2013-07-11 19:02 ` Rolf Eike Beer
2013-08-11 6:09 ` Rolf Eike Beer
2013-08-11 8:37 ` Borislav Petkov
2013-08-11 11:10 ` Rolf Eike Beer
2013-08-13 10:38 ` Borislav Petkov
2013-08-13 11:57 ` Rolf Eike Beer
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=8484013.LsABBJRIOx@devpool02 \
--to=eike-kernel@sf-tec.de \
--cc=linux-kernel@vger.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