xserver fail after upgrade from image-4.10.0-37-generic

Bug #1723613 reported by Emanuele Cisbani
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
High
Joseph Salisbury

Bug Description

blank screen after boot, rebooting with previous kernel work fine

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-37-generic 4.10.0-37.41
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: emanuele 2283 F.... pulseaudio
CurrentDesktop: Unity:Unity7
Date: Sat Oct 14 12:58:08 2017
HibernationDevice: RESUME=UUID=cd4e1983-2ff1-4199-b9a1-ba1cb0175aaf
InstallationDate: Installed on 2016-07-09 (461 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ZOTAC XXXXXX
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=b483e7af-edbd-49ca-a3bd-542c88843248 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
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-06-11 (124 days ago)
dmi.bios.date: 04/06/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: B273P018
dmi.board.asset.tag: N/A
dmi.board.name: XXXXXX
dmi.board.vendor: ZOTAC
dmi.board.version: XX
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 2
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB273P018:bd04/06/2016:svnZOTAC:pnXXXXXX:pvrXX:rvnZOTAC:rnXXXXXX:rvrXX:cvnDefaultstring:ct2:cvrDefaultstring:
dmi.product.name: XXXXXX
dmi.product.version: XX
dmi.sys.vendor: ZOTAC

Revision history for this message
Emanuele Cisbani (cisba) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Emanuele Cisbani (cisba) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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-rc5

Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
tags: added: kernel-da-key needs-bisect
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

If the bug still exists in mainline, we can perform a kernel bisect to identify the commit that introduced this regression.

Changed in linux (Ubuntu):
assignee: nobody → Joseph Salisbury (jsalisbury)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.