From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: 3.11-rc2: panic in __rdmsr_on_cpu
Date: Fri, 26 Jul 2013 08:00:21 -0700 [thread overview]
Message-ID: <51F28F05.50807@linux.intel.com> (raw)
In-Reply-To: <CAKb7UvjYNz8KRnny8EB6rxQcLPrp0Y8CWHZaVG0qzAJisC8dog@mail.gmail.com>
This is already fixed and it is in Linus main line. Check commit id
"f3ed0a17f0292300b3caca32d823ecd32554a667"
Thanks for analysis and you are correct.
Thanks,
Srinivas
On 07/26/2013 06:15 AM, Ilia Mirkin wrote:
> On Fri, Jul 26, 2013 at 7:59 AM, Ilia Mirkin <imirkin@alum.mit.edu> wrote:
>> On Thu, Jul 25, 2013 at 6:32 PM, Ilia Mirkin <imirkin@alum.mit.edu> wrote:
>>> Hi,
>>>
>>> I just built a 3.11-rc2 kernel (+ a few patches, but nothing
>>> arch-related), and I saw the following: http://i.imgur.com/dCTqOyR.jpg
>>>
>>> The rough transcription is
>>>
>>> Call Trace:
>>> <IRQ>
>>> generic_smp_call_fucntion_single_interrupt
>>> smp_call_function_single_interrupt
>>> call_function_single_interrupt
>>> <EOI>
>>> ? default_idle
>>> ? default_idle
>>> arch_cpu_idle
>>> cpu_startup_entry
>>> rest_init
>>> start_kernel
>>> ? repair_env_string
>>> x86_64_start_reservations
>>> x86_64_start_kernel
>>> Code: ... cc 81 8b 0f <0f> 32 48 c1 e2 20 89 c0 ...
>>> RIP: __rdmsr_on_cpu+0x2e/0x44
>>> Kernel panic - not syncing: Fatal exception in interrupt
>>>
>>> A 3.10-rc7 kernel booted just fine. Is this likely a real issue? Or
>>> perhaps a mis-build of some sort?
>> FWIW this is repeatable. I did a clean build (make clean && make) and
>> I still see the same thing. I have a Core i7-920 cpu, not sure what
>> other information would be relevant. I'd love to avoid a bisect, so
>> some likely candidates would be most welcome.
> Aha, figured it out. I had enabled "X86 package temperature thermal
> driver" = Y, which caused my Core i7-920 to produce the above trace on
> boot. Glancing over the code, should this:
>
> if (!cpu_has(c, X86_FEATURE_DTHERM) &&
> !cpu_has(c, X86_FEATURE_PTS))
> return -ENODEV;
>
> perhaps be
>
> if (!cpu_has(c, X86_FEATURE_DTHERM) ||
> !cpu_has(c, X86_FEATURE_PTS))
> return -ENODEV;
>
> i.e. are both of those things required, or just one of them? My cpu
> has DTHERM but not PTS, according to /proc/cpuinfo.
>
> -ilia
>
prev parent reply other threads:[~2013-07-26 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 22:32 3.11-rc2: panic in __rdmsr_on_cpu Ilia Mirkin
2013-07-26 11:59 ` Ilia Mirkin
2013-07-26 13:15 ` Ilia Mirkin
2013-07-26 15:00 ` Srinivas Pandruvada [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=51F28F05.50807@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=imirkin@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.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