Cannot get past login after update to 4.4.0.75-generic

Bug #1686299 reported by Ben Langmuir
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-375 (Ubuntu)
New
Undecided
Unassigned

Bug Description

After running software update on 16.04 and rebooting, I cannot get past the login screen. The screen appears the wrong resolution and squashed smaller than the screen with a black border. When I login, it accepts the password, but after a few seconds the screen gets corrupted then resets back to the login screen.

Rebooting to an older kernel fixed the issue.

Working:
 4.4.0-72-generic

Failed:
 4.4.0.75-generic

I'm using nvidia 340.102

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-72-generic 4.4.0-72.93
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: ben 2228 F.... pulseaudio
 /dev/snd/controlC1: ben 2228 F.... pulseaudio
 /dev/snd/controlC0: ben 2228 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 25 23:46:40 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=a1a4d11a-a791-49f3-9542-90dbd821d0d2
InstallationDate: Installed on 2012-04-28 (1823 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=7d577aa7-441e-43e2-b6b3-a8500fe017c9 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-72-generic N/A
 linux-backports-modules-4.4.0-72-generic N/A
 linux-firmware 1.157.8
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2017-03-27 (30 days ago)
dmi.bios.date: 04/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.40
dmi.board.name: X58 Extreme
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Ben Langmuir (benlangmuir) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

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

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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.4.63

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: needs-bisect
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ben Langmuir (benlangmuir) wrote :

Okay I was able to fix this. I tried updating to nvidia-375 in case that was the issue, and during the install I noticed it was compiling something with clang instead of gcc. After that I was getting the same behaviour from both 4.4.0-72 and 4.4.0-75.

I think what happened was:
1. I did update-alternatives to switch cc/c++ to clang
2. I updated my kernel, which rebuilt part of nvidia's driver with clang
3. Broken.

I fixed it by doing:
1. apt-get-purge nvidia-*
2. update-alternatives back to gcc
3. re-install nvidia-375

I'm now using nvidia-375 with kernel 4.4.0-75.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Sounds like maintainer scripts in Nvidia need some tweaks.

no longer affects: linux (Ubuntu)
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.