Kernel 4.4.0-39 fails to detect NVMe SSD

Bug #1627040 reported by Stefan Lindblad on 2016-09-23
This bug report is a duplicate of:  Bug #1626894: nvme drive probe failure. Edit Remove
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

After updating to linux-image-4.4.0-39 the system fails to boot because it is unable to find any boot device [1].

The output looks like this: (this is not my exact output but it is very similar)
[ 1.452270] genirq: Flags mismatch irq 0. 00000080 (nvme0q0) vs. 00015a00 (timer)
[ 1.452551] iounmap: bad address ffffc90001b88000
Scanning for Btrfs filesystems
Gave up waiting for root device. Common problems:
 - Boot args (cat /proc/cmdline)
  - Check rootdelay= (did the system wait for the right device?)
  - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT! UUID=a5ccaf22-ffde-44c2-8c59-84a851f9fd90 does not exist. Dropping to shell!

BusyBox v1.222.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

Picking the -38 kernel in the grub menu allows the system to boot normally.

Description: Ubuntu 16.04.1 LTS
Release: 16.04
Ubuntu 4.4.0-38.57-generic 4.4.19


ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.4.0-38.57
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
 /dev/snd/controlC3: stefan 3535 F.... pulseaudio
 /dev/snd/controlC2: stefan 3535 F.... pulseaudio
 /dev/snd/controlC1: stefan 3535 F.... pulseaudio
 /dev/snd/controlC0: stefan 3535 F.... pulseaudio
CurrentDesktop: GNOME
Date: Fri Sep 23 15:47:55 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=85533f1a-1042-454d-af93-43fcdfe643d9
InstallationDate: Installed on 2015-08-15 (405 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
 tun0 no wireless extensions.

 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=37ccd6d8-18f8-4813-813a-4a604c380aed ro noprompt persistent quiet splash
 linux-restricted-modules-4.4.0-38-generic N/A
 linux-backports-modules-4.4.0-38-generic N/A
 linux-firmware 1.157.4

SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-22 (154 days ago) 08/29/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2001
dmi.board.asset.tag: Default string Z170-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd08/29/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Stefan Lindblad (stli72) wrote :

This change was made by a bot.

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

Other bug subscribers