Summary: | Suse11-64 : System hangs on killing the X server with CTRL+ALT+Backspace | ||
---|---|---|---|
Product: | Mesa | Reporter: | samit vats <hysvats> |
Component: | Drivers/DRI/r300 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | critical | ||
Priority: | high | ||
Version: | 7.2 | ||
Hardware: | x86 (IA32) | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Xorg.log
lspci glxinfo xorg.conf |
Description
samit vats
2009-07-29 05:06:26 UTC
Created attachment 28156 [details]
lspci
Created attachment 28157 [details]
glxinfo
Created attachment 28158 [details]
xorg.conf
If this is a regression is there any chance you could use git bisect to track down what commit caused it? Also is there anything drm related in your kernel log after the hang? Does disabling the DRI (Option "DRI" "False") fix it? (In reply to comment #4) > If this is a regression is there any chance you could use git bisect to track > down what commit caused it? Also is there anything drm related in your kernel > log after the hang? Does disabling the DRI (Option "DRI" "False") fix it? > a) This issue is specific to suse11-64. It was observed intermittently in old builds. But with the present builds the frquency of occurence is always. b) After rebooting the /var/log/dump is empty. c) Yes, the issue in not re-produced with Option "DRI" "False" The classic r300 driver has been abandoned long ago. It was replaced by the Gallium driver r300g. If you have issues with r300g please file a new bug report with component Drivers/Gallium/r300 Thanks. |
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.