regular hard lockup on bionic kernel

Bug #1767443 reported by Tycho Andersen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
High
Unassigned
Bionic
Expired
High
Unassigned

Bug Description

Hi guys,

I'm sorry I have no real information to add to this, but Serge encouraged me to file a bug to get you guys to help me to debug this, so blame him.

I've been running the bionic kernels on a thinkpad X1 carbon 3rd generation for several months, and experiencing 2x hard lockups per day. Nothing in /var/log/kern.log looks very obvious to me, and I'm not lucky enough to get a stack trace or anything.

Attached are the `ubuntu-bug linux` things that are uploaded automatically, but I'm happy to do whatever science experiments are necessary to get further info.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri Apr 27 10:45:49 2018
InstallationDate: Installed on 2017-11-13 (164 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: linux-signed
UpgradeStatus: Upgraded to bionic on 2018-03-09 (48 days ago)

Revision history for this message
Tycho Andersen (tycho-s) wrote :
Revision history for this message
Tycho Andersen (tycho-s) wrote :

Here's /var/log/kern.log, just for grins.

Revision history for this message
Tyler Hicks (tyhicks) wrote :

FWIW, I verified that Tycho's microcode revision is what's expected for his CPU:

  142: sig 0x000306d4, pf mask 0xc0, 2018-01-18, rev 0x002a, size 18432

I don't think his lockups are due to running a previously published microcode revision that Intel pulled or any bad interactions with the 4.15 kernel.

Andy Whitcroft (apw)
affects: linux-signed (Ubuntu) → linux (Ubuntu)
Revision history for this message
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.17-rc2

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key
tags: added: kernel-key
removed: kernel-da-key
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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 1767443

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
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.