Kernel bug at nvme

[Jussi Saarinen]

Hardware is HP Zbook Studio G3 with two nvme devices in m.2 slots.

I was running three Virtualbox clients while two of them hung. Those two which hung were on same nvme disk while the one which remained in operation was another nvme disk.

Dmesg error is attached as "kernel_bug.txt"

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-20-generic 4.10.0-20.22
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Wed Apr 26 12:57:42 2017
HibernationDevice: RESUME=UUID=976a908c-349d-4393-8d5c-aabba5f56909
InstallationDate: Installed on 2017-02-14 (70 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: HP HP ZBook Studio G3
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=f7076591-2c4c-485d-9b65-751bf9ce132d ro acpi_osi=Linux
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-20-generic N/A
 linux-backports-modules-4.10.0-20-generic N/A
 linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-04-16 (9 days ago)
dmi.bios.date: 11/02/2016
dmi.bios.vendor: HP
dmi.bios.version: N82 Ver. 01.15
dmi.board.name: 80D4
dmi.board.vendor: HP
dmi.board.version: KBC Version 11.67
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrN82Ver.01.15:bd11/02/2016:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.67:cvnHP:ct10:cvr:
dmi.product.name: HP ZBook Studio G3
dmi.sys.vendor: HP

[Brad Figg (brad-figg)]

This change was made by a bot.

[Jussi Saarinen (jms)]

Full dmesg with error is attached

[Jussi Saarinen (jms)]

This issue seems to affect only another nvme device:

lspci:
02:00.0 Non-Volatile memory controller: Intel Corporation Device f1a5 (rev 03)

mounted at:
/dev/nvme0n1p1 973844116 277803160 646502624 31% /opt/store

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]