date:20190205

[Kernel-packages] [Bug 503138] Re: Lucid & Natty, KVM, After kernel message hrtimer: interrupt too slow.... the SMP kvm guest becomes slow.

2019-02-05 Thread Arie Skliarouk

This happened because guest used lots of memory on NUMA machine. The KSM
might merge similar memory pages of different VMs, sitting on different
NUMA memory regions, causing the affected processes to crawl.

Disabled KSM merge_across_nodes:

echo 2 > /sys/kernel/mm/ksm/run && sleep 300 && cat 
/sys/kernel/mm/ksm/pages_shared
If there are no pages shared :

echo 0 > /sys/kernel/mm/ksm/merge_across_nodes && echo 1 > 
/sys/kernel/mm/ksm/run
make sure to set merge_across_nodes in /etc/sysctl.d to stay across reboots.

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

Title:
  Lucid & Natty, KVM, After kernel message  hrtimer: interrupt too
  slow the SMP kvm guest becomes slow.

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  KVM Host is running a clean 9.10 server install with just qemu-kvm and 
virt-manager kernel=2.6.31-17-generic
  uname -a: Linux VMMASTER 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 
UTC 2009 i686 GNU/Linux
  version signature: Ubuntu 2.6.31-17.54-generic

  KVM Guest is running a clean 9.10 server install with some userland services 
(apache/postfix/whatnot) kernel=2.6.31-16-generic-pae (from the 
linux-image-virtual package)
  uname -a: Linux VM1 2.6.31-16-generic-pae #53-Ubuntu SMP Tue Dec 8 05:20:21 
UTC 2009 i686 GNU/Linux
  version signature: Ubuntu 2.6.31-16.53-generic-pae

  KVM guest startup command (as invoked by virt-manager):
  /usr/bin/kvm -S -M pc-0.11 -m 1024 -smp 2 -name lexx -uuid [UUID] -monitor 
unix:/var/run/libvirt/qemu/VM1.monitor,server,nowait -boot c -drive 
file=,if=ide,media=cdrom,index=2 -drive 
file=/var/lib/libvirt/images/VM1.img,if=virtio,index=0,boot=on -net 
nic,macaddr=[MAC],vlan=0,model=virtio,name=virtio.0 -net 
tap,fd=16,vlan=0,name=tap.0 -serial none -parallel none -usb -vnc 127.0.0.1:0 
-k en-us -vga cirrus

  Problem description:

  After a while (and high network IO) I see this pop up in my guest dmesg:
hrtimer: interrupt too slow, forcing clock min delta to 215997540 ns
  after that the guest becomes very slow to respond, sometimes taking seconds 
to echo my ssh input back, on a local lan. Only a reboot of the kvm guest fixes 
this, until the dreaded hrtimer message pops up 

  After a lot of googling and trying a lot of things I found this discussion on 
the patchwork kernel mailinglist, which contains a possible solution:
  http://patchwork.kernel.org/patch/51561/

  Please look into it, perhaps this solves a lot of kvm-users' problems

  I'd like to patch my kvm guests' kernel myself to test this hrtimer
  patch, do you have the correct procedure for me so i can create a
  custom kernel?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/503138/+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

[Kernel-packages] [Bug 1778844] Re: nvme multipath does not report path relationships

2019-02-05 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Incomplete => Confirmed

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  Invalid
Status in initramfs-tools source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Invalid

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   73.058099] GPR20: 0e4f79d8d5d8 0001

[Kernel-packages] [Bug 1346917] Re: Using KSM on NUMA capable machines can cause KVM guest performance and stability issues

2019-02-05 Thread Arie Skliarouk

The guest used lots of memory on NUMA machine. Turned out KSM merged
some of the processes pages causing the particular processes to crawl.

Disabled KSM merge_across_nodes and it solved the problem:
echo 2 > /sys/kernel/mm/ksm/run && sleep 300 && cat 
/sys/kernel/mm/ksm/pages_shared
echo 0 > /sys/kernel/mm/ksm/merge_across_nodes && echo 1 > 
/sys/kernel/mm/ksm/run

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

Title:
  Using KSM on NUMA capable machines can cause KVM guest performance and
  stability issues

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  When using KVM on NUMA machines, both Linux and Windows guests can
  exhibit very poor performance and potential crashes. Disabling KSM is
  a known workaround to fix this issue.

  [Fix]

  The following patch fixes the issue in our testing:
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=64a9a34e22896dad430e21a28ad8cb00a756fefc

  This patch is present in v3.14-rc1 and onwards.

  [Test Case]

  General test case:
  1) On a NUMA capable machine, setup the machine as a KVM hypervisor
    - lscpu should show more than 1 NUMA node
  2) Install 4 KVM VMs
  3) Run the following in another terminal to ensure that pages_shared and 
pages_sharing is increasing
   - watch 'tail /sys/kernel/mm/ksm/*'
  4) In another terminal run a program that continually pings each node and 
alerts on high latencies

  What we've observed is that in Linux guests, the ping latencies can go
  into the ~2 second range for a few pings, then return back to the <
  1ms range. (This is machine dependent.) In addition, occasionally when
  running this test with Windows guests we observe BSODs during this
  test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346917/+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

[Kernel-packages] [Bug 1778844] woo_kdump_console logs

2019-02-05 Thread bugproxy

--- Comment on attachment From indira.pr...@in.ibm.com 2019-02-06 01:56 
EDT---


Attached woo kdump scenario console logs

** Attachment added: "woo_kdump_console logs"
   
https://bugs.launchpad.net/bugs/1778844/+attachment/5236276/+files/woo_consolelogs_with_patch.txt

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  Incomplete
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  Invalid
Status in initramfs-tools source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Invalid

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0

[Kernel-packages] [Bug 1778844] Comment bridged from LTC Bugzilla

2019-02-05 Thread bugproxy

--- Comment From indira.pr...@in.ibm.com 2019-02-06 01:54 EDT---
Have installed below patch and retried kdump scenario with root disk as nvme 
disk. Now system is not dropping to initramfs state its moving further but not 
saving dump file (core) properly.

initramfs-tools_0.130ubuntu3.6+nvme1_all.deb
initramfs-tools-bin_0.130ubuntu3.6+nvme1_ppc64el.deb
initramfs-tools-core_0.130ubuntu3.6+nvme1_all.deb

root@woo:~# dpkg -l | grep initramfs
ii  busybox-initramfs 1:1.27.2-2ubuntu3 
ppc64el  Standalone shell setup for initramfs
ii  initramfs-tools   0.130ubuntu3.6+nvme1  all 
 generic modular initramfs generator (automation)
ii  initramfs-tools-bin   0.130ubuntu3.6+nvme1  
ppc64el  binaries used by initramfs-tools
ii  initramfs-tools-core  0.130ubuntu3.6+nvme1  all 
 generic modular initramfs generator (core tools)
ii  libklibc  2.0.4-9ubuntu2
ppc64el  minimal libc subset for use with initramfs
root@woo:~#

rm /var/lib/kdump/initr*
reboot
After reboot triggered crash

> Attached console logs

Regards,
Indira

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  Incomplete
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  Invalid
Status in initramfs-tools source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Invalid

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink

[Kernel-packages] [Bug 503138] Re: Lucid & Natty, KVM, After kernel message hrtimer: interrupt too slow.... the SMP kvm guest becomes slow.

2019-02-05 Thread Christian Ehrhardt 

Hi Arie,
I saw you also posting on some other old bugs with the same symptom (e.g. 
1346917).
And that exactly is the problem with this issue - the message only represents 
the symptom but not the root cause. Fixing the symptom makes no sense, because 
if your IRQ delivery is stalled then it is stalled - there is only very little 
the system can do other than trottling it down.
If you follow the discussion around [1] you'll see that this was the thought 
back then and it didn't change since then AFAIK.

There were cases around KSM (bug 1346917), but also others around broken
RAM, then others had just overloaded their CPUs, others had scheduler
bug triggering the same while in other cases there was a thundering herd
issue. The only thing all of these cases share is that eventually
something (tm) happened which made IRQ/hrtimers stutter to then throttle
them down.

Many of the underlying issues causing that have been fixed over the
years - this got more rare nowadays. But for each case still left one
would not need a "this happened again here" message. But instead a way
to reproduce, to then debug the root cause of this exact case and check
for a fix then.

Therefore three recommendations for people affected:
1. Try as good as you can to get it to reproduce reliably and then outline 
these steps, this will help people to hopefully get a grasp of the root cause. 
Do -not- just report the "hrtimer: interrupt took" being the symptom
2. Always try the same setup you have, but with the very latest virtualization 
stack provided - quite often things are fixed there and if that is confirmed it 
becomes "only" a binary search what would need to be backported.
3. open a new bug for these, because until a root cause of a given case is 
found and identified to be the same we don't know if it is the same issue.

[1]: http://www.mail-archive.com/kvm@vger.kernel.org/msg23491.html

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: kvm (Ubuntu) => qemu (Ubuntu)

** Changed in: qemu (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  Lucid & Natty, KVM, After kernel message  hrtimer: interrupt too
  slow the SMP kvm guest becomes slow.

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  KVM Host is running a clean 9.10 server install with just qemu-kvm and 
virt-manager kernel=2.6.31-17-generic
  uname -a: Linux VMMASTER 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 
UTC 2009 i686 GNU/Linux
  version signature: Ubuntu 2.6.31-17.54-generic

  KVM Guest is running a clean 9.10 server install with some userland services 
(apache/postfix/whatnot) kernel=2.6.31-16-generic-pae (from the 
linux-image-virtual package)
  uname -a: Linux VM1 2.6.31-16-generic-pae #53-Ubuntu SMP Tue Dec 8 05:20:21 
UTC 2009 i686 GNU/Linux
  version signature: Ubuntu 2.6.31-16.53-generic-pae

  KVM guest startup command (as invoked by virt-manager):
  /usr/bin/kvm -S -M pc-0.11 -m 1024 -smp 2 -name lexx -uuid [UUID] -monitor 
unix:/var/run/libvirt/qemu/VM1.monitor,server,nowait -boot c -drive 
file=,if=ide,media=cdrom,index=2 -drive 
file=/var/lib/libvirt/images/VM1.img,if=virtio,index=0,boot=on -net 
nic,macaddr=[MAC],vlan=0,model=virtio,name=virtio.0 -net 
tap,fd=16,vlan=0,name=tap.0 -serial none -parallel none -usb -vnc 127.0.0.1:0 
-k en-us -vga cirrus

  Problem description:

  After a while (and high network IO) I see this pop up in my guest dmesg:
hrtimer: interrupt too slow, forcing clock min delta to 215997540 ns
  after that the guest becomes very slow to respond, sometimes taking seconds 
to echo my ssh input back, on a local lan. Only a reboot of the kvm guest fixes 
this, until the dreaded hrtimer message pops up 

  After a lot of googling and trying a lot of things I found this discussion on 
the patchwork kernel mailinglist, which contains a possible solution:
  http://patchwork.kernel.org/patch/51561/

  Please look into it, perhaps this solves a lot of kvm-users' problems

  I'd like to patch my kvm guests' kernel myself to test this hrtimer
  patch, do you have the correct procedure for me so i can create a
  custom kernel?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/503138/+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

[Kernel-packages] [Bug 1808743] sosreport

2019-02-05 Thread bugproxy

--- Comment (attachment only) From sthou...@in.ibm.com 2019-02-06 01:40 
EDT---


** Attachment added: "sosreport"
   
https://bugs.launchpad.net/bugs/1808743/+attachment/5236275/+files/sosreport-ubuntu1810.guest-20181203024833.tar.xz

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

Title:
  [Ubuntu 1810] Kdump fails to dump vmcore and enters initramfs inside
  Power9 KVM guest

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Triaged

Bug description:
  Kdump fails to dump vmcore even with workaround suggested

  This issue is submitted to
  track on Power9 Guest where it uses file type qcow2 disk (virtio-scsi)

  
  Boot Log: (Attached full console log)

  [3.754031]32regs: 19616.000 MB/sec
  [3.794031]32regs_prefetch: 17280.000 MB/sec
  [3.834030]altivec   : 22480.000 MB/sec
  [3.834063] xor: using function: altivec (22480.000 MB/sec)
  done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
done.
  Begin: Running /scripts/local-premount ... done.
  Begin: Waiting for root file system ... Begin: Running /scripts/local-block 
... mdadm: No devices listed in conf file were found.
  done.
  mdadm: No devices listed in conf file were found.
  mdadm: No devices listed in conf file were found.
  mdadm: No devices listed in conf file were found.
  done.
  Gave up waiting for root file system device.  Common problems:
   - Boot args (cat /proc/cmdline)
 - Check rootdelay= (did the system wait long enough?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT!  UUID=5e1fe9e9-cf03-4c73-adce-0e57676f98e0 does not exist.  Dropping 
to a shell!

  
  BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)

  Contact Information = Balamuruhan S / balamuruh...@in.ibm.com 
   
  ---uname output---

  Guest Kernel: 4.18.0-11-generic
  Host Kernel:  4.18.0-11-generic
   
  Machine Type = Boston 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Have a healthy KVM guest with Ubuntu 1810 with kernel 4.18.0-11-generic
  2. Install kdump, kexec and crash tools in the guest,
  # dpkg -l | grep crash
  ii  apport2.20.10-0ubuntu13.1 
 all  automatically generate crash reports for debugging
  ii  crash 7.2.3+real-1
 ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools   1:1.6.4-2ubuntu1
 ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  linux-crashdump   4.18.0.11.12
 ppc64el  Linux kernel crashdump setup for the latest generic kernel
  ii  python3-apport2.20.10-0ubuntu13.1 
 all  Python 3 library for Apport crash report handling

  3. Ensure workaround suggested in Bug 172389 is followed by uncomment the 
`KDUMP_CMDLINE_APPEND`
  and change nr_cpus to maxcpus in /etc/default/kdump-tools config file,
   
  # cat /etc/default/kdump-tools | grep -i cmdline
  # KDUMP_CMDLINE - The default is to use the contents of /proc/cmdline.  
  # Set this variable to override /proc/cmdline.
  # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line 
  #KDUMP_CMDLINE=""
  KDUMP_CMDLINE_APPEND="1 maxcpus=1 systemd.unit=kdump-tools.service irqpoll 
noirqdistrib nousb reset_devices"

  4. restart the kdump tools service,
  # service kdump-tools restart
  # service kdump-tools status
  ? kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: active (exited) since Mon 2018-12-03 02:34:03 CST; 1 weeks 3 days 
ago
Process: 1560 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/S
   Main PID: 1560 (code=exited, status=0/SUCCESS)

  Dec 03 02:34:02 ubuntu1810 systemd[1]: Starting Kernel crash dump capture 
servic
  Dec 03 02:34:02 ubuntu1810 kdump-tools[1560]: Starting kdump-tools:  * 
Creating 
  Dec 03 02:34:02 ubuntu1810 kdump-tools[1560]:  * Creating symlink 
/var/lib/kdump
  Dec 03 02:34:03 ubuntu1810 kdump-tools[1560]: Modified 
cmdline:BOOT_IMAGE=/boot/
  Dec 03 02:34:03 ubuntu1810 kdump-tools[1560]:  * loaded kdump kernel
  Dec 03 02:34:03 ubuntu1810 kdump-tools[1678]: /sbin/kexec -p 
--command-line="BOO
  Dec 03 02:34:03 ubuntu1810 kdump-tools[1679]: loaded kdump kernel
  Dec 03 02:34:03 ubuntu1810 systemd[1]: Started Kernel crash dump capture 
service

  5. check kdump-config is state is ready to dump,
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL:

[Kernel-packages] [Bug 1808743] console.log

2019-02-05 Thread bugproxy

--- Comment (attachment only) From sthou...@in.ibm.com 2019-02-06 01:39 
EDT---


** Attachment added: "console.log"
   
https://bugs.launchpad.net/bugs/1808743/+attachment/5236274/+files/console.log

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

Title:
  [Ubuntu 1810] Kdump fails to dump vmcore and enters initramfs inside
  Power9 KVM guest

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Triaged

Bug description:
  Kdump fails to dump vmcore even with workaround suggested

  This issue is submitted to
  track on Power9 Guest where it uses file type qcow2 disk (virtio-scsi)

  
  Boot Log: (Attached full console log)

  [3.754031]32regs: 19616.000 MB/sec
  [3.794031]32regs_prefetch: 17280.000 MB/sec
  [3.834030]altivec   : 22480.000 MB/sec
  [3.834063] xor: using function: altivec (22480.000 MB/sec)
  done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
done.
  Begin: Running /scripts/local-premount ... done.
  Begin: Waiting for root file system ... Begin: Running /scripts/local-block 
... mdadm: No devices listed in conf file were found.
  done.
  mdadm: No devices listed in conf file were found.
  mdadm: No devices listed in conf file were found.
  mdadm: No devices listed in conf file were found.
  done.
  Gave up waiting for root file system device.  Common problems:
   - Boot args (cat /proc/cmdline)
 - Check rootdelay= (did the system wait long enough?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT!  UUID=5e1fe9e9-cf03-4c73-adce-0e57676f98e0 does not exist.  Dropping 
to a shell!

  
  BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)

  Contact Information = Balamuruhan S / balamuruh...@in.ibm.com 
   
  ---uname output---

  Guest Kernel: 4.18.0-11-generic
  Host Kernel:  4.18.0-11-generic
   
  Machine Type = Boston 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Have a healthy KVM guest with Ubuntu 1810 with kernel 4.18.0-11-generic
  2. Install kdump, kexec and crash tools in the guest,
  # dpkg -l | grep crash
  ii  apport2.20.10-0ubuntu13.1 
 all  automatically generate crash reports for debugging
  ii  crash 7.2.3+real-1
 ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools   1:1.6.4-2ubuntu1
 ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  linux-crashdump   4.18.0.11.12
 ppc64el  Linux kernel crashdump setup for the latest generic kernel
  ii  python3-apport2.20.10-0ubuntu13.1 
 all  Python 3 library for Apport crash report handling

  3. Ensure workaround suggested in Bug 172389 is followed by uncomment the 
`KDUMP_CMDLINE_APPEND`
  and change nr_cpus to maxcpus in /etc/default/kdump-tools config file,
   
  # cat /etc/default/kdump-tools | grep -i cmdline
  # KDUMP_CMDLINE - The default is to use the contents of /proc/cmdline.  
  # Set this variable to override /proc/cmdline.
  # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line 
  #KDUMP_CMDLINE=""
  KDUMP_CMDLINE_APPEND="1 maxcpus=1 systemd.unit=kdump-tools.service irqpoll 
noirqdistrib nousb reset_devices"

  4. restart the kdump tools service,
  # service kdump-tools restart
  # service kdump-tools status
  ? kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: active (exited) since Mon 2018-12-03 02:34:03 CST; 1 weeks 3 days 
ago
Process: 1560 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/S
   Main PID: 1560 (code=exited, status=0/SUCCESS)

  Dec 03 02:34:02 ubuntu1810 systemd[1]: Starting Kernel crash dump capture 
servic
  Dec 03 02:34:02 ubuntu1810 kdump-tools[1560]: Starting kdump-tools:  * 
Creating 
  Dec 03 02:34:02 ubuntu1810 kdump-tools[1560]:  * Creating symlink 
/var/lib/kdump
  Dec 03 02:34:03 ubuntu1810 kdump-tools[1560]: Modified 
cmdline:BOOT_IMAGE=/boot/
  Dec 03 02:34:03 ubuntu1810 kdump-tools[1560]:  * loaded kdump kernel
  Dec 03 02:34:03 ubuntu1810 kdump-tools[1678]: /sbin/kexec -p 
--command-line="BOO
  Dec 03 02:34:03 ubuntu1810 kdump-tools[1679]: loaded kdump kernel
  Dec 03 02:34:03 ubuntu1810 systemd[1]: Started Kernel crash dump capture 
service

  5. check kdump-config is state is ready to dump,
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:

[Kernel-packages] [Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays

2019-02-05 Thread Slava Koyfman

I'm also experiencing this issue on a Thinkpad T480 (20L5) connecting to
a ThinkPad Thunderbolt 3 Dock. It worked fine on Ubuntu 18.04 LTS until
about a week ago, when I started experiencing this issue and the bug in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663 more or
less simultaneously.

The latter issue was resolved by downgrading to kernel 4.15.0-43, and
later upgrading to 4.15.0-45.

This one remained a problem even after upgrading to Ubuntu 18.10 and
kernel 4.18.0-14. I can confirm that installing kernel 4.20.6-042006 via
Ukuu fixes it.

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

Title:
TB16 dock freezes X on hotplug when used with external displays

Status in Dell Sputnik:
New
Status in linux package in Ubuntu:
Confirmed

Bug description:
Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux
REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released
12/15/2017. If it can be of any help, I can get this tested on an XPS
9560 (GTX 1050) too.

Steps to reproduce:

1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI
cables are used, but I doubt that it matters.
2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME.
3. Select nVidia GPU in PRIME settings, reboot if needed.
4. Either boot with the dock connected or connect it after booting into user
session.
5. Set up monitors if necessary. At this point everything should be working
fine.
6. Disconnect the dock, give it a moment to adjust to the new window layout
etc.
7. Re-connect the dock. Within a few seconds laptop screen should freeze and
external monitors should remain blank, as if not connected.
8. Disconnect the dock. Within a few seconds laptop screen should unfreeze.
There is a small chance that it won't if you repeat this procedure multiple
times.

Errors in dmesg indicate that i915 driver is somehow involved:

[ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out
waiting for DP idle patterns
[ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting
for DDI BUF B idle bit
[ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out
waiting for DP idle patterns
[ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting
for DDI BUF C idle bit

The kernel logs are flooded with these between steps 7 and 8 above.

This behaviour does not occur when Intel GPU is selected in PRIME
settings or when nouveau is used. However, nouveau performance leaves
a lot to be desired, particularly with 3D acceleration in Windows 10
VMs.

I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make
any difference.

Other reports that may be related:

https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a
-docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes-
hangs-the-whole-machine/ - same error messages

https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189
- "Connecting and disconnecting the TB16 sometimes freeze the laptop."

https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466
- "Hot-plugging the screen does not work."
---
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gboiko 2491 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c
InstallationDate: Installed on 2017-10-01 (149 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp.
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5520
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic
root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0
biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
RelatedPackageVersions:
linux-restricted-modules-4.13.0-36-generic N/A
linux-backports-modules-4.13.0-36-generic N/A
linux-firmware 1.170
Tags: xenial
Uname: Linux 4.13.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin

1 2 3 >

1 - 100 of 247 matches

Mail list logo