Since Linux-image-4.13, as soon as the laptop screen is closed on my inspiron 1545 with Debian Stretch, my VGA monitor start to display an infinite amount of (white?) horizontale line. So much that it hide everything and the display is unusuable. The bug happen as soon as Systemd is starting services. If i open my laptop screen again everything become normal. Same thing on the Gnome desktop. Kernel from 4.9 to 4.12 work correctly, 4.13, 4.14, 4,15 and 4.15 + drm-next have the bug. Closing my laptop screen with Xrander or gnome-control-center produce the same bug on my VGA monitor too.I tried to pass numerous kernel parameter found on the web but no one worked. I can submit a picture if it helps. -----some information------ description: Host bridge produit: Mobile 4 Series Chipset Memory Controller Hub fabriquant: Intel Corporation identifiant matériel: 100 information bus: pci@0000:00:00.0 version: 07 bits: 32 bits horloge: 33MHz *-display:0 description: VGA compatible controller produit: Mobile 4 Series Chipset Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@0000:00:02.0 version: 07 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:27 mémoire:f6c00000-f6ffffff mémoire:e0000000-efffffff portE/S:efe8(taille=8) mémoire:c0000-dffff *-display:1 NON-RÉCLAMÉ description: Display controller produit: Mobile 4 Series Chipset Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2.1 information bus: pci@0000:00:02.1 version: 07 bits: 64 bits horloge: 33MHz fonctionnalités: pm bus_master cap_list configuration: latency=0 ressources: mémoire:f6b00000-f6bfffff ------------------------ [root@debian /home/masou]# cat /home/masou/syslog-linux-image-4.9 | grep -i vga Feb 7 11:07:10 debian kernel: [ 0.000000] Console: colour VGA+ 80x25 Feb 7 11:07:10 debian kernel: [ 0.440042] vgaarb: setting as boot device: PCI:0000:00:02.0 Feb 7 11:07:10 debian kernel: [ 0.440110] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none Feb 7 11:07:10 debian kernel: [ 0.440227] vgaarb: loaded Feb 7 11:07:10 debian kernel: [ 0.440302] vgaarb: bridge control possible 0000:00:02.0 Feb 7 11:07:10 debian kernel: [ 3.117866] [drm] Replacing VGA console driver Feb 7 11:07:10 debian kernel: [ 3.145728] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Feb 7 11:07:10 debian kernel: [ 3.225110] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work. Feb 7 11:08:22 debian /usr/lib/gdm3/gdm-x-session[2590]: (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support Feb 7 11:08:23 debian /usr/lib/gdm3/gdm-x-session[2590]: (II) modeset(0): Output VGA-1 has no monitor section Feb 7 11:08:23 debian /usr/lib/gdm3/gdm-x-session[2590]: (II) modeset(0): EDID for output VGA-1 Feb 7 11:08:23 debian /usr/lib/gdm3/gdm-x-session[2590]: (II) modeset(0): Printing probed modes for output VGA-1 Feb 7 11:08:23 debian /usr/lib/gdm3/gdm-x-session[2590]: (II) modeset(0): Output VGA-1 connected Feb 7 11:08:23 debian /usr/lib/gdm3/gdm-x-session[2590]: (II) modeset(0): Output VGA-1 using initial mode 1920x1080 +0+0 ----------------------------------- [root@debian /home/masou]# cat /home/masou/syslog-linux-image-4.15 | grep -i vga Feb 7 11:15:46 debian kernel: [ 0.000000] Console: colour VGA+ 80x25 Feb 7 11:15:46 debian kernel: [ 0.361232] pci 0000:00:02.0: vgaarb: setting as boot VGA device Feb 7 11:15:46 debian kernel: [ 0.361232] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none Feb 7 11:15:46 debian kernel: [ 0.361232] pci 0000:00:02.0: vgaarb: bridge control possible Feb 7 11:15:46 debian kernel: [ 0.361232] vgaarb: loaded Feb 7 11:15:46 debian kernel: [ 4.870793] [drm] Replacing VGA console driver Feb 7 11:15:46 debian kernel: [ 4.887516] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Feb 7 11:15:46 debian kernel: [ 4.969795] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work. Feb 7 11:18:51 debian /usr/lib/gdm3/gdm-x-session[2446]: (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support Feb 7 11:18:51 debian /usr/lib/gdm3/gdm-x-session[2446]: (II) modeset(0): Output VGA-1 has no monitor section Feb 7 11:18:51 debian /usr/lib/gdm3/gdm-x-session[2446]: (II) modeset(0): EDID for output VGA-1 Feb 7 11:18:51 debian /usr/lib/gdm3/gdm-x-session[2446]: (II) modeset(0): Printing probed modes for output VGA-1 Feb 7 11:18:51 debian /usr/lib/gdm3/gdm-x-session[2446]: (II) modeset(0): Output VGA-1 connected Feb 7 11:18:51 debian /usr/lib/gdm3/gdm-x-session[2446]: (II) modeset(0): Output VGA-1 using initial mode 1920x1080 +0+0
I finally found a temporary solution for this bug. If I remove the laptop battery the bug don't happen! So this bug seem to be related to power management! So maybe the solution would be to disable any kind of power management when something else than a LVDS screen is connected. At least for this kind of graphic card!
Finally removing the battery didn't solve the problem completly. That's very weird because I can boot my computer 10 time in a row without any problem. the next 10 times my VGA screen is corrupted! But it's not a hardware failure because this bug only happen since Kernel 4.13 when my laptop screen is closed. There is something very strange with the way the i915 module handle a second monitor since 4.13.
Hello Maximeqc, Do you have an idea of what commit introduced the issue for you? Have you tried with i915_enable_rc6=0 parameter on grub? Could you attach logs (kern log or dmesg) with boot information and debug information(drm.debug=0x1e parameter on grub) with the issue from good and bad commits? Thank you.
Created attachment 137311 [details] syslog-linux-image-4.9
Created attachment 137312 [details] syslog-linux-image-4.14
Created attachment 137314 [details] DRM debug linux-image-4.9 (starting when I close my laptop screen)
Created attachment 137315 [details] DRM debug linux-image-4.14 (starting when I close my laptop screen)
Created attachment 137316 [details] lspci --vvv
I included few attachements from Kernel 4.9 and Kernel 4.14. I can't submit a picture because for some reason picture capture and video capture work correctly even when my external monitor is totaly corrupted! I past many hours on this and compiled few kernel but I'm totaly lost. I suspect the problem started during the devlopment of kernel 4.13 (I mean around linux-image-4.13-RC1). However it's pretty clear in the DRM debug log that kernel 4.14 handle connected screen completly differently than kernel 4.9.
A cellphone photo may help. Which cpu do you have?
Processor: Intel(R) Pentium(R) Dual CPU T3400 @ 2.16GHz. I added a picture I found on the web. It's the same result.
Created attachment 137326 [details] picture
Created attachment 137348 [details] DRM debug linux-image-4.9 (Full log)
Created attachment 137349 [details] DRM debug linux-image-4.14 (Full log)
Today I did some test with Debian testing (Kernel 4.14) and the bug is very less serious. 1)The bug still happen if I disable my laptop screen at boot (video=LVDS-1:d). 2)The bug DOESN'T HAPPEN if I close my laptop screen in Gnome 3.26.2 To summarize: 1)From kernel 4.13, the laptop screen can't be disabled with a kernel parameter or the bug will happen. This is the real problem. 2)With my dual monitor setup, kernel 4.13 and newer are incompatible with Debian Stretch and Gnome 3.22(not really a problem because kernel 4.9 is working great and allow me to disable laptop screen at boot time with video=LVDS-1:d)
(In reply to maximeqc from comment #14) > Created attachment 137349 [details] > DRM debug linux-image-4.14 (Full log) That's incomplete. Please attach the full log from boot 1) all the way to reproducing the problem with video=LVDS-1:d set, and 2) without the parameter.
Created attachment 137408 [details] syslog-linux-image-4.9(video=LVDS-1:d)
Created attachment 137409 [details] syslog-linux-image-4.14(video=LVDS-1:d)
Created attachment 137410 [details] drm-4.9-full(video=LVDS-1:d)
Created attachment 137411 [details] drm-4.14-full(video=LVDS-1:d)
I added log with the "video=LVDS-1:d" kernel parameter. So everything is included! I will continue to investigate and test. I will also test linux-image-4.16RC"X" as soon as it appear in Debian experimental and report the logs.
(In reply to Jani Nikula from comment #16) > "all the way to reproducing the problem" Just close the laptop screen while i915 module is loaded and a VGA monitor is connected! Any way to close the laptop screen will reproduce the bug(Kernel parameter, LID switch,Xrandr,Gnome control-center 3.22)! The exeption is Gnome-shell 3.28 because multi screen is now managed internaly which is great in my case!
First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Jani, any advice here?
Feb 16 20:49:16 debian kernel: [ 4.956125] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work. Worth a shot, though I'm not optimistic that'll fix anything.
I tried that few week ago and it didn't work. I tried kernel 4.16.3 today and same result. This bug is not a big problem for me because I can stick with kernel 4.9 for 4 more years as i'm using Debian Stretch. Then my laptop will have 15 years! I will continue to find a way to solve this before Debian Buster, but if it doesn't work I will stick with kernel 4.9 until it becomes a security concern and then it will be game over!
I tried few minutes ago with 4.17 rc2 and same result.
What if you just disable LVDS with xrandr after you've booted? Does that reproduce the problem or not?
No feedback from many months, closing as resolved works for me. Please re-open if issue persists with latest drm-tip https://cgit.freedesktop.org/drm-tip and send dmesg from boot with kernel parameters drm.debug=0x1e log_buf_len=4M?
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.