We discussed if just the Graphics output might be dead, I'll set up SSH and try to retrigger.
** Description changed: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic (to be specific Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 as seen in the boot log) - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD; with just the laptop screen it works) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected 00000000d293602a, found 000000007548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x00000003, found 0x00000001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 270000, found 540000) - Only resolves with a hard shutdown (5 sec power press), pressing it - shortly doesn't help - also the keyboard shortcuts for and further e.g. - CTRL+ALT+F* does not switch to consoles anymore. + Keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to + consoles anymore. I can only hard reset via 5sec power button. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16 right away. -- 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/1823618 Title: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux-hwe source package in Cosmic: Invalid Bug description: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic (to be specific Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 as seen in the boot log) - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD; with just the laptop screen it works) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected 00000000d293602a, found 000000007548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x00000003, found 0x00000001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 270000, found 540000) Keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to consoles anymore. I can only hard reset via 5sec power button. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16 right away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
