Bug 528482 - X freezes at startup or later on Intel hardware (82G33) - Fedora 11.91
Summary: X freezes at startup or later on Intel hardware (82G33) - Fedora 11.91
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 12
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: card_G33
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-12 13:16 UTC by Patrick Proche
Modified: 2018-04-11 10:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 07:29:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
xorg-log (22.45 KB, text/plain)
2009-10-12 13:17 UTC, Patrick Proche
no flags Details
New X log file (21.31 KB, application/octet-stream)
2009-11-26 14:37 UTC, Patrick Proche
no flags Details

Description Patrick Proche 2009-10-12 13:16:23 UTC
Description of problem:
X hangs at startup or just randomly after a while, blank sreen, no mouse pointer, keyboard dead

Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.9.0-2.fc12.x86_64

How reproducible:
Always: X hangs first at startup, after rebooting the second or third startup works fine, then X crashes randomly some time afterwards

Steps to Reproduce:
---

Actual results:
---

Expected results:
---

Additional info:
The problem occurs generally in all window managers: FVWM, Gnome, Xfce, but mostly in FVWM. Xfce seems to be the most stable.

After logging in at the console ans starting for example FVWM, the graphical display flashes up for a split second, the the screen goes blank. If I reboot and start X again, it is usually working, but freezes randomly later. Killing X is not possible because keyboard or mouse are not working anymore. Sometimes (especially when X crashes later), the control lamps on the keyboard blink. 

The system itself does not crash, I can log in via ssh, save the xorg-log (see attachment) and reboot. Killing X via ssh does not solve anything.

I found a description of a similar problem once, and the solution was to downgrade DRM packages, tried this, but it did not work.

Installed X components:

xorg-x11-fonts-ISO8859-9-75dpi-7.2-9.fc12.noarch
xorg-x11-server-common-1.7.0-1.fc12.x86_64
xorg-x11-fonts-truetype-7.1-2.noarch
xorg-x11-drv-sis-0.10.2-1.fc12.x86_64
xorg-x11-proto-devel-7.4-31.fc12.noarch
xorg-x11-server-Xorg-1.7.0-1.fc12.x86_64
xorg-x11-fonts-misc-7.2-9.fc12.noarch
xorg-x11-twm-1.0.3-5.fc12.x86_64
xorg-x11-drv-keyboard-1.3.99.1-1.fc12.x86_64
xorg-x11-fonts-ISO8859-2-100dpi-7.2-9.fc12.noarch
xorg-x11-drv-void-1.3.0-2.fc12.x86_64
xorg-x11-drv-vga-4.1.0-2.1.x86_64
xorg-x11-xauth-1.0.2-7.fc12.x86_64
xorg-x11-drv-openchrome-0.2.903-16.fc12.x86_64
xorg-x11-fonts-ISO8859-9-100dpi-7.2-9.fc12.noarch
xorg-x11-fonts-ISO8859-14-75dpi-7.2-9.fc12.noarch
xorg-x11-server-utils-7.4-11.fc12.x86_64
xorg-x11-drv-vmmouse-12.6.5-2.fc12.x86_64
xorg-x11-font-utils-7.2-9.fc12.x86_64
xorg-x11-fonts-ISO8859-1-75dpi-7.2-9.fc12.noarch
xorg-x11-fonts-75dpi-7.2-9.fc12.noarch
xorg-x11-apps-7.4-5.fc12.x86_64
xorg-x11-drv-mouse-1.4.99.1-2.fc12.x86_64
xorg-x11-fonts-Type1-7.2-9.fc12.noarch
xorg-x11-xkb-utils-7.4-5.fc12.x86_64
xorg-x11-fonts-ISO8859-14-100dpi-7.2-9.fc12.noarch
xorg-x11-fonts-ISO8859-2-75dpi-7.2-9.fc12.noarch
xorg-x11-drv-sisusb-0.9.3-1.fc12.x86_64
xorg-x11-fonts-ISO8859-15-75dpi-7.2-9.fc12.noarch
xorg-x11-xdm-1.1.6-14.fc12.x86_64
xorg-x11-drv-vesa-2.2.1-1.fc12.x86_64
xorg-x11-drv-vmware-10.16.7-2.fc12.x86_64
xorg-x11-fonts-ISO8859-1-100dpi-7.2-9.fc12.noarch
xorg-x11-fonts-syriac-7.1-2.noarch
xorg-x11-drv-ast-0.89.9-1.fc12.x86_64
xorg-x11-fonts-ISO8859-15-100dpi-7.2-9.fc12.noarch
xorg-x11-utils-7.4-6.fc12.x86_64
xorg-x11-drv-dummy-0.3.2-3.fc12.x86_64
xorg-x11-fonts-cyrillic-7.2-9.fc12.noarch
xorg-x11-drv-intel-2.9.0-2.fc12.x86_64
xorg-x11-xfs-utils-1.0.5-6.fc12.x86_64
xorg-x11-drv-evdev-2.2.99-8.20090923.fc12.x86_64
xorg-x11-fonts-100dpi-7.2-9.fc12.noarch
xorg-x11-xinit-1.0.9-12.fc12.x86_64
xorg-x11-xfs-1.0.5-6.fc12.x86_64
xorg-x11-drv-nv-2.1.15-1.fc12.x86_64

Output of lspci:
00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02)
00:02.1 Display controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC Interface Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801IB (ICH9) 2 port SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 Family) 2 port SATA IDE Controller (rev 02)
02:00.0 IDE interface: JMicron Technologies, Inc. JMB368 IDE controller
03:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10)
03:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

Output of uname -a:
Linux CARACAS 2.6.31-i64 #2 Sun Sep 27 15:38:16 CEST 2009 x86_64 x86_64 x86_64 GNU/Linux

Comment 1 Patrick Proche 2009-10-12 13:17:29 UTC
Created attachment 364453 [details]
xorg-log

Comment 2 Matěj Cepl 2009-10-21 00:09:57 UTC
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x49e758]
1: /usr/bin/X (0x400000+0x619a9) [0x4619a9]
2: /lib64/libpthread.so.0 (0x31a0e00000+0xf320) [0x31a0e0f320]
3: /usr/lib64/libdrm_intel.so.1 (0x7fa408f1b000+0x5ade) [0x7fa408f20ade]
4: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fa409138000+0x439db) [0x7fa40917b9db]
5: /usr/bin/X (0x400000+0x28d60) [0x428d60]
6: /usr/bin/X (0x400000+0x2c60c) [0x42c60c]
7: /usr/bin/X (0x400000+0x21c9a) [0x421c9a]
8: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x31a061eb4d]
9: /usr/bin/X (0x400000+0x21849) [0x421849]
Segmentation fault at address 0x8

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting

Comment 4 Matěj Cepl 2009-11-05 17:17:58 UTC
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions).

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Comment 5 Patrick Proche 2009-11-06 12:01:50 UTC
I made every update so far, the last today just before starting X (FVWM). After approx. 1 hour the system crashed again. Sorry, I have no log file of it. If it crashes again, I will send it.

Comment 6 Patrick Proche 2009-11-11 15:12:58 UTC
Despite of all the latest updates, FVWM froze again yesterday. I couldn't get a log file because I could not log in from outside.

Comment 7 Patrick Proche 2009-11-16 10:56:15 UTC
FVWM froze again several times during the last few days. I cannot get a Xorg log file because when FVWM freezes, the network connection seems to get lost, too. I cannot log in from outside with ssh anymore.

I installed all available updates so far.

Comment 8 Bug Zapper 2009-11-16 13:32:58 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Patrick Proche 2009-11-20 17:04:04 UTC
X froze again. I had a little script written which should copy the Xorg.0.log file in case X hangs. I semms that it did not work, so I cannot provide a log for the current crashes.

Comment 10 Patrick Proche 2009-11-25 14:18:33 UTC
FVWM just crashed again. It is not possible to save the Xorg.0.lof file after the crash anymore (login from outside not working, so I had a script running which copies the log file the /tmp every 3 seconds), so it is not only X/FVWM that crashes but the whole machine stops.

Comment 11 Patrick Proche 2009-11-26 14:37:46 UTC
Created attachment 374015 [details]
New X log file

I got this log file from the latest crash. Maybe you can read something out of it.

Comment 12 Bug Zapper 2010-11-04 09:30:16 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 13 Bug Zapper 2010-12-04 07:29:59 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.