Bug 100501

Summary: Intel framebuffer causes screen to rapidly move from right to left, and up and around.
Product: Drivers Reporter: Jeff Z (shakuganxxii)
Component: Video(DRI - Intel)Assignee: intel-gfx-bugs (intel-gfx-bugs)
Status: CLOSED CODE_FIX    
Severity: normal CC: intel-gfx-bugs, matt
Priority: P3    
Hardware: x86-64   
OS: Linux   
Kernel Version: 4.1 4.0 Subsystem:
Regression: No Bisected commit-id:
Attachments: My kernel config

Description Jeff Z 2015-06-26 13:33:46 UTC 
Created attachment 180971 [details]
My kernel config

~ # lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
==============================================
Kernel config (4.1):
Device Drivers --->
    Graphics Support --->
        < > /dev/agpgart (AGP Support) ---
        [*] VGA Arbitration
        Direct Rendering Manager --->
            <*> Direct Rendering Manager (Xfree...) --->
                <*> Intel 8xx/9xx/G3x/G4x/HD Graphics
                [*]  Enable modesetting on intel by default
                [*]  Enable legacy fbdev support for modesetting intel driver
# I also have my kernel .config attached
===============================================

So I found out that you can use the Intel framebuffer instead of EFI framebuffer for EFI booting.
But it causes the framebuffer to rapidly move the screen from right to left. Its also slowly moving up as well.

The behavior of this is a bit weird:
- The first time its in framebuffer (boot up time) is ok.
- The first time its in Xorg is ok.
- But when I leave Xorg and into the command line again, it happens
- If I try to go back into Xorg again, it happens. Unless I use a wallpaper using 'feh'

This is on the new Intel Broadwell i7-5500 with HD Graphics 5500.

Here is a video on it: https://youtu.be/NODaj7CsMdE
The first time was with no wallpaper, The second time was with a wallpaper.

I can try to provide more information if you need me to.
Comment 1 Jeff Z 2015-07-07 15:11:26 UTC 
I believe it also caused this: 
======================
~ # cat /sys/kernel/debug/kmemleak
unreferenced object 0xffff8802545c6000 (size 1024):
  comm "kworker/u16:0", pid 6, jiffies 4294667796 (age 10545.196s)
  hex dump (first 32 bytes):
    00 20 83 54 02 88 ff ff 00 00 00 00 00 00 00 00  . .T............
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<ffffffff813be67f>] __intel_set_mode+0x6f/0xc40
    [<ffffffff81111c65>] kmem_cache_alloc+0x95/0xe0
    [<ffffffff813be67f>] __intel_set_mode+0x6f/0xc40
    [<ffffffff813bf9d4>] intel_modeset_compute_config+0x514/0xfd0
    [<ffffffff813c5f26>] intel_crtc_set_config+0xaa6/0xfd0
    [<ffffffff813d7acf>] intel_atomic_commit+0xbf/0xf0
    [<ffffffff8133a525>] drm_atomic_helper_plane_set_property+0x85/0xd0
    [<ffffffff8134ca50>] drm_mode_set_config_internal+0x60/0x100
    [<ffffffff8133bf78>] restore_fbdev_mode+0xb8/0xe0
    [<ffffffff8133dd1b>] drm_fb_helper_restore_fbdev_mode_unlocked+0x1b/0x60
    [<ffffffff8133dd7d>] drm_fb_helper_set_par+0x1d/0x40
    [<ffffffff813d3d81>] intel_fbdev_set_par+0x11/0x60
    [<ffffffff812bbdca>] fbcon_init+0x56a/0x5f0
    [<ffffffff813127fc>] visual_init+0xac/0x110
    [<ffffffff81314bd5>] do_bind_con_driver+0x155/0x330
    [<ffffffff813150c3>] do_take_over_console+0x103/0x1b0
unreferenced object 0xffff880097323800 (size 1024):
  comm "X", pid 3383, jiffies 4296898287 (age 8314.719s)
  hex dump (first 32 bytes):
    00 20 83 54 02 88 ff ff 00 00 00 00 00 00 00 00  . .T............
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<ffffffff813be67f>] __intel_set_mode+0x6f/0xc40
    [<ffffffff81111c65>] kmem_cache_alloc+0x95/0xe0
    [<ffffffff813be67f>] __intel_set_mode+0x6f/0xc40
    [<ffffffff813bf9d4>] intel_modeset_compute_config+0x514/0xfd0
    [<ffffffff813c5f26>] intel_crtc_set_config+0xaa6/0xfd0
    [<ffffffff8134ca50>] drm_mode_set_config_internal+0x60/0x100
    [<ffffffff81350690>] drm_mode_setcrtc+0xd0/0x600
    [<ffffffff81343198>] drm_ioctl+0x308/0x590
    [<ffffffff813505c0>] drm_mode_setcrtc+0x0/0x600
    [<ffffffff81129bd7>] do_vfs_ioctl+0x2e7/0x4f0
    [<ffffffff810f76dd>] vm_mmap_pgoff+0x6d/0xa0
    [<ffffffff8103b1ec>] __do_page_fault+0x16c/0x3b0
    [<ffffffff81129e16>] SyS_ioctl+0x36/0x80
    [<ffffffff8169c697>] system_call_fastpath+0x12/0x6a
    [<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff880213c44c00 (size 1024):
  comm "X", pid 3383, jiffies 4298998144 (age 6214.971s)
  hex dump (first 32 bytes):
    00 20 83 54 02 88 ff ff 00 00 00 00 00 00 00 00  . .T............
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<ffffffff813be67f>] __intel_set_mode+0x6f/0xc40
    [<ffffffff81111c65>] kmem_cache_alloc+0x95/0xe0
    [<ffffffff813be67f>] __intel_set_mode+0x6f/0xc40
    [<ffffffff813bf9d4>] intel_modeset_compute_config+0x514/0xfd0
    [<ffffffff813c5f26>] intel_crtc_set_config+0xaa6/0xfd0
    [<ffffffff8134ca50>] drm_mode_set_config_internal+0x60/0x100
    [<ffffffff81350690>] drm_mode_setcrtc+0xd0/0x600
    [<ffffffff81343198>] drm_ioctl+0x308/0x590
    [<ffffffff813505c0>] drm_mode_setcrtc+0x0/0x600
    [<ffffffff81129bd7>] do_vfs_ioctl+0x2e7/0x4f0
    [<ffffffff810f76dd>] vm_mmap_pgoff+0x6d/0xa0
    [<ffffffff8103b1ec>] __do_page_fault+0x16c/0x3b0
    [<ffffffff81129e16>] SyS_ioctl+0x36/0x80
    [<ffffffff8169c697>] system_call_fastpath+0x12/0x6a
    [<ffffffffffffffff>] 0xffffffffffffffff
unreferenced object 0xffff880252bf7800 (size 1024):
  comm "X", pid 3383, jiffies 4301534510 (age 3678.655s)
  hex dump (first 32 bytes):
    00 20 83 54 02 88 ff ff 00 00 00 00 00 00 00 00  . .T............
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<ffffffff813be67f>] __intel_set_mode+0x6f/0xc40
    [<ffffffff81111c65>] kmem_cache_alloc+0x95/0xe0
    [<ffffffff813be67f>] __intel_set_mode+0x6f/0xc40
    [<ffffffff813bf9d4>] intel_modeset_compute_config+0x514/0xfd0
    [<ffffffff813c5f26>] intel_crtc_set_config+0xaa6/0xfd0
    [<ffffffff8134ca50>] drm_mode_set_config_internal+0x60/0x100
    [<ffffffff81350690>] drm_mode_setcrtc+0xd0/0x600
    [<ffffffff81343198>] drm_ioctl+0x308/0x590
    [<ffffffff813505c0>] drm_mode_setcrtc+0x0/0x600
    [<ffffffff81129bd7>] do_vfs_ioctl+0x2e7/0x4f0
    [<ffffffff810f76dd>] vm_mmap_pgoff+0x6d/0xa0
    [<ffffffff8103b1ec>] __do_page_fault+0x16c/0x3b0
    [<ffffffff81129e16>] SyS_ioctl+0x36/0x80
    [<ffffffff8169c697>] system_call_fastpath+0x12/0x6a
    [<ffffffffffffffff>] 0xffffffffffffffff
=============================

Its causing my system to idle around 1Gb of RAM usage.
Comment 2 Matt Fleming 2015-07-08 14:43:35 UTC 
Not an EFI bug. Reassigning to video drivers.
Comment 3 Jani Nikula 2015-10-20 08:32:33 UTC 
Please try latest v4.3-rc kernel. If the problem persists, please add drm.debug=14 module parameter, and attach dmesg.
Comment 4 Jeff Z 2015-10-20 11:47:58 UTC 
It's been fixed by kernel 4.2 
Sorry for not reporting it.
Comment 5 Jani Nikula 2015-10-20 12:39:34 UTC 
(In reply to Jeff Z from comment #4)
> It's been fixed by kernel 4.2 
> Sorry for not reporting it.

Don't worry about it, thanks for following up.