From: Thomas Gleixner <tglx@linutronix.de>
To: "Miloslav Hůla" <miloslav.hula@gmail.com>
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: Mon, 20 Feb 2017 15:24:45 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.20.1702201524110.4208@nanos> (raw)
In-Reply-To: <194d53c8-0c2f-d70c-2aa4-de8af393c94f@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
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.
Thanks,
tglx
next prev parent reply other threads:[~2017-02-20 23:24 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 [this message]
2017-02-21 9:10 ` Miloslav Hůla
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=alpine.DEB.2.20.1702201524110.4208@nanos \
--to=tglx@linutronix.de \
--cc=855183@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miloslav.hula@gmail.com \
--cc=peterz@infradead.org \
--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®