Displays not properly recognized after upgrading kernel to 4.10.0-37-generic

[Danilo Azevedo]

I have a multi-monitor setup and after upgrading kernel to 4.10.0-37-generic, the displays weren't properly recognized. Only 1 monitor appears on display config and it's limited to 1024x768 resolution. Reverting kernel to 4.10.0-35-generic solves the problem.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-35-generic 4.10.0-35.39
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: danilo 1261 F.... pulseaudio
CurrentDesktop: XFCE
Date: Tue Oct 10 10:31:47 2017
InstallationDate: Installed on 2017-09-25 (15 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IwConfig:
 lo no wireless extensions.

 enp0s25 no wireless extensions.
Lsusb:
 Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: POSITIVO POS-PIQ57BQ
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=4d0acbb7-f921-4364-8c42-4a83a19fadd6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-35-generic N/A
 linux-backports-modules-4.10.0-35-generic N/A
 linux-firmware 1.164.1
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/28/2010
dmi.bios.vendor: Desenvolvida para Positivo Informatica SA
dmi.bios.version: 0110
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: POS-PIQ57BQ
dmi.board.vendor: Positivo Informatica SA
dmi.board.version: POSITIVO
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: POSITIVO
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnDesenvolvidaparaPositivoInformaticaSA:bvr0110:bd12/28/2010:svnPOSITIVO:pnPOS-PIQ57BQ:pvr0110_POS:rvnPositivoInformaticaSA:rnPOS-PIQ57BQ:rvrPOSITIVO:cvnPOSITIVO:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: POS-PIQ57BQ
dmi.product.version: 0110_POS
dmi.sys.vendor: POSITIVO
---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: danilo 1265 F.... pulseaudio
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-25 (17 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IwConfig:
 enp0s25 no wireless extensions.

 lo no wireless extensions.
Lsusb:
 Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: POSITIVO POS-PIQ57BQ
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=4d0acbb7-f921-4364-8c42-4a83a19fadd6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-37-generic N/A
 linux-backports-modules-4.10.0-37-generic N/A
 linux-firmware 1.164.1
RfKill:

Tags: zesty
Uname: Linux 4.10.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 12/28/2010
dmi.bios.vendor: Desenvolvida para Positivo Informatica SA
dmi.bios.version: 0110
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: POS-PIQ57BQ
dmi.board.vendor: Positivo Informatica SA
dmi.board.version: POSITIVO
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: POSITIVO
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnDesenvolvidaparaPositivoInformaticaSA:bvr0110:bd12/28/2010:svnPOSITIVO:pnPOS-PIQ57BQ:pvr0110_POS:rvnPositivoInformaticaSA:rnPOS-PIQ57BQ:rvrPOSITIVO:cvnPOSITIVO:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: POS-PIQ57BQ
dmi.product.version: 0110_POS
dmi.sys.vendor: POSITIVO

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc4

[Danilo Azevedo (hertz1)]

Yes, I can confirm that the bug doesn't happen on the latest upstream kernel (4.14-rc4). Thanks!

[Kai-Heng Feng (kaihengfeng)]

Hmm, there's no change to i915 from 4.10.0-35 to 4.10.0-37.
Can you attach the output of `dpkg -l | grep linux-image`?

[Mélodie (meets)]

Hi,

I'm not sure it is the same bug, but here is my story:
I was running a linux-image 4.10.0-35 in Ubuntu 16.04, with a GPU nvidia 8800 GTS, and using the nvidia 304 driver (nouveau gives poor resolution choice 800x600 or 600x480 as a choice) and the 340 driver gives poor smoothing.

Today I ran an update and the linux-image 4.10.0.37 appeared among other packages so I updated, rebooted, then it appeared it would not be able to start the lightdm service! Then I tried startx (I have a config file) but no more success, could not find the screen. So what next, I reinstall the nvidia driver! That's when I saw this message that it COULD NOT FIND the kernel sources!

Well here is the thing : no linux-headers no screen!

What do I do? I install it of course! 'sudo apt install linux-headers-4.10.0.37' (and the "generic" package as well), then re install the nvidia driver once again, 'sudo start lightdm.service' : problem solved!!!

Conclusion : this is my bug report, the package linux-image-4.10.0.37 does not pull in it's linux-headers of the same number, hence some trouble met for several users! →

https://bugs.launchpad.net/bugs/+bugs?field.searchtext=linux-image-4.10.0-37&search=Search+Bug+Reports&field.scope=all&field.scope.target=

Best regards,
Mélodie

[Danilo Azevedo (hertz1)]

>> Can you attach the output of `dpkg -l | grep linux-image`?

Yes, here you go.

[Kai-Heng Feng (kaihengfeng)]

Can you try 4.10.0-36?

[Kai-Heng Feng (kaihengfeng)]

Also, please apport-collet under 4.10.0-37-generic.

[Danilo Azevedo (hertz1)]

apport information

[Danilo Azevedo (hertz1)]

apport information

[Danilo Azevedo (hertz1)]

apport information

[Danilo Azevedo (hertz1)]

apport information

[Danilo Azevedo (hertz1)]

apport information

[Danilo Azevedo (hertz1)]

apport information

[Danilo Azevedo (hertz1)]

apport information

[Danilo Azevedo (hertz1)]

apport information

[Danilo Azevedo (hertz1)]

apport information

[Danilo Azevedo (hertz1)]

apport information

[Danilo Azevedo (hertz1)]

apport information

[Danilo Azevedo (hertz1)]

apport information

[Danilo Azevedo (hertz1)]

>> Can you try 4.10.0-36?
There's no shuch version of 4.10.0 kernel. This is what I get when I try to install it:

sudo apt install linux-headers-4.10.0-36-gerenic
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-headers-4.10.0-36-gerenic
E: Couldn't find any package by glob 'linux-headers-4.10.0-36-gerenic'
E: Couldn't find any package by regex 'linux-headers-4.10.0-36-gerenic'

>> Also, please apport-collet under 4.10.0-37-generic.
Done.

[Danilo Azevedo (hertz1)]

This is a picture of what it looks like on kernel 4.10.0-37. See that although I have two monitors, only one is detected and is limited to 1024x768 resolution.

[Kai-Heng Feng (kaihengfeng)]

[ 2.412673] drm: loading out-of-tree module taints kernel.
[ 2.412889] drm: module verification failed: signature and/or required key missing - tainting kernel
...
[ 2.445205] i915: Unknown symbol drm_mm_init_scan_with_range (err 0)
[ 2.445267] i915: Unknown symbol drm_kms_helper_poll_enable_locked (err 0)
[ 2.445327] i915: Unknown symbol drm_crtc_get_hv_timing (err 0)
[ 2.445574] i915: Unknown symbol drm_mm_init_scan (err 0)
[ 2.445627] i915: Unknown symbol drm_mm_insert_node_in_range_generic (err 0)

Seems like you were loading out-of-tree i915.

What's the output of `modinfo i915`?

[Danilo Azevedo (hertz1)]

Output of `modinfo i915` on kernel 4.10.0-35.

[Danilo Azevedo (hertz1)]

Output of `modinfo i915` on kernel 4.10.0-37.

[Kai-Heng Feng (kaihengfeng)]

-35:
filename: /lib/modules/4.10.0-35-generic/updates/dkms/i915.ko
-37:
filename: /lib/modules/4.10.0-37-generic/kernel/drivers/gpu/drm/i915/i915.ko

Apparently you were using DKMS and it worked fine until 4.10.0-37.

I think the best approach here is to remove the DKMS.

[Danilo Azevedo (hertz1)]

And how do I do that?

[Kai-Heng Feng (kaihengfeng)]

Please attach "dpkg -l" here, thanks!

[Kai-Heng Feng (kaihengfeng)]

You have Intel's graphics driver installed, and others are having the same issue [1].

The DKMS package that causing problem is i915-4.11.6-4.10.0-dkms.

It should be safe to remove the DKMS.

[1] https://01.org/linuxgraphics/forum/update-tool-support-forum/unable-logon-after-running-intel-graphics-2.0.5-ubuntu-17.04

[Danilo Azevedo (hertz1)]

Just a note: I've reinstalled the i915-4.11.6-4.10.0-dkms package and this solved the problem. Is this something I have to do everytime I upgrade to a newer kernel version?

[Kai-Heng Feng (kaihengfeng)]

DKMS rebuild should be triggered every time a new kernel installed. If something go south in the process, it may not be built or be included in the initramfs.

But anyway, it's not a linux kernel bug per se.

[Danilo Azevedo (hertz1)]

I see. Thanks for your attention anyway!