Bug 123603
Summary: | Xorg is crashing when Idle (Matrox DRI ?) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Richard Allen <ra> |
Component: | xorg-x11 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | robert |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-03-06 20:32:35 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Richard Allen
2004-05-19 16:20:58 UTC
I think I figured out whats going on. My machine is a HP NX7010 laptop with a ATI card that is supported in 3D mode in Xorg. I had KDE set to use a 3D screensaver, however I had configured Xorg do use Xinerama when docked at work (head 1 the built in display and head 2 the monitor.). Xinerama apparently disables GL. So after I changed screensavers from Euphoria to blank screen I dont get crashes any more. I'm seeing crashes running 3D screensavers on my Fujitsu Lifebook S6120 Centrino laptop. This is with xorg-x11-6.7.0-2 and kernels kernel-2.6.5-1.358 through kernel-2.6.6-1.383. The relevant part of lspci looks like: 00:00.0 Host bridge: Intel Corp. 82852/855GM Host Bridge (rev 02) 00:00.1 System peripheral: Intel Corp. 855GM/GME GMCH Memory I/O Control Registers (rev 02) 00:00.3 System peripheral: Intel Corp. 855GM/GME GMCH Configuration Process Registers (rev 02) 00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) and the kernel log says: May 25 10:49:41 localhost kernel: [drm] Initialized i830 1.3.2 20021108 on minor 0: May 25 10:49:41 localhost kernel: [drm] Initialized i830 1.3.2 20021108 on minor 1: May 25 10:49:41 localhost kernel: mtrr: base(0xd8020000) is not aligned on a size(0x300000) boundary I'm seeing a problem similar to the original report. However, I'm running an Athlon XP 1700 with a Matrox G550 agp card. Using only one head. Several times I've come back to find X has either crashed and bounced me back to the login screen or is hung running with 100% of the processor. A kill -9 on the process is necessary to return me to the login screen. Typically the applications that are running are Moz, Gaim, and Xscreensaver. I use DPMS power settings on the monitor. My WM is Enlightenment 0.16.6. Can you try the i586 kernel especially the people with Matrox cards and report back if this makes it work. I'm using 2.6.7 compiled from source on my box. I compile it for Athlon. I also downloaded the latest Xscreensaver from jwz 4.16 and built it from source. After doing this I ceased experiencing this problem. My hunch is that the xscreensaver update did the trick. If updating xscreensaver stops the X server or system from crashing, it wasn't a bug in xscreensaver, but rather a bug in either the X server (video driver likely) or kernel. No application should ever be able to crash the system, and while the code in xscreensaver could theoretically be found that triggers the problem, it isn't the cause of the problem. Working around that in the screensaver, just potentially leaves faulty code either in the driver or kernel for something else to eventually trigger. If you've recompiled the kernel itself and the problem is not reproduceable anymore, I would assume the root cause is a kernel bug. Can you set up your old setup that had the problem, and using the original xscreensaver, try to reproduce the issue with your new kernel? I'm assuming this will also resolve the problem, at which point this points to a bug in the kernel mga DRM or some other kernel interaction I believe. Of course that's not conclusive yet without more info, but it's a reasonable hypothesis for now. Thanks in advance, TTYL *** This is an automated comment update *** The X11 implementation included with Fedora Core 2 and 3, is "X.Org X11" provided by the X.Org project located at "http://www.x.org". XFree86 is no longer included in Fedora Core. To ensure faster review and investigation of X related Fedora Core bug reports, please be sure to file the bug against the correct component of "xorg-x11" in the future. Thanks in advance. Reassigning several bugs from XFree86 component to proper xorg-x11 component ... Since this bugzilla report was filed, there have been several major updates to the X Window System, which may resolve this issue. Users who have experienced this problem are encouraged to upgrade to the latest version of Fedora Core, which can be obtained from: http://fedora.redhat.com/download If this issue turns out to still be reproduceable in the latest version of Fedora Core, please file a bug report in the X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg" component. Once you've filed your bug report to X.Org, if you paste the new bug URL here, Red Hat will continue to track the issue in the centralized X.Org bug tracker, and will review any bug fixes that become available for consideration in future updates. Setting status to "CURRENTRELEASE". |