Both posted journalctl logs feature sections like this: May 21 11:03:29 asgard kernel: [drm] GPU HANG: ecode 11:0:0x85dffffb, in Xorg [2421], reason: hang on rcs0, action: reset May 21 11:03:29 asgard kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 May 21 11:03:37 asgard kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 May 21 11:03:45 asgard kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 May 21 11:03:53 asgard kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 May 21 11:04:01 asgard kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 May 21 11:04:01 asgard /usr/lib/gdm3/gdm-x-session[2419]: i965: Failed to submit batchbuffer: Input/output error May 21 11:04:01 asgard gnome-calendar[3680]: gnome-calendar: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. May 21 11:04:01 asgard seahorse[3679]: seahorse: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
The GPU stopped responding, so the session falls over. Which makes sense. SO, this does look very much like bug 1872001 - did a bad graphics driver update get backported to the 5.0.0 OEM kernel? @lihow731 Do you need anything else to progress on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
