Created attachment 123435 [details] Xorg.0.log Been getting frequent Xorg crashes lately. Here's the stack trace from the latest. I will attach the entire Xorg.0.log. [3809520.740] (EE) [3809520.765] (EE) Backtrace: [3809520.786] (EE) 0: /usr/libexec/Xorg (?+0x0) [0x59ae80] [3809520.793] (EE) 1: /lib64/libc.so.6 (?+0x0) [0x7fb144fb7b1f] [3809520.888] (EE) 2: /usr/lib64/xorg/modules/drivers/intel_drv.so (?+0x0) [0x7fb13fbbc2c0] [3809520.889] (EE) 3: /usr/lib64/xorg/modules/drivers/intel_drv.so (?+0x0) [0x7fb13fc93440] [3809520.889] (EE) 4: /usr/lib64/xorg/modules/drivers/intel_drv.so (?+0x0) [0x7fb13fc95810] [3809520.889] (EE) 5: /usr/libexec/Xorg (?+0x0) [0x5690a0] [3809520.889] (EE) 6: /usr/libexec/Xorg (?+0x0) [0x56a290] [3809520.900] (EE) 7: /usr/libexec/Xorg (?+0x0) [0x4366e0] [3809520.900] (EE) 8: /usr/libexec/Xorg (?+0x0) [0x43a590] [3809520.900] (EE) 9: /lib64/libc.so.6 (?+0x0) [0x7fb144fa3490] [3809520.900] (EE) 10: /usr/libexec/Xorg (?+0x0) [0x424cc0] [3809520.967] (EE) 11: ? (?+0x0) [0x0] [3809520.967] (EE) [3809520.968] (EE) Segmentation fault at address 0x80 [3809520.968] (EE) Fatal server error: [3809520.968] (EE) Caught signal 11 (Segmentation fault). Server aborting [3809520.968] (EE) [3809520.968] (EE) Happy to provide any additional information needed to chase these down.
Insufficient clue I'm afraid. Can you please try running with xf86-video-intel and then converting the addresses into symbolic locations using addr2line? I can give you the exact commandline to use if you can build from https://cgit.freedesktop.org/xorg/driver/xf86-video-intel/
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/109.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.