Out of curiosity I've tested the latest official trusty kernel
(3.13.0-30-generic) and found, that this issue is fixed now.
It seems, that one/some of the backports of 3.14-rc1 or later, which
went into the kernel updates, was the one which solved this bug as seen
upstream. I might add, that I
b3nmore, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250498/comments/40
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line
** Tags removed: kernel-bug-exists-upstream-v3.13-rc6
** Tags added: kernel-fixed-upstream-3.14-rc1
** Tags added: needs-reverse-bisect
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Upstream bug report: https://bugzilla.kernel.org/show_bug.cgi?id=66741
** Bug watch added: Linux Kernel Bug Tracker #66741
http://bugzilla.kernel.org/show_bug.cgi?id=66741
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
b3nmore, thank you for git bisecting. Could you please test the latest
mainline kernel via
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc6-trusty/ and advise to
the results?
Tested 3.13-rc6, same as before.
--
You received this bug notification because you are a member of Kernel
In the original bug description I mentioned, that resume may also result in a
complete system freeze (no more ssh, hard reset necessary). I believe, I found
out how to trigger it: it depends on whether the power is cut completely during
hibernation.
The situation is now:
i) computer stays
I've tested 3.9.11 again against the new test case: resume works as long as the
power supply cable stays plugged and fails if the power supply is cut off
completely.
That means, in my case resume from hibernate is broken for all kernel version,
if the pc is disconnected from the mains during
b3nmore, the issue you are reporting is an upstream one. Could you
please report this problem through the appropriate channel by following
the instructions _verbatim_ at
https://wiki.ubuntu.com/Bugs/Upstream/kernel ?
Please provide a direct URL to your e-mail to the mailing list once you
have
Finally finished a full commit bisect:
5aa1c98862d3f365d9cf6d0833d5dc127d2a76e7 is the first bad commit
** Attachment added: bisect.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250498/+attachment/3938137/+files/bisect.log
--
You received this bug notification because you are a
** Tags removed: needs-bisect
** Tags added: bisect-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1250498
Title:
8086:0412 [Asus B85M-G] No video output after 2nd resume from
b3nmore, thank you for git bisecting. Could you please test the latest
mainline kernel via http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.13-rc6-trusty/ and advise to the results?
** Tags added: needs-upstream-testing
--
You received this bug notification because you are a member of Kernel
In precise with kernel 3.8.0-33 resume works. I ran it 3 times to be
sure. It's weird (or maybe not), according to
https://01.org/linuxgraphics/downloads/2013/2013q1-intel-graphics-stack-
release full haswell support was reached with 3.8.2.
However the lts-saucy kernel in precise (3.11.0) chokes
Using 3.11.0.13 kernel (lts-saucy) in precise results in no video output
as before.
** Attachment added: dmesg_3.11_2nd_resume
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250498/+attachment/3920771/+files/dmesg_3.11_2nd_resume
--
You received this bug notification because you are
b3nmore, regarding your comments:
...according to
https://01.org/linuxgraphics/downloads/2013/2013q1-intel-graphics-stack-release
full haswell support was reached with 3.8.2.
As per http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html
Ubuntu 3.8.0-33 is based on mainline 3.8.13.11.
A kernel version bisect narrowed it down so far to:
3.9.11-saucy last working version
3.10-rc1-saucy first failing version.
Which git repo should I use for a commit bisect?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
b3nmore, as per
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_bisect_the_upstream_kernel.3F
you would want to use:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
--
You received this bug notification because you are a member of Kernel
Packages, which is
b3nmore, could you please post the following terminal command results:
sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date:
0703
10/30/2013
Sorry for the delay, its (hidden) in the previous kernel logs, so I
didn't bother.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
b3nmore, did this problem not occur in a release prior to Saucy?
** Tags removed: bios-outdated-0703
** Tags added: latest-bios-0703
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1250498
b3nmore, did this problem not occur in a release prior to Saucy?
Can't really tell, I bought it recently and started directly with saucy
or trusty respectively. However, I started my old precise 3.2 32bit
installation from my previous system (amd athlon xp, nvidia gpu), mainly
because I was
kernel log resume with 3.11 in single user mode.
** Attachment added: dmesg_bios0703_3.11.0
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250498/+attachment/3919956/+files/dmesg_bios0703_3.11.0
--
You received this bug notification because you are a member of Kernel
Packages, which
No changes at all.
I tested the saucy 3.11 kernel and the 3.13rc1 mainline kernel: After
the second resume the screen shows the progress of the resume and then
goes into powersave. The system is, apart from the failing video output,
fully functional.
The attached kernel logs were made from
22 matches
Mail list logo
