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 https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2017-11-09T11:54:00+00:00 Alexander Kops wrote: I reported this issue in the Ubuntu bug tracker: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662 I was advised to cross post it here. It can be reproduced in the latest Mainline kernel 4.14-rc8 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc8/ but doesn't seem to appear (after 1.5 days of testing) with the current drm-tip build http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ Copying original bug description here: "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 is found shut down. * Sometimes the notebook screen flickers weirdly and one of the two external monitors show pixelation. * The notebook screen shows the lock screen but is completely frozen. Occasionally unlocking works. I have two external monitors attached to the docking station. When I dock my laptop, the battery indicator does recognize its charging. I've not seen this issue when: 1) With the laptop in the dock, while actively using the laptop. 2) With the laptop out of the dock and no external monitors present. This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10. Using or not using the following kernel parameter didn't change anything: i915.enable_rc6=0 PC temperatures are normal as per lm-sensors." Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/35 ------------------------------------------------------------------------ On 2017-11-09T21:02:25+00:00 Elizabethx-de-la-torre-mena wrote: Hello Alexander, Could you share a dmesg or/and kern.log with debug information from boot til problem: drm.debug=0x1e log_bug_len=2M on grub. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/40 ------------------------------------------------------------------------ On 2017-11-09T21:18:32+00:00 Alexander Kops wrote: I'm currently running my computer with the current Mainline kernel (4.14-rc8) and these settings and will post the dmesg as soon as I'm able to reproduce it. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/41 ------------------------------------------------------------------------ On 2017-11-10T12:57:04+00:00 Alexander Kops wrote: Created attachment 135371 kern.log - Crash seemed to happen at 13:31:38 I added a compressed kern.log (the computer shut down at Nov 10 13:31:38 I reproduced the bug running the current Mainline kernel 4.14.0-041400rc8-generic Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/42 ------------------------------------------------------------------------ On 2017-11-13T14:34:17+00:00 Alexander Kops wrote: Created attachment 135436 kern.log with running drm-tip kernel from today - Computer shut down at 15:20:39 Today I was able to reproduce it with the drm-tip kernel found here: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ I attach the kern.log, the computer shut itself down at 15:20:39 This time no messages about a fifo underrun are in the log. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/44 ------------------------------------------------------------------------ On 2017-11-13T16:13:20+00:00 Elizabethx-de-la-torre-mena wrote: (In reply to Alexander Kops from comment #4) > Created attachment 135436 [details] > kern.log with running drm-tip kernel from today - Computer shut down at > 15:20:39 > > Today I was able to reproduce it with the drm-tip kernel found here: > http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ > > I attach the kern.log, the computer shut itself down at 15:20:39 > This time no messages about a fifo underrun are in the log. Hello Alexander, it seems that the log is keeping all the information that you already shared in the first attachment. Could you reproduce with a clean kern.log, since it shuts I guess a dmesg can't be obtained. To clean kern.log: # rm /var/logs/kern.log # reboot The kern.log will regenerate after boot. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/45 ------------------------------------------------------------------------ On 2017-11-13T16:16:35+00:00 Elizabethx-de-la-torre-mena wrote: Also I noticed you marked this bug as a regression, could you please share latest good know kernel commit and bad know commit. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/46 ------------------------------------------------------------------------ On 2017-11-13T16:46:18+00:00 Alexander Kops wrote: Created attachment 135438 kern.log with running drm-tip kernel from today - Computer shut down at 15:20:39 Oops, looks like I re-uploaded the kern.log from last time. This one is the correct one from today. Also the regression tag was added by "Christopher M. Penalver" from the Ubuntu bug tracker. So I can't point to specific kernel commits. I just noticed that it started appearing after using the Kernel shipping with Ubuntu 17.10 and it wasn't happening with the kernel from 17.04 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/47 ------------------------------------------------------------------------ On 2017-11-13T19:35:47+00:00 Elizabethx-de-la-torre-mena wrote: (In reply to Alexander Kops from comment #7) > ... > Also the regression tag was added by "Christopher M. Penalver" from the > Ubuntu bug tracker. So I can't point to specific kernel commits. > I just noticed that it started appearing after using the Kernel shipping > with Ubuntu 17.10 and it wasn't happening with the kernel from 17.04 That would be 4.9 and 4.13, I guess... Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/48 ------------------------------------------------------------------------ On 2017-11-14T14:46:04+00:00 Ville-syrjala-e wrote: (In reply to Alexander Kops from comment #7) > Created attachment 135438 [details] > kern.log with running drm-tip kernel from today - Computer shut down at > 15:20:39 > > Oops, looks like I re-uploaded the kern.log from last time. This one is the > correct one from today. The logs contain multiple boots with multiple different kernels, so it's hard to say what's what. But this log doesn't seem to have any FIFO underruns. So am I to assume this is now fixed? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/49 ------------------------------------------------------------------------ On 2017-11-14T16:01:51+00:00 Alexander Kops wrote: > But this log doesn't seem to have any FIFO underruns. So am I to assume this is now fixed? Well, it is fixed in a sense that these FIFO underruns don't appear anymore with the drm-tip kernel. But the behaviour, that the computer will just turn itself off a lot of times after enabling lock screen is still there. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/50 ------------------------------------------------------------------------ On 2017-11-14T16:19:29+00:00 Alexander Kops wrote: Created attachment 135451 kern.log with running drm-tip kernel from today - Computer froze at 16:17:45 I'll attach this current kern.log. This time the situation was a bit different, I didn't find the notebook turned off, but the power light was still on, but all three screens were black and it didn't react to anything. So I had to hard reboot it. Maybe you can see something in the logs that would lead to a follow up bug report? The last thing I see in the log before the crash are a bunch of [drm:drm_mode_addfb2 [drm]] [FB:87] lines. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/51 ------------------------------------------------------------------------ On 2017-11-14T17:01:10+00:00 Ville-syrjala-e wrote: (In reply to Alexander Kops from comment #11) > Created attachment 135451 [details] > kern.log with running drm-tip kernel from today - Computer froze at 16:17:45 > > I'll attach this current kern.log. This time the situation was a bit > different, I didn't find the notebook turned off, but the power light was > still on, but all three screens were black and it didn't react to anything. > So I had to hard reboot it. > > Maybe you can see something in the logs that would lead to a follow up bug > report? > > The last thing I see in the log before the crash are a bunch of > > [drm:drm_mode_addfb2 [drm]] [FB:87] > > lines. Nothing interesting there unfortunately. So I guess we're dealing with some kind of hard system hang, and it doesn't manage to write anything useful to the logs. So it's not even clear whether this has anything to do with i915, or caused by something totally different. Maybe try netconsole/serial console if the machine has a ethernet/serial port. Or you may want to look into pstore to see if that might catch something when the machine dies. Maybe also enable various debug features in the kernel config: CONFIG_LOCKUP_DETECTOR=y CONFIG_SOFTLOCKUP_DETECTOR=y CONFIG_HARDLOCKUP_DETECTOR=y CONFIG_DETECT_HUNG_TASK=y CONFIG_PROVE_LOCKING=y PS. Your logs are huuuuge. Might want to trim away the unrelated boots from the logs. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/52 ------------------------------------------------------------------------ On 2017-11-15T09:21:23+00:00 Bugs-i wrote: iirc when ubuntu puts system in slumber it first calls a bunch of addfb's for the fade to black animation. It doesn't mean it's the cause of the issue, though could very well be related to dpms off. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/53 ------------------------------------------------------------------------ On 2018-01-23T19:32:08+00:00 Angelo Lisco wrote: I can confirm that this weird issue also happens without a docking station. It happens both with an external screen and without it. system-manufacturer: LENOVO system-version: ThinkPad T450s bios-version: JBET66WW (1.30 ) bios-release-date: 09/13/2017 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/55 ------------------------------------------------------------------------ On 2018-01-24T10:23:25+00:00 Jani-nikula wrote: (In reply to Angelo Lisco from comment #14) > I can confirm that this weird issue also happens without a docking station. > It happens both with an external screen and without it. Alexander Kops, as the original reporter, can you confirm the same without a docking station or external screen? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/56 ------------------------------------------------------------------------ On 2018-01-24T10:26:55+00:00 Alexander Kops wrote: I tried to reproduce it without docking station once, but wasn't able to. But I also don't use the notebook without docking station for longer times usually, so no throughout testing happened. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/57 ------------------------------------------------------------------------ On 2018-03-29T07:10:37+00:00 Jani-saarinen-g wrote: First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/66 ------------------------------------------------------------------------ On 2018-04-20T14:51:26+00:00 Jani-saarinen-g wrote: Closing, please re-open if still occurs. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/70 ------------------------------------------------------------------------ On 2019-03-02T12:31:46+00:00 Johan-freedesktop wrote: 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 by changing display settings through xrandr. Dock model is SD20F82750. Dmesg error message: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun GPU: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/74 ** Changed in: linux Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727662 Title: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1727662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
