Summary: | system crash randomly with no errors | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Marco Boffo <marcoboffo.waves> | ||||||||||
Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> | ||||||||||
Status: | RESOLVED MOVED | QA Contact: | |||||||||||
Severity: | critical | ||||||||||||
Priority: | medium | ||||||||||||
Version: | XOrg git | ||||||||||||
Hardware: | x86-64 (AMD64) | ||||||||||||
OS: | Linux (All) | ||||||||||||
Whiteboard: | |||||||||||||
i915 platform: | i915 features: | ||||||||||||
Attachments: |
|
Description
Marco Boffo
2014-10-30 08:55:51 UTC
Please attach the dmesg output here, and preferably the output of glxinfo and the Xorg.0.log file as well. Does anything appear in dmesg when the problem occurs? Created attachment 108677 [details]
Full dmesg
Created attachment 108678 [details]
full glxinfo
Created attachment 108679 [details]
Xorg.0.log
Comment on attachment 108679 [details]
Xorg.0.log
I guess you're using a recent version of gdm which prevents the X server from writing to /var/log/Xorg.0.log. You'll probably need to look for the X server log output in the systemd journal.
By issuing this: journalctl -e /usr/bin/Xorg the log appears empty ~ ~ ~ ~ -- Logs begin at ven 2014-10-03 11:22:44 CEST, end at gio 2014-10-30 10:38:17 CET. -- This problem seems vanished when I got the last kernel update: 3.17.2-1-ARCH. (In reply to Marco Boffo from comment #7) > This problem seems vanished when I got the last kernel update: 3.17.2-1-ARCH. Oh, it's not vanished. It happens only less times. -- 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/drm/amd/issues/553. |
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.