New kernel causes black screen after login

[Tommy_CZ]

New kernel causes black screen after login, I cannot use it nor switch to ttyX.
It came as regular upgrade during installation of Ubuntu.
Downgrade to kernel 3.13.0-32-generic is a workaround.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-generic 3.13.0.43.50
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: zabava 2173 F.... pulseaudio
 /dev/snd/controlC2: zabava 2173 F.... pulseaudio
 /dev/snd/controlC0: zabava 2173 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Dec 14 14:22:01 2014
HibernationDevice: RESUME=UUID=26dc94e4-a3a2-4d85-81c3-f7b77a41b5b1
InstallationDate: Installed on 2014-12-14 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: ASUS All Series
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=447ed435-5a74-44ce-996f-7a6fc4f83b70 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic N/A
 linux-firmware 1.127.10
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0602
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: AM1I-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd07/11/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnAM1I-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

[Brad Figg (brad-figg)]

This change was made by a bot.

[Tommy_CZ (t-kijas)]

It seems upgraded kernel has serious issues with AMD GPUs, probably same problem is here: http://askubuntu.com/questions/560350/boot-hangs-after-upgrade-to-kernel-3-13-0-43

Athlon 5150 with radeon R3 (HD8400). Black screen, system freeze during boot, started after upgrade of Ubuntu (this upgrade is included into installation of Ubuntu(!!!) )

The worse is, the kernel 3.16.0-28 is also plagued by this bug.

This bug cripples the upgrade-enabled installation of Ubuntu on AMD CPUs with GPUs ! Critical!

[Joshua Wiedekopf (jpwiedekopf)]

This also affects me on Xubuntu 14.04.1 and Elementary OS 0.3 Beta 1. I'll attach my lshw output and will try to generate a proper set of logs tomorrow.

[Joshua Wiedekopf (jpwiedekopf)]

Interestingly, I was able to resolve this issue on 3.13.0-43-generic (eOS Freya) by installing the current AMD proprietary driver, version 14.12 in tty1 which I was - curiously - able to access when basically hammering the keyboard as soon as the OS logo showed up. This started for me by issuing an upgrade through apt-get. I'll attach my apt history.log.

[Tommy_CZ (t-kijas)]

Yes, but this is not a resolution, it is just a workaround, mentioned in askubuntu.
Do not forget for many people fglrx is not an option because of lack of proper vdpau support, etc.
There is something really bad in latest Ubuntu kernels.

[Joshua Wiedekopf (jpwiedekopf)]

True, especially because installing fglrx is sometimes quite a pain and not really an option for many out there, as you pointed out.

I just checked in the kernel.org bugtracker and it appears that this is actually a known bug (https://bugzilla.kernel.org/show_bug.cgi?id=88481). This bug was, however, logged for v3.17.3.

[Joshua Wiedekopf (jpwiedekopf)]

Tommy, if you did not install fglrx under 3.13.0-43, could you perhaps try to boot using the new kernel with "radeon.runpm=0" appended to the GRUB command line? According to this [1] bug report this might work. I can't really do that because uninstalling fglrx is too unreliable.

[1]https://bugzilla.kernel.org/show_bug.cgi?id=72831