Hide Forgot
Created attachment 490213 [details] dmesg without X11 Description of problem: LVDS picture is flickering In dmesg log with grub option "drm.debug=0xe" there is a lot of "pipe a underrun" This is only in X11 - first I boot to level 3 ( attachment dmesg_no_x11.txt) there is no "pipe a underrun" (or few) in the log. When I start xfce, and then check dmesg - there is a lot of "pipe a underrun". I attached two files - dmesg_no_x11.txt and dmesg_x11.txt. Version-Release number of selected component (if applicable): Everything is updated. Video: 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04) 00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04) How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 490214 [details] dmesg with X11
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), 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.
This seems to be similar as bug 617617, and bug 655331.
Created attachment 490924 [details] Messages.txt
Created attachment 490925 [details] Second dmesg This dmesg is very demonstrative - when I start to move mouse around "pipe a underrun" doesn't come: [ 770.770220] [drm:i915_driver_irq_handler], pipe a underrun [ 770.783140] [drm:i915_driver_irq_handler], pipe a underrun [ 770.783153] [drm:i915_driver_irq_handler], pipe a underrun [ 770.783158] [drm:i915_driver_irq_handler], pipe a underrun [ 770.783438] [drm:i915_driver_irq_handler], pipe a underrun [ 770.784284] [drm:i915_driver_irq_handler], pipe a underrun [ 771.045040] [drm:intel_crtc_cursor_set], [ 771.045044] [drm:intel_crtc_cursor_set], cursor off [ 771.046400] [drm:intel_crtc_cursor_set], [ 776.680412] [drm:intel_crtc_cursor_set], [ 776.680417] [drm:intel_crtc_cursor_set], cursor off
Ok, want and have to say "Thanks" for new libdrm-2.4.25-1. Results of updating. Very unusual: when I do nothing "pipe a underrun" doesn't come at all. But when I start to do something: typing or move any program window,they starts to go: [ 1594.129626] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.129666] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.129762] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.129893] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.130515] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.130524] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.130710] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.130966] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.134959] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.135380] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.135532] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.135681] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.347493] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.403290] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.403324] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.403343] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.451721] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.451771] [drm:i915_driver_irq_handler], pipe a underrun [ 1594.451817] [drm:i915_driver_irq_handler], pipe a underrun [ 1600.395316] [drm:i915_driver_irq_handler], pipe a underrun [ 1600.395332] [drm:i915_driver_irq_handler], pipe a underrun [ 1600.395353] [drm:i915_driver_irq_handler], pipe a underrun [ 1600.395368] [drm:i915_driver_irq_handler], pipe a underrun [ 1600.490877] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.128390] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.219764] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.245366] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.245548] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.245557] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.245685] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.248243] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.248255] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.248643] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.248830] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.248994] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.262599] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.262614] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.262636] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.262709] [drm:i915_driver_irq_handler], pipe a underrun [ 1601.262770] [drm:i915_driver_irq_handler], pipe a underrun Hope, it will help.
can you try with drm.debug=0xe and see if has anything about fifo entries https://bugs.freedesktop.org/show_bug.cgi?id=22996 may be the upstream bug.
The only thing in fedora dmesg after X11 start about fifo is: [ 2827.431100] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) A: 28 [ 2827.431105] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) B: 31 [ 2827.433042] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) A: 28 [ 2827.433047] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) B: 31 [ 2827.433094] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) A: 28 [ 2827.433099] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) B: 31 [ 2827.480518] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) A: 28 [ 2827.480522] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) B: 31 [ 2827.483033] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) A: 28 [ 2827.483038] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) B: 31 [ 2827.483085] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) A: 28 [ 2827.483090] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) B: 31 [ 2827.529461] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) A: 28 [ 2827.529466] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) B: 31 [ 2827.532034] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) A: 28 [ 2827.532038] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) B: 31 [ 2827.557132] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) A: 28 [ 2827.557136] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) B: 31 [ 2827.649361] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) A: 28 [ 2827.649366] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) B: 31 [ 2827.651033] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) A: 28 [ 2827.651037] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) B: 31 [ 2827.676127] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) A: 28 [ 2827.676132] [drm:i9xx_get_fifo_size], FIFO size - (0x00001d9c) B: 31 And no more. Is there anything else I can check and help?
Installed xorg-x11-drv-intel-2.15.0-1.fc16 on fedora 15. There is no any difference. "pipe a underrun" goes as it was before, when something changes on the screen. I also post dmesg with drm.debug=0xe and 2.15.0-1.fc16.
Created attachment 492440 [details] dmesg with 2.15.0-1.fc16
Additionally want to say that gears in glxgears doesn't rotate at all (2-5 fps)
I installed F15 and got the same "pipe a underrun" every time something changes on the screen. If nothing happen - there is no "pipe a underrun". As long screen picture is awful (flickers) I upgrade to rawhide - and got the same result - a lot of "pipe a underrun". I checked every driver - vesa, fbdev and i915 - there is no any difference. So I would like to ask - can this problem with i915 be solved somehow in the future or you are not going to support it any more. If not I wont be checking it. It is very annoying, really, it is exist since F13.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. 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 '15' 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 15 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