kernel panic on boot after upgrade to ubuntu 15.10

[Mr.Gosh]

the installed Kernel in the release upgrade to the development line of ubuntu 15.10 creates a kernel panic on my
Lenovo yoga 2 pro

the previously isntalled ubuntu 15.04 Kernel does still boot.

Ubuntu Release:
Description: Ubuntu Wily Werewolf (development branch)
Release: 15.10

Expected:
Clean Upgrade to 150.10 development branch
reboot

happend instead:
system got updated but dropped to a non responding cmd
after a reboot i have a blinking caps lock
after selecting an old kernel (and not the 4.2) it boots...

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ubuntu-release-upgrader-core 1:15.10.6
ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: GNOME
Date: Thu Sep 24 16:55:16 2015
InstallationDate: Installed on 2015-04-25 (152 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to wily on 2015-09-24 (0 days ago)

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

We would like to review the details of the panic. Do you have a screen shot, digital image or the text details of the panic that you could provide?

[Leo (leo4ward)]

Hi,
since 3 weeks I have tried to track the reasons for a kernel panic I had with my Thinkpad T450s.

Unfortunately, the panic happen only one in many hours and isolating the true reasons was very difficult. I'm quite sure now that it's not related to intel graphics nor the intel wifi driver (graphics was my ideal suspect).

What I have found (95% certitude):
- the panic occur only on when on battery
- removing the TLP package solve the issue (so, it's probably a driver flag set by TLP that causes the issue)
- Upgrading to upstream kernel 4.3RC4/5 definitely solve the problem.

FYI: when the panic occurs, the screen/image completely freezes, no kernel logs, no magic key working.

Hope it helps !
Lorenzo

[RumtumTugger (tp-groen)]

Ubuntu Wily crashes on several occasions but intermittantly during boot on my Acer Aspire V15 Nitro. I have the F12 boot menu enabled. This problem also exists when booting from DVD or USB-pendrive. I had these problems from the firsts attempts to run the Live USB or installing a fresh new system.

***No such problems with 15.04.***

What happens is that the boot process ends and the system reboots itself. When not quick enough pressing F12, the system will boot into M$-Windows. Otherwise the F12 boot menu comes up. Today, at the 4th or 5th attempt, Ubuntu came up at last.

Some last red lines in syslog.log:
Nov 22 11:44:09 jupiter com.canonical.Unity.Scope.Home[1352]: (unity-scope-home:2547): unity-scope-home-WARNING **: platform-info.vala:112: Unable to read SIM properties: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
Nov 22 11:44:09 jupiter com.canonical.Unity.Scope.LocalFiles[1352]: (process:2563): unity-files-daemon-WARNING **: folder.vala:65: Failed to read favorites: Failed to open file '/home/theo/.gtk-bookmarks': No such file or directory
Nov 22 11:44:10 jupiter com.canonical.Unity.Scope.Home[1352]: (unity-scope-home:2547): Json-CRITICAL **: json_object_get_object_member: assertion 'node != NULL' failed
Nov 22 11:44:10 jupiter com.canonical.Unity.Scope.Home[1352]: message repeated 9 times: [ (unity-scope-home:2547): Json-CRITICAL **: json_object_get_object_member: assertion 'node != NULL' failed]
Nov 22 11:44:10 jupiter com.canonical.Unity.Scope.Home[1352]: (unity-scope-home:2547): libunity-WARNING **: unity-aggregator-scope.vala:145: Error serializing GVariant with type string 'mv' to the D-Bus wire format
Nov 22 11:44:11 jupiter com.canonical.Unity.Scope.Home[1352]: (unity-scope-home:2547): unity-scope-home-WARNING **: scope.vala:849: Remote search failed: Request failed with error 6
Nov 22 11:44:11 jupiter com.canonical.Unity.Scope.Home[1352]: (unity-scope-home:2547): Json-CRITICAL **: json_object_get_object_member: assertion 'node != NULL' failed
Nov 22 11:44:11 jupiter com.canonical.Unity.Scope.Home[1352]: message repeated 9 times: [ (unity-scope-home:2547): Json-CRITICAL **: json_object_get_object_member: assertion 'node != NULL' failed]
Nov 22 11:44:30 jupiter systemd[1]: Stopping User Manager for UID 119...
Nov 22 11:44:30 jupiter systemd[1029]: Stopped target Default.
Nov 22 11:44:30 jupiter systemd[1029]: Stopped target Basic System.
Nov 22 11:44:30 jupiter systemd[1029]: Stopped target Sockets.
Nov 22 11:44:30 jupiter systemd[1029]: Stopped target Paths.
Nov 22 11:44:30 jupiter systemd[1029]: Stopped target Timers.
Nov 22 11:44:30 jupiter systemd[1029]: Reached target Shutdown.
Nov 22 11:44:30 jupiter systemd[1029]: Starting Exit the Session...
Nov 22 11:44:30 jupiter systemd[1029]: Received SIGRTMIN+24 from PID 2720 (kill).
Nov 22 11:44:30 jupiter systemd[1]: Stopped User Manager for UID 119.
Nov 22 11:44:30 jupiter systemd[1]: Removed slice user-119.slice.

Attached: a file with kern.log and syslog.log output.