Random reboots with 4.13.0-26 on Ubuntu 16.04 LTS

Bug #1745464 reported by Trey Tabner on 2018-01-25
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Unassigned
Artful
High
Unassigned

Bug Description

After installing kernel 4.13.0-26 (and 4.13.0-31) we are seeing random reboots on virtual machines (VSIs) hosted by SoftLayer. The physical hosts were patched earlier this month but I don't have the details yet or access to the hypervisors. We noticed 4.13.0-31 was rebooting frequently and went to 4.13.0-26 instead which was performing better but still suffering from the random reboots. The VMs still on the old 4.4 kernels haven't had any random reboots at all. We don't have any intel-microcode package installed, and I'm not sure it would make a difference for VMs...? We have seen this on both Broadwell and Haswell systems. The attached apport file is from one of the Broadwell servers.
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Jan 25 11:43 seq
 crw-rw---- 1 root audio 116, 33 Jan 25 11:43 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1:
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcFB:

ProcKernelCmdLine: root=UUID=52c6959b-79b0-4bdd-8ed6-71e0ba782fb4 ro console=hvc0 elevator=noop
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-26-generic N/A
 linux-backports-modules-4.13.0-26-generic N/A
 linux-firmware 1.157.8
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial uec-images xenial uec-images xenial uec-images
Uname: Linux 4.13.0-26-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: False

Trey Tabner (trey) wrote :
Trey Tabner (trey) wrote :
Trey Tabner (trey) wrote :
Trey Tabner (trey) wrote :

There is no output from lspci -vvnn, so not uploading lspci-vvnn.log.

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 1745464

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
tags: added: artful
Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key pti
Changed in linux (Ubuntu Artful):
status: New → Triaged
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Changed in linux (Ubuntu Artful):
importance: Undecided → High
Trey Tabner (trey) wrote : CRDA.txt

apport information

information type: Public → Private Security
tags: added: apport-collected uec-images xenial
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Trey Tabner (trey) on 2018-01-25
information type: Private Security → Public
Joseph Salisbury (jsalisbury) wrote :

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

Download full text (4.1 KiB)

Jim/Christine,

Please look into this.

From: Joseph Salisbury <email address hidden>
To: <email address hidden>
Date: 03/06/2018 09:27 AM
Subject: [Bug 1745464] Re: Random reboots with 4.13.0-26 on Ubuntu 16.04
            LTS
Sent by: <email address hidden>

Would it be possible for you to test the latest upstream kernel? Refer
to
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.ubuntu.com_KernelMainlineBuilds&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=CJEdoL-rwJef2imkYZDMTg&m=kWOu479yyXgkYCuA3cjtxYr1u6gJZ912yJG8rtvZBoE&s=Hkhru8wewXVpuBhsvhsmjA_AlIiovjnjQ0Et9aYrFJs&e=
 . Please test the latest
v4.16 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]
https://urldefense.proofpoint.com/v2/url?u=http-3A__kernel.ubuntu.com_-7Ekernel-2Dppa_mainline_v4.16-2Drc4&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=CJEdoL-rwJef2imkYZDMTg&m=kWOu479yyXgkYCuA3cjtxYr1u6gJZ912yJG8rtvZBoE&s=JsIbFNx75DnKSRHgrmeQdjz90X8oRKZ83ZRBooxKtUE&e=

--
You received this bug notification because you are subscribed to the bug
report.
https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_bugs_1745464&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=CJEdoL-rwJef2imkYZDMTg&m=kWOu479yyXgkYCuA3cjtxYr1u6gJZ912yJG8rtvZBoE&s=rH79xWtZ5MQfW7JXfx3w5wslTCRv9yOwF0WXYvpEDok&e=

Title:
  Random reboots with 4.13.0-26 on Ubuntu 16.04 LTS

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  After installing kernel 4.13.0-26 (and 4.13.0-31) we are seeing random
reboots on virtual machines (VSIs) hosted by SoftLayer. The physical hosts
were patched earlier this month but I don't have the details yet or access
to the hypervisors. We noticed 4.13.0-31 was rebooting frequently and went
to 4.13.0-26 instead which was performing better but still suffering from
the random reboots. The VMs still on the old 4.4 kernels haven't had any
random reboots at all. We don't have any intel-microcode package
installed, and I'm not sure it would make a difference for VMs...? We have
seen this on both Broadwell and Haswell systems. The attached apport file
is from one of the Broadwell servers.
  ---
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116, 1 Jan 25 11:43 seq
   crw-rw---- 1 root audio 116, 33 Jan 25 11:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB:

  ProcKernelCmdLine: root=UUID=52c6959b-79b0-4bdd-...

Read more...

This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu Artful):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers