[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497520
For your Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz processor, what is the
normal minimum pstate? I ask because I have only seen on battery power
resume from suspend issues that are related to Clock Modulation becoming
enabled. i.e. I am wondering if 800MHz is a normal minimum frequency or
below the
> did you confirm that the quoted commit does indeed fix your issue?
No, I am not building Linux from source currently, and have not tried
e.g. applying that patch/commit to the Ubuntu package.
I am now back using the Ubuntu kernel, since the workaround is trivial
in case it is required - once
Christopher, please change the status back to Confirmed/Triaged,
according to my feedback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497520
Title:
Slow performance after resuming from/on
Daniel Hahler, could you please test the patch to confirm it actually
fixes your issue? Instructions may be found at
https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream
.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
To the best of my knowledge, this specific (resume from suspend,
intel_pstate, performance mode) issue has been fixed in the upstream
kernel. However, I never understood this issue to be specific to battery
mode, an interesting twist.
Note that there are other issues, and sometimes it is hard to
Thanks a lot for this insights, Doug!
I really think it is related to battery mode, but I cannot say that it has to
be on battery before suspend and/or during resume really. It's just that I've
noticed this issue to pop up when suspending on battery.
It might be even be only / more related to
Daniel Hahler, did you confirm that the quoted commit does indeed fix
your issue?
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I could not trigger it using the upstream kernel for now
(4.3.0-040300rc1-generic).
But it's maybe noteworthy, that the governors of CPU 1-3 get changed from
"powersave" to "performance", regardless of using the Ubuntu or upstream kernel
(/sys/devices/system/cpu/cpu*/cpufreq/scaling_governor).
Daniel Hahler, please feel free to stress test it for longer if it's
intermittent, to better confirm your initial results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497520
Title:
Slow
Daniel Hahler, thank you for reporting this and helping make Ubuntu
better. Could you please test the latest upstream kernel available from
the very top line at the top of the page from http://kernel.ubuntu.com
/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for
testing, and
11 matches
Mail list logo
