Created attachment 370342 [details] Log file Description of problem: X-windows freezes in Fedora 12, mouse/keyboard don't work. Only option is to power down the system and restart. How reproducible: always Steps to Reproduce: Actual results: x freezes Expected results: Additional info:
You cannot start X at all, or it freezes after some time of working? Could we get please output of the command dmesg after you start of Xorg (if possilbe), and also /etc/X11/xorg.conf (if you have any)? We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 372482 [details] output of dmesg
(In reply to comment #1) > You cannot start X at all, or it freezes after some time of working? Could we > get please output of the command dmesg after you start of Xorg (if possilbe), > and also /etc/X11/xorg.conf (if you have any)? > > We will review this issue again once you've had a chance to attach this > information. > > Thanks in advance. X starts ok.. But freezes after some time. hmmm.. Don't have /etc/X11/xorg.conf Hope this helps.
This happens in both i686.PAE and regular kernels. (don't know if this is relevant, but thought I would mention it anyway)
I am having this problem too. See Bug #538563. I have included additional log files of each time it locks up; dmesg output; and lspci (-v -vv) output. And I am getting the same error message as you. Do you have an Intel card? 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
Created attachment 373994 [details] Output of lspci -vv
(In reply to comment #5) > I am having this problem too. See Bug #538563. I have included additional log > files of each time it locks up; dmesg output; and lspci (-v -vv) output. And I > am getting the same error message as you. Do you have an Intel card? 00:02.0 > VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset > Integrated Graphics Device (rev 01) Yes, I've an Intel Card with the same chipset as yours (rev 03 though).
*** This bug has been marked as a duplicate of bug 538563 ***