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=2251652p=13160836#post13160836
--
You
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
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: kernel-da-key kernel-stable-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328630
Title:
[Asus TX201LA] Kernel panic immediately during boot
Status in “linux”
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
** Tags added:
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
?
** Changed in: linux (Ubuntu)
Status:
OK.
Do I need first to reverse bisect upstream kernel versions from v3.13-trusty/
to v3.15-utopic/.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328630
Title:
[Asus TX201LA] Kernel
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
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
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.
--
You received this bug notification because you are a member of Kernel
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.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328630
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
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
13 matches
Mail list logo
