@Joseph Salisbury,

Hi.

It looks as if the Ubuntu kernel source has diverged from stable in a 
significant way.  In particular,
as has already been noted, on 3/10/2017, Canonical cherry-picked several 
patches from 4.11-pre, apparently relating to:

http://bugs.launchpad.net/bugs/1671613

Somewhere in there, I suspect, is the underlying cause of the present
BUG.

You already tried overlaying an essential fix-up,
d75450ff40df0199bf13dfb19f435519ff947138, as suggested in comment #52,
and that did appear to improve stability, but not completely resolve the
issue for myself and others.

Looking at mainline, I see a rather large number of memory memory
management-related patches from Kirill A. Shutemov and others that
follow ace71a19cec5eb430207c3269d8a2683f0574306 "mm: introduce
page_vma_mapped_walk()" from 2/24/2017.  It could be that adding one or
more of those patches would stabilize the backported series relating to
http://bugs.launchpad.net/bugs/1671613.

The reason for this note is to observe that the absence of the present
BUG in 4.10.x stable may well be due to the absence of the Canonical
backported patches, rather than due to some additive fix.

Reverting the http://bugs.launchpad.net/bugs/1671613 patch series might
be another path to isolating the source of the BUG.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu    2221 F.... pulseaudio
   /dev/snd/pcmC1D0p:   mathieu    2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu    2221 F.... pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware                             1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to