Bug 501256
Summary: | Toshiba M9 Laptop crashes when lid is closed or power state changes on Fedora 10 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Greg Dolph <gdolph-c> |
Component: | xorg-x11 | Assignee: | Richard Hughes <richard> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | mcepl, richard, vedran |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-06 09:24:53 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Greg Dolph
2009-05-18 09:24:38 UTC
I can still SSH onto the system so I know that it's not a total crash. If I killall -9 Xorg X restarts and I can re-login. from the /var/log/Xorg.0.log: EQ Overflowing. The server is probably stuck in an infinite loop! I can still SSH onto the system so I know that it's not a total crash. If I killall -9 Xorg X restarts and I can re-login. from the /var/log/Xorg.0.log: EQ Overflowing. The server is probably stuck in an infinite loop! 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), /var/log/dmesg, and COMPLETE X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance. It's likely a duplicate of bug 464866. *** This bug has been marked as a duplicate of bug 464866 *** |