From: Kashyap Chamarthy <kchamart@redhat.com>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Gleb Natapov <gleb@kernel.org>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Viresh Kumar <viresh.kumar@linaro.org>,
Dirk Brandewie <dirk.brandewie@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: intel_pstate divide error with v3.13-rc4-256-gb7000ad
Date: Fri, 27 Dec 2013 15:15:39 +0100 [thread overview]
Message-ID: <52BD8B8B.1050209@redhat.com> (raw)
In-Reply-To: <CA+5PVA60GSC0tTLJWLtVqb5eTPMzrszxtoBnUP8B_Q_60=oGyw@mail.gmail.com>
[. . .]
>> KVM does not emulate P-states at all. intel_pstate_init() calls
>> intel_pstate_msrs_not_valid() before printing "Intel P-state driver
>> initializing." which suppose to fail since it checks that two reads of
>> MSR_IA32_APERF return different values, but KVM does not emulate this msr
>> at all, so both calls should return zero (KVM suppose to inject #GP, all rdmsrl
>> are patched to be rdmsrl_safe in a guest).
>>
>> Anything interesting in host dmesg?
Heya Gleb,
Here's the relevant dmesg snippet (full dmesg, refer the attachment below):
=====
.
.
.
[ 3.462741] Intel pstate controlling: cpu 0
[ 3.463972] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.465399] Intel pstate controlling: cpu 1
[ 3.466505] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.468056] Intel pstate controlling: cpu 2
[ 3.469208] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.470751] Intel pstate controlling: cpu 3
[ 3.471870] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.473289] Intel pstate controlling: cpu 4
[ 3.474545] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.475957] Intel pstate controlling: cpu 5
[ 3.477135] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.478544] Intel pstate controlling: cpu 6
[ 3.479670] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.481124] Intel pstate controlling: cpu 7
[ 3.482288] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.483752] Intel pstate controlling: cpu 8
[ 3.484986] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.486396] Intel pstate controlling: cpu 9
[ 3.488000] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.489684] Intel pstate controlling: cpu 10
[ 3.491027] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.492647] Intel pstate controlling: cpu 11
[ 3.494026] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.495662] Intel pstate controlling: cpu 12
[ 3.497065] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.498733] Intel pstate controlling: cpu 13
[ 3.500071] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.501787] Intel pstate controlling: cpu 14
[ 3.503105] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.504809] Intel pstate controlling: cpu 15
[ 3.506142] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.507825] Intel pstate controlling: cpu 16
[ 3.509175] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.510780] Intel pstate controlling: cpu 17
[ 3.512158] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.513765] Intel pstate controlling: cpu 18
[ 3.515225] cpufreq: __cpufreq_add_dev: ->get() failed
[ 3.516898] Intel pstate controlling: cpu 19
.
.
.
=====
Full dmesg output: https://bugzilla.kernel.org/attachment.cgi?id=119701
(Kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=67761)
>> Is it reproducible?
Yes, just now I was able to reproduce it again. It's trivial with
libguestfs-test-tool:
$ export LIBGUESTFS_BACKEND=direct
$ guestfish get-backend
direct
$ libguestfs-test-tool
You see the Kernel panic on stdout.
NOTE: You can reproduce the issue without setting LIBGUESTFS_BACKEND=direct,
in which case, it'll default to 'libvirt' back-end.
Version:
$ uname -r; rpm -q libguestfs libvirt qemu-system-x86
3.13.0-0.rc4.git5.1.fc21.x86_64
libguestfs-1.25.18-1.fc21.x86_64
libvirt-1.1.3.1-2.fc20.x86_64
qemu-system-x86-1.6.1-2.fc20.x86_64
>
> Seems reproducible. I forgot to link to the actual bug in my original
> report, but you can find it here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1046317
>
> Adding Richard and Kashyap on CC.
>
> josh
>
--
/kashyap
next prev parent reply other threads:[~2013-12-27 14:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 14:36 intel_pstate divide error with v3.13-rc4-256-gb7000ad Josh Boyer
2013-12-24 16:06 ` Viresh Kumar
2013-12-27 12:24 ` One Thousand Gnomes
2013-12-27 12:47 ` Gleb Natapov
2013-12-27 13:46 ` Josh Boyer
2013-12-27 14:15 ` Kashyap Chamarthy [this message]
2013-12-27 14:34 ` Richard W.M. Jones
2013-12-27 16:52 ` Gleb Natapov
2013-12-27 17:01 ` Gleb Natapov
2013-12-27 17:17 ` Richard W.M. Jones
2013-12-27 17:17 ` Kashyap Chamarthy
2013-12-27 21:51 ` Rafael J. Wysocki
2013-12-29 12:12 ` Kashyap Chamarthy
2013-12-29 15:04 ` Rafael J. Wysocki
2013-12-30 14:58 ` Kashyap Chamarthy
2013-12-31 2:07 ` Rafael J. Wysocki
2014-01-03 17:30 ` Dirk Brandewie
2014-01-03 18:04 ` Gleb Natapov
2014-01-03 20:00 ` Dirk Brandewie
2014-01-03 22:06 ` Paolo Bonzini
2014-01-06 17:18 ` Dirk Brandewie
2014-01-07 16:11 ` Gleb Natapov
2014-01-03 22:46 ` Rafael J. Wysocki
2014-01-04 8:35 ` Paolo Bonzini
2014-01-04 14:38 ` Rafael J. Wysocki
2014-01-04 17:38 ` Paolo Bonzini
2014-01-04 17:48 ` Gleb Natapov
2014-01-04 21:38 ` Rafael J. Wysocki
2014-01-06 11:20 ` Paolo Bonzini
2014-01-06 11:37 ` Rafael J. Wysocki
2014-01-06 18:40 ` Dirk Brandewie
2013-12-27 14:35 ` Rafael J. Wysocki
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=52BD8B8B.1050209@redhat.com \
--to=kchamart@redhat.com \
--cc=cpufreq@vger.kernel.org \
--cc=dirk.brandewie@gmail.com \
--cc=gleb@kernel.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjones@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).