kernel 4.13.0-32.35 mangles display

[Russell Ayling]

Today I applied the latest series of updates to 16.04. After rebooting about 80% of the graphics display is corrupted, leaving a strip down the right side which is still legible. This was evident on the desktop and also the virtual consoles. Everything seemed to be running normally apart from the display.
After some experimentation I confirmed it was the 4.13.0-32.35 kernel, I reverted to 4.10.0.28-generic and all was good.
EEE-PC 901 (Intel Atom N270 with Mobile 945GSE integrated graphics)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.23
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Sat Jan 27 23:22:12 2018
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: a-user 1416 F.... pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=c9603762-f6c9-49b1-9ec2-dd0fae3ef99b
MachineType: ASUSTeK Computer INC. 901
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=e8a6eae1-a061-4c74-bd53-a8aed65c035d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-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-28-generic N/A
 linux-backports-modules-4.10.0-28-generic N/A
 linux-firmware 1.157.14
Tags: xenial
Uname: Linux 4.10.0-28-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 06/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 901
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 901
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Paul White (paulw2u)]

If you think that the kernel is at fault then the bug should be filed against "linux".
Reassigning...

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

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1745734

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

apport information

[Russell Ayling (hound58)]

I was unable to collect any logs while running on the suspect kernel as th system was effectively unusable from desktop or console. I've collected the logs from the current state running with the reverted kernel.

[Serpico (arnaud-abbal)]

Installed kernel 4.13.0-31 via Synaptic, booted up with it --> display works fine
Shutted down --> booted up with kernel 4.13.0-32 ( the one from the update ) --> no display issue, display works fine...strange

[Serpico (arnaud-abbal)]

At second consecutive reboot with kernel 4.13.0-32 the display issue comes back
Reboot with 4.13.0-31 , display works fine again

[Serpico (arnaud-abbal)]

After another reboot 4.13.0-31 problem is also present with this kernel

[Serpico (arnaud-abbal)]

I tried several kernels I could find using synaptic with an asus Eee PC 1005HA, here are the results :
- 4.11.0-13 --> display works
- 4.11.0-14 --> display works
- 4.13.0-19 up to 4.13.0-32 ( including -21 ; -24 ; -26 ; -31 and of course 4.13.0-32 ) display shows the same symptom as described by Russel Ayling in the initial bug report
Is there a PPA to install and test 4.12 kernel(s) ? try and see when the problem started...

[Kai-Heng Feng (kaihengfeng)]

Same as LP: #1724639 ?

It should be fixed in v4.15.