Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc5/
If the issue persists, please file an upstream bug at
https://bugs.freedesktop.org/
Product: DRI
Component: DRM/intel
--
You received this bug notification because you are a member of Kernel
Packages,
Thanks for those logs. They show the problem happening immediately, as
soon as 2.5 seconds after the kernel starts.
This bug is now assigned to the kernel ('linux' component). I believe
this is a kernel bug, if not a hardware fault.
--
You received this bug notification because you are a member
This time I turned off the displayed, unplugged it, then left it
unplugged while I rebooted. After rebooting and logging in, I turned on
the display and plugged it in. Attached is the dmesg from this boot.
** Attachment added: "dmesg from functional boot"
** Attachment added: "journalctl -b0 from successful screen activation"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5270412/+files/journal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Thanks. You seem to have a few different crashes in the i915 kernel
driver still :(
I wonder if they are unique to your CPU/GPU generation or something else
about this machine is unusual...
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: mutter (Ubuntu)
This is still 100% reproducible. I have attached the dmesg below.
** Attachment added: "dmesg from 2019/06/06"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5269157/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
... then if the new kernel log continues to show similar errors we will
have at least narrowed this bug down to the kernel (or a
hardware/connection fault).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks for your efforts.
If you feel you have checked the connections thoroughly then the next
step is to wait until the problem happens again and then run:
dmesg > newdmesg.txt
and send us the file 'newdmesg.txt'.
--
You received this bug notification because you are a member of Kernel
I did plug/unplug the monitor because if I do that enough times is
generally resolves the problem until the next time I reboot. It has not
done so this time. I also tried a new cable, but that does not fix the
problem either.
--
You received this bug notification because you are a member of
Thanks. Your new kernel log shows different crashes in the i915 kernel
driver when using Wayland. In particular, the kernel driver seems to
think the monitor has been unplugged/replugged:
[2.606884] drm_fb_helper_hotplug_event.part.38+0x97/0xc0 [drm_kms_helper]
[2.606887]
It seems unlikely to be a cable or signal problem since I can eventually
coax it into working, and it continues working until I reboot. If it
were a cable problem or something about the signal I would have to
physically modify the connection to create and/or correct the problem.
Since the mere act
** Attachment added: "output of xrandr > xrandr.txt (on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267692/+files/xrandr.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I tried that and it didn't fix the problem. I am attaching the output of
some of those files again for further data.
** Attachment added: "dmesg output ( on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267690/+files/dmesg.txt
--
You received this
** Attachment added: "output of journalctl -b0 > journal.txt (on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267691/+files/journal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
14 matches
Mail list logo
