From: "Miloslav Hůla" <miloslav.hula@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ben Hutchings <ben@decadent.org.uk>,
x86@kernel.org, 855183@bugs.debian.org,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Kan Liang <kan.liang@intel.com>
Subject: Re: Bug#855183: linux-image-4.9.0-0.bpo.1-amd64: modprobe intel_rapl_perf stay in uninterruptible sleep
Date: Tue, 21 Feb 2017 10:10:51 +0100 [thread overview]
Message-ID: <33175c4f-c791-4b2d-8009-680a3fd8c7c4@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1702201524110.4208@nanos>
Dne 21.02.2017 v 0:24 Thomas Gleixner napsal(a):
> On Mon, 20 Feb 2017, Miloslav Hůla wrote:
>> Dne 17.02.2017 v 11:47 Thomas Gleixner napsal(a):
>>> What's really confusing is this information from the bug report:
>>>
>>> " When I changed:
>>>
>>> Power technology:
>>> - from Energy Efficient
>>> - to Custom
>>>
>>> Energy Performance BIAS Setting:
>>> - from Balanced Performance
>>> - to Performance
>>>
>>> problem disappeared. systemd-udevd starts normally, module can be
>>> normally rmmod/insmod'ed now, load is 0.07."
>>>
>>> Miloslav: Is there any chance you can try a 4.10-rc8 kernel on that
>>> machine?
>>
>> I compiled 4.10-rc8 kernel with a stock '/boot/config-4.9.0-0.bpo.1-amd64'
>> config from Debian Jessie backports. Then I reverted BIOS settings to previous
>> state and rebooted the server. Kernel and all modules loaded normally,
>> rmmod/insmod intel_rapl_perf passed normally.
>>
>> Then, without any BIOS change, I rebooted with stock 4.9.0-0.bpo.1-amd64 and
>> suprisingly, everything works, I cannot reproduce it.
>>
>> My knowledge on the field of BIOS are shallow. I don't know what I can do to
>> reproduce the bug now.
>
> Did you just reboot or go through a cold start? That might make a difference.
Reboot only. I'll test it again in next maintenance window.
Regards, Milo
prev parent reply other threads:[~2017-02-21 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170215080829.27308.94177.reportbug@imap.fsv.cvut.cz>
2017-02-17 0:49 ` Ben Hutchings
2017-02-17 10:47 ` Thomas Gleixner
2017-02-20 22:34 ` Miloslav Hůla
2017-02-20 23:24 ` Thomas Gleixner
2017-02-21 9:10 ` Miloslav Hůla [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=33175c4f-c791-4b2d-8009-680a3fd8c7c4@gmail.com \
--to=miloslav.hula@gmail.com \
--cc=855183@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®