** 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 unlock
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 /drm-in
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 https://01.org/linuxgraphics/docume
** 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: [drm:intel_cpu_fifo_und
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 station
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 adde
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.
https://bugs.launch
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 Ub
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.
https://bugs.launchpad.net/
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 temperat
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 lates
** 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: [drm:intel_cpu_fifo_underrun_irq_h
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
Packages,
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: [drm:in
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"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5003088/+files/energy-s
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: [dr
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 be
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.
https://bugs.launchp
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 to
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 [i91
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 happens
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 the
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 working
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 http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
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 /build/linux-XO_uEE/linux-4.13.0/driv
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.
https://bugs.launchpad.net/bugs/17
32 matches
Mail list logo
