** Changed in: linux
Status: Confirmed => Fix Released
--
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/1727662
Title:
[Lenovo ThinkPad T450s] Issues after docking and locking
I'm happy to report that I've not had a single problem since I installed
5.4.0-rc7-drm-tip-git-g3ff71899c56c.
I'm marking this as resolved, with thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Excellent to hear, thank you.
--
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/1727662
Title:
[Lenovo ThinkPad T450s] Issues after docking and locking
Status in Linux:
Fix Released
Thanks.
--
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/1727662
Title:
[Lenovo ThinkPad T450s] Issues after docking and locking
Status in Linux:
Confirmed
Status in linux package in
I've just built the drm-tip kernel. Will test this for a few days and
report back.
--
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/1727662
Title:
[Lenovo ThinkPad T450s] Issues after
(In reply to Johan Thorén from comment #27)
> Hi Anshuman,
>
> 1. Is this issue is seen when u connect a external display directly to
> laptop without dock?
>
> It happens more frequently (it seems) when connected through a dock, but it
> also happens when using a cable directly to the laptop.
>
Johan - can you re-run on drm-tip, and see if the issue persists? If it
does, please provide the dmesg log output
--
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/1727662
Title:
[Lenovo
Just lately there was some fixes on drm-tip on MST. Are you able to test
with latest drm-tip and report back behaviour.
--
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/1727662
Title:
Hi Anshuman,
1. Is this issue is seen when u connect a external display directly to
laptop without dock?
It happens more frequently (it seems) when connected through a dock, but
it also happens when using a cable directly to the laptop.
2. Have u screen the display tear issue on embedder panel
I've now verified that the error still occurs with or without that
command issued, especially when coming back from suspend.
--
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/1727662
Title:
I was experiencing the same issue with a ThinkPad 25 (which is almost
the same thing as T470) and I implemented these precautions as a
workaround:
- disable DPMS when docked and external monitors enabled
- never switch VTs with external monitors enabled
- always disable external monitors before
(In reply to Johan Thorén from comment #29)
> I've now verified that the error still occurs with or without that command
> issued, especially when coming back from suspend.
hmm, i was expecting this command to improve the issue, if it would
improve the issue, then we could think of a watermark
Created attachment 144595
New dmesg 2019-06-19 running drm-tip
James, the issue persists running drm-tip as of today.
--
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/1727662
Title:
I've done some additional testing, and after issuing 'echo "2 0 0 0 0 0
0 0" > /sys/kernel/debug/dri/0/i915_pri_wm_latency' I ran for over 2
hours without any freeze, and I tried to provoke the error by switching
resolution and screen layout several times.
--
You received this bug notification
Hi johan,
I need few inputs.
1. Is this issue is seen when u connect a external display directly to
laptop without dock ?
2. Have u screen the display tear issue on embedder panel of laptop.
3. As i see from dmesg logs your external display resolution is
1920x1080, have u observed the issue
Hello! I think i got the same issue.
Using a Thinkpad T440 with a Dockingstation (Ultra Dock) using two external
Monitors.
The attached kernel.log contains all infos from the time i unlocked my laptop
until i turned it off because it is completly frozen.
I cannot reproduce it, but it occures
Alexander Kops, to keep this relevant to upstream, one would want to
periodically check for, and test the latest mainline kernel (now
5.4-rc3) as it is released, to confirm if the drm-tip improvements have
been made available for inclusion into Ubuntu.
Could you please advise?
** This bug is no
*** This bug is a duplicate of bug 1550779 ***
https://bugs.launchpad.net/bugs/1550779
Same problem on Dell Lattitude 5591 with K17A USB C Dock. Laptop crashed
after screen lock.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
*** This bug is a duplicate of bug 1550779 ***
https://bugs.launchpad.net/bugs/1550779
** Tags added: cscc
--
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/1727662
Title:
[Lenovo
*** This bug is a duplicate of bug 1550779 ***
https://bugs.launchpad.net/bugs/1550779
** This bug has been marked a duplicate of bug 1550779
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO
underrun
--
You received this bug notification because you are a member
** Changed in: linux
Importance: High => Medium
--
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/1727662
Title:
[Lenovo ThinkPad T450s] Issues after docking and locking:
** Changed in: linux
Status: Incomplete => Confirmed
--
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/1727662
Title:
[Lenovo ThinkPad T450s] Issues after docking and locking:
Would appreciate feedback on the data given, if more is needed or if a
separate bug report should be filed. Thanks.
--
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/1727662
Title:
[Lenovo
Created attachment 143608
Video showing the screen
--
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/1727662
Title:
[Lenovo ThinkPad T450s] Issues after docking and locking:
Created attachment 143607
dmesg
Here is my dmesg output with the requested parameters. I'm now running
the 5.0.0 kernel with the same behavior. The trigger is sometimes a
xrandr change, but almost always coming back from suspend. Reboot is
necessary.
--
You received this bug notification
** Changed in: linux
Status: Confirmed => Incomplete
--
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/1727662
Title:
[Lenovo ThinkPad T450s] Issues after docking and locking:
(In reply to Johan Thorén from comment #19)
> This error still occurs on kernel 4.20.
>
> My model is T470s and the behavior is consistent: It only happens when
> connected to an external display through the dock, not when using it
> disconnected from the dock. Can (most of the time) be triggered
Launchpad has imported 20 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=103643.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Tags removed: latest-bios-1.30
** Tags added: bios-outdated-1.35
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Same Problem seems to occur on my T480s with Thinkpad Ultra Docking
station and two external displays.
After booting and login, all displays work, but after executing:
# xrandr --output DP2-3 --rotate left
Display DP2-3 does not display anything any more, even though xrandr claims it
should:
Hi, I would like to confirm this as this also affects not only my client
but also my Colleagues (thinkpad T460s and T470s). The Problem seem to
occur after a few minutes of inactiviy randomly. Some experience this
3-4 times/day while some 2-5 times a week.
Running on Ubuntu Bionic 18.04
Kernel
** Changed in: linux (Ubuntu)
Status: Triaged => Confirmed
--
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/1727662
Title:
[Lenovo ThinkPad T450s] Issues after docking and locking:
Sounds like the Dock is losing its network connection (I'm assuming its wired
to the NIC on the dock)
When this issue occurs again, remove the network cable from the dock and try
logging in. If it lets you in - The dock may be in some sort of power save
mode stopping network connectivity.
for
** Changed in: linux
Status: Incomplete => Invalid
--
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/1727662
Title:
[Lenovo ThinkPad T450s] Issues after docking and locking:
Here is my syslog
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5110429/+files/syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I am also observing this issue on a Thinkpad T470s using a Thinkpad
Ultra Type 40A2 dock.
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5110416/+files/kern.log
--
You received this bug notification because you are a member of Kernel
I primarily observe this issue when manually turning on my monitor after
unlock, after it fails to autowake. The problem appears to occur at Apr
11 09:08:41 in the attached kern.log.
Running on Ubuntu 16.04
/proc/version:
Linux version 4.13.0-36-generic (buildd@lgw01-amd64-033) (gcc version
Christopher, I am trying to provide debugging information for myself and
the Ubuntu developers. I have NOT asked anybody to perform a root cause
analysis, debug my problem, or perform any video review. I have only
asked if the observed behavior in the bug in this thread is similar to
the one I am
lanrat, Launchpad is a development platform, for Ubuntu users to provide
debugging information of problems for developers to review, and fix.
Asking folks to review a video without providing debugging information
is unhelpful here.
--
You received this bug notification because you are a member
Christopher, I apologize if I am miscommunicating.
All I am asking is if what you are observing is similar to the video I
posted, nothing more.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
lanrat, nobody can root cause your issue simply by reviewing a video.
However, posting a report allows developers to review debugging logs for
root causing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Christopher, the purpose of my question was because, after some
research, I do not think that this is a device specific issue, and is
actually the result of the kernel and graphics card. Hence why I posted
the video to see if you are all seeing the same issue or if it is
unrelated.
--
You
lanrat, in order to address your issue, it will help immensely if you use the
computer the problem is reproducible with, and file a new report with Ubuntu
via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a member of
I think I am having the same issue on my DELL XPS 13 with intel graphics
(no dock).
Is this what you are all seeing?
https://www.youtube.com/watch?v=2g2GRca3nik
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
As reported upstream, when I used the drm-tip kernel I didn't see the FIFO
error message in the logs again (but still had random power downs).
I'm running the mainline kernel 4.15.0-041500rc8-generic and also don't see any
of the described issues anymore (although I still have 1-2 random
Hi Alexander. Thanks for your bug report and all your effort to troubleshoot
and fix this weird issue.
I'm not using any docking station but I'm experiencing the same behaviour
(screen flickering and unable to lock my screen) here on a Lenovo T450s with a
Intel HD Graphics 5500 (Broadwell GT2)
** Description changed:
What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the
following three things happen ~50% of the time when I come back to unlock it:
* Most of the time the computer
** Changed in: linux
Status: Unknown => Incomplete
** Changed in: linux
Importance: Unknown => High
--
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/1727662
Title:
[Lenovo
** Also affects: linux via
https://bugs.freedesktop.org/show_bug.cgi?id=103643
Importance: Unknown
Status: Unknown
--
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/1727662
So I was just able to reproduce the shut-down issue with the kernel
4.14.0-041400rc8-generic and the debugging flags enabled.
I submitted a kern.log to the upstream bug report.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Alexander Kops:
"2) I know, I'm trying to reproduce the issue with "drm.debug=0x1e
log_buf_len=1M" added right now, and will add the information later"
If it's not reproducible in drm-tip, if reproducible in mainline then
one could take this debug log from there. This will given them a hint on
1) Currently trying to reproduce
2) I know, I'm trying to reproduce the issue with "drm.debug=0x1e
log_buf_len=1M" added right now, and will add the information later
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Alexander Kops, couple of issues:
1) To clarify, after the firmware update, is the issue still reproducible with
latest mainline?
2) Your upstream post is missing all the information requested by Intel as
documented in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/30 .
Some updates:
* I cross posted the issue to the freedesktop bugtracker here:
https://bugs.freedesktop.org/show_bug.cgi?id=103643
* I got my docking station firmware updated, it is now at 2.33.00.
Unfortunately I was not able to determine what the previous version was
* I'm running with the
Alexander Kops, to advise, if you can't reproduce in drm-tip, still
report it as per their instructions as it's reproducible in mainline
(i.e. upstream issue).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ok, I'll install the drm-tip kernel from http://kernel.ubuntu.com
/~kernel-ppa/mainline/drm-tip/current/ , try to reproduce it there, and
report it to Intel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
- What happens is after I dock my laptop, lock it via clicking the lock icon,
and wait ~30 minutes, one of the following three things happen ~50% of the time
when I come back to unlock it:
+ What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type
Alexander Kops:
>"1) It's a lenovo ThinkPad Ultra Dock Type 40A2 20V I didn't know docking
>stations had firmwares up until now. Is there a way to find out via Ubuntu?
>Otherwise I have to talk to my company helpdesk about it."
While I'm not sure how to check via Ubuntu, the path of least
** Summary changed:
- Crashes after unlock: [drm:intel_cpu_fifo_underrun_irq_handler [i915]]
*ERROR* CPU pipe A FIFO underrun
+ [Lenovo ThinkPad T450s] Issues after docking and locking:
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO
underrun
--
You received this bug
** Description changed:
- After upgrading from Ubtuntu 17.04 to Ubuntu 17.10 this bug started appearing.
- When I lock my screen on my Lenovo T450s and the notebook sits in the dock
(two external screens attached), one of the three things happen when I come
back after some time and try to
1) It's a lenovo ThinkPad Ultra Dock Type 40A2 20V
I didn't know docking stations had firmwares up until now. Is there a way to
find out via Ubuntu? Otherwise I have to talk to my company helpdesk about it.
2) Ok, will report it there. Do I have to try with another kernel again? Since
the
Alexander Kops:
1) What is the manufacturer, model, and firmware version of your docking
station?
2) Your recent logs much better confirm the root cause. Hence, could you please
cross post this issue to Intel following their instructions for 1.1-DRM KERNEL
via
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.14-rc8
--
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/1727662
Title:
Crashes after unlock:
Regarding your other questions:
1) The issues have not happened without locking so far. Everything works
smoothly when I don't lock (so that's why my workaround is to not lock the
screen when I'm only away for short, although it's against company policies...)
2) When docked in the docking
Syslog from todays crash with 4.14.0-041400rc8-generic
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5005424/+files/syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Today I installed 4.14.0-041400rc8-generic
I had a crash again, this time the computer did not power down but I came back
to a completely frozen lock screen (only visible on the main monitor, not the
secondary screens), so I had to hard reboot.
I'll attach kern.log and syslog
** Attachment
Alexander Kops, yes please. Also, it would be helpful to attach the
information via SSH or netconsole via
https://help.ubuntu.com/community/DebuggingSystemCrash .
In addition, to follow up:
1) Have the issues happened without having to lock the computer (i.e. during
active daily use, with the PC
So if I got you right, additionally you want me to install the latest
mainline 4.14-rc8, reproduce the bug there and then attach kern.log and
syslog here?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Alexander Kops, to advise, if the root cause problem is drm-intel (I'll
let Kai-Heng Feng speak to this as the root cause since he asked you to
test this), and this is confirmed an issue in the latest mainline kernel
(which is now 4.14-rc8) then testing drm-intel makes sense.
This is due to how
The kern.log
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5004796/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
So I used the kernel at drm-intel-nightly/current/
It ran fine the whole day, but now I saw again that the notebook was shut down
after locking the screen and coming back after half an hour.
But I'm not sure if it's the same bug, since I don't see any of the error
messages previously reported in
Please try kernel here http://kernel.ubuntu.com/~kernel-ppa/mainline
/drm-intel-nightly/current/.
If the same issue still happens, file an upstream bug at:
http://bugzilla.freedesktop.org
Product: DRI
Component: DRM/Intel
--
You received this bug notification because you are a member of Kernel
1) I forgot to mention that I removed "i915.enable_rc6=0" after I tried the
first mainline kernel. So everything after that was already with RC6 enabled.
2) I'll try to reproduce it with the latest mainline kernel on Monday and
attach the requested files.
4) I can't hear the fan and the
Alexander Kops:
1) Could you please remove the kernel parameter "i915.enable_rc6=0", and any
other non-default kernel parameters and keep it that way going forward? It is
best to keep this as close to the default configurations as possible.
2) Could you please reproduce the problem with the
** Tags removed: bios-outdated-1.30
** Tags added: latest-bios-1.30
--
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/1727662
Title:
Crashes after unlock:
Here the screen lock settings in English again.
** Attachment added: "screen-lock-settings.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5003089/+files/screen-lock-settings.png
--
You received this bug notification because you are a member of Kernel
Note that I usually lock the screen manually via the top right menu when
I leave the computer.
--
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/1727662
Title:
Crashes after unlock:
Here a screenshot of the energy settings (switched language to english).
I'm not sure if there is any other setting where I could influence the
behaviour.
** Attachment added: "energy-settings.png"
Automatic locking is set to on after 3 minutes.
** Attachment added: "lockscreen.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5003087/+files/lockscreen.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Alexander Kops, I'd like to circle back on some issues I raised that
were unaddressed/unanswered in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/10:
1) Please make a comment to if you have the GUI setup to suspend and/or
hibernate after a set amount of time, and how long
Somebody else seems to have a similar problem:
https://bugzilla.redhat.com/show_bug.cgi?id=1506339
--
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/1727662
Title:
Crashes after unlock:
I updated my BIOS to the current version
~ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
JBET66WW (1.30 )
09/13/2017
It didn't fix the [Firmware Bug] lines in the syslog though
Also the actual bug still appears. There seem to be some lines in the log that
I haven't seen
Oh, right now I'm running on the BIOS version
JBET51WW (1.16 )
07/08/2015
That's indeed a lot behind the current one. I'll try to update and report back.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Alexander Kops, to advise, posting small snips of syslog, or any log for
that matter, isn't helpful, as what you posted could be a result of some
other issue earlier in the log. Instead, you would want to post the log
in its entirety, and advise when in the log you performed an action
correlated
Tried it now with kernel 4.14.0-041400rc7-generic and it still appears.
(Notebook sits in dock, locked the screen, let it sit for 45 minutes,
came back to computer being shut down).
In /var/log/syslog I find
Nov 1 10:01:05 xxx kernel: [ 404.329288]
[drm:intel_cpu_fifo_underrun_irq_handler
Hi
1) When using the current kernels 4.13.0-16-generic or 4.13.0-16-lowlatency it
is insofar reproducible, that it happens most of the time (I'd say more than
50%).
But not every time, that's why I'm not confident to say the bug is fixed after
one or two unlocks.
2) Yes, I think it only
Alexander Kops, to clarify:
1) When using the Ubuntu kernel, is the issue consistently reproducible?
2) You mention in your Bug Description:
>"...one of the three things happen when I come back after some time and try to
>unlock (so it went to power save in-between)"
Are you stating that only
So I tried to reproduce it with the kernel v4.14-rc6
(bb176f67090ca54869fc1262c913aa69d2ede070)
I tried to get that error for an hour with some lock/unlock, suspend and
hibernate cycles but it didn't appear.
Unfortunately I can't test it for a whole working day, since the internet is
not
Alexander Kops, thank you for reporting this and helping make Ubuntu
better.
In order to allow additional upstream developers to examine the issue, at your
earliest convenience, could you please test the latest upstream kernel
available from
Another thing I found in /var/log/kern.log inbetween the FIFI underrun
messages is this:
Oct 26 09:32:02 ako-notebook kernel: [58379.446230] [ cut here
]
Oct 26 09:32:02 ako-notebook kernel: [58379.446267] WARNING: CPU: 2 PID: 2653
at
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1727662
Title:
Crashes after unlock:
One thing that I tried was disabling RC6 in grub, but that didn't seem to help:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_rc6=0"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I upgraded from Ubtuntu 17.04 to Ubuntu 17.10 and this bug started appearing
(didn't have this with the versions before).
When I lock my screen on my Lenovo T450s and the notebook sits in the dock (two
external screens attached), one of the three things happen when I come
93 matches
Mail list logo
