[Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 4.19.26 and later (but 4.19.25 and earlier works)

[Torsten Römer]

Updated from kubuntu 18.10 to 19.04 beta without problems. After first reboot, first the kubuntu logo, then just a blank screen, no login screen. Switching to console and log in there possible. All seems fine, including wlan etc.

systemd status sddm says sddm is running, any attempt to start KDE (including startkde) however fails with "could not connect to any x display".

This happens with Kernel 5.0.0. Starting with 4.18.0-16-generic, the login screen comes up and all is fine.

Anything I can contribute?

Description: Ubuntu Disco Dingo (development branch)
Release: 19.04

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Sat Mar 30 21:51:04 2019
DistUpgraded: 2019-03-30 14:41:04,209 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 1.1.0, 4.18.0-16-generic, x86_64: installed
 acpi-call, 1.1.0, 5.0.0-8-generic, x86_64: installed
 tp_smapi, 0.43, 5.0.0-8-generic, x86_64: installed
 virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21dd]
InstallationDate: Installed on 2017-07-07 (631 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 78545HG
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=ce827244-1d04-4bdd-99bf-d70675baefef ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to disco on 2019-03-30 (0 days ago)
dmi.bios.date: 04/12/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 8GET44WW (1.21 )
dmi.board.name: 78545HG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad L420
dmi.product.name: 78545HG
dmi.product.version: ThinkPad L420
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[Daniel van Vugt (vanvugt)]

It looks like this might be problem:

[ 1277.981] (EE) modeset(0): failed to set mode: Invalid argument

[Daniel van Vugt (vanvugt)]

which is related to what you say:

> This happens with Kernel 5.0.0. Starting with 4.18.0-16-generic, the login screen comes up and all is fine.

[Daniel van Vugt (vanvugt)]

Can you please try some more kernel versions to get a better idea of which version it first broke in?

[Daniel van Vugt (vanvugt)]

Other kernel versions can be found in:

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

[Torsten Römer (dode)]

So I tried a lot of kernels :-)

The latest it still works with was 4.19.25-generic (currently using it).
It fails starting with 4.19.26-generic.

I tried many versions older than 4.19.25-generic, they all worked, and any version later than 4.19.26-generic failed as well.

So it seems something broke in 4.19.26-generic.

[Torsten Römer (dode)]

Also with 4.19.26-generic there is the error:

[ 7.575] (EE) modeset(0): failed to set mode: Invalid argument

[Rosen Papazov (shadowzzz)]

After reverting https://patchwork.freedesktop.org/series/58893/ (commit d179b88deb3bf6fed4991a31fd6f0f2cad21fab5 upstream kernel drm/i915/fbdev) and rebuilding default disco kernel 5.0.0-8-generic everything works as expected. Possible regression in upstream kernel.

[Kai-Heng Feng (kaihengfeng)]

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/i915

[Torsten Römer (dode)]

Created attachment 143902
Xorg Log containing the error

Since kernel 4.19.26 and later (4.19.25 and earlier works), with Intel integrated graphics i915 (Intel® HD Graphics 3000), Xorg fails to start with: "(EE) modeset(0): failed to set mode: Invalid argument".

After reverting https://patchwork.freedesktop.org/series/58893/ (commit d179b88deb3bf6fed4991a31fd6f0f2cad21fab5 upstream kernel drm/i915/fbdev) and rebuilding default disco kernel 5.0.0-8-generic everything works as expected.

This bug was initially reported as: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441

Possible duplicate: https://bugs.freedesktop.org/show_bug.cgi?id=109174

[Torsten Römer (dode)]

Done: https://bugs.freedesktop.org/show_bug.cgi?id=110359

Thanks to all helping out!

[Lakshminarayana-vudum (lakshminarayana-vudum)]

(In reply to Torsten from comment #0)
> Created attachment 143902 [details]
> Xorg Log containing the error
>
> Since kernel 4.19.26 and later (4.19.25 and earlier works), with Intel
> integrated graphics i915 (Intel® HD Graphics 3000), Xorg fails to start
> with: "(EE) modeset(0): failed to set mode: Invalid argument".
>
> After reverting https://patchwork.freedesktop.org/series/58893/ (commit
> d179b88deb3bf6fed4991a31fd6f0f2cad21fab5 upstream kernel drm/i915/fbdev) and
> rebuilding default disco kernel 5.0.0-8-generic everything works as expected.
>
> This bug was initially reported as:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441
>
> Possible duplicate: https://bugs.freedesktop.org/show_bug.cgi?id=109174

or It could be a duplicate to Bug 107100 not i915 bug?

[Torsten Römer (dode)]

I just received Kernel 5.0.0-11-generic via Ubuntu update and the issue seems to be solved :-)

[Lakshminarayana-vudum (lakshminarayana-vudum)]

(In reply to Torsten from comment #2)
> I just received Kernel 5.0.0-11-generic via Ubuntu update and the issue
> seems to be solved :-)

Thanks for the feedback. Closing this bug.