kernel crash / BUG: unable to handle kernel paging request at fffffe3ed8000020

Bug #1749221 reported by Scott Moser on 2018-02-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Joseph Salisbury
Joseph Salisbury

Bug Description

Booted under maas in rescue mode system console has the attached failure.
First bit is

[ 440.196466] BUG: unable to handle kernel paging request at fffffe3ed8000020

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-generic (not installed)
ProcVersionSignature: User Name 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
 total 0
 crw-rw---- 1 root audio 116, 33 Feb 13 15:32 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1:
Date: Tue Feb 13 15:34:40 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: HP ProLiant DL360 Gen9

 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=username/amd64/generic/xenial/daily/boot-kernel nomodeset root=squash: ro ip=::::hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url= apparmor=0 log_host= log_port=514 --- console=ttyS1 BOOTIF=01-ec:b1:d7:7f:2a:6c
 linux-restricted-modules-4.13.0-32-generic N/A
 linux-backports-modules-4.13.0-32-generic N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install) 03/05/2015
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrP89:bd03/05/2015:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: ProLiant ProLiant DL360 Gen9
dmi.sys.vendor: HP

Scott Moser (smoser) wrote :
Scott Moser (smoser) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Can you reproduce the bug, or was it a one time event?

Changed in linux (Ubuntu):
importance: Undecided → High
Changed in linux (Ubuntu Artful):
importance: Undecided → High
status: New → Confirmed
tags: added: kernel-da-key
Scott Moser (smoser) wrote :

It happens within 3 minutes of system boot into 4.13 kernel.
2 systems reproduced this. You're lucky to be able to log in before it crashes.

Since you are using apparmor=0 parameter,
this will be a duplicate of bug 1734327.

Try removing apparmor=0 parameter for now.

Changed in linux (Ubuntu):
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Artful):
assignee: nobody → Joseph Salisbury (jsalisbury)
Scott Moser (smoser) wrote :

Thanks for the info. Removing 'apparmor=0' isn't an option right now both because MAAS doesn't let you control that and because it is there to work around other bugs (originally bug 1677336).

Joseph Salisbury (jsalisbury) wrote :

I built a test kernel with the patch from Tetsuo. The test kernel can be downloaded from:

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and linux-image-extra .deb packages.

Thanks in advance!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers