Comment 10 for bug 1727662
Revision history for this message
| penalvch (penalvch) wrote Re: Crashes after unlock: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
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 the problem. In this case, the event most correlated to your computer improperly shutting down is the act of locking it.
With this in mind, I'd like to follow up on your comment:
https:/
>"Yes, I think it only happens after suspend though."
It needs to be confirmed without doubt via you checking the GUI settings that your computer is set after you lock the screen that it will only turn off the monitor, only suspend, or turn off the monitor first, then some time after this event, it goes into suspend, etc. Could you please advise to which situation precisely is the case?
Also, with issues like these, folks typically update their buggy, outdated, and insecure BIOS prior to reporting, as BIOS bugs can manifest issues like this. As per your dmesg:
https:/
[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)
...
[ 0.120112] pnp 00:01: [Firmware Bug]: PNP resource [mem 0xfed10000-
In addition, there are numerous BIOS bugs fixed as identified by Lenovo:
https:/
Once updated, could you please post the result of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date