Created attachment 478978 [details] Dmesg output from console after startup Description of problem: Fedora Rawhide LiveCD - crashes on startup @ mutter Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Download Rawhide LiveCD (tested dsktop-i386-20110214.15.iso) 2. make bootable USB stick, and boot from it. 3. You will get "flashing" screen saying that mutter has crashed No menu, no login screen Actual results: Crash on startup Expected results: I should be able to boot to Desktop Additional info:
Created attachment 478981 [details] dmesg output from Acer6935G (also crash on startup in mutter) segfault: ---------------------- ... [ 45.899676] mutter[1903]: segfault at bfeb8278 ip 037e582e sp bfeb42c0 error 4 in nouveau_dri.so[35f9000+3bf000] [ 47.160702] mutter[2178]: segfault at bf8d45c1 ip 06b9e79b sp bf8ce050 error 4 in nouveau_dri.so[69b2000+3bf000]
Created attachment 478982 [details] Xorg.0.log - crash after manual X restart Xorg.0.log from Acer6935G. Switched to runlevel 3, than back to Runlevel 5. again got message sbaout crash in daemon and mutter. Exited X. Log - attached.
Crash in nouveau driver so reassigning to nouveau X component.
Peter, if you look at first log - on notebook with ATI video chipset (MSI S271) crash is in r300_dri.so ... [ 54.529030] Bluetooth: SCO (Voice Link) ver 0.6 [ 54.529035] Bluetooth: SCO socket layer initialized [ 64.152621] mutter[1753]: segfault at bfbf7fa8 ip 0571032e sp bfbf20d0 error 4 in r300_dri.so[5561000+386000] [ 72.582898] mutter[2031]: segfault at bd6120c8 ip 0315e3b3 sp bfe110a0 error 4 in r300_dri.so[2faf000+386000] Is it possible to have "dual-assignment" in Bugzilla, for nouveau driver and for AMD/ATI r300 driver?
> Is it possible to have "dual-assignment" in Bugzilla, for nouveau driver and > for AMD/ATI r300 driver? Should be 2 different bugs then.
Done. Submitted new bug report #677931 https://bugzilla.redhat.com/show_bug.cgi?id=677931 - for ATI R300 driver.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * ~/.xsession-errors, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 479168 [details] xsession-errors (MSI S271), ATI video
sorry, last xsession-errors is for ATI driver (Bug 677931). I wil add required info for NVIDIA later.
Created attachment 479181 [details] Xorg.0.log - Acer6935G (NVIDIA)
Created attachment 479182 [details] xsession-errors - Acer6935G (NVIDIA)
Created attachment 479183 [details] /var/log/messages - Acer6935G (NVIDIA)
Created attachment 480729 [details] /var/log/messages - Acer6935G, x86_64 - GNOME LiveCD x86_64 - GNOME LiveCD (20110224) boots fine on Acer 6935G notebook. Install to HDD doesn't work, but it's another issue So it seems problem with GNOME/mutter is indeed specific to x86 (32-bit) version of GNOME LiveCD
I think this may in fact be a dupe of 677842, contrary to what I wrote before (sorry). I think the bug with gcc producing bad code on 32-bit seems to affect more than just radeon...
can anyone affected by the 'works on 64-bit, doesn't work on 32-bit' issue please test https://admin.fedoraproject.org/updates/mesa-7.10-0.27.fc15 quickly? Thanks!
I have x86_64 system (Fedora 15) installed on this computer. What additional information is required? Do you want to test lastest 32-bit LiveCD?
Yes, that would be helpful.
Fedora 15 (x86) boots fine on reported system (Acer 6935G) No crash. BTW: host name after boot is localhost.localdomain System doesn't get right (correct) host name from DHCP server, despite I have specific name defined for this system (its mac address). While such workaround has solved this (and may be some other) bug, such behavior is not correct.