kernel-packages team mailing list archive

Thread
Date
[Bug 1223851] Re: [Samsung NP550P5C-T01AR] High CPU load after resuming on in BIOS mode

To: kernel-packages@xxxxxxxxxxxxxxxxxxx
From: "Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>
Date: Sat, 15 Feb 2014 00:26:25 -0000
Reply-to: Bug 1223851 <1223851@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
Agustin Barto, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223851/comments/31
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: linux (Ubuntu)
       Status: Triaged => Invalid

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

Title:
  [Samsung NP550P5C-T01AR] High CPU load after resuming on in BIOS mode

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  Description of problem:

  After I resume the system and plug something in one of the machine's USB3 ports, the CPU load raises to 50%, with one particular process with the highest load:
  4 root      20   0     0    0    0 R  50.1  0.0   1:43.63 kworker/0:0

  WORKAROUND: It doesn't happen if I plug the same device on a USB2
  port.

  WORKAROUND:  I noticed that the ACPI dumps differed when the "USB S3
  Wake-Up" was enabled or disabled, so what I took the DSDT for when the
  option is enabled, recompiled it, and forced it using the instructions
  given in http://blog.michael.kuron-germany.de/2011/03/patching-dsdt-
  in-recent-linux-kernels-without-recompiling/ . I then disabled the
  option (so the laptop won't turn itself on when it's in the bag). So
  far, I haven't seen any storms when plunging stuff into the USB3 ports
  and the box stays off at suspend.

  The problem seems to be caused by too many ACPI interrupts:
  root@ubuntu:~# grep -r . /sys/firmware/acpi/interrupts/
  /sys/firmware/acpi/interrupts/sci:12554973
  /sys/firmware/acpi/interrupts/error:       0
  /sys/firmware/acpi/interrupts/gpe00:       0   invalid
  /sys/firmware/acpi/interrupts/gpe01:       0   invalid
  /sys/firmware/acpi/interrupts/gpe02:       0   enabled
  /sys/firmware/acpi/interrupts/gpe03:       0   disabled
  /sys/firmware/acpi/interrupts/gpe04:       0   disabled
  /sys/firmware/acpi/interrupts/gpe05:       0   disabled
  /sys/firmware/acpi/interrupts/gpe06:       0   enabled
  /sys/firmware/acpi/interrupts/gpe07:       0   invalid
  /sys/firmware/acpi/interrupts/gpe08:       0   invalid
  /sys/firmware/acpi/interrupts/gpe09:       0   disabled
  /sys/firmware/acpi/interrupts/gpe10:       0   invalid
  /sys/firmware/acpi/interrupts/gpe11:       0   invalid
  /sys/firmware/acpi/interrupts/gpe12:       0   invalid
  /sys/firmware/acpi/interrupts/gpe13:       0   invalid
  /sys/firmware/acpi/interrupts/gpe14:       0   invalid
  /sys/firmware/acpi/interrupts/gpe15:       0   invalid
  /sys/firmware/acpi/interrupts/gpe16:       0   invalid
  /sys/firmware/acpi/interrupts/gpe0A:       0   invalid
  /sys/firmware/acpi/interrupts/gpe17:    1504   enabled
  /sys/firmware/acpi/interrupts/gpe0B:       0   disabled
  /sys/firmware/acpi/interrupts/gpe18:       0   invalid
  /sys/firmware/acpi/interrupts/gpe0C:       0   disabled
  /sys/firmware/acpi/interrupts/gpe19:       0   invalid
  /sys/firmware/acpi/interrupts/gpe0D:12553562   enabled
  /sys/firmware/acpi/interrupts/gpe0E:       0   disabled
  /sys/firmware/acpi/interrupts/gpe20:       0   disabled
  /sys/firmware/acpi/interrupts/gpe0F:       0   invalid
  /sys/firmware/acpi/interrupts/gpe21:       0   invalid
  /sys/firmware/acpi/interrupts/gpe22:       0   invalid
  /sys/firmware/acpi/interrupts/gpe23:       0   invalid
  /sys/firmware/acpi/interrupts/gpe24:       0   invalid
  /sys/firmware/acpi/interrupts/gpe25:       0   disabled
  /sys/firmware/acpi/interrupts/gpe26:       0   invalid
  /sys/firmware/acpi/interrupts/gpe1A:       0   invalid
  /sys/firmware/acpi/interrupts/gpe27:       0   invalid
  /sys/firmware/acpi/interrupts/gpe1B:       0   invalid
  /sys/firmware/acpi/interrupts/gpe28:       0   invalid
  /sys/firmware/acpi/interrupts/gpe1C:       0   invalid
  /sys/firmware/acpi/interrupts/gpe29:       0   invalid
  /sys/firmware/acpi/interrupts/gpe1D:       0   invalid
  /sys/firmware/acpi/interrupts/gpe1E:       0   enabled
  /sys/firmware/acpi/interrupts/gpe30:       0   invalid
  /sys/firmware/acpi/interrupts/gpe1F:       0   enabled
  /sys/firmware/acpi/interrupts/gpe31:       0   invalid
  /sys/firmware/acpi/interrupts/gpe32:       0   invalid
  /sys/firmware/acpi/interrupts/gpe33:       0   invalid
  /sys/firmware/acpi/interrupts/gpe34:       0   invalid
  /sys/firmware/acpi/interrupts/gpe35:       0   invalid
  /sys/firmware/acpi/interrupts/gpe36:       0   invalid
  /sys/firmware/acpi/interrupts/gpe2A:       0   invalid
  /sys/firmware/acpi/interrupts/gpe37:       0   invalid
  /sys/firmware/acpi/interrupts/gpe2B:       0   invalid
  /sys/firmware/acpi/interrupts/gpe38:       0   invalid
  /sys/firmware/acpi/interrupts/gpe2C:       0   invalid
  /sys/firmware/acpi/interrupts/gpe39:       0   invalid
  /sys/firmware/acpi/interrupts/gpe2D:       0   invalid
  /sys/firmware/acpi/interrupts/gpe2E:       0   invalid
  /sys/firmware/acpi/interrupts/gpe2F:       0   invalid
  /sys/firmware/acpi/interrupts/gpe3A:       0   invalid
  /sys/firmware/acpi/interrupts/gpe3B:       0   invalid
  /sys/firmware/acpi/interrupts/gpe3C:       0   invalid
  /sys/firmware/acpi/interrupts/gpe3D:       0   invalid
  /sys/firmware/acpi/interrupts/gpe3E:       0   invalid
  /sys/firmware/acpi/interrupts/gpe3F:       0   invalid
  /sys/firmware/acpi/interrupts/sci_not:       0
  /sys/firmware/acpi/interrupts/ff_pmtimer:       0   invalid
  /sys/firmware/acpi/interrupts/ff_rt_clk:       0   disabled
  /sys/firmware/acpi/interrupts/gpe_all:12556159
  /sys/firmware/acpi/interrupts/ff_gbl_lock:       0   disabled
  /sys/firmware/acpi/interrupts/ff_pwr_btn:       0   enabled
  /sys/firmware/acpi/interrupts/ff_slp_btn:       0   invalid

  I can mitigate the problem by disabling that particular source

  # echo disable > /sys/firmware/acpi/interrupts/gpe0D

  This also happens on Fedora 19 but doesn't happen on Ubuntu 13.04, so
  it seems the bug was introduced after the 3.8 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-5-generic 3.11.0-5.11
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu     4220 F.... pulseaudio
  CasperVersion: 1.336
  Date: Wed Sep 11 12:31:17 2013
  LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130910)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper  quiet splash -- persistent BOOT_IMAGE=/casper/vmlinuz.efi
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-5-generic N/A
   linux-backports-modules-3.11.0-5-generic  N/A
   linux-firmware                            1.113
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P08AAA.045.130418.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP08AAA.045.130418.dg:bd04/18/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn550P5C/550P7C:pvrP08AAA:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 550P5C/550P7C
  dmi.product.version: P08AAA
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

[Bug 1223851] [NEW] High CPU load after resuming on Samsung NP550P5C in BIOS mode
From: Agustin Barto, 2013-09-11