kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.

Before we start the bisect, can you first confirm that 3.19 final does
not have the bug an 4.0-rc1 does have it?  The two kernels can be
downloaded from:

v3.19 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/
4.0-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/

Thanks in advance!

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Also affects: linux (Ubuntu Wily)
   Importance: Medium
       Status: Confirmed

** Changed in: linux (Ubuntu Wily)
     Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Wily)
       Status: Confirmed => In Progress

** Bug watch added: Linux Kernel Bug Tracker #53071
   http://bugzilla.kernel.org/show_bug.cgi?id=53071

** Also affects: linux via
   http://bugzilla.kernel.org/show_bug.cgi?id=53071
   Importance: Unknown
       Status: Unknown

-- 
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/1491467

Title:
  kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  On Fujitsu A544 laptop (and likely others) fitted with SSD, kworker
  takes 100% of one core of CPU due to GPE13 interrupt storm

  See upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=53071

  The bug can be identified by repeatedly running 
  cat /sys/firmware/acpi/interrupts/gpe13
  where a rapidly increasing count will be seen.

  Workaround:
  sudo sh -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpe13'
  disables it until reboot
  Using 
  sudo crontab -e
  and adding the line
  @reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe13
  works around for subsequent boots.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-3-generic 4.1.0-3.3
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  colinl     1699 F.... pulseaudio
   /dev/snd/controlC1:  colinl     1699 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep  2 16:03:19 2015
  InstallationDate: Installed on 2014-10-21 (316 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware                           1.147
  RfKill:
   0: phy0: Wireless LAN
   	Soft blocked: yes
   	Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-08-31 (1 days ago)
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.19
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd04/01/2015:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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