[Asus TX201LA] Kernel panic immediately during boot

[guillaume ramelet]

I can boot with linux-image-3.13.0-24-generic.
0-26, 0-27, 0-29 fail to boot with the following message (see screenshot attached)

Ubuntu 14.04

Machine Asus Transformer Book TX201LA.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.47
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: guillaume 1614 F.... pulseaudio
 /dev/snd/controlC1: guillaume 1614 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Jun 10 19:50:23 2014
HibernationDevice: RESUME=UUID=4caecfd8-8a1c-46ec-a6a8-84ba961534ac
InstallationDate: Installed on 2014-04-03 (67 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140403)
MachineType: ASUSTeK COMPUTER INC. TX201LA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=bfdc6176-d88e-4568-ad59-eb7e4993131a ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127.2
SourcePackage: linux
StagingDrivers: rtl8821ae
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: TX201LA.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: TX201LA
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.:bvrTX201LA.211:bd11/20/2013:svnASUSTeKCOMPUTERINC.:pnTX201LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTX201LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: TX201LA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Brad Figg (brad-figg)]

This change was made by a bot.

[guillaume ramelet (guillaume-ramelet)]

Hi Christopher,

thank you for your answer.
I have updated bios (using easy flash for ones asking, took me 3h to figure out how I would do that without windows...) according to your recommandation and it doesn't change anything.

Here are the command outputs :
guillaume@transformer:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
TX201LA.213
02/27/2014

What happened when selecting kernels 0-26, 0-27, 0-29 in grub is something like 1 sec of a black screen (with light on it, not as when it is shutdown) and directly after the kernel panic I have joint in the screenshot : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328630/+attachment/4129066/+files/IMG_20140514_203441.jpg
When I select 0-24 I have immediately 2 lines of text saying it is loading 0-24 image (not sure of text I can retrieve precise info if needed) * I don't have these 2 lines before the kernel panics * and after that it boots normaly.

Eager to apply any further recommandations to help debug the issue

[penalvch (penalvch)]

guillaume ramelet, could you please test the latest upstream kernel available from the first line at the top page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.15

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[guillaume ramelet (guillaume-ramelet)]

Here is the kernel 3.15 tested : linux-image-3.15.0-031500-generic_3.15.0-031500.201406111300_amd64.deb

guillaume@transformer:~$ uname -a
Linux transformer 3.15.0-031500-generic #201406111300 SMP Wed Jun 11 17:01:45 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

guillaume ramelet, the next step is to fully reverse commit bisect the kernel, in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

[guillaume ramelet (guillaume-ramelet)]

OK.
Do I need first to reverse bisect upstream kernel versions from v3.13-trusty/ to v3.15-utopic/.

[guillaume ramelet (guillaume-ramelet)]

Christopher,

I am not sure to follow the correct procedure.
All the 6 upstream kernels I have tested work :

v3.15-utopic/ OK
v3.15-rc8-utopic/
v3.15-rc7-utopic/
v3.15-rc6-utopic/
v3.15-rc5-utopic/
v3.15-rc4-utopic/
v3.15-rc3-utopic/
v3.15-rc2-trusty/ OK
v3.15-rc1-trusty/
v3.14.7-utopic/
v3.14.6-utopic/
v3.14.5-utopic/
v3.14.4-utopic/
v3.14.3-utopic/
v3.14.2-utopic/
v3.14.1-trusty/
v3.14-trusty/ OK
v3.14-rc8-trusty/
v3.14-rc7-trusty/
v3.14-rc6-trusty/
v3.14-rc5-trusty/
v3.14-rc4-trusty/
v3.14-rc3-trusty/
v3.14-rc2-trusty/
v3.14-rc1-trusty/
v3.13.11.2-trusty/ OK (no wifi)
v3.13.11.1-trusty/ OK (no wifi)
v3.13.11-trusty/
v3.13.10-trusty/
v3.13.9-trusty/
v3.13.8-trusty/
v3.13.7-trusty/
v3.13.6-trusty/
v3.13.5-trusty/
v3.13.4-trusty/
v3.13.3-trusty/
v3.13.2-trusty/
v3.13.1-trusty/
v3.13-trusty/ OK (no wifi)

If I understand correctly, ubuntu kernel 3.13.0-26 which kernel panics here is based on v3.13.11.2-trusty. No kernel panic in upstream. (no wifi though)

Can you provide guidance for next tests?

[guillaume ramelet (guillaume-ramelet)]

If I read correctly Ubuntu to Mainline kernel version mapping, Ubuntu-3.13.0-29.52 is based on 3.13.11.2.

I don't have Ubuntu-3.13.0-29.52, I have Ubuntu-3.13.0-29.53.
Ubuntu-3.13.0-29.53 kernel panics and v3.13.11.2-trusty doesn't.

Does that mean it is not a bug in kernel but more in something added within ubuntu-3.13.0-29.53 ?

[penalvch (penalvch)]

guillaume ramelet, it could very well be a downstream patch causing this issue, versus an upstream one. It would be helpful if the kenrnel issue is fully commit bisected to find the commit that caused the problem initially.

[guillaume ramelet (guillaume-ramelet)]

Between each version of mainstream kernel do I have to bisect?

I am out of computer for the week-end. I will resume on monday.

[Launchpad Janitor (janitor)]

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

[EDEMPCO (edemco)]

I see that this thread has expired with the last post being 2014-08-13, however, if anyone (like me) looked for a solution to kernel panic, I offer the following solution that I posted on Ubuntu Forums. Please see

http://ubuntuforums.org/showthread.php?t=2251652&p=13160836#post13160836

[penalvch (penalvch)]

EDEMPCO, WORKAROUNDs aren't solutions here on Launchpad. For more on what constitutes a fix, please see https://wiki.ubuntu.com/Bugs/Status .

Despite this, if you are having a problem in Ubuntu, so your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

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