Wayland Lock Ups #1669
Comments
|
00:02.0 VGA compatible controller: Intel Corporation Meteor Lake-P [Intel Arc Graphics] (rev 08) (prog-if 00 [VGA controller]) |
|
I just spoke with @castrojo and @m2Giles and this is likely an issue with the 6.10 kernel. Our suggestion is to rebase to the You will want to use the command: Let me know if you are running into further issues! |
|
Instead of going for the rebase is it non-trivial to switch from Wayland to
x11?
…On Fri, Sep 13, 2024 at 12:55 PM Noel Miller ***@***.***> wrote:
I just spoke with @castrojo <https://github.com/castrojo> and @m2Giles
<https://github.com/m2Giles> and this is likely an issue with the 6.10
kernel. Our suggestion is to rebase to the :stable image which is still
Fedora 40, but it utilizes the CoreOS Kernel (which is slightly older).
This is the same kernel that gts uses.
You will want to use the command: ujust rebase-helper and select stable.
Here is an article for more information:
https://docs.projectbluefin.io/administration#switching-between-channels
Let me know if you are running into further issues!
—
Reply to this email directly, view it on GitHub
<#1669 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7I67XSPHJAU76IYY6V6X3ZWMKIBAVCNFSM6AAAAABOFOY2KSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBZGQZDENJWGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
X11 session should be available on the login screen with the gear. |
|
The important thing to note is in F41, they are not going to make X11 easy to install anymore, so it's a temporary solution at best. Definitely worth trying to see if it's specifically a Wayland problem on this kernel. |
|
I am now seeing this on X11 while using the stable branch: So it seems X11 is not a workaround? EDIT: From: https://www.reddit.com/r/System76/comments/1fdthbv/darter_pro_darp10_fedora_wayland_freezes/ Another user seeing this on X11:
Seems like a PopOS user but message is the same so likely same kernel bug (likely released earlier in PopOS)? Is there a bug report in fedora or the kernel itself that we can follow? |
Describe the bug
For the past week, using bluefin-dx:latest this system has been locking up. I'm able to use crtl-alt-f4 to get to a virtual terminal and see messages like this in dmesg.
[ 523.454549] i915 0000:00:02.0: [drm] GPU HANG: ecode 12:0:00000000What did you expect to happen?
Expect the system not to crash.
Output of
rpm-ostree statusrpm-ostree status State: busy AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot Transaction: upgrade Initiator: client(id:cli dbus:1.227 unit:ublue-update.service uid:0) Deployments: ● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest Digest: sha256:af63e83ac89602aa83bdd3a9c87b1004adb6fea454e3cae75c8720ab1cd83016 Version: 40.20240911.0 (2024-09-12T18:44:11Z) LocalPackages: redhat-internal-cert-install-0.1-29.el7.noarch redhat-internal-NetworkManager-openvpn-profiles-0.1-61.el7.noarch ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest Digest: sha256:fe590337f2a5b758dae84980cc2a8302107050ad531ee2c53a2aa2d45a687045 Version: 40.20240909.0 (2024-09-11T04:52:52Z) LayeredPackages: libguestfs libguestfs-tools libguestfs-tools-c memtester nmap speedtest-cli LocalPackages: redhat-internal-cert-install-0.1-29.el7.noarch redhat-internal-NetworkManager-openvpn-profiles-0.1-61.el7.noarchOutput of
groupsExtra information or context
The text was updated successfully, but these errors were encountered: