Bug 517987
| Summary: | Visiting webpage causes ~hard lock | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andy Lawrence <dr.diesel> | ||||||||||||||||
| Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> | ||||||||||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||||
| Priority: | low | ||||||||||||||||||
| Version: | 11 | CC: | ajax, jspaleta, mcepl, mcepl, xgl-maint | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | i386 | ||||||||||||||||||
| OS: | Linux | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||
| Last Closed: | 2009-11-05 18:50:54 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: | |||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
|
Description
Andy Lawrence
2009-08-18 10:11:32 UTC
Cannot reproduce here, so we need as much information as you can provide. Let's start with this: Please attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and 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. I can confirm.... I'll get you my logs as well. I think ssh still works so I can remote in and pull the logs. Created attachment 357824 [details]
dmesg from affected F-11 laptop
Created attachment 357825 [details]
Xorg.0.log from affected F-11 laptop
Created attachment 357827 [details]
xorg.conf from affected F-11 laptop
Okay the logs and the xorg.conf file were scp'd off the affected system while it was experience the problem without a reboot. If you need me to reconfirm with a different xorg configuration just let me know.
-jef
Created attachment 357848 [details]
dmesg as requested
Created attachment 357849 [details]
Xorg.0.log
Created attachment 357850 [details]
Xorg.0.log.old
Created attachment 357851 [details]
dmesg.old
Please see the attached files. I do not have an xorg.conf and included some of the old files as it was split about the time of the lock-up. Any further info/debugging by request. Thanks Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command yum upgrade --enablerepo='*-updates-testing' Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD . Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.] I can no longer reproduce, closing bug as fixed/closed/now works for me. |