Hide Forgot
Description of problem: I've a ACER 5601 AWLMi Laptop with ATI Mobility X1300 Graphic card and using the open source drivers that comes with the F16 distro. The system seems to work ok until it suddenly freeze. It must be rebooted to recover and all your work will be gone, which is very bad at all. When I could use the ATI proprietary Catalyst drivers it never happened. But now the new Catalyst drivers are not compatible with my card and the old drivers are not compatible with Xorg. I must use the open source fedora drivers. Version-Release number of selected component (if applicable): Fedora 16 kernel 3.1.0-7.fc16.i686 #1 SMP It happened in Fedora 15. How reproducible: It happens randomly but often when mouse scrolling in any application or watching a online flash stream. Steps to Reproduce: 1. Watch an online flash TV stream 2. Do mouse scrolling in a webpage or document. (not so often) 3. Actual results: CPU overheat messages in log file Expected results: Should no have those messages and the system should not freeze. Additional info:
When it's in freeze status I can switch to console and read the following log messages: Nov 13 22:41:52 vivaldi kernel: [ 9360.884381] CPU0: Core temperature above threshold, cpu clock throttled (total events = 107956) Nov 13 22:41:52 vivaldi kernel: [ 9360.885360] CPU0: Core temperature/speed normal Nov 13 22:42:53 vivaldi kernel: [ 9422.403003] CPU1: Core temperature above threshold, cpu clock throttled (total events = 32328) Nov 13 22:42:53 vivaldi kernel: [ 9422.403979] CPU1: Core temperature/speed normal Nov 13 22:43:21 vivaldi kernel: [ 9450.000060] [Hardware Error]: Machine check events logged Nov 13 22:44:20 vivaldi kernel: [ 9509.671260] libfcoe_device_notification: NETDEV_UNREGISTER lo Nov 13 22:44:33 vivaldi dbus[1015]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Nov 13 22:44:33 vivaldi dbus-daemon[1015]: dbus[1015]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Nov 13 22:44:33 vivaldi dbus-daemon[1015]: Launching FprintObject Nov 13 22:44:33 vivaldi dbus[1015]: [system] Successfully activated service 'net.reactivated.Fprint' Nov 13 22:44:33 vivaldi dbus-daemon[1015]: dbus[1015]: [system] Successfully activated service 'net.reactivated.Fprint' Nov 13 22:44:33 vivaldi dbus-daemon[1015]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Nov 13 22:44:33 vivaldi dbus-daemon[1015]: ** Message: entering main loop I can also do a Ctrl-Alt-BS, Xorg restarts but the system remains freeze. Mouse pointer still respond anyway but I'm not able to do anything. Just a reboot will make my system work with graphics again.
It's seems to be somehow related to wifi buffer data. when streaming from yahoo sometimes the streaming stops with no more buffer until I pause the video and data comes in again to buffer. If I do that repeatedly and do scrolling on the browser I increase the probability of freezing. Maybe the system is not managing properly my video card memory or the system shared memory.
Closing the laptop lit or by pressing the laptop sleep key combination on the keyboard (to hibernate) and open it again (to wake it up) sometimes resolves the X11 crash.
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), X server log file (/var/log/Xorg.*.log) and the output of "dmesg" to the bug report as individual uncompressed text/plain file attachments using the bugzilla file attachment link above called "Add an attachment". Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thank you in advance. --- Jason Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. --- Jason Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers