ami-0567566f (release 20160217.1) is still affected.

$ uptime ; uname -a ; cat /proc/interrupts
 13:57:50 up 7 min,  1 user,  load average: 1.01, 1.06, 0.61
Linux ip-192-168-119-211 4.2.0-27-generic #32-Ubuntu SMP Fri Jan 22 04:49:08 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
           CPU0
  0:      81530  xen-percpu-virq      timer0
  1:          0  xen-percpu-ipi       spinlock0
  2:          0  xen-percpu-ipi       resched0
  3:          0  xen-percpu-ipi       callfunc0
  4:          0  xen-percpu-virq      debug0
  5:          0  xen-percpu-ipi       callfuncsingle0
  6:          0  xen-percpu-ipi       irqwork0
  7:        395   xen-dyn-event     xenbus
  8:        283   xen-dyn-event     rtc0
  9:       6084   xen-dyn-event     blkif
 10:        574   xen-dyn-event     blkif
 11:       1533   xen-dyn-event     eth0
NMI:          0   Non-maskable interrupts
LOC:          0   Local timer interrupts
SPU:          0   Spurious interrupts
PMI:          0   Performance monitoring interrupts
IWI:          0   IRQ work interrupts
RTR:          0   APIC ICR read retries
RES:          0   Rescheduling interrupts
CAL:          0   Function call interrupts
TLB:          0   TLB shootdowns
TRM:          0   Thermal event interrupts
THR:          0   Threshold APIC interrupts
DFR:          0   Deferred Error APIC interrupts
MCE:          0   Machine check exceptions
MCP:          0   Machine check polls
HYP:      89928   Hypervisor callback interrupts
ERR:          0
MIS:          0
PIN:          0   Posted-interrupt notification event
PIW:          0   Posted-interrupt wakeup event

Here's a bit of screen capture from top, later. The instance feels quite
slow due to the competition with kworker and the steal time:

top - 14:05:52 up 15 min,  1 user,  load average: 1.26, 1.40, 0.95
Tasks:  68 total,   3 running,  65 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us, 58.3 sy,  0.0 ni,  0.0 id,  0.0 wa,  0.0 hi,  0.0 si, 41.7 st
KiB Mem:   3837672 total,   345992 used,  3491680 free,    12376 buffers
KiB Swap:        0 total,        0 used,        0 free.   261884 cached Mem

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND
  358 root      20   0       0      0      0 R 99.9  0.0   1:06.65 kworker/0:5
 1918 ubuntu    20   0   23576   3088   2660 R  0.3  0.1   0:00.03 top
    1 root      20   0   37440   5496   3944 S  0.0  0.1   0:03.42 systemd
    2 root      20   0       0      0      0 S  0.0  0.0   0:00.00 kthreadd
    3 root      20   0       0      0      0 S  0.0  0.0   0:00.00 ksoftirqd/0
    4 root      20   0       0      0      0 S  0.0  0.0  13:19.18 kworker/0:0
    5 root       0 -20       0      0      0 S  0.0  0.0   0:00.00 kworker/0:0H
    7 root      20   0       0      0      0 S  0.0  0.0   0:01.68 rcu_sched
    8 root      20   0       0      0      0 S  0.0  0.0   0:00.00 rcu_bh
    9 root      20   0       0      0      0 R  0.0  0.0   0:00.16 rcuos/0
   10 root      20   0       0      0      0 S  0.0  0.0   0:00.00 rcuob/0
   11 root      rt   0       0      0      0 S  0.0  0.0   0:00.00 migration/0
   12 root      rt   0       0      0      0 S  0.0  0.0   0:00.35 watchdog/0
   13 root       0 -20       0      0      0 S  0.0  0.0   0:00.00 khelper
   14 root      20   0       0      0      0 S  0.0  0.0   0:00.00 kdevtmpfs
   15 root       0 -20       0      0      0 S  0.0  0.0   0:00.00 netns
   16 root       0 -20       0      0      0 S  0.0  0.0   0:00.00 perf

I was unable to run powertop on this instance; it exited with a
suggestion to enable CONFIG_X86_MSR.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1544094

Title:
  kworker 100% CPU usage on Xen PV (AWS)

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to