Ubuntu
linux package

  1. Bug #1727662
  2. Comment #12

Comment 12 for bug 1727662

Revision history for this message
Alexander Kops (alexkops) wrote : Re: Crashes after unlock: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

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 before though

Nov 3 12:37:05 xxx kernel: [ 8137.161988] [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999)
Nov 3 12:37:05 xxx kernel: [ 8137.162024] [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected ffff9818ca8b46e0, found ffff9818ca8b47
78)
Nov 3 12:37:05 xxx kernel: [ 8137.162051] [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999
)
Nov 3 12:37:05 xxx kernel: [ 8137.162076] [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 270000, found 540000)
Nov 3 12:37:05 xxx kernel: [ 8137.162078] pipe state doesn't match!

Can you advise on how to narrow down the error to the actual state where it happens?
Can it be achieved through changing settings in /etc/systemd/logind.conf?
Because currently the only way to reproduce it is locking the screen while the computer is sitting in the docking station and come back after a longer period of time (e.g. 30 minutes)