Booted into blank screen after the security update

[Aikawa Takuya]

I am using Ubuntu 14.04 on ASUS X200MA laptop.
After applying the security update to the linux kernel, the boot process failed.

Summary:
Grub load, empty purple screen appears and disappears,
then the backlight turns off... it DOES NOT turn on and the log in drum sound rings.

It is just like the former bug reported below:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/919350

Now I am running on the previous kernel 3.13.0-44 #73-Ubuntu
(with selecting from Grub menu), and have no problem on booting.

I appreciate your help and cooperation. Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-45-generic 3.13.0-45.74
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: aikawatakuya 1859 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Feb 2 00:18:17 2015
HibernationDevice: RESUME=UUID=1d9c88a7-1473-4d4e-917d-46fc21e38a98
InstallationDate: Installed on 2014-11-09 (84 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: ASUSTeK COMPUTER INC. X200MA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic.efi.signed root=UUID=7ac07a5f-b038-40ac-a6a1-e0f4ccbb69c3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-44-generic N/A
 linux-backports-modules-3.13.0-44-generic N/A
 linux-firmware 1.127.11
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/04/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X200MA.500
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X200MA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX200MA.500:bd05/04/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X200MA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Donald Church (dchurch315)]

Same issue, same laptop. Setting nomodeset does NOT provide a workaround.

[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 v3.19 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/v3.19-rc7-vivid/

[Aikawa Takuya (riumutu)]

Thank you for your proposal.
I'll certainly test the latest kernel, but this is my main laptop and
it is difficult to test it for a couple of days because of my own work...

Probably I can test the v3.19 kernel on Thursday or Friday.
Then I'll go on to adding some tags!

[ziessow (khziessow)]

Same issue, also on ASUS X200MA.

[Kevin Sapper (kevinsapper88)]

Same issue, on ASUS F200M.

[Aikawa Takuya (riumutu)]

The latest v3.19 mainline kernel doesn't produce this bug.

Some messages were displayed during the boot session (sorry I couldn't write them down, but 3 short lines),
but my laptop booted successfully.

[Aikawa Takuya (riumutu)]

Hi,

I've just done the latest security update,
but the same problem exists with the newly installed(updated) v. 3.13.0-46 kernel.
Also on ASUS X200MA. The hardware configurations are the same as reported above.

I expect further developments. Thank you.

[Jaime Giraldo (sposmen)]

Equal issue, also on ASUS X200MA and 3.13.0-46

[Kamolwan Lueprasert (kamolwan-l)]

I also use ASUS X200MA and have the same issue since the upgrade to 3.13.0-45 and continue to have a problem when upgraded to 3.13.0-46.

The last kernel that worked for this laptop is 3.13.0-45.

I tried reintalled using USB with 3.13.0-45. I currently used this laptop to report but booted from advance ubuntu options and select the 3.13.0-32 which I have last on my USB installer. Sadly, my 3.13.0-45 was wiped out when I reinstalled. I am currently using the 3.13.0-32 to report this problem.

Looking forward to see new development and fix or workaround in this issue.

[Keith Brown (keith-geoffreybrown)]

I use an Asus X200MA with Ubuntu 14.04 and have had the same issue i.e. a black screen since the update from 3.13.0-40 to 3.13.0-45. The update to 3.13.0-46 didn't help so I'm back to using 3.13.0-40.

I tried Christopher Penalver's suggestion and upgraded the BIOS to the latest version 504 (from November 2014). With 3.13.0-46 this results in an initially scrambled screen that slowly becomes a white screen after a minute or so. I can still use 3.13.0-40.

Here's the requested output of sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date:

X200MA.504
11/13/2014

Thanks a lot.

[penalvch (penalvch)]

Keith Brown, it would help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Keith Brown (keith-geoffreybrown)]

Christopher Penalver: I have done so. Thanks.

[Aikawa Takuya (riumutu)]

Thanks for your advice, Christopher.

I've just done the BIOS update and tested booting.

With the 3.13.0-45 and 3.13.0-46 kernel:
The backlight turns off (as normal boot process) and on with some oddly scrambled lines,
then the screen generally becomes white. While the screen whiting out, the log in drum rings.

With the 3.13.0-44 kernel, my laptop boots successfully.

The output of the dmidecode commands:
X200MA.504
11/13/2014

Thanks.

[penalvch (penalvch)]

Aikawa Takuya, the next step is to fully reverse commit bisect from kernel 3.13 to 3.19 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Jaime Giraldo (sposmen)]

If an extra information make sense to detect the bug after installation of 3.16.0-31.41 continue with a normal start up.(headers, headers-generic, image, image-extra, signed-image)

[superfloflo (superfloflo1775)]

Same problem here with this laptop : ASUS X200MA...
Any update on the debugging process ?

[superfloflo (superfloflo1775)]

I must add that booting to 3.13.0-43 works for me. Maybe someone could find what kind of changes could have been at the origin of the bug between kernels 3.13.0-44 and 3.13.0-45.

[Armin (ar-bin)]

I have also this problem with my ASUS X200MA.
kernel 3.13.0-44 is still working, the problem appeared with 3.13.0-45!

[Kamolwan Lueprasert (kamolwan-l)]

I would like to report like my blank screen problem with X200MA has been resolved with the kernel update 3.13.0-53 a couple of days ago.

Thank you.

[Theodore McLeod (tcm-mcleodhome)]

I too would like to report that kernel update 3.13.0-53.89 resolved my
blank screen problem.
Thanks to all.
Ted

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]