4.4.0-38-generic reboots periodically

[Eugene Lazutkin]

When upgrading a server to 4.4.0-38-generic, it started to reboot every ~45 minutes without any visible reasons. Logs look fine. Just reboots. My other computer (a desktop) works fine with the same setup. Another difference: the server hosts ZFS raid.

Unfortunately (fortunately) I had this problem ~2 years ago. That time after much debugging it turned out to be a kernel problem. So I loaded a previous kernel (4.4.0-36-generic), and it is rock solid again.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic 4.4.0-36.55
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-36-generic.
AplayDevices: aplay: device_list:268: no soundcards found...
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: arecord: device_list:268: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Fri Sep 30 17:35:35 2016
HibernationDevice: RESUME=/dev/mapper/croc--vg-swap_1
InstallationDate: Installed on 2013-11-05 (1060 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic root=/dev/mapper/hostname--vg-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-36-generic N/A
 linux-backports-modules-4.4.0-36-generic N/A
 linux-firmware 1.157.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-24 (159 days ago)
dmi.bios.date: 05/02/2007
dmi.bios.vendor: Intel Corp.
dmi.bios.version: DPP3510J.86A.0216.2007.0502.1916
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DP35DP
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD81073-206
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0216.2007.0502.1916:bd05/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-206:cvn:ct2:cvr:

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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.4.23

[Eugene Lazutkin (eugene-lazutkin-gmail)]

Downloaded kernel 4.4.23, rebooted in it, compiled in zfs, waiting now to see if it reboots or not. So far it was up for 40 minutes. If everything goes well, I'll wait several hours, and mark the ticket as instructed. If not, I'll mark ticket as instructed faster. :-)

[Eugene Lazutkin (eugene-lazutkin-gmail)]

The kernel was up for 4:44 without rebooting, so I deem it a success.

[Joseph Salisbury (jsalisbury)]

That is good news. The Ubuntu Xenial kernel should receive this fix when it gets the v4.4.23 updates via the normal stable update process.