kernel panic during installation

Bug #1507333 reported by Daniel Kessel
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

During the installation using the ISO image, a kernel panic happened.

I could only capture a photo of the screen contents.

Note that the kernel panic happened without the "wl" kernel module. I only activated it so I could upload this report.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-16-generic 4.2.0-16.19
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: xubuntu 1713 F.... pulseaudio
CasperVersion: 1.365
CurrentDesktop: XFCE
Date: Sun Oct 18 16:09:31 2015
LiveMediaBuild: Xubuntu 15.10 "Wily Werewolf" - Alpha i386 (20151017.1)
MachineType: Dell Inc. Inspiron 1011
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=de keyboard-configuration/layoutcode?=de
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-16-generic N/A
 linux-backports-modules-4.2.0-16-generic N/A
 linux-firmware 1.149
SourcePackage: linux
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: CN0Y53
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A06
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/29/2009:svnDellInc.:pnInspiron1011:pvrA06:rvnDellInc.:rnCN0Y53:rvrA06:cvnDellInc.:ct8:cvrA06:
dmi.product.name: Inspiron 1011
dmi.product.version: A06
dmi.sys.vendor: Dell Inc.

Revision history for this message
Daniel Kessel (dkessel) wrote :
Revision history for this message
Daniel Kessel (dkessel) wrote :
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Daniel Kessel, thank you for reporting this and helping make Ubuntu better.

Are you able to finish the installation, and reboot into a working OS?

tags: added: latest-bios-a06
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Daniel Kessel (dkessel) wrote :

No. After rebooting, I got a GRUB error about a missing grub.cfg file

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1507333

tags: added: iso-testing
Revision history for this message
penalvch (penalvch) wrote :

Daniel Kessel, would using one release back (Vivid) allow you a working environment via http://releases.ubuntu.com/vivid/ ?

Revision history for this message
Adam Conrad (adconrad) wrote :

Does this happen reproducibly? It looks like systemd is segfaulting.

affects: linux (Ubuntu) → systemd (Ubuntu)
Revision history for this message
Martin Pitt (pitti) wrote :

Can you please boot without the "quiet", and add "debug" on the kernel command line? The CurrentDmesg attachment looks normal, so I figure this was from a clean boot. Right now we have zero information what goes wrong here, I'm afraid. Thanks!

Revision history for this message
Kev Bowring (flocculant) wrote :

Not seeing that here with the same image.

Revision history for this message
Daniel Kessel (dkessel) wrote :

Not reproducible anymore. Might have been a bad SD card.

Changed in systemd (Ubuntu):
status: Incomplete → 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.