crs, the issue you are reporting is an upstream one. Could you please
report this problem to the appropriate mailing list (intel-gfx) 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
Sure, you may take look at the file attached.
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454160/+attachment/4422947/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Output of 'cat /proc/acpi/wakeup wakeup' attached.
** Attachment added: wakeup
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454160/+attachment/4422948/+files/wakeup
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because
crs, could you please provide the missing information following
https://wiki.ubuntu.com/DebuggingKernelSuspend ?
** Tags removed: needs-bisect
** Tags added: bisect-done
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a
And there we have the bisect result:
git bisect good a5872ca0a6f5e889d628b2946e550c7d0e892430
ddf6f9a4c9fb1c72ea2e8d196c9a580a8e914dbd is the first bad commit
commit ddf6f9a4c9fb1c72ea2e8d196c9a580a8e914dbd
Author: Dave Airlie airl...@redhat.com
Date: Mon Dec 8 13:23:37 2014 +1000
Hi crs,
I found the tags in
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git . Which
will help you to bisect.
I had a look at the commits between 3.18.3 and 4. The two very last commits
before 3.18.4 are my primary suspects:
commit
last good kernel: 3.18.3-031803-generic
first bad kernel: 3.18.4-031804-generic
I tried to do a git bisect but I didn't make it far because there are no tags
3.18.3/3.18.4 in kernel repo (kernel.org) I cloned.
These are the only tags containing 3.18:
v3.18
v3.18-rc1
...
v3.18-rc7
Is there
crs, 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
This bug still exists on 4.1.0-040100rc4-generic #201505181436 SMP Mon
May 18 18:38:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1-rc4
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this
crs, the next step is to fully commit bisect from kernel 3.17 to 3.19 in
order to identify the last good kernel commit, followed immediately by
the first bad one. This will allow for a more expedited analysis of the
root cause of your issue. Could you please do this following
I tested it on Utopic and this behavior didn't occur: both monitors work
after resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454160
Title:
External monitor is disabled after resume
To
crs, are you able to test the latest mainline kernel in Utopic (or a
Utopic kernel in Vivid)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454160
Title:
External monitor is disabled after resume
Yes.
vivid + 3.17.1-031701-generic #201410150735 SMP Wed Oct 15 11:36:31 UTC 2014
x86_64 x86_64 x86_64:
The problem does *not* occur.
However, with a recent kernel (3.19.0-16-generic #16-Ubuntu SMP Thu Apr
30 16:09:58 UTC 2015 x86_64 x86_64 x86_64), the problem occurs.
--
You received this
** Summary changed:
- External monitor is disabled after resume (only on 15.04)
+ External monitor is disabled after resume
** Description changed:
I have an external screen connected to my machine (T450s, via docking
station) and after resuming from suspend, my external monitor is
After some trial and error it seems like I have to rephrase the initial
bug report:
If I resume from suspend caused by systemctl suspend, sudo pm-suspend,
or via the hotkey on my keyboard (K750), the login screen is only shown
on the build-in screen and not on the external monitor. In this case
I would really like to test this, but I'm unable to boot into a kernel
from Trusty.
I installed
linux-headers-3.13.11-0313_3.13.11-0313.20141336_all.deb
linux-headers-3.13.11-0313-generic_3.13.11-0313.20141336_amd64.deb
Unfortunately, it seems like that the T450s is not fully supported by
Trusty. Suspend and resume doesn't even work when only the build-in
screen is used.
Thus, there is no way for me to test if this behavior does exist on
Trusty.
--
You received this bug notification because you are a member of
crs, would Utopic provide a testable environment?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454160
Title:
External monitor is disabled after resume
To manage notifications about this bug go
crs, while still in Vivid, if you boot into a kernel from Trusty, is
this still reproducible?
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
crs, it may be easier to boot into Trusty directly, then install the
latest mainline kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454160
Title:
External monitor is disabled after resume
Thanks for your response, Christopher.
I updated my BIOS to the latest version available:
JBET48WW (1.13 )
04/20/2015
Unfortunately, nothing has changed. The system still behaves like in the
initial post of this report.
** Changed in: xorg (Ubuntu)
Status: Incomplete = New
--
You
crs, thank you for reporting this and helping make Ubuntu better. As per
http://support.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-t
-series-laptops/thinkpad-t450s an update to your computer's buggy and
outdated BIOS is available (1.13). If you update to this following
crs, just to clarify, if you boot into a kernel from Trusty, is this
still reproducible?
** Tags removed: bios-outdated-1.13
** Tags added: latest-bios-1.13
** Tags added: regression-release
** Changed in: xorg (Ubuntu)
Importance: Low = Medium
** Changed in: xorg (Ubuntu)
Status:
By the way: Could this bug be related to systemd? I could imagine that,
because (a) this does not occur on Utopic and (b) I just found someone
having problems using an external screen, and those problems are related
to systemd (http://askubuntu.com/questions/613693/15-04-closing-lid-
** Description changed:
- After resuming from suspend, my external monitor is disabled.
+ I have an external screen connected to my machine (T450s, via docking
+ station) and after resuming from suspend, my external monitor is
+ disabled.
After some trial and error I made an interesting
25 matches
Mail list logo
