Description of problem: I have a AMILO 4700 2GB, Laptop Intel 855GM Chipsatz, 64 MB Shared Memory Every kernel which worked fine under F10 and XP. Now I get random X crashes under Gnome, KDE and XFCE. And CPUload is 100% ......... If I'm doing nothing, X runs. When I open up some windows, it ocassionally crashes. Other processes work fine, can ssh the machine. The mouse is moveable. Cannot change with ctrl-alt f to a console. Tried the nolapic and vga=normal. Added a Xorg.conf via system-config-display Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start Fedora 12 2. Login Gnome/KDE/XFCE 3. Move Mouse, start some apps or not 4. Screen freezes, Mouse isn't frozen Actual results: Expected results: Additional info:
Holger, could you please attach the portions of your /var/log/messages that I mentioned were of interest in the forum? Thanks! ajax, if you want to get a head-start on this, see the logs attached in: http://forums.fedoraforum.org/showpost.php?p=1283149&postcount=6 -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 366900 [details] Xorglog_dmesg_messages_lspci
Sorry, the attachment didn't upload ....... but now. Regards, Holger BTW, I tried to install ubuntu 9.1 and the 'live' installer crashed the same way. But the mouse was also frozen. I checked back Fedora 10, and it works like a charm. So it really seems to be a kernel problem. Regards, Holger
Created attachment 367584 [details] the nasty chunk from his /var/log/messages this is an extract from the logs attached as a zip file, purely for convenience.
Duplicate : https://bugzilla.redhat.com/show_bug.cgi?id=531111 Intel 855GM harware won't be supported in F12 unless someone knows differently. Exactly the same behaviour exhibited by 2.6.32-rc6 from kernel.org. I've tried to get a stack trace but the debug instructions on the xorg wiki do not work.
'do not work' how, exactly? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** This bug has been marked as a duplicate of bug 531111 ***