Transient panic on boot with wily proposed kernel (4.2.0-39)

Bug #1593835 reported by Mike Gerow
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
High
Unassigned

Bug Description

Attached picture of panic, although there's not really much there. It kinda looks like init has decided to kill itself.

It's only happened once in the three times I've booted into the new kernel. I haven't had a chance to test it more beyond that.

Revision history for this message
Mike Gerow (gerow) wrote :
Revision history for this message
Mike Gerow (gerow) wrote :

$ cat /proc/version_signature
Ubuntu 4.2.0-39.46~14.04.1-generic 4.2.8-ckt11

Revision history for this message
Mike Gerow (gerow) wrote :
Revision history for this message
Mike Gerow (gerow) wrote :

Also relevant, I have installed a few dkms modules that could be causing trouble (including one that is unfortunately closed-source and that I can't share...):

$ dkms status -k 4.2.0-39-generic
bbswitch, 0.7, 4.2.0-39-generic, x86_64: installed
hpuefi, 1.0.3+gg8, 4.2.0-39-generic, x86_64: installed
nvidia-340, 340.96, 4.2.0-39-generic, x86_64: installed

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1593835

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Mike Gerow (gerow) wrote :

Company policy disables apport, but if there's anything specific I'm happy to provide it.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Mike Gerow (gerow) wrote :

If none of y'all are seeing anything like this in the proposed kernel I wouldn't be surprised if it has something to do with my setup, so this bug probably shouldn't block the release.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Do you happen to have a way to reproduce the panic? Also, Is it only happening with 4.2 based kernels?

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key
tags: added: wily
Revision history for this message
Mike Gerow (gerow) wrote :

Sadly no, I only saw it happen once and I have no idea what might have caused it. The one and only time I saw it was with the 4.2 kernel, though.

I don't have access to the machine that it happened on anymore, unfortunately, but I'll see if I can reproduce the issue on another machine I have access to.

Revision history for this message
Mike Gerow (gerow) wrote :

I haven't seen this happen in a while and I'm beginning to think more and more it actually had something to do with my system and not the kernel. Moving to invalid.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.