[Kernel-packages] [Bug 1793369] Re: Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc/sysrq-trigger

[Vipin K Parashar]

** Summary changed:

- Ubuntu18.10:Witherspoon:DD2.2 - Sysrq trigger disabled when writing to 
/proc/sysrq-trigger
+ Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to 
/proc/sysrq-trigger

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

Title:
  Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc
  /sysrq-trigger

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Cosmic:
  Triaged

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2018-09-19 
04:49:39 ==
  ---Problem Description---
   [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] : Sysrq trigger disabled 
when writing to /proc/sysrq-trigger 

  while  testing kdump trying trigger kdump panic via /proc/sysrq-trigger it 
failed as : SysRq : This sysrq operation is disabled
  LOG:

  root@test:~# cat /proc/sys/kernel/sysrq 
  176
  root@test:~# echo c > /proc/sysrq-trigger
  root@test:~# dmesg
  [  380.340051] mlx5_core :01:00.1 enp1s0f1: Self test out: status 
flags(0x2)
  [  389.404239] sysrq: SysRq : This sysrq operation is disabled.
  root@test~# cat /boot/config-4.18.0-7-generic | grep CONFIG_MAGIC_SYSRQ
  CONFIG_MAGIC_SYSRQ=y
  CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x01b6
  CONFIG_MAGIC_SYSRQ_SERIAL=y
  root@test:~# cat /etc/sysctl.conf | grep kernel.sysrq
  #kernel.sysrq=438
  root@test:~# 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.18.0-7-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.18.0-7-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=c0302064-c5a3-49a7-8bd4-402283e6fcbe ro quiet splash 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@test:~# 

  Regards
  Praveen

  == Comment: #2 - Praveen K. Pandey  - 2018-09-19 
05:16:11 ==
  when i enable  in /etc/sysctl.conf it works  . i append below value in  
sysctl.conf

  echo "kernel.sysrq = 1" >> /etc/sysctl.conf

  I think this is should be enable by default  in ubuntu 18.10 as
  earlier ubuntu distro it has , not sure why it got removed as kdump
  mechanism require this .

  Praveen
  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1793369/+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 1775527] Re: Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test running after a day #345

[Vipin K Parashar]

** Summary changed:

- ISST-LTE:Briggs:Ubuntu16.04:KVM - xfs_log_force: error -5 returned after 
stress test running after a day #345
+ Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test running 
after a day #345

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

Title:
  Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test
  running after a day #345

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2016-09-08 15:01:30 
==
  We have installed 16.04.1 on our guest and running IO stress test against via 
virtual qlogic disk. After running around 8 hrs, this error popping up 
"xfs_imap_to_bp: xfs_trans_read_buf() returned error -5" then with all of these 
errors "xfs_log_force: error -5 returned" fill up all the log.

  Jul 19 19:03:41 tinyg2 kernel: [65047.974604] XFS (vdb9): metadata I/O error: 
block 0x2f140 ("xfs_trans_read_buf_map") error 5 numblks 32
  Jul 19 19:03:41 tinyg2 kernel: [65047.975885] XFS (vdb9): xfs_imap_to_bp: 
xfs_trans_read_buf() returned error -5.
  Jul 19 19:03:41 tinyg2 kernel: [65047.976069] XFS (vdb9): 
xfs_do_force_shutdown(0x8) called from line 3433 of file 
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_inode.c. Return address = 
0xd37951f4
  Jul 19 19:03:41 tinyg2 kernel: [65047.976457] XFS (vdb9): metadata I/O error: 
block 0x703d54 ("xlog_iodone") error 5 numblks 64
  Jul 19 19:03:41 tinyg2 kernel: [65047.976662] XFS (vdb9): 
xfs_do_force_shutdown(0x2) called from line 1197 of file 
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_log.c. Return address = 
0xd37a4c00
  Jul 19 19:03:41 tinyg2 kernel: [65047.976995] XFS (vdb9): Log I/O Error 
Detected. Shutting down filesystem
  Jul 19 19:03:41 tinyg2 kernel: [65047.977114] XFS (vdb9): Please umount the 
filesystem and rectify the problem(s)

  follow with all of these error that quickly fill up dmesg log
  Jul 19 19:04:37 tinyg2 kernel: [65103.515386] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:05:07 tinyg2 kernel: [65133.595369] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:05:37 tinyg2 kernel: [65163.679358] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:06:07 tinyg2 kernel: [65193.755383] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:06:37 tinyg2 kernel: [65223.835396] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:06:51 tinyg2 kernel: [65237.091455] EXT4-fs (loop1): mounting ext2 
file system using the ext4 subsystem
  Jul 19 19:06:51 tinyg2 kernel: [65237.093219] EXT4-fs (loop1): mounted 
filesystem without journal. Opts: (null)
  Jul 19 19:06:51 tinyg2 kernel: [65237.623893] Process accounting resumed
  Jul 19 19:07:07 tinyg2 kernel: [65253.919361] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:07:37 tinyg2 kernel: [65283.995393] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:08:08 tinyg2 kernel: [65314.075378] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:08:38 tinyg2 kernel: [65344.155397] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:09:08 tinyg2 kernel: [65374.235367] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:09:38 tinyg2 kernel: [65404.319354] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:10:08 tinyg2 kernel: [65434.395368] XFS (vdb9): xfs_log_force: 
error -5 returned.

  == Comment: #1 - Chanh H. Nguyen  - 2016-09-08 15:02:27 
==
  We recently re-created this bug on our new system "cressg2" which is using a 
different SAN on kernel -36. 
  My Ubuntu 16.04.1 guest, cressg2, are running the IO and other stress test, 
and it is hitting "xfs_log_force: error -5 returned"  problem after it runs the 
tests for 15 hours. It is using our lab storage (SVC SAN storage configuation 
with access to DS8000 Volume) and switch, compare to tinyg3, so it is using 
different storage and fabric switch. 

  root@cressg2:~# uname -a
  Linux cressg2 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:00:57 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  [Wed Sep  7 10:26:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:18 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:32 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:49 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:56 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:28:18 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:28:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:29:18 2016] XFS 

[Kernel-packages] [Bug 1755712] Re: Ubuntu18.04 - KVM on S390 - Multiple epoch facility bugs

[Vipin K Parashar]

** Summary changed:

- KVM: multiple epoch facility bugs
+ Ubuntu18.04 - KVM on S390 -  Multiple epoch facility bugs

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

Title:
  Ubuntu18.04 - KVM on S390 -  Multiple epoch facility bugs

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  The bionic 4.15 kernel contains KVM/s390 support for the multiple epoch 
facility.
  This code has some bugs which can result in hanging guests when running the 
guest on a  z14 with a recent guest kernel (containing 
6e2ef5e4f6cc57344762932d70d38ba4ec65fa8bs390/time: add support for the TOD 
clock epoch extension)

  The following upstream commits are necessary to fix the multi epoch facility
  0e7def5fb0dc KVM: s390: provide only a single function for setting the tod 
(fix SCK)
  1575767ef3cf KVM: s390: consider epoch index on TOD clock syncs
  d16b52cb9cdb KVM: s390: consider epoch index on hotplugged CPUs
  5fe01793dd95 KVM: s390: take care of clock-comparator sign control

  As an alternative 4.15.8 also contains these fixes.

  
  ---uname output---
  4.15
   
  ---Additional Hardware Info---
  Z14 LPAR 

   
  Machine Type = IBM z14 
   
  ---System Hang---
  A simple test case to trigger the hang of guests:

  qemu-system-s390x  -drive file=/data/bionic-server-
  s390x.iso,if=none,id=d1 -nographic -enable-kvm -device virtio-scsi-ccw
  -device scsi-cd,drive=d1 -m 1G   -cpu z14,mepoch=on

  it hangs
  just before printing the network dialog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1755712/+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 1693566] Re: Ubuntu 16.04.03: "NMI watchdog: BUG: soft lockup" occurs while running stress-ng on PowerNV machine.

[Vipin K Parashar]

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Ubuntu 16.04.03: "NMI watchdog: BUG: soft lockup" occurs while running
  stress-ng on PowerNV machine.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <pavra...@in.ibm.com> - 2017-05-17 
05:55:38 ==
  --- Problem description 

  Ubuntu 16.04.03: "NMI watchdog: BUG: soft lockup" occurs while running
  stress-ng on NV machine.

  --- Steps to recreate--

  1. Install ubuntu16.04.03.
  2. Run "stress-ng -a 0".

  Logs:
  

  [ 2660.437087] INFO: rcu_sched self-detected stall on CPU
  [ 2660.437111]22-...: (5247 ticks this GP) idle=e19/141/0 
softirq=905/905 fqs=2380 
  [ 2660.437114] (t=5251 jiffies g=95606 c=95605 q=2545946)
  [ 2660.437750]24-...: (5250 ticks this GP) idle=0b7/141/0 
softirq=5805/5805 fqs=2380 
  [ 2660.437859]
  [ 2664.172796] NMI watchdog: BUG: soft lockup - CPU#22 stuck for 23s! 
[stress-ng-mmap:3509]
  [ 2664.172808] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 23s! 
[stress-ng-mrema:3536]
  [ 2674.848037] NMI watchdog: BUG: soft lockup - CPU#5 stuck for 33s! 
[stress-ng-fork:3381]
  [ 2676.172894] NMI watchdog: BUG: soft lockup - CPU#30 stuck for 22s! 
[kswapd0:992]
  [ 2680.336844] NMI watchdog: BUG: soft lockup - CPU#98 stuck for 23s! 
[stress-ng-clock:5099]
  [ 2686.140931] NMI watchdog: BUG: soft lockup - CPU#16 stuck for 39s! 
[stress-ng-clone:3366]
  [ 2686.987192] xhci_hcd 0003:09:00.0: HC died; cleaning up
  [ 2686.987212] usb 1-3-port3: cannot reset (err = -108)

  After few hours machine will become completely unresponsive

  [pavithra@localhost ~]$ ping 9.47.69.255
  PING 9.47.69.255 (9.47.69.255) 56(84) bytes of data.
  ^C
  --- 9.47.69.255 ping statistics ---
  12 packets transmitted, 0 received, 100% packet loss, time 11000ms

  
  Thanks,
  Pavithra

  == Comment: #6 - VIPIN K. PARASHAR <vipar...@in.ibm.com> - 2017-05-25 
03:32:26 ==
  ubuntu@ltc-firep2:~$ hostname -i
  9.47.69.255
  ubuntu@ltc-firep2:~$ uname -a
  Linux ltc-firep2 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
  ubuntu@ltc-firep2:~$ cat /etc/os-release
  NAME="Ubuntu"
  VERSION="16.04.2 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.2 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  ubuntu@ltc-firep2:~$ tail /proc/cpuinfo
  processor : 159
  cpu   : POWER8 (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.0 (pvr 004d 0200)

  timebase  : 51200
  platform  : PowerNV
  model : 8335-GTA
  machine   : PowerNV 8335-GTA
  firmware  : OPAL
  ubuntu@ltc-firep2:~$

  
  == Comment: #11 - VIPIN K. PARASHAR <vipar...@in.ibm.com> - 2017-05-25 
06:27:12 ==
  System Memory stats
  ==
  ubuntu@ltc-firep2:~$ numactl -H
  available: 2 nodes (0,8)
  node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 
25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 
51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 
77 78 79
  node 0 size: 61321 MB
  node 0 free: 60297 MB
  node 8 cpus: 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 
101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 
121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 
141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159
  node 8 size: 65303 MB
  node 8 free: 64923 MB
  node distances:
  node   0   8 
0:  10  40 
8:  40  10 
  ubuntu@ltc-firep2:~$ free -h 
totalusedfree  shared  buff/cache   
available
  Mem:   123G534M122G 20M868M
121G
  Swap:   37G  0B 37G
  ubuntu@ltc-firep2:~$ sudo sysctl vm | grep free
  vm.min_free_kbytes = 360448
  ubuntu@ltc-firep2:~$ 

  Host is having 123 GB of memory spread across two nodes. 
  Swap is configured to be 37GB and VM min free bytes is set to 360MB.

  == Comment: #13 - VIPIN K. PARASHAR <vipar...@in.ibm.com> - 2017-05-25
  07:25:35 ==

  [  280.494345] NMI watchdog: BUG: soft lockup - CPU#5 stuck for 23s! 
[stress-ng-mmap:4172]
  [  280.495250] CPU: 5 PID: 4172 Comm: stress-ng-mmap Not tainted 
4.10.0-21-generic #23~16.04.1-Ubuntu
  [  280.495262] task: c00fe318c600 task.stack: c00fc0d7c000
  [  280.495271] NIP: c01a3248 LR: c

[Kernel-packages] [Bug 1680390] Re: Ubuntu17.04: Kernel Oops: Exception in kernel mode, sig: 5 [#1] during Avocado KVM Test runs [Regression]

[Vipin K Parashar]

079] [c007f07bb930] [c02b59ac] 
get_user_pages_fast+0xac/0x100
  [20751.912152] [c007f07bb980] [df66ca74] 
kvmppc_book3s_hv_page_fault+0x2bc/0xbb0 [kvm_hv]
  [20751.912236] [c007f07bba70] [df6696f8] 
kvmppc_vcpu_run_hv+0xe60/0x1220 [kvm_hv]
  [20751.912312] [c007f07bbb80] [df6131ac] 
kvmppc_vcpu_run+0x34/0x48 [kvm]
  [20751.912387] [c007f07bbba0] [df61030c] 
kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm]
  [20751.912462] [c007f07bbbe0] [df603db8] 
kvm_vcpu_ioctl+0x500/0x780 [kvm]
  [20751.912534] [c007f07bbd40] [c035b1f4] do_vfs_ioctl+0xd4/0x8c0
  [20751.912594] [c007f07bbde0] [c035bab4] SyS_ioctl+0xd4/0xf0
  [20751.912654] [c007f07bbe30] [c000b184] system_call+0x38/0xe0
  [20751.912713] Instruction dump:
  [20751.912749] 3d020017 79293448 39481a68 ebca 7fde4a14 e93e0020 712a0001 
4082014c 
  [20751.912822] 7fc9f378 e929 7d2948f8 792907e0 <0b09> 3940 
3bbe001c 3901 
  [20751.912899] ---[ end trace 5eaae2f83c5daa20 ]---

  System Dump Info:
The system is not configured to capture a system dump.
   

  == Comment: #3 - IRANNA D. ANKAD <iranna.an...@in.ibm.com> - 2017-03-28 
01:50:15 ==
  This is a regression from 4.10.0-13 kernel and blocking our regression tetsing

  
  == Comment: #10 - VIPIN K. PARASHAR <vipar...@in.ibm.com> - 2017-03-30 
03:44:13 ==

  root@ltc-test-ci1:~# uname -a
  Linux ltc-test-ci1 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
  root@ltc-test-ci1:~# cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="17.04 (Zesty Zapus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Zesty Zapus (development branch)"
  VERSION_ID="17.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=zesty
  UBUNTU_CODENAME=zesty
  root@ltc-test-ci1:~# tail /proc/cpuinfo 
  processor : 79
  cpu   : POWER8E (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.1 (pvr 004b 0201)

  timebase  : 51200
  platform  : PowerNV
  model : 8247-21L
  machine       : PowerNV 8247-21L
  firmware  : OPAL
  root@ltc-test-ci1:~# 

  == Comment: #11 - VIPIN K. PARASHAR <vipar...@in.ibm.com> - 2017-03-30 
03:58:04 ==
  Mar 24 07:15:57
  ===

  [ 1955.041619] [ cut here ]
  [ 1955.041623] kernel BUG at 
/build/linux-HLNhAK/linux-4.10.0/include/linux/swapops.h:129!
  [ 1955.041633] Oops: Exception in kernel mode, sig: 5 [#1]
  [ 1955.041637] SMP NR_CPUS=2048
  [ 1955.041638] NUMA
  [ 1955.041641] PowerNV
  [ 1955.041645] Modules linked in: vhost_net macvtap macvlan rpcsec_gss_krb5 
nfsv4 nfs fscache xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 kvm_hv 
kvm_pr kvm tcm_fc libfc usb_f_tcm tcm_usb_gadget libcomposite udc_core 
tcm_qla2xxx qla2xxx scsi_transport_fc ib_srpt iscsi_target_mod tcm_loop 
vhost_scsi vhost target_core_user target_core_file target_core_iblock 
target_core_pscsi target_core_mod ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 
xt_tcpudp ipt_REJECT nf_reject_ipv4 xt_conntrack ip_set nfnetlink 
ebtable_broute bridge stp llc ebtable_nat ip6table_raw ip6table_security 
ip6table_mangle ip6table_nat iptable_raw iptable_security iptable_mangle 
iptable_nat ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter 
openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4
  [ 1955.041724]  nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc powernv_rng 
powernv_op_panel ipmi_powernv ipmi_devintf ipmi_msghandler leds_powernv 
uio_pdrv_genirq uio vmx_crypto nfsd auth_rpcgss nfs_acl lockd grace sunrpc 
ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas 
crc32c_vpmsum tg3 ipr
  [ 1955.041786] CPU: 40 PID: 7306 Comm: CPU 13/KVM Not tainted 
4.10.0-14-generic #16-Ubuntu
  [ 1955.041792] task: c007937b5a00 task.stack: c007f2a48000
  [ 1955.041796] NIP: c030d748 LR: c030d658 CTR: 

  [ 1955.041801] REGS: c007f2a4b3b0 TRAP: 0700   Not tainted  
(4.10.0-14-generic)
  [ 1955.041805] MSR: 9282b033 <SF,HV,VEC,VSX,EE,FP,ME,IR,DR,RI,LE>
  [ 1955.041813]   CR: 44882882  XER: 
  [ 1955.041819] CFAR: c030d884 SOFTE: 1
  [ 1955.041819] GPR00: c030d658 c007f2a4b630 c144c900 
f1fb8b30
  [ 1955.041819] GPR04: c007ee2cd2c8 f1fb8b30 1f005977 
7759001f
  [ 1955.041819] GPR08: c15bc900 00

[Kernel-packages] [Bug 1678745] Re: Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c

[Vipin K Parashar]

** Summary changed:

- Ubuntu KVM guest crashed @ xfs_perag_get_tag+0x6c
+ Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c

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

Title:
  Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Lata Kuntal  - 2017-03-30 09:44:23 ==
  Ubuntu 17.04 KVM guest gusg8 was having ubuntu 16.04.2 and was running stress 
test IO, Base,TCP and NFS.The guest is having XFS as rootFS and after running 
few hours of regression test it dropped at xmon.

  Console logs :
  
  root@guskvm:~# virsh console gusg8 --force
  Connected to domain gusg8
  Escape character is ^]

  
  1:mon> r
  R00 = d288edf4   R16 = 024200ca
  R01 = c000378cb1f0   R17 = 
  R02 = d2936080   R18 = 0020
  R03 = 0001   R19 = c002734d1800
  R04 = c000378cb190   R20 = 
  R05 =    R21 = 
  R06 = 3c00d03fe056   R22 = c0027e26ccf0
  R07 =    R23 = 
  R08 = c48492d0   R24 = 
  R09 = 3c00d03fe056   R25 = 
  R10 = 3c00d03fe062   R26 = 00024df4cd49
  R11 = d28fa360   R27 = 
  R12 =    R28 = d28ac7b0
  R13 = cfb80900   R29 = c4849000
  R14 =    R30 = 
  R15 = c137ad08   R31 = 
  pc  = d288ee0c xfs_perag_get_tag+0x6c/0x170 [xfs]
  cfar= c096a494 perf_trace_mmc_request_start+0x104/0x440
  lr  = d288edf4 xfs_perag_get_tag+0x54/0x170 [xfs]
  msr = 80010280b033   cr  = 82428424
  ctr = c05e4950   xer = 2000   trap =  300
  dar = 3c00d03fe062   dsisr = 4000
  1:mon> t
  [c000378cb250] d28ac7b0 xfs_reclaim_inodes_count+0x70/0xa0 [xfs]
  [c000378cb290] d28c0ea8 xfs_fs_nr_cached_objects+0x28/0x40 [xfs]
  [c000378cb2b0] c03292d8 super_cache_count+0x68/0x120
  [c000378cb2f0] c0271530 shrink_slab.part.14+0x150/0x4f0
  [c000378cb430] c0276db8 shrink_node+0x158/0x3f0
  [c000378cb4f0] c0277178 do_try_to_free_pages+0x128/0x460
  [c000378cb590] c02775ac try_to_free_pages+0xfc/0x280
  [c000378cb620] c0260158 __alloc_pages_nodemask+0x758/0xe30
  [c000378cb7e0] c02dbb98 alloc_pages_vma+0x108/0x360
  [c000378cb880] c029d080 wp_page_copy+0xf0/0x9d0
  [c000378cb920] c02a0770 do_wp_page+0x210/0xb20
  [c000378cb9b0] c02a656c handle_mm_fault+0x9cc/0x14c0
  [c000378cba60] c0b511a0 do_page_fault+0x260/0x7d0
  [c000378cbb10] c0008948 handle_page_fault+0x10/0x30
  --- Exception: 301 (Data Access) at c010aec4 schedule_tail+0x84/0xb0
  [c000378cbe30] c0009844 ret_from_fork+0x4/0x54
  --- Exception: c00 (System Call) at 3fffa2b5bf44
  1:mon> d
      ||
  1:mon> c
  cpus stopped: 0x0-0x3
  1:mon>

  Kernel host build
  =
  root@guskvm:~# uname -r
  4.10.0-13-generic
  root@guskvm:~#

  
  == Comment: #1 - Luciano Chavez  - 2017-03-30 10:42:15 ==
  At first glance, based on the following assembly from around the failure 
point:

  d288edd4  38c1  li  r6,1
  d288edd8  7f8802a6  mflrr28
  d288eddc  78a70020  clrldi  r7,r5,32
  d288ede0  7c7d1b78  mr  r29,r3
  d288ede4  7c852378  mr  r5,r4
  d288ede8  386302c8  addir3,r3,712
  d288edec  38810020  addir4,r1,32
  d288edf0  4806b571  bl  d28fa360# 
exit_xfs_fs+0x180c/0xfd44 [xfs]
  d288edf4  e8410018  ld  r2,24(r1)
  d288edf8  2f83  cmpwi   cr7,r3,0
  d288edfc  409d0104  ble cr7,d288ef00# 
xfs_perag_get_tag+0x160/0x170 [xfs]
  d288ee00  7c0004ac  sync
  d288ee04  e9210020  ld  r9,32(r1)
  d288ee08  3949000c  addir10,r9,12
  d288ee0c  7fc05028  lwarx   r30,0,r10
  d288ee10  33de0001  addic   r30,r30,1
  d288ee14  7fc0512d  stwcx.  r30,0,r10

  I believe the crash in fs_perag_get_tag() is after we come back from
  the radix_tree_gang_lookup_tag() call and are attempting the
  atomic_inc_return() and struct xfs_perag*pag is R09 =
  3c00d03fe056 which is invalid.

   85 rcu_read_lock();  
 
   86 found = radix_tree_gang_lookup_tag(>m_perag_tree, 
 
   87 

[Kernel-packages] [Bug 1667599] Re: CAPI:Ubuntu: Kernel panic while rebooting

[Vipin K Parashar]

I think the issue is caused by pcieport_drv by which the MSI is enabled
on 0021:02:01.0. Behind the PLX downstream port, there is surprise
hotpluggable slot. When pnv-php.ko is loaded, it tries to enable MSI and
the backtrace is thrown this time. Two things can be done to avoid this
awkward situation:

(1) Prohibit pcieport_drv. It does nothing on PowerNV platform. pnv-php.ko 
doesn't depend on any functionalities exported by it.
(2) I will add some code in pnv-php.ko to skip enabling MSIx/MSI if the PLX 
downstream port has associated driver. With it, we won't see the backtrace 
hopefully. However, the surprise hotplug functionality is lost.

root@ltc84-pkvm1:~# lspci -vvvs 0021:02:01.0 | grep "Kernel driver in use"
Kernel driver in use: pcieport
root@ltc84-pkvm1:~# echo 0021:02:01.0 > /sys/bus/pci/drivers/pcieport/unbind 
root@ltc84-pkvm1:~# lspci -vvvs 0021:02:01.0 | grep "Kernel driver in use"
root@ltc84-pkvm1:~# insmod 
/lib/modules/4.9.0-15-generic/kernel/drivers/pci/hotplug/pnv-php.ko
root@ltc84-pkvm1:~# dmesg | tail -30
[8.677661] audit: type=1400 audit(1487122689.888:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/libvirtd" 
pid=4220 comm="apparmor_parser"
[8.677671] audit: type=1400 audit(1487122689.888:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/sbin/libvirtd//qemu_bridge_helper" pid=4220 comm="apparmor_parser"
[8.679095] audit: type=1400 audit(1487122689.888:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="virt-aa-helper" pid=4219 
comm="apparmor_parser"
[8.751964] audit: type=1400 audit(1487122689.960:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=4218 
comm="apparmor_parser"
[8.751974] audit: type=1400 audit(1487122689.960:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=4218 
comm="apparmor_parser"
[8.751979] audit: type=1400 audit(1487122689.960:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=4218 comm="apparmor_parser"
[8.751984] audit: type=1400 audit(1487122689.960:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/lib/connman/scripts/dhclient-script" pid=4218 comm="apparmor_parser"
[8.781147] audit: type=1400 audit(1487122689.992:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=4222 
comm="apparmor_parser"
[   12.169618] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   12.196455] Ebtables v2.0 registered
[   12.229787] systemd[1]: apt-daily.timer: Adding 8h 33min 26.836791s random 
time.
[   12.238212] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[   12.367033] IPv6: ADDRCONF(NETDEV_UP): enP34p1s0f0: link is not ready
[   12.443774] bridge: filtering via arp/ip/ip6tables is no longer available by 
default. Update your scripts to load br_netfilter if you need this.
[   12.460617] systemd[1]: apt-daily.timer: Adding 1h 54min 42.960931s random 
time.
[   12.483745] Netfilter messages via NETLINK v0.30.
[   12.539679] ip_set: protocol 6
[   13.610428] Rounding down aligned max_sectors from 4294967295 to 4294967168
[   14.424319] qla2xxx [:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 
8.07.00.38-k.
[   15.175489] tg3 0022:01:00.0 enP34p1s0f0: Link is up at 1000 Mbps, full 
duplex
[   15.175502] tg3 0022:01:00.0 enP34p1s0f0: Flow control is off for TX and off 
for RX
[   15.175509] tg3 0022:01:00.0 enP34p1s0f0: EEE is disabled
[   15.175532] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f0: link becomes ready
[   17.712986] virbr0: port 1(virbr0-nic) entered blocking state
[   17.712990] virbr0: port 1(virbr0-nic) entered disabled state
[   17.713205] device virbr0-nic entered promiscuous mode
[   17.901095] virbr0: port 1(virbr0-nic) entered blocking state
[   17.901099] virbr0: port 1(virbr0-nic) entered listening state
[   18.035009] virbr0: port 1(virbr0-nic) entered disabled state
[  154.054440] PowerPC PowerNV PCI Hotplug Driver version: 0.1

root@ltc84-pkvm1:~# ls /sys/bus/pci/slots/
Slot1  Slot2  Slot3  Slot4  Slot5
root@ltc84-pkvm1:~# cat /sys/bus/pci/slots/Slot3/address 
0021:03

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

Title:
  CAPI:Ubuntu: Kernel panic while rebooting

Status in linux package in Ubuntu:
  Triaged

Bug description:
  default desc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667599/+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 1667599] Re: CAPI:Ubuntu: Kernel panic while rebooting

[Vipin K Parashar]

Added bug comments as above.

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

Title:
  CAPI:Ubuntu: Kernel panic while rebooting

Status in linux package in Ubuntu:
  Triaged

Bug description:
  default desc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667599/+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 1667599] Re: CAPI:Ubuntu: Kernel panic while rebooting

[Vipin K Parashar]

---Problem Description---
While rebooting the firestone machine which is having a CAPI card,  just after 
the reboot command, kernel is getting panicked.
 
---uname output---
Linux ltc84-pkvm1 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20 15:28:49 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
 
---Additional Hardware Info---
0001:01:00.0 Processing accelerators: IBM Device 0477 (rev 01)
0002:00:00.0 Processing accelerators: IBM Device 4350 (rev 0a) 

 
Machine Type = PowerNV 8335-GTA  
 
---System Hang---
 reset via ipmitool
 
 
---Steps to Reproduce---
 1. on a  Firestone machine with CAPI Nallatech card , run reboot command from 
the terminal

 
Contact Information = sudeeshj...@in.ibm.com 

Oops output:
 Ubuntu 17.04.  .  .  .Ubuntu 17.04.  .  .  .Ubuntu 17.04.  .  .  .Ubuntu 
17.04.  .  .  .Ubuntu 17.04.  .  .  .Ubuntu 17.04.  .  .  .[  283.410962] Oops: 
Exception in kernel mode, sig: 5 [#1]
[  283.410962] Oops: Exception in kernel mode, sig: 5 [#1]
[  283.411564] SMP NR_CPUS=2048 [  283.411564] SMP NR_CPUS=2048 [  283.411962] 
NUMA
[  283.411962] NUMA
[  283.412166] PowerNV
[  283.412166] PowerNV
[  283.412505] Modules linked in:[  283.412505] Modules linked in: kvm_hv 
kvm_hv kvm_pr kvm_pr kvm kvm usb_f_tcm usb_f_tcm libcomposite libcomposite 
udc_core udc_core target_core_mod target_core_mod configfs configfs ip_set 
ip_set nfnetlink nfnetlink bridge bridge stp stp llc llc joydev joydev 
input_leds input_leds mac_hid mac_hid hid_generic hid_generic usbhid usbhid hid 
hid ofpart ofpart cmdlinepart cmdlinepart at24 at24 nvmem_core nvmem_core 
powernv_flash powernv_flash ipmi_powernv ipmi_powernv ipmi_msghandler 
ipmi_msghandler mtd mtd uio_pdrv_genirq uio_pdrv_genirq uio uio ibmpowernv 
ibmpowernv vmx_crypto vmx_crypto opal_prd opal_prd powernv_rng powernv_rng 
binfmt_misc binfmt_misc x_tables x_tables autofs4 autofs4 uas uas usb_storage 
usb_storage nouveau nouveau crc32c_vpmsum crc32c_vpmsum ast ast i2c_algo_bit 
i2c_algo_bit ttm ttm ahci ahci drm_kms_helper drm_kms_helper syscopyarea 
syscopyarea tg3 tg3 libahci libahci sysfillrect sysfillrect sysimgblt sysimgblt 
fb_sys_fops fb_sys_fo
 ps drm drm cxl cxl pnv_php pnv_php [last unloaded: ip_tables] [last unloaded: 
ip_tables]

[  283.417833] CPU: 19 PID: 1 Comm: systemd-shutdow Tainted: GW   
4.9.0-15-generic #16-Ubuntu
[  283.417833] CPU: 19 PID: 1 Comm: systemd-shutdow Tainted: GW   
4.9.0-15-generic #16-Ubuntu
[  283.418795] task: c063bb938600 task.stack: c027f1188000
[  283.418795] task: c063bb938600 task.stack: c027f1188000
[  283.419412] NIP: c064fd40 LR: c0630564 CTR: c06304f0
[  283.419412] NIP: c064fd40 LR: c0630564 CTR: c06304f0
[  283.420277] REGS: c027f118b8b0 TRAP: 0700   Tainted: GW
(4.9.0-15-generic)
[  283.420277] REGS: c027f118b8b0 TRAP: 0700   Tainted: GW
(4.9.0-15-generic)
[  283.421161] MSR: 9282b033 [  283.421161] MSR: 9282b033 
<>[  
283.422060]   CR: 4428  XER: 
[  283.422060]   CR: 4428  XER: 
[  283.422475] CFAR: c0630560 [  283.422475] CFAR: c0630560 
SOFTE: 1 SOFTE: 1
GPR00:
GPR00: c0630564 c0630564 c027f118bb30 c027f118bb30 
c141a300 c141a300 c027f1069000 c027f1069000
GPR04:
GPR04: 0001 0001 c0081100 c0081100 
9280b033 9280b033 001b 001b
GPR08:
GPR08:   0001 0001 
c027f1069288 c027f1069288 92803003 92803003
GPR12:
GPR12: 2422 2422 cfb8ab00 cfb8ab00 
0004 0004 0001 0001
GPR16:
GPR16: 38af7370 38af7370 0138 0138 
38af6be0 38af6be0  
GPR20:
GPR20: 38af6b10 38af6b10 38af6fd0 38af6fd0 
3fffcb9f3f10 3fffcb9f3f10 38b0f9c8 38b0f9c8
GPR24:
GPR24: 38af7040 38af7040   
  c027f1069100 c027f1069100
GPR28:
GPR28: c1731f98 c1731f98 c1377630 c1377630 
c027f10690a0 c027f10690a0 c027f1069000 c027f1069000

NIP [c064fd40] pci_msi_shutdown+0x60/0x190
NIP [c064fd40] pci_msi_shutdown+0x60/0x190
[  283.431503] LR [c0630564] pci_device_shutdown+0x74/0xf0
[  283.431503] LR [c0630564] pci_device_shutdown+0x74/0xf0
[  283.432841] Call Trace:
[  283.432841] Call Trace:
[  283.433696] [c027f118bb30] [c072a0a4] 
__pm_runtime_resume+0x94/0xd0[  283.433696] [c027f118bb30] 
[c072a0a4] __pm_runtime_resume+0x94/0xd0 (unreliable) (unreliable)

[  283.435213] [c027f118bb70] 

[Kernel-packages] [Bug 1667416] Re: PowerNV: No rate limit for kernel error "KVM can't copy data from"

[Vipin K Parashar]

** Attachment removed: "Kernel debian package with fix"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667416/+attachment/4825345/+files/linux-image-4.9.0-15-generic_4.9.0-15.16_ppc64el.deb

** Attachment removed: "Patch - KVM data copy error"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667416/+attachment/4825344/+files/0001-KVM-PPC-Book3S_64-Ratelimit-copy-data-failure-error-.patch

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

Title:
  PowerNV: No rate limit for kernel error "KVM can't copy data from"

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - MIKHAIL S. MEDVEDEV <mmedv...@us.ibm.com> - 2017-02-03 
14:40:58 ==
  ---Problem Description---
  I am experiencing a problem with KVM on Power with a symptom of "KVM can't 
copy data" message being spammed to kern.log at about 10 messages a second. 
Apart from original problem that triggers the error, the printk is a problem on 
its own. System might run out of space for logs, and would have high CPU load 
caused by journald.

  This bug is to address an absence of rate limiter on printk at
  
https://github.com/torvalds/linux/blob/f64e8084c94bb0449177364856d8117e2f14c4c0/arch/powerpc/kvm/book3s_64_mmu.c#L268

  Maybe wrapping the printk in printk_ratelimit() is all that is
  required?

  if(printk_ratelimit()){
 printk("KVM can't copy");
  }
   
  Contact Information = Mikhail Medvedev / mmedv...@us.ibm.com, Rafael Folco / 
rfo...@br.ibm.com 
   
  ---uname output---
  4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le 
ppc64le ppc64le GNU/Linux
   
  Machine Type = KVM guest on P8 8247 21L  
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Deploy OpenStack with devstack
  2. Run simultaneously between 4 and 6 instances of a script that
  - boots a VM (openstack server create)
  - immediately creates the backup of the VM (openstack server backup 
create)

  This is not a very good way to reproduce it. I am still unable to
  reproduce the problem just by using libvirt and qemu.

  
  == Comment: #5 - VIPIN K. PARASHAR <vipar...@in.ibm.com> - 2017-02-07 
09:42:31 ==

  From kernel logs
  ===

  [852719.001593] KVM can't copy data from 0x3fff86683c80!
  [852719.001614] KVM can't copy data from 0x3fff86683c80!
  [852719.001617] KVM can't copy data from 0x3fff66a83c80!
  [852719.001624] KVM can't copy data from 0x3fff86683c80!
  [852719.001634] KVM can't copy data from 0x3fff86683c80!
  [852719.001637] KVM can't copy data from 0x3fff66a83c80!
  [852719.001645] KVM can't copy data from 0x3fff86683c80!
  [852719.001655] KVM can't copy data from 0x3fff86683c80!
  [852719.001658] KVM can't copy data from 0x3fff66a83c80!
  [852719.001665] KVM can't copy data from 0x3fff86683c80!
  [852719.001668] KVM can't copy data from 0x3fff66a83c80!
  [852719.001678] KVM can't copy data from 0x3fff66a83c80!
  [852719.001686] KVM can't copy data from 0x3fff86683c80!

  
  "KVM can't copy data from" error is being logged at very high rate
  by kernel. rate limiting this error should fix this issue.

  
  == Comment: #20 - VIPIN K. PARASHAR <vipar...@in.ibm.com> - 2017-02-23 
12:01:26 ==
  Fix for this is submitted to PowerPC mailing list 
  and is available at below location:

  https://patchwork.ozlabs.org/patch/728831/

  It reads:

  "KVM: PPC: Book3S: Ratelimit copy data failure error messages"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667416/+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 1469771] Re: [FEAT Ubuntu 15.10]: EPOW, DPO support for PowerNV platform

[Vipin K Parashar]

** Package changed: ubuntu = linux (Ubuntu)

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

Title:
  [FEAT Ubuntu 15.10]: EPOW, DPO support for PowerNV platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This feature adds support for FSP EPOW (Early Power Off Warning) and DPO 
(Delayed Power Off) events for PowerNV platform. Small description of these 
events follows as below:
  On FSP based POWER systems EPOW events are generated to notify about 
various critical system conditions that need system shutdown. Few examples of 
these conditions are high ambient temperature or system running on UPS power 
with low UPS battery.  DPO event is generated in response to admin initiated 
system shutdown request.

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