see also: https://bugzilla.kernel.org/show_bug.cgi?id=90421
particularly the entries from Marien.
This issue does not manifest the same for all i7 processors.
** Bug watch added: Linux Kernel Bug Tracker #90421
http://bugzilla.kernel.org/show_bug.cgi?id=90421
--
You received this bug
Jasper, for regression testing purposes, could you please test http
://old-releases.ubuntu.com/releases/14.04.0/ubuntu-14.04-desktop-
amd64.iso and advise to the results?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Jasper, did this issue not occur in a release prior to Vivid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452460
Title:
Turbo mode on i7 is not enabled upon resume
To manage notifications about
Sorry Christopher,
Further testing reveals that the bug is still present in 4.1-rc2. No idea why
it worked the first time, but it has not subsequently.
** Tags removed: kernel-bug-fixed-upstream kernel-bug-fixed-upstream-4.1-rc2
needs-reverse-bisect
** Tags added: kernel-bug-exists-upstream
I have never used this machine with anything less than 15.04, so sorry I
cannot say.
On 10 May 2015 at 12:13, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
Jasper, did this issue not occur in a release prior to Vivid?
--
You received this bug notification because you are
Jasper, just to clarify, in 4.1-rc2 do you have to use your WORKAROUND
to enable turbo mode after resuming from suspend, or is it automatically
enabled?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I do not use the workaround, and turbo mode is automatically enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452460
Title:
Turbo mode on i7 is not enabled upon resume
To manage
Jasper, the next step is to fully reverse commit bisect from kernel 3.19
to 4.1-rc2 in order to identify the last bad commit, followed
immediately by the first good one. Once this commit has been identified,
then it may be reviewed as a candidate for backporting into your
release. Could you please
Using linus' latest kernel from git (12 hours old) the `problem' persists, and
turbo must be re-enabed manually or via systemd script.
I built the deb-pkg target.
I will test the other ubuntu versions soon.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1.0-rc2
--
You
Jasper, could you please test the latest mainline kernel 4.1-rc2 (not a
daily pulled from git) and then advise to the results?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452460
Title:
Turbo
Jasper, could you please test the latest upstream kernel available from
the very top line at the top of the page (the release names are
irrelevant for testing, and please do not test the daily folder)
following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
additional upstream
The `problem' is fixed in 4.1-rc2.
But
As with the `echo 0... echo 1`... method the processor is _always_ in turbo
once it has resumed from sleep.
On my i7-4500U this is about 2.78 and 2.97Ghz.
** Tags removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1.0-rc2
** Tags added:
That should be done by the kernel itself. In the meantime you can put a
script into /lib/systemd/system-sleep/, they work much like the old pm-
utils/sleep.d/ scripts. See man systemd-sleep for details.
** Package changed: systemd (Ubuntu) = linux (Ubuntu)
--
You received this bug notification
Many thanks for the quick response. I will disseminate this to the many
questions in ask-ubuntu relating to resume scripts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452460
Title:
Turbo mode
14 matches
Mail list logo
