Created attachment 464483 [details] Example Xorg.0.log Description of problem: I did a fresh install of Fedora 14 on a Dell Latitude E5400. Previously the laptop ran Fedora 13 with no problems. When I did the install, I had an external monitor (VGA) attached, and everything worked as expected. A couple days later I powered down and went on the road. When I booted the laptop without an external monitor, the problem started happening. The GDM login screen takes forever to load, and blinks constantly. Keyboard input is often ignored and/or slowly recognized. When I finally get logged in, the system is mostly unusable, and the screen is constantly blinking. The Xorg.0.log grows very large, and it seems as if it is constantly probing the hardware. Version-Release number of selected component (if applicable): kernel is 2.6.35.6-48.fc14.x86_64 The system is completely updated, so every package is at the current level. How reproducible: Steps to Reproduce: 1. Boot laptop without external monitor 2. 3. Actual results: As described above. Expected results: System should behave the same and be responsive whether or not an external monitor is attached. Additional info: If I boot into runlevel 3, and startx into a gnome-session manually, the problem still exists. However, if I change my window manager to icewm in .xinitrc and startx manually, the problem is NOT there. If I plug in an external monitor, the problem goes away. This problem seems related to bug 573200, but that was Fedora 12 and kernel 2.6.32 lscpi -k yields: 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Subsystem: Dell Device 0262 Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Subsystem: Dell Device 0262
Hi, can you try the 2.6.36 kernel from rawhide (you can pull it on top of F-14 out of koji) or the 2.6.37-rc5 kernel from http://repos.fedorapeople.org/repos/kyle/kernel/fedora-kernel.repo and let us know if it helps at all? regards, Kyle
Per your suggestion, I have tried both the 2.6.36 and 2.6.37 kernels, but there was no change in the behavior. It continues to be regularly reproducible.
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 add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, 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 469621 [details] Requested files in .zip format Attached is the dump of dmesg (dmesg.txt) All of the Xorg.*.log files /var/log/messages I'm not using an xorg.conf file for configuration, so none attached.
Created attachment 469870 [details] dmesg.txt from the archive
Created attachment 469871 [details] messages from the archive
Created attachment 469872 [details] Xorg.0.log from the archive
Created attachment 469873 [details] Xorg.1.log from the archive
Created attachment 469874 [details] Xorg.2.log from the archive
Created attachment 469875 [details] Xorg.3.log from the archive
Created attachment 469876 [details] Xorg.4.log from the archive
Created attachment 469877 [details] Xorg.5.log from the archive
Created attachment 469878 [details] Xorg.9.log from the archive
If you boot with: drm_kms_helper.poll=0 on the kernel command line, does that help at all?
Yes, booting with that on the kernel line does help the problem, and it is an adequate workaround. However, that does disable auto polling for changes, so it makes the user experience less than ideal.
Great, well, at least it works around the worst of it for now while we try to fix it. regards, Kyle
Have the same problem on a Dell E5500, drm_kms_helper.poll=0 does not fix the issue. Tried with the 2.6.37 kernel also. F1464bit all update as of today. 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device 0263 Flags: bus master, fast devsel, latency 0, IRQ 43 Memory at f6c00000 (64-bit, non-prefetchable) [size=4M] Memory at e0000000 (64-bit, prefetchable) [size=256M] I/O ports at efe8 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 3 Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Subsystem: Dell Device 0263 Flags: bus master, fast devsel, latency 0 Memory at f6b00000 (64-bit, non-prefetchable) [size=1M] Capabilities: [d0] Power Management version 3
Created attachment 472388 [details] dmesg
Created attachment 472389 [details] xorg.0.log
Forgot to note, F13 did NOT have this issue. Thanks
This is likely a dup of https://bugzilla.redhat.com/show_bug.cgi?id=655432, removing gnome-color-manager fixes the issue.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping