Init corrupted when running 4.15.0-42

Bug #1808069 reported by RS
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS (x86_64) I get the following error on system bootup (freeze):

Failed to execute /init (error -2)
Kernel panic - not syncing: no working init found.

So apparently the init is broken.

My solution was to remove 4.15.0-42

sudo apt remove linux-image-4.15.0-42
sudo apt autoremove

and, thus, automatically go back to 4.15.0-39 which works fine.

The autoremove removed amd64-microcode, intel-microcode iucode-tool and thermald which appear to be needed by -42 only.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.29
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CrashDB: ubuntu
Date: Wed Dec 12 00:36:04 2018
InstallationDate: Installed on 2013-06-03 (2017 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptclonesystemstate.tar.gz:
 Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
 Error executing command as another user: Not authorized

 This incident has been reported.
VarLogDistupgradeAptlog:
 Log time: 2018-12-12 00:10:47.798784
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=none
InstallationDate: Installed on 2013-06-03 (2017 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: GIGABYTE GB-BPCE-3350C
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-39-generic N/A
 linux-backports-modules-4.15.0-39-generic N/A
 linux-firmware 1.173.2
Tags: bionic
Uname: Linux 4.15.0-39-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/28/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F7
dmi.board.asset.tag: Default string
dmi.board.name: MZAPLCP-00
dmi.board.vendor: GIGABYTE
dmi.board.version: 1.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: BRIX
dmi.product.name: GB-BPCE-3350C
dmi.product.version: 1.x
dmi.sys.vendor: GIGABYTE

Revision history for this message
RS (ro2ert) wrote :
affects: ubuntu-release-upgrader (Ubuntu) → linux (Ubuntu)
summary: - Init corrupted when upgrading to 4.15.0-42
+ Init corrupted when running 4.15.0-42
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1808069

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
RS (ro2ert) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
RS (ro2ert) wrote : CRDA.txt

apport information

Revision history for this message
RS (ro2ert) wrote : CurrentDmesg.txt

apport information

Revision history for this message
RS (ro2ert) wrote : IwConfig.txt

apport information

Revision history for this message
RS (ro2ert) wrote : Lspci.txt

apport information

Revision history for this message
RS (ro2ert) wrote : Lsusb.txt

apport information

Revision history for this message
RS (ro2ert) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
RS (ro2ert) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
RS (ro2ert) wrote : ProcEnviron.txt

apport information

Revision history for this message
RS (ro2ert) wrote : ProcInterrupts.txt

apport information

Revision history for this message
RS (ro2ert) wrote : ProcModules.txt

apport information

Revision history for this message
RS (ro2ert) wrote : RfKill.txt

apport information

Revision history for this message
RS (ro2ert) wrote : UdevDb.txt

apport information

Revision history for this message
RS (ro2ert) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
RS (ro2ert) wrote :

All apport information from last working kernel -39

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.