[Kernel-packages] [Bug 1665447] Re: kernel ppa is building amd64 files inside mainline ppc64el package
This continues to be a issue on recent kernel: These are amd64 files on a ppc64el .deb package: /usr/src/linux-headers-4.19.0-041900-generic/scripts/basic/fixdep /usr/src/linux-headers-4.19.0-041900-generic/scripts/mod/mk_elfconfig /usr/src/linux-headers-4.19.0-041900-generic/scripts/mod/modpost /usr/src/linux-headers-4.19.0-041900-generic/scripts/scripts/sign-file -- 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/1665447 Title: kernel ppa is building amd64 files inside mainline ppc64el package Status in linux package in Ubuntu: Incomplete Bug description: Kernel PPA contains a files that are compiled against amd64 instead of ppc64el. This makes this kernel unusable: Example: PPA: http://kernel.ubuntu.com/~kernel-ppa/mainline/ Kernel: http://kernel.ubuntu.com/\~kernel-ppa/mainline/v4.10-rc8 /linux- headers-4.10.0-041000rc8-generic_4.10.0-041000rc8.201702121731_ppc64el.deb ➜ ppa dpkg-deb -x linux- headers-4.10.0-041000rc8-generic_4.10.0-041000rc8.201702121731_ppc64el.deb . ➜ ppa find . -name fixdep ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep ➜ ppa file ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=438d1c0255e4943c4af1b9568a4cbe83d9034737, not stripped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665447/+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 1792957] Re: Provide mode where all vCPUs on a core must be the same VM
hi Joseph,
I understand this patch will make the next SRU, correct?
--
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/1792957
Title:
Provide mode where all vCPUs on a core must be the same VM
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
This patch has been requested by IBM. It provides a mode where all vCPUs
on a core must be the same VM. This is intended for use in
security-conscious settings where users are concerned about possible
side-channel attacks between threads which could perhaps enable one VM
to attack another VM on the same core, or the host.
== Fix ==
linux-next commit:
aa2278644ae5 ("KVM: PPC: Book3S HV: Provide mode where all vCPUs on a core
must be the same VM")
== Regression Potential ==
Low. Changes limited to powerpc.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Leonardo Augusto Guimaraes Garcia -
2018-09-13 07:12:48 ==
+++ This bug was initially created as a clone of Bug #171443 +++
Please, add the following patch:
http://patchwork.ozlabs.org/patch/968786/
which adds a mode where all vCPUs on a core must be the same VM on
POWER8 and POWER9.
This is intended for use in security-conscious settings where users
are concerned about possible side-channel attacks between threads
which could perhaps enable one VM to attack another VM on the same
core, or the host.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792957/+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 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
** Changed in: ubuntu-power-systems Importance: Medium => High -- 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/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- inux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+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 1792957] Re: Provide mode where all vCPUs on a core must be the same VM
Hi Joseph, > I built a test kernel with the requested commit. > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1792957 > > Can you test this kernel and see if it resolves this bug? I tested this kernel in the following scenarios: - Booted the host on a P9 machine and started an 18.04 guest using the default parameters. - Removed the kvm_hv module and reinstalled it using the 'one_vm_per_core' parameter, shut down the 18.04 guest and restarted it. ➜ ~ sudo virsh destroy breno-1804 ➜ ~ sudo rmmod kvm_hv ➜ ~ sudo modprobe kvm_hv one_vm_per_core=1 ➜ ~ sudo virsh start --console breno-1804 On both guests I ran sysbench, as: breno@ubuntu:~$ sysbench --threads=16 cpu run sysbench 1.0.11 (using system LuaJIT 2.1.0-beta3) Running the test with following options: breno@ubuntu:~$ sysbench --threads=16 cpu run Number of threads: 16 Initializing random number generator from current time Prime numbers limit: 1 Initializing worker threads... Threads started! CPU speed: events per second: 33648.49 . Everything worked fine. I think this patch is good to get accepted. -- 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/1792957 Title: Provide mode where all vCPUs on a core must be the same VM Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - Leonardo Augusto Guimaraes Garcia - 2018-09-13 07:12:48 == +++ This bug was initially created as a clone of Bug #171443 +++ Please, add the following patch: http://patchwork.ozlabs.org/patch/968786/ which adds a mode where all vCPUs on a core must be the same VM on POWER8 and POWER9. This is intended for use in security-conscious settings where users are concerned about possible side-channel attacks between threads which could perhaps enable one VM to attack another VM on the same core, or the host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792957/+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 1751994] Re: ppc64el: Support firmware disable of RFI flush
I also tested the trusty GA kernel: ➜ ~ uname -a Linux ubuntu140403 3.13.0-142-generic #191~lp1751994 SMP Thu Mar 8 15:49:48 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ➜ ~ dmesg | grep rfi [0.00] rfi-flush: Using fallback displacement flush [0.00] rfi-flush: patched 9 locations Thanks for the custom kernels! -- 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/1751994 Title: ppc64el: Support firmware disable of RFI flush Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - Breno Leitao - 2018-02-26 13:59:55 == Hi Canonical, We still need some changes regarding spectre and meltdown. We need to backport the following commit to all supported kernel. I undertand that the backport for kernel 4.XX should be trivial. Not sure about kernel 3.13 yet. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751994/+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 1751994] Re: ppc64el: Support firmware disable of RFI flush
I also tested the xenial GA kernel: # uname -a Linux 1604 4.4.0-116-generic #140~lp1751994 SMP Thu Mar 8 15:31:31 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux # dmesg | grep rfi [0.00] rfi-flush: Using fallback displacement flush [0.00] rfi-flush: patched 10 locations -- 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/1751994 Title: ppc64el: Support firmware disable of RFI flush Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - Breno Leitao - 2018-02-26 13:59:55 == Hi Canonical, We still need some changes regarding spectre and meltdown. We need to backport the following commit to all supported kernel. I undertand that the backport for kernel 4.XX should be trivial. Not sure about kernel 3.13 yet. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751994/+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 1751994] Re: ppc64el: Support firmware disable of RFI flush
I just tested artful and it is working fine: 1604 ➜ ~ uname -a Linux 1604 4.13.0-36-generic #40~lp1751994 SMP Thu Mar 8 15:19:19 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux 1604 ➜ ~ dmesg | grep rfi [0.00] rfi-flush: Using fallback displacement flush [0.00] rfi-flush: patched 11 locations -- 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/1751994 Title: ppc64el: Support firmware disable of RFI flush Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - Breno Leitao - 2018-02-26 13:59:55 == Hi Canonical, We still need some changes regarding spectre and meltdown. We need to backport the following commit to all supported kernel. I undertand that the backport for kernel 4.XX should be trivial. Not sure about kernel 3.13 yet. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751994/+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 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal
hi Joseph, I tried to discover if the patchset above was accepted/acked but I didn't find anything. Do you know if the patchset would make the SRU criteria? -- 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/1772991 Title: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. This pull request is for those other 9 commits. == Regression Potential == All of the commits are specific to powerpc. == Test Case == A test kernel was built with these patches and tested by IBM. == Comment: #0 - Barry B. Arndt - 2018-05-23 13:40:33 == 12 kernel patches have been identified as needed to support Nvidia Volta on bare metal. All are accepted upstream in 4.17. Three of those are already in bionic, leaving a total of 9 remaining commits needed in bionic. Those 9 commits are: 720c84046c26 powerpc/npu-dma.c: Fix crash after __mmu_notifier_register failure 2b74e2a9b39d powerpc/powernv/npu: Fix deadlock in mmio_invalidate() 5ee573e8ef03 powerpc/powernv/mce: Don't silently restart the machine fb5924fddf9e powerpc/mm: Flush cache on memory hot(un)plug 7fd6641de28f powerpc/powernv/memtrace: Let the arch hotunplug code flush cache 28a5933e8d36 powerpc/powernv/npu: Add lock to prevent race in concurrent context init/destroy a1409adac748 powerpc/powernv/npu: Prevent overwriting of pnv_npu2_init_contex() callback parameters d0cf9b561ca9 powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a large address range 75ecfb49516c powerpc/mce: Fix a bug where mce loops on memory UE. We cherry-picked the commits, and all applied cleanly. The resultant kernel built successfully and loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1772991/+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 1773973] Re: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel.
I think this is a clone of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773162. Can someone please test with the following kernel? http://kernel.ubuntu.com/~jsalisbury/lp1773162 -- 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/1773973 Title: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. Status in The Ubuntu-power-systems project: New Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in debian-installer source package in Bionic: New Status in linux source package in Bionic: Incomplete Bug description: ---Problem Description--- Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. ---Environment-- Kernel Build: 4.15.0-22-generic System Name : ltc-garri1 Model/Type : P8 Platform: BML ---Uname output--- Unable to boot. ---Steps to reproduce-- 1. Install Ubuntu 18.04 on Garison BML from http://ports.ubuntu.com /ubuntu-ports/dists/bionic/main/installer- ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ and try to boot. ---Logs Attaching console lob. [4.578205] Bad kernel stack pointer 7b0dd870 at c000b9ec [4.578244] Oops: Bad kernel stack pointer, sig: 6 [#11] [4.578271] LE SMP NR_CPUS=2048 NUMA PowerNV [4.578301] Modules linked in: [4.578324] CPU: 27 PID: 1225 Comm: modprobe Tainted: G D 4.15.0-22-generic #24-Ubuntu [4.578371] NIP: c000b9ec LR: CTR: [4.578413] REGS: c0003febbd40 TRAP: 0300 Tainted: G D (4.15.0-22-generic) [4.578460] MSR: 90001031 CR: XER: [4.578504] CFAR: c000b934 DAR: 0002b200 DSISR: 4000 SOFTE: -4611686018403131680 [4.578504] GPR00: 7b0dd870 [4.578504] GPR04: [4.578504] GPR08: [4.578504] GPR12: 75dcd8781700 0002b200 [4.578504] GPR16: [4.578504] GPR20: [4.578504] GPR24: [4.578504] GPR28: [4.615667] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [4.616210] LR [] (null) [4.616237] Call Trace: [4.616768] Instruction dump: [4.616789] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [4.617697] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 63ff [4.618195] ---[ end trace a0d70ba94f583cca ]--- [4.675899] usb 1-3.3: new high-speed USB device number 5 using xhci_hcd [4.782923] [4.783061] Key type encrypted registered [4.783087] AppArmor: AppArmor sha1 policy hashing enabled [4.783117] ima: No TPM chip found, activating TPM-bypass! (rc=-19) [4.783181] evm: HMAC attrs: 0x1 [4.806062] rtc-opal opal-rtc: setting system clock to 2018-05-29 07:49:29 UTC (1527580169) [4.806350] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [4.806353] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [4.807260] Freeing unused kernel memory: 4800K [4.807321] This architecture does not have kernel memory protection. == Comment: #2 - SEETEENA THOUFEEK - 2018-05-29 06:47:06 == Symptoms looks exactly like . https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691978 . https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656908 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1773973/+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 1767927] Re: ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU ATTEMPT TO RE-ENTER FIRMWARE!
Hey Frank, I understand all of these patches are upstreamed already on Linus' tree and most of the patches seem to be clean cherry picks (except 15b4dd7981496f51c5f9262a5e0761e48de6655f, which was backported). -- 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/1767927 Title: ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU ATTEMPT TO RE-ENTER FIRMWARE! Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - Application Cdeadmin - 2018-03-20 14:10:53 == == Comment: #1 - Application Cdeadmin - 2018-03-20 14:10:54 == == Comment: #2 - Application Cdeadmin - 2018-03-20 14:10:56 == --- Comment From dougmill-ibm 2018-03-20 13:51:47 EDT --- This problem is not tied to a Linux distro. It will be fixed in firmware, as I understand it. Let us close any redundant issues for this same problem. Mark them as duplicate. == Comment: #3 - Application Cdeadmin - 2018-03-20 15:50:54 == --- Comment From mzipse 2018-03-20 15:44:26 EDT --- @stewart-ibm @svaidy , I need to you take a first look. The stop fixes that Vaidy had previously highlighted in a recent note are included in the 3/15 PNOR. == Comment: #5 - Application Cdeadmin - 2018-04-04 16:10:56 == --- Comment From haochanh 2018-04-04 16:04:07 EDT --- We update to 0330, bmc=1.18, then we hit bug 1134. Currently we are running with disable stop5 but still see the watchdog: hard lockup. After 2 hours of test run, I am seeing the "Watchdog: Lockup' and "became unstuck" [Wed Apr 4 13:38:25 2018] Watchdog CPU:42 Hard LOCKUP [Wed Apr 4 13:38:25 2018] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter rpcsec_gss_krb5 nfsv4 nfs fscache 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) mlx5_ib(OE) mlx5_core(OE) mlxfw(OE) cxl pnv_php mlx4_en(OE) mlx4_ib(OE) ib_core(OE) mlx4_core(OE) devlink mlx_compat(OE) kvm_hv kvm binfmt_misc dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua input_leds joydev mac_hid idt_89hpesx ipmi_powernv [Wed Apr 4 13:38:25 2018] vmx_crypto ipmi_devintf at24 ofpart uio_pdrv_genirq cmdlinepart uio powernv_flash ipmi_msghandler mtd crct10dif_vpmsum opal_prd ibmpowernv nfsd sch_fq_codel auth_rpcgss nfs_acl lockd grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq ses enclosure scsi_transport_sas hid_generic usbhid hid lpfc ast i2c_algo_bit ttm drm_kms_helper nvmet_fc syscopyarea sysfillrect nvmet sysimgblt fb_sys_fops nvme_fc nvme_fabrics crc32c_vpmsum drm i40e scsi_transport_fc aacraid [last unloaded: mlxfw] [Wed Apr 4 13:38:25 2018] CPU: 42 PID: 0 Comm: swapper/42 Tainted: G OE4.15.0-12-generic #13 [Wed Apr 4 13:38:25 2018] NIP: c00a3ca4 LR: c00a3ca4 CTR: c0008000 [Wed Apr 4 13:38:25 2018] REGS: c00ff596fc40 TRAP: 0100 Tainted: G OE (4.15.0-12-generic) [Wed Apr 4 13:38:25 2018] MSR: 90001033 CR: 24004482 XER: 2004 [Wed Apr 4 13:38:25 2018] CFAR: c00ff596fda0 SOFTE: 42 GPR00: c00a3ca4 c00ff596fda0 c16eb200 c00ff596fc40 GPR04: b0001033 c00a3690 24004484 000ffa45 GPR08: 0001 c0d10ed8 00ff GPR12: 90121033 c7a3ce00 c00ff596ff90 GPR16: c0047840 c0047810 c11b5380 GPR20: 0800 c1722484 002a GPR24: 00a8 0007 0007 GPR28: c161d270 c00ffb666fd8 c161d528 0007 [Wed Apr 4 13:38:25 2018] NIP [c00a3ca4] power9_idle_type+0x24/0x40 [Wed Apr 4 13:38:25 2018] LR [c00a3ca4] power9_idle_type+0x24/0x40 [Wed Apr 4 13:38:25 2018] Call Trace: [Wed Apr 4 13:38:25 2018] [c00ff596fda0] [c00a3ca4] power9_idle_type+0x24/0x40 (unreliable) [Wed Apr 4 13:38:25 2018] [c00ff596fdc0] [c0ad1240] stop_loop+0x40/0x5c [Wed Apr 4 13:38:25 2018] [c00ff596fdf0] [c0
[Kernel-packages] [Bug 1744173] Re: rfi-flush: Switch to new linear fallback flush
Hi Juerg, > When updating to 4.4.117 we reverted a bunch of SAUCE rfi-flush patches and > replaced them with the > upstream versions. Is there a possibility that your patches are no longer > required with those updates? None of these patches seems to be integrated int 4.4.0-124. So, we will need to backport them again. I will be working to get this done. What about artful (kernel 4.13). Are the patches still applying? -- 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/1744173 Title: rfi-flush: Switch to new linear fallback flush Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Bug description: [Impact] Change flush from congruence-first with dependencies to linear with no dependencies, which increases flush performance by 8x on P8, and 3x on P9 (as measured with null syscall loop, which will have the flush area in the L2). The flush also becomes simpler and more adaptable to different cache geometries. [Test Case] TBD. [Regression Potential] The risk is deemed low since the changes are confined to POWER only and the provided test kernels have been tested by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744173/+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 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()
Doug said:
Using kernel from http://kernel.ubuntu.com/~jsalisbury/lp1770003, I have
confirmed that the disks are discovered and I am running some scenarios now.
Doing portdisable/portenable from the FC switch occasionally, while running HTX
I/O load. No problems seen so far.
--
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/1770003
Title:
qla2xxx: Fix page fault at kmem_cache_alloc_node()
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
Dear Canonical,
We found that the current Ubuntu kernel contains a problem related to
qla2xxx driver which causes:
[ 66.295233] Unable to handle kernel paging request for data at address
0x8882f6ed90e9151a
[ 66.295297] Faulting instruction address: 0xc038a110
cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
sp: c692f8d0
msr: 90009033
dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000 softe: 0irq_happened: 0x01
pid = 1762, comm = systemd-journal
Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu
4.15.0-20.21-generic 4.15.20)
enter ? for help
[c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350
(unreliable)
[c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
[c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
[c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
[c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
[c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
[c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
[c692fe30] c000b184 system_call+0x58/0x6c
--- Exception: c00 (System Call) at 74826f6fa9c4
SP (75dc5510) is in userspace
We were able to get rid of this problem cherry picking some of the
upstream patches. Do you think they might fit in the SRU criteria?
The commit ids are below and they were easily cherry picked.
eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug
after firmware timeout
6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin
trigger from sending too many commands
7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in
qla2x00_async_iocb_timeout()
045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call
dma_free_coherent with IRQ disabled.
1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session
free in qlt_free_session_done
d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session
deletion by using work_lock
Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx:
Fixup locking for session deletion')
94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused
argument from qlt_schedule_sess_for_dele?
9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup
for N2N
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+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 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()
Hi,
Since Manoj's kernel didn't work, I created a kernel with the fixes
above and it is working on ppc64el (on a 24 hours test).
These are the patches I added:
scsi: qla2xxx: Fixup locking for session deletion
scsi: qla2xxx: Fix double free bug after firmware timeout
scsi: qla2xxx: Prevent relogin trigger from sending too many commands
scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout()
scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled.
scsi: qla2xxx: Serialize session free in qlt_free_session_done
scsi: qla2xxx: Serialize session deletion by using work_lock
scsi: qla2xxx: Remove unused argument from qlt_schedule_sess_for_deletion()
scsi: qla2xxx: Fix session cleanup for N2N
You can find the patches at
https://github.com/leitao/linux/commits/bionic
Is it possible to add these patches in this next SRU?
--
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/1770003
Title:
qla2xxx: Fix page fault at kmem_cache_alloc_node()
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
Dear Canonical,
We found that the current Ubuntu kernel contains a problem related to
qla2xxx driver which causes:
[ 66.295233] Unable to handle kernel paging request for data at address
0x8882f6ed90e9151a
[ 66.295297] Faulting instruction address: 0xc038a110
cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
sp: c692f8d0
msr: 90009033
dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000 softe: 0irq_happened: 0x01
pid = 1762, comm = systemd-journal
Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu
4.15.0-20.21-generic 4.15.20)
enter ? for help
[c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350
(unreliable)
[c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
[c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
[c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
[c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
[c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
[c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
[c692fe30] c000b184 system_call+0x58/0x6c
--- Exception: c00 (System Call) at 74826f6fa9c4
SP (75dc5510) is in userspace
We were able to get rid of this problem cherry picking some of the
upstream patches. Do you think they might fit in the SRU criteria?
The commit ids are below and they were easily cherry picked.
eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug
after firmware timeout
6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin
trigger from sending too many commands
7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in
qla2x00_async_iocb_timeout()
045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call
dma_free_coherent with IRQ disabled.
1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session
free in qlt_free_session_done
d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session
deletion by using work_lock
Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx:
Fixup locking for session deletion')
94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused
argument from qlt_schedule_sess_for_dele?
9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup
for N2N
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+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 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()
I also created a vimdiff of both logs, and I noted something that caused
the whole difference later:
On the OK kernel, I see:
[0001:03:00.0]-001d: : Found an ISP2532 irq 41 iobase 0xdb2a8857.
On the NOK kernel I see:
[0001:03:00.0]-001d: : Found an ISP2532 irq 41 iobase 0x6baeaf0e.
Later, The addresses are different again:
OK Kernel:
[0001:03:00.1]-001d: : Found an ISP2532 irq 42 iobase 0xc67eaba1
NOK Kernel:
[0001:03:00.1]-001d: : Found an ISP2532 irq 42 iobase 0x507ae35c
After that, the OK kernel follows with:
[0001:03:00.0]-580e:2: Asynchronous P2P MODE received
[0001:03:00.0]-18b9:2: Format 1: VP[0] enabled - status 0 - with port id
050500.
[0001:03:00.0]-5875:2: Format 1: Remote WWPN 20:05:00:05:1e:02:da:3e.
While the NOK kernel follows with:
[0001:03:00.0]-5809:2: LIP occurred (f700)
[0001:03:00.0]-580c:2: LIP reset occurred (f7f7).
Later, when the OK kernel seems to detect something, as:
[0001:03:00.0]-289f:2: Device wrap (030a00).
[0001:03:00.0]-28d8:2: qla24xx_fcport_handle_login 50:05:07:68:02:16:5e:37
DS 0 LS 7 P 0 fl 3 confl
[0001:03:00.0]-28bd:2: qla24xx_fcport_handle_login 982
50:05:07:68:02:16:5e:37 post gnl
The NOK kernel just prints:
[0001:03:00.0]-107ff:2: Async-gpnft hdl=2 FC4Type 8.
--
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/1770003
Title:
qla2xxx: Fix page fault at kmem_cache_alloc_node()
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
Dear Canonical,
We found that the current Ubuntu kernel contains a problem related to
qla2xxx driver which causes:
[ 66.295233] Unable to handle kernel paging request for data at address
0x8882f6ed90e9151a
[ 66.295297] Faulting instruction address: 0xc038a110
cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
sp: c692f8d0
msr: 90009033
dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000 softe: 0irq_happened: 0x01
pid = 1762, comm = systemd-journal
Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu
4.15.0-20.21-generic 4.15.20)
enter ? for help
[c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350
(unreliable)
[c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
[c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
[c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
[c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
[c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
[c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
[c692fe30] c000b184 system_call+0x58/0x6c
--- Exception: c00 (System Call) at 74826f6fa9c4
SP (75dc5510) is in userspace
We were able to get rid of this problem cherry picking some of the
upstream patches. Do you think they might fit in the SRU criteria?
The commit ids are below and they were easily cherry picked.
eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug
after firmware timeout
6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin
trigger from sending too many commands
7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in
qla2x00_async_iocb_timeout()
045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call
dma_free_coherent with IRQ disabled.
1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session
free in qlt_free_session_done
d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session
deletion by using work_lock
Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx:
Fixup locking for session deletion')
94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused
argument from qlt_schedule_sess_for_dele?
9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup
for N2N
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://
[Kernel-packages] [Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()
Manoj,
Do you have the git tree you used to build this kernel? I would like to
take a look if any backport was missing.
--
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/1770003
Title:
qla2xxx: Fix page fault at kmem_cache_alloc_node()
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
Dear Canonical,
We found that the current Ubuntu kernel contains a problem related to
qla2xxx driver which causes:
[ 66.295233] Unable to handle kernel paging request for data at address
0x8882f6ed90e9151a
[ 66.295297] Faulting instruction address: 0xc038a110
cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
sp: c692f8d0
msr: 90009033
dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000 softe: 0irq_happened: 0x01
pid = 1762, comm = systemd-journal
Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu
4.15.0-20.21-generic 4.15.20)
enter ? for help
[c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350
(unreliable)
[c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
[c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
[c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
[c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
[c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
[c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
[c692fe30] c000b184 system_call+0x58/0x6c
--- Exception: c00 (System Call) at 74826f6fa9c4
SP (75dc5510) is in userspace
We were able to get rid of this problem cherry picking some of the
upstream patches. Do you think they might fit in the SRU criteria?
The commit ids are below and they were easily cherry picked.
eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug
after firmware timeout
6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin
trigger from sending too many commands
7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in
qla2x00_async_iocb_timeout()
045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call
dma_free_coherent with IRQ disabled.
1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session
free in qlt_free_session_done
d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session
deletion by using work_lock
Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx:
Fixup locking for session deletion')
94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused
argument from qlt_schedule_sess_for_dele?
9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup
for N2N
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+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 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()
Hi Joseph,
The original patchset just included 4 patches, they are:
d8630bb scsi: qla2xxx: Serialize session deletion by using work_lock
1ae634e scsi: qla2xxx: Serialize session free in qlt_free_session_done
9cd883f scsi: qla2xxx: Fix session cleanup for N2N
eaf75d1 scsi: qla2xxx: Fix double free bug after firmware timeout
The other three patches came as a requirement to backport these 4
patches.
On top of it, the commit id d8630bb95f46 had a regression which would
require the last patch:
1c6cacf scsi: qla2xxx: Fixup locking for session deletion
--
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/1770003
Title:
qla2xxx: Fix page fault at kmem_cache_alloc_node()
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
Dear Canonical,
We found that the current Ubuntu kernel contains a problem related to
qla2xxx driver which causes:
[ 66.295233] Unable to handle kernel paging request for data at address
0x8882f6ed90e9151a
[ 66.295297] Faulting instruction address: 0xc038a110
cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
sp: c692f8d0
msr: 90009033
dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000 softe: 0irq_happened: 0x01
pid = 1762, comm = systemd-journal
Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu
4.15.0-20.21-generic 4.15.20)
enter ? for help
[c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350
(unreliable)
[c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
[c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
[c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
[c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
[c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
[c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
[c692fe30] c000b184 system_call+0x58/0x6c
--- Exception: c00 (System Call) at 74826f6fa9c4
SP (75dc5510) is in userspace
We were able to get rid of this problem cherry picking some of the
upstream patches. Do you think they might fit in the SRU criteria?
The commit ids are below and they were easily cherry picked.
eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug
after firmware timeout
6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin
trigger from sending too many commands
7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in
qla2x00_async_iocb_timeout()
045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call
dma_free_coherent with IRQ disabled.
1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session
free in qlt_free_session_done
d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session
deletion by using work_lock
Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx:
Fixup locking for session deletion')
94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused
argument from qlt_schedule_sess_for_dele?
9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup
for N2N
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+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 1744173] Re: artful: rfi-flush: Switch to new linear fallback flush
Hello Joseph, Any update on this bug? -- 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/1744173 Title: artful: rfi-flush: Switch to new linear fallback flush Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Bug description: Change flush from congruence-first with dependencies to linear with no dependencies, which increases flush performance by 8x on P8, and 3x on P9 (as measured with null syscall loop, which will have the flush area in the L2). The flush also becomes simpler and more adaptable to different cache geometries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744173/+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 1762928] Re: [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest
Joseph, Thanks for the fix.
We would like to have the fix backported to 16.04 kernels also, since
this problem is on those kernel also. Could you please target this bug
against artful and xenial also?
Thanks
--
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/1762928
Title:
[LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
---Problem Description---
tm_trap_test failed on P8 compat mode [16.04.04 daily build as well bionic ]
guests on a P9 host running bionic final beta version.
Contact Information = srikanth/bssrika...@in.ibm.com
---uname output---
16.04.04 Guest running in P8compat mode:
Linux guest 4.15.0-15-generic #16~16.04.1-Ubuntu SMP Thu Apr 5 12:18:22 UTC
2018 ppc64le ppc64le ppc64le GNU/Linux
18.04 guest running in P8compat mode:
Linux ubuntu 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018
ppc64le ppc64le ppc64le GNU/Linux
Machine Type = boston-LC
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1. Log into P9 Ubuntu 18.04 host, take console of guest
`srikanth_ubuntu160404`
2. Run TM selftests
git clone --depth 1 https://github.com/torvalds/linux.git;cd
linux/tools/testing/selftests/powerpc/;git log --oneline -1;make;make -C tm
run_tests
We will observe one of the tm tests failing, mentioned below:
selftests: tm-trap
test: tm_trap_test
tags: git_version:c18bb39
Little-Endian machine detected. Checking if endianness flips inadvertently on
trap in TM... yes!
failure: tm_trap_test
not ok 1..11 selftests: tm-trap [FAIL]
Expected result: All tm selftests should have been pass on the P8 compat
guest.. giventhat we had TM workaround patches in latest Ubuntu BIONIC host
kernel
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
*Additional Instructions for srikanth/bssrika...@in.ibm.com:
-Attach sysctl -a output output to the bug.
== Comment: #2 - SRIKANTH AITHAL - 2018-04-10
01:32:00 ==
== Comment: #3 - SRIKANTH AITHAL - 2018-04-10
01:33:41 ==
== Comment: #4 - SRIKANTH AITHAL - 2018-04-10
01:34:02 ==
Please pick
`1c200e63d055 ("powerpc/tm: Fix endianness flip on trap")`
ie. the commit that the test was written for
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1762928/+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 1761104] Re: fix regression in mm/hotplug, allows NVIDIA driver to work
I understand there is not a released kernel with this fix yet, right? -- 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/1761104 Title: fix regression in mm/hotplug, allows NVIDIA driver to work Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Fix Committed Bug description: == SRU Justification, ARTFUL == Bug fix #1747069 causes an issue for NVIDIA drivers on ppc64el platforms. According to Will Davis at NVIDIA: "- The original patch 3d79a728f9b2e6ddcce4e02c91c4de1076548a4c changed the call to arch_add_memory in mm/memory_hotplug.c to call with the boolean argument set to true instead of false, and inverted the semantics of that argument in the arch layers. - The revert patch 4fe85d5a7c50f003fe4863a1a87f5d8cc121c75c reverted the semantic change in the arch layers, but didn't revert the change to the arch_add_memory call in mm/memory_hotplug.c" And also: "It looks like the problem here is that the online_type is _MOVABLE but can_online_high_movable(nid=255) is returning false: if ((zone_idx(zone) > ZONE_NORMAL || online_type == MMOP_ONLINE_MOVABLE) && !can_online_high_movable(pfn_to_nid(pfn))) This check was removed by upstream commit 57c0a17238e22395428248c53f8e390c051c88b8, and I've verified that if I apply that commit (partially) to the 4.13.0-37.42 tree along with the previous arch_add_memory patch to make the probe work, I can fully online the GPU device memory as expected. Commit 57c0a172.. implies that the can_online_high_movable() checks weren't useful anyway, so in addition to the arch_add_memory fix, does it make sense to revert the pieces of 4fe85d5a7c50f003fe4863a1a87f5d8cc121c75c that added back the can_online_high_movable() check?" == Fix == Fix partial backport from bug #1747069, remove can_online_high_movable and fix the incorrectly set boolean argument to arch_add_memory(). == Testing == run ADT memory hotplug test, should not regress this. Without the fix, the nvidia driver on powerpc will not load because it cannot map memory for the device. With the fix it loads. == Regression Potential == This fixes a regression in the original fix and hence the regression potential is the same as the previously SRU'd bug fix for #1747069, namely: "Reverting this commit does remove some functionality, however this does not regress the kernel compared to previous releases and having a working reliable memory hotplug is the preferred option. This fix does touch some memory hotplug, so there is a risk that this may break this functionality that is not covered by the kernel regression testing." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761104/+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 1763386] Re: Fix trying to "push" an already active pool VP
https://lists.ubuntu.com/archives/kernel-team/2018-April/091582.html -- 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/1763386 Title: Fix trying to "push" an already active pool VP Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Hello Canonical, Could you please include the following patch in Bionic? -- When setting up a CPU, we "push" (activate) a pool VP for it. However it's an error to do so if it already has an active pool VP. This happens when doing soft CPU hotplug on powernv since we don't tear down the CPU on unplug. The HW flags the error which gets captured by the diagnostics. Fix this by making sure to "pull" out any already active pool first. -- Patch: https://patchwork.ozlabs.org/patch/897035/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1763386/+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 1744173] Re: artful: rfi-flush: Switch to new linear fallback flush
hi Joseph, I tested on both versions and the kernel solves the problem: == Xenial == # uname -a Linux 1604 4.4.0-116-generic #140~lp1744174 SMP Tue Mar 6 14:15:54 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux == Artful == # uname -a Linux 1710 4.13.0-36-generic #40~lp1744173 SMP Tue Mar 6 14:17:17 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux The patches can make the official tree in my opinion. PS: You look the kernel version, it has the extesion ~lpXX, one refers to lp1744173 and the other one to lp1744174, but I understand it was a typo, and both refers to the same fix (lp1744173), right? Thanks! -- 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/1744173 Title: artful: rfi-flush: Switch to new linear fallback flush Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: Incomplete Bug description: Change flush from congruence-first with dependencies to linear with no dependencies, which increases flush performance by 8x on P8, and 3x on P9 (as measured with null syscall loop, which will have the flush area in the L2). The flush also becomes simpler and more adaptable to different cache geometries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744173/+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 1760099] Re: Additional spectre and meltdown patches
Patch sent to the mailing list: https://lists.ozlabs.org/pipermail /linuxppc-dev/2018-April/171510.html -- 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/1760099 Title: Additional spectre and meltdown patches Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - Breno Leitao - 2018-03-29 08:53:56 == Hi Canonical, There are some additional patches for Spectre and Meltdown that is required on ppc64el. We would need to have them included on all Ubuntu kernels. This is the patch series: [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,08/10] powerpc/pseries: Use the security flags in pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,04/10] powerpc/powernv: Set or clear security feature flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,03/10] powerpc/pseries: Set or clear security feature flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown http://patchwork.ozlabs.org/project/linuxppc- dev/list/?series=36012&state=* == Comment: #1 - Breno Leitao - 2018-03-29 08:55:48 == This is a better formatted patch series list: [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1() [v2,08/10] powerpc/pseries: Use the security flags in pseries_setup_rfi_flush() [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus() [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown() [v2,05/10] powerpc/64s: Move cpu_show_meltdown() [v2,04/10] powerpc/powernv: Set or clear security feature flags [v2,03/10] powerpc/pseries: Set or clear security feature flags [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1760099/+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 1760099] Re: Additional spectre and meltdown patches
Hi Tyler,
Yes, we need to backport this patchset to all the current supported
kernel. Since most of the supported kernel contains the whole RFI infra
structure, I do not expect it to be hard. If you need help, I can find
someone to help on the backport.
Regarding the problem you are facing, I talked to the powerpc maintainer
(Michael Ellerman) and he suggested squashing the warning using
something as the code below. He will be also sending the patch upstream.
```
diff --git a/arch/powerpc/kernel/setup_64.c b/arch/powerpc/kernel/setup_64.c
index 66f2b6299c40..44c30dd38067 100644
--- a/arch/powerpc/kernel/setup_64.c
+++ b/arch/powerpc/kernel/setup_64.c
@@ -880,7 +880,7 @@ void rfi_flush_enable(bool enable)
rfi_flush = enable;
}
-static void init_fallback_flush(void)
+static void __ref init_fallback_flush(void)
{
u64 l1d_size, limit;
int cpu;
```
--
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/1760099
Title:
Additional spectre and meltdown patches
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Trusty:
Triaged
Status in linux source package in Xenial:
Triaged
Status in linux source package in Artful:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
== Comment: #0 - Breno Leitao - 2018-03-29 08:53:56 ==
Hi Canonical,
There are some additional patches for Spectre and Meltdown that is
required on ppc64el. We would need to have them included on all Ubuntu
kernels.
This is the patch series:
[v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() [v2,01/10] powerpc:
Add security feature flags for Spectre/Meltdown
[v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1() [v2,01/10] powerpc:
Add security feature flags for Spectre/Meltdown
[v2,08/10] powerpc/pseries: Use the security flags in
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature
flags for Spectre/Meltdown
[v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
[v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
[v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc:
Add security feature flags for Spectre/Meltdown
[v2,04/10] powerpc/powernv: Set or clear security feature flags
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
[v2,03/10] powerpc/pseries: Set or clear security feature flags
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
[v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
http://patchwork.ozlabs.org/project/linuxppc-
dev/list/?series=36012&state=*
== Comment: #1 - Breno Leitao - 2018-03-29 08:55:48 ==
This is a better formatted patch series list:
[v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()
[v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()
[v2,08/10] powerpc/pseries: Use the security flags in
pseries_setup_rfi_flush()
[v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
[v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()
[v2,05/10] powerpc/64s: Move cpu_show_meltdown()
[v2,04/10] powerpc/powernv: Set or clear security feature flags
[v2,03/10] powerpc/pseries: Set or clear security feature flags
[v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1760099/+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 1758910] Re: Important Kernel fixes to be backported for Power9 (kvm)
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed -- 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/1758910 Title: Important Kernel fixes to be backported for Power9 (kvm) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: == Comment: #0 - Satheesh Rajendran - 2018-03-26 02:18:44 == ---Problem Description--- Important Kernel fixes to be backported for Power9 (kvm) Contact Information = sathe...@in.ibm.com ---uname output--- 4.15.0-13-generic Machine Type = power9 boston 2.2 (pvr 004e 1202) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Following upstream patches are need to be backported for Power9 KVM to function well. * Emulation of VMX loads and stores for MMIO. 09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions 6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc versions (needed once 09f984961c13 is in) * Other important fixes. 05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT resizing code 790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9 a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from __kvmppc_vcore_entry https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=ff6781fd1bb404d8a551c02c35c70cec1da17ff1 https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=e4b79900222b8cccd4da4a7a89581f0e1b764ed2 and https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=a5d4b5891c2f1f865a2def1eb0030f534e77ff86 Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for sathe...@in.ibm.com: -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1758910/+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 1760099] Re: Additional spectre and meltdown patches
Hey Tyler, I thought these patches were in already, so, let's bring them also. Backporting without these fixes might not be easy to accomplish, and nothing something we want to keep for the whole 18.04 life. Let's try to be as near as possible to upstream and bring the required patches in. Thanks for asking, Breno -- 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/1760099 Title: Additional spectre and meltdown patches Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - Breno Leitao - 2018-03-29 08:53:56 == Hi Canonical, There are some additional patches for Spectre and Meltdown that is required on ppc64el. We would need to have them included on all Ubuntu kernels. This is the patch series: [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,08/10] powerpc/pseries: Use the security flags in pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,04/10] powerpc/powernv: Set or clear security feature flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,03/10] powerpc/pseries: Set or clear security feature flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown http://patchwork.ozlabs.org/project/linuxppc- dev/list/?series=36012&state=* == Comment: #1 - Breno Leitao - 2018-03-29 08:55:48 == This is a better formatted patch series list: [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1() [v2,08/10] powerpc/pseries: Use the security flags in pseries_setup_rfi_flush() [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus() [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown() [v2,05/10] powerpc/64s: Move cpu_show_meltdown() [v2,04/10] powerpc/powernv: Set or clear security feature flags [v2,03/10] powerpc/pseries: Set or clear security feature flags [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1760099/+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 1751994] Re: ppc64el: Support firmware disable of RFI flush
Can we increase the priority of this bug from medium to high, please? -- 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/1751994 Title: ppc64el: Support firmware disable of RFI flush Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Breno Leitao - 2018-02-26 13:59:55 == Hi Canonical, We still need some changes regarding spectre and meltdown. We need to backport the following commit to all supported kernel. I undertand that the backport for kernel 4.XX should be trivial. Not sure about kernel 3.13 yet. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751994/+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 1744173] Re: artful: rfi-flush: Switch to new linear fallback flush
Yes, Andy. This is part of the Meltdown patchset. It is very important to have it integrated, as, it increase the flush performance in 8x on a POWER8. -- 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/1744173 Title: artful: rfi-flush: Switch to new linear fallback flush Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Change flush from congruence-first with dependencies to linear with no dependencies, which increases flush performance by 8x on P8, and 3x on P9 (as measured with null syscall loop, which will have the flush area in the L2). The flush also becomes simpler and more adaptable to different cache geometries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744173/+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 1744173] Re: artful: rfi-flush: Switch to new linear fallback flush
Hi, Any update about this patchset? -- 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/1744173 Title: artful: rfi-flush: Switch to new linear fallback flush Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Change flush from congruence-first with dependencies to linear with no dependencies, which increases flush performance by 8x on P8, and 3x on P9 (as measured with null syscall loop, which will have the flush area in the L2). The flush also becomes simpler and more adaptable to different cache geometries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744173/+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 1746299] Re: update makedumpfile tool version to v1.6.3
Hi Cascardo, How are you planning to fix it on 16.04 since package version upgrade is not allowed? Are you going to cherry pick the patches? -- 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/1746299 Title: update makedumpfile tool version to v1.6.3 Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Bug description: [Impact] New upstream kernel versions, as those in linux-hwe package, require a newer makedumpfile to be supported. Otherwise, all copies fallback to copying the entire memory. [Test case] kdump-tools has been installed, system rebooted, then crash trigerred and verified that a small dump file was present on /var/crash/. Tested on amd64 and ppc64le. [Regression potential] Many other bug fixes have been included in the latest version of the package. The changes are supposed to fix these bugs, and have been tested as well. However, as the total of changes is not trivial, there is impact of regression that has been minimized by the tests done. Regression potential of not supporting older kernels has been tested with the kernels shipped on xenial and artful as well. == Comment: #0 - Hari Krishna Bathini - 2018-01-30 10:46:53 == ---Problem Description--- update makedumpfile to latest version v1.6.3 that officially supports up to kernel version 4.14.8. Since makedumpfile is inherently backward compatible, this would not break existing functionality.. Contact Information = hbath...@in.ibm.com ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- makedumpfile reports ""The kernel version is not supported" while generating vmcore Also, there is a possibility of bogus address translations in makedumpfile tool with missing upstream patches. Can't be so sure without an exhaustive testing. Instead, it would be a good idea to go with the version which officially supports the kernel version in question. Userspace tool common name: makedumpfile The userspace tool has the following bit modes: 64-bit Userspace rpm: makedumpfile Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Hari Krishna Bathini - 2018-01-30 10:49:13 == With kernel version updated to 4.13.0, please update makedumpfile tool version to 1.6.3 which officially supports up to kernel version 4.14.8 [1]. Thanks Hari [1] http://lists.infradead.org/pipermail/kexec/2018-January/019853.html This needs to be tagged for both 16.04.4 & 18.04 releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746299/+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 1724120] Re: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured
hi Andrew, I understand that the patches are already accepted on upstream release, aren't they? I can see them on Linus' tree. -- 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/1724120 Title: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Triaged Bug description: Issue: Call traces occurs when memory-hotplug script is run with 16Gb hugepages configured. Environment: ppc64le PowerVM Lpar root@ltctuleta-lp1:~# uname -r 4.4.0-34-generic root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge AnonHugePages: 0 kB HugePages_Total: 2 HugePages_Free:2 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 16777216 kB root@ltctuleta-lp1:~# free -h totalusedfree shared buff/cache available Mem:85G 32G 52G 16M193M 52G Swap: 43G 0B 43G Steps to reproduce: 1 - Download kernel source and enter to the directory- tools/testing/selftests/memory-hotplug/ 2 - Run mem-on-off-test.sh script in it. System gives call traces like: offline_memory_expect_success 639: unexpected fail online-offline 668 [ 57.552964] Unable to handle kernel paging request for data at address 0x0028 [ 57.552977] Faulting instruction address: 0xc029bc04 [ 57.552987] Oops: Kernel access of bad area, sig: 11 [#1] [ 57.552992] SMP NR_CPUS=2048 NUMA pSeries [ 57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel rtc_generic mdio libcrc32c [ 57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 4.4.0-34-generic #53-Ubuntu [ 57.553059] task: c0072773c8e0 ti: c0072778 task.ti: c0072778 [ 57.553067] NIP: c029bc04 LR: c029bbdc CTR: c01107f0 [ 57.553076] REGS: c00727783770 TRAP: 0300 Not tainted (4.4.0-34-generic) [ 57.553083] MSR: 80019033 CR: 24242882 XER: 0002 [ 57.553104] CFAR: c0008468 DAR: 0028 DSISR: 4000 SOFTE: 1 GPR00: c029bbdc c007277839f0 c15b5d00 GPR04: 0029d000 0800 fa01 GPR08: fa700020 0008 c185e270 c00e7e50 GPR12: 2200 ce6ea200 0029d000 2200 GPR16: 1000 c15e2200 0a70 GPR20: 0001 0100 0200 c15f16d0 GPR24: c1876510 0001 c1872a00 GPR28: 0029d000 f000 fa70 0029c000 [ 57.553211] NIP [c029bc04] dissolve_free_huge_pages+0x154/0x220 [ 57.553219] LR [c029bbdc] dissolve_free_huge_pages+0x12c/0x220 [ 57.553226] Call Trace: [ 57.553231] [c007277839f0] [c029bbdc] dissolve_free_huge_pages+0x12c/0x220 (unreliable) [ 57.553244] [c00727783a80] [c02dcbc8] __offline_pages.constprop.6+0x3f8/0x900 [ 57.553254] [c00727783bd0] [c06fbb38] memory_subsys_offline+0xa8/0x110 [ 57.553265] [c00727783c00] [c06d6424] device_offline+0x104/0x140 [ 57.553274] [c00727783c40] [c06fba80] store_mem_state+0x180/0x190 [ 57.553283] [c00727783c80] [c06d1e58] dev_attr_store+0x68/0xa0 [ 57.553293] [c00727783cc0] [c0398110] sysfs_kf_write+0x80/0xb0 [ 57.553302] [c00727783d00] [c0397028] kernfs_fop_write+0x188/0x200 [ 57.553312] [c00727783d50] [c02e190c] __vfs_write+0x6c/0xe0 [ 57.553321] [c00727783d90] [c02e2640] vfs_write+0xc0/0x230 [ 57.553329] [c00727783de0] [c02e367c] SyS_write+0x6c/0x110 [ 57.553339] [c00727783e30] [c0009204] system_call+0x38/0xb4 [ 57.553346] Instruction dump: [ 57.553351] 7e831836 4bfff991 e91e0028 e8fe0020 7d32e82a f9070008 f8e8 fabe0020 [ 57.553366] fade0028 79294620 79291764 7d234a14 3908 f9030028 81091458 [ 57.553383] ---[ end trace 617f7bdd75bcfc10 ]--- [ 57.557133] Segmentation fault The following commit IDs were built into a 4.10.0-37-generic #41 test kernel and verified to fix the problem: a525108cf1cc14651602d678da38fa627a76a724 e1073d1e7920946ac4776a619cc40668b9e1401b 40692eb5eea209c2dd55857f44b4e1d7206e91d6 e24a1307ba1f99fc62a0bd61d5e87fcfb6d5503d 79cc38ded1e1ac86e69c90f604efadd50b0b3762 4ae279c2c96ab38a78b954d218790a8f6db714e5 To manage
[Kernel-packages] [Bug 1707875] Re: [18.04] include support for Python bindings in "perf"
Tes, let's target this one for 18.04. -- 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/1707875 Title: [18.04] include support for Python bindings in "perf" Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: == Comment: #0 - Paul A. Clarke - 2017-07-26 09:59:57 == ---Problem Description--- Request to build python bindings support with perf. ---Steps to Reproduce--- Ubuntu-17.04# perf script -g python Python scripting not supported. Install libpython and rebuild perf to enable it. For example: # apt-get install python-dev (ubuntu) # yum install python-devel (Fedora) etc. Userspace tool common name: perf Userspace rpm: linux-tools-common Userspace tool obtained from project website: na == Comment: #2 - MAMATHA INAMDAR - 2017-08-01 05:02:34 == After installing libpython, downloaded ubuntu 17.04 linux source code and compiled perf tool then it works fine. # ./perf script -g python generated Python script: perf-script.py but when I run perf tool without rebuilding after installing libpython it shows an error # perf script -g python Python scripting not supported. Install libpython and rebuild perf to enable it. For example: # apt-get install python-dev (ubuntu) # yum install python-devel (Fedora) etc. root@p8wookie:/home/Mamatha/ubuntu/ubuntu-zesty/tools/perf# perf --version perf version 4.10.17 == Comment: #3 - MAMATHA INAMDAR - 2017-08-01 05:03:44 == Request to build python bindings support with perf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1707875/+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 1725350] Re: KVM on 17.10 crashes the machine
I tested kernel 4.13.0-18 and I do not see this problem anymore. Marking it as verification-done. I am also not seeing the problem reported at LP#1733864 also. I am wondering if they were related. ➜ ~ uname -a Linux 1710 4.13.0-18-generic #21-Ubuntu SMP Tue Nov 21 17:00:07 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux -- 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/1725350 Title: KVM on 17.10 crashes the machine Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: When you start qemu on a 17.10 machine, the whole machine goes down and crashes: [ 90.689627] Unable to handle kernel paging request for data at address 0xf2d3bda0 [ 90.689705] Faulting instruction address: 0xc0361224 [ 90.689840] Oops: Kernel access of bad area, sig: 11 [#1] [ 90.689911] SMP NR_CPUS=2048 [ 90.689912] NUMA [ 90.690053] PowerNV [ 90.690092] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm 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 nf_defrag_ipv6 nf_nat nf_conntrack_netlink nf_conntrack nfnetlink idt_89hpesx snd_hda_codec_hdmi xfs joydev input_leds mac_hid snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundcore ofpart opal_prd cmdlinepart powernv_flash mtd at24 ipmi_powernv ipmi_devintf ipmi_msghandler powernv_rng uio_pdrv_genirq vmx_crypto ibmpowernv uio ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables [ 90.690724] autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage ast crct10dif_vpmsum i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm tg3 ahci libahci [ 90.690937] CPU: 48 PID: 3986 Comm: qemu-system-ppc Not tainted 4.13.0-12-generic #13-Ubuntu [ 90.691001] task: c00b122d8700 task.stack: c00b431cc000 [ 90.691167] NIP: c0361224 LR: c0998960 CTR: c09a19b0 [ 90.691223] REGS: c00bff61b800 TRAP: 0300 Not tainted (4.13.0-12-generic) [ 90.691277] MSR: 90009033 [ 90.691282] CR: 88002844 XER: [ 90.691347] CFAR: c099895c DAR: f2d3bda0 DSISR: 4000 SOFTE: 0 [ 90.691347] GPR00: c0998960 c00bff61ba80 c15e3000 c00b4ef61f20 [ 90.691347] GPR04: c00b44c61680 001f 001f [ 90.691347] GPR08: 001f 02d3bd80 c178e8e8 c00b5a0c26f0 [ 90.691347] GPR12: 28002842 cfadf800 c00b52d07880 c00b44c61680 [ 90.691347] GPR16: 001f 001f c553a560 [ 90.691347] GPR20: 0001 0002 08000553a560 c00b5c62a228 [ 90.691347] GPR24: c5531110 c00b5c632238 0210 [ 90.691347] GPR28: c0998960 c00bff61bc20 c00b4ef61f20 f2d3bd80 [ 90.692089] NIP [c0361224] kfree+0x54/0x270 [ 90.692133] LR [c0998960] xhci_urb_free_priv+0x20/0x40 [ 90.692325] Call Trace: [ 90.692345] [c00bff61ba80] [c00bff61bad0] 0xc00bff61bad0 (unreliable) [ 90.692402] [c00bff61bac0] [c0998960] xhci_urb_free_priv+0x20/0x40 [ 90.692459] [c00bff61bae0] [c099bfc8] xhci_giveback_urb_in_irq.isra.22+0x78/0x190 [ 90.692645] [c00bff61bb40] [c099c350] xhci_td_cleanup+0x130/0x200 [ 90.692702] [c00bff61bbc0] [c09a175c] handle_tx_event+0x74c/0x1380 [ 90.692759] [c00bff61bcc0] [c09a2894] xhci_irq+0x504/0xf20 [ 90.692808] [c00bff61bde0] [c017b110] __handle_irq_event_percpu+0x90/0x300 [ 90.692977] [c00bff61bea0] [c017b3b8] handle_irq_event_percpu+0x38/0x90 [ 90.693038] [c00bff61bee0] [c017b474] handle_irq_event+0x64/0xb0 [ 90.693094] [c00bff61bf10] [c0180da0] handle_fasteoi_irq+0xc0/0x230 [ 90.693155] [c00bff61bf40] [c017972c] generic_handle_irq+0x4c/0x70 [ 90.693332] [c00bff61bf60] [c001767c] __do_irq+0x7c/0x1c0 [ 90.693383] [c00bff61bf90] [c002ab70] call_do_irq+0x14/0x24 [ 90.693431] [c00b431cf9d0] [c001785c] do_IRQ+0x9c/0x130 [ 90.693478] [c00b431cfa20] [c0008ac4] hardware_interrupt_common+0x114/0x120 [ 90.693663] --- interrup
[Kernel-packages] [Bug 1735159] Re: powerpc/powernv: Flush console before platform error reboot
Joseph, I tested this kernel and it works fine without any seen regression. Thanks for the kernel: # uname -a Linux cake 4.10.0-40-generic #44~lp1735159 SMP Wed Nov 29 16:04:16 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux -- 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/1735159 Title: powerpc/powernv: Flush console before platform error reboot Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Unrecovered MCE and HMI errors are sent through a special restart OPAL call to log the platform error. The downside is that they don't go through normal Linux crash paths, so they don't give much information to the Linux console. We need to have the commit b746e3e01e70d23ef53dcde1203ab78a1b7ac514 in kernel 4.10. I did the backport and that will be attached to this bug. I also tested kernel -41 with this patch in several scenarios (KVM guest, Hypervisor) and I see no regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1735159/+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 1733864] Re: kernel 4.10.0-40 is hanging with a CPU soft lock
I also found that if I run artful VM on the same hypervisor, I do not see this problem on artful kernel. So, from what I see, it seems to be a problem on kernel 4.10 that is being exposed better on a KVM that runs on kernel 4.13. This is better log I was able to capture: [ 32.029274] NMI watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [swapper/10:0] [ 32.029402] Modules linked in: vmx_crypto kvm ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum virtio_blk [ 32.029464] CPU: 10 PID: 0 Comm: swapper/10 Not tainted 4.10.0-383-generic #383 [ 32.029466] task: c007f7663c00 task.stack: c007fe158000 [ 32.029467] NIP: c00163c4 LR: c00163c4 CTR: 0006 [ 32.029467] REGS: c007fe15b590 TRAP: 0901 Not tainted (4.10.0-383-generic) [ 32.029468] MSR: 80009033 [ 32.029472] CR: 28002824 XER: [ 32.029472] CFAR: c01894e4 SOFTE: 1 GPR00: c018995c c007fe15b810 c14ac900 0900 GPR04: c010bc30 c007ffda2980 8000 c007fe15b8c8 GPR08: 0600 0100 c007ffd8e128 GPR12: c09b8450 c7b85a00 [ 32.029483] NIP [c00163c4] arch_local_irq_restore+0x74/0x90 [ 32.029484] LR [c00163c4] arch_local_irq_restore+0x74/0x90 [ 32.029485] Call Trace: [ 32.029486] [c007fe15b810] [fffee2c1] 0xfffee2c1 (unreliable) [ 32.029488] [c007fe15b830] [c018995c] expire_timers+0x13c/0x210 [ 32.029490] [c007fe15b8a0] [c0189bd8] run_timer_softirq+0x1a8/0x230 [ 32.029492] [c007fe15b940] [c0bae11c] __do_softirq+0x19c/0x3fc [ 32.029494] [c007fe15ba30] [c00f28c8] irq_exit+0xe8/0x120 [ 32.029496] [c007fe15ba50] [c00250d4] timer_interrupt+0xa4/0xe0 [ 32.029498] [c007fe15ba80] [c00090d4] decrementer_common+0x114/0x120 [ 32.029501] --- interrupt: 901 at plpar_hcall_norets+0x1c/0x28 LR = check_and_cede_processor+0x38/0x50 [ 32.029502] [c007fe15bd70] [c09b80d4] check_and_cede_processor+0x24/0x50 (unreliable) [ 32.029504] [c007fe15bdd0] [c09b84a4] shared_cede_loop+0x54/0x150 [ 32.029506] [c007fe15be00] [c09b53ec] cpuidle_enter_state+0x17c/0x450 [ 32.029507] [c007fe15be60] [c01519a0] call_cpuidle+0x50/0xa0 [ 32.029509] [c007fe15be80] [c0151ec0] do_idle+0x2d0/0x340 [ 32.029510] [c007fe15bf00] [c01521c0] cpu_startup_entry+0x40/0x60 [ 32.029512] [c007fe15bf30] [c0047200] start_secondary+0x340/0x390 [ 32.029514] [c007fe15bf90] [c000aa6c] start_secondary_prolog+0x10/0x14 [ 32.029515] Instruction dump: [ 32.029517] 994d01d2 2fa3 409e0024 e92d0020 61298000 7d210164 38210020 e8010010 [ 32.029520] 7c0803a6 4e800020 6042 4bff42e5 <6000> 4be4 6042 e92d0020 [ 34.073274] INFO: rcu_sched detected stalls on CPUs/tasks: [ 34.073318] 10-...: (8 GPs behind) idle=ab9/1/0 softirq=703/703 fqs=2514 [ 34.073352] (detected by 13, t=5252 jiffies, g=-67, c=-68, q=6813) [ 34.073386] Task dump for CPU 10: [ 34.073387] swapper/10 R running task0 0 1 0x0804 [ 34.073389] Call Trace: [ 34.073391] [c007fe15bb20] [0001] 0x1 (unreliable) [ 97.093266] INFO: rcu_sched detected stalls on CPUs/tasks: [ 97.093310] 10-...: (8 GPs behind) idle=ab9/1/0 softirq=703/703 fqs=10197 [ 97.093342] (detected by 13, t=21007 jiffies, g=-67, c=-68, q=169213) [ 97.093378] Task dump for CPU 10: [ 97.093379] swapper/10 R running task0 0 1 0x0804 [ 97.093382] Call Trace: [ 97.093384] [c007fe15bb20] [0001] 0x1 (unreliable) -- 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/1733864 Title: kernel 4.10.0-40 is hanging with a CPU soft lock Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Bug description: Kernel 4.10.0-40-generic is causing CPU hung on POWER machines. I got this problem on a POWER8 KVM virtual machine [ 1912.003255] NMI watchdog: BUG: soft lockup - CPU#12 stuck for 24s! [dpkg-deb:31284] [ 1912.004496] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ipt_REJECT nf_reject_ipv4 xfrm_user xfrm_algo xt_addrtype xt_conntrack br_netfilter ebtable_filter ebtables ip6table_filter ip6_tables ib_srpt dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio tcm_qla2xxx qla2xxx vhost_scsi vhost usb_f_tcm tcm_usb_gadget libcomposite udc_core tcm_fc libfc scsi_tra
[Kernel-packages] [Bug 1733864] Re: kernel 4.10.0-40 is hanging with a CPU soft lock
I found something interesting. The original dump above was reproduced with kernel 4.4.0-94-generic in the hypervisor. It is very hard to reproduce this issue on the following hypervisor (I just reproduce this once in a while). I migrated to a machine to use kernel 4.13.0-17-generic and the problem is being reproduced instantaneously. That said, I understand that the problem has something to do with the hypervisor kernel version. -- 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/1733864 Title: kernel 4.10.0-40 is hanging with a CPU soft lock Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Bug description: Kernel 4.10.0-40-generic is causing CPU hung on POWER machines. I got this problem on a POWER8 KVM virtual machine [ 1912.003255] NMI watchdog: BUG: soft lockup - CPU#12 stuck for 24s! [dpkg-deb:31284] [ 1912.004496] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ipt_REJECT nf_reject_ipv4 xfrm_user xfrm_algo xt_addrtype xt_conntrack br_netfilter ebtable_filter ebtables ip6table_filter ip6_tables ib_srpt dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio tcm_qla2xxx qla2xxx vhost_scsi vhost usb_f_tcm tcm_usb_gadget libcomposite udc_core tcm_fc libfc scsi_transport_fc tcm_loop iscsi_target_mod target_core_file target_core_iblock target_core_pscsi target_core_mod ipmi_devintf ipmi_msghandler xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp iptable_filter ip_tables x_tables openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) [ 1912.004575] znvpair(PO) spl(O) bridge 8021q garp mrp stp llc vmx_crypto kvm ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum virtio_blk [ 1912.004624] CPU: 12 PID: 31284 Comm: dpkg-deb Tainted: P O 4.10.0-40-generic #44~16.04.1-Ubuntu [ 1912.004626] task: c00775551e00 task.stack: c007755ac000 [ 1912.004627] NIP: 3fff86b71960 LR: 3fff86b7319c CTR: 002d [ 1912.004628] REGS: c007755afea0 TRAP: 0901 Tainted: P O (4.10.0-40-generic) [ 1912.004629] MSR: 8280f033 [ 1912.004635] CR: 42004442 XER: 2000 [ 1912.004636] CFAR: 3fff86b719b4 SOFTE: 1 GPR00: 00a4 3fffd53f7d70 3fff86ba5008 0040 GPR04: 038a20fc 3fff86467d4b 036c0ed8 002a GPR08: 3fff81c41010 000a20f5 0081 ffec0ed1 GPR12: 00a6 3fff86c8db30 [ 1912.004646] NIP [3fff86b71960] 0x3fff86b71960 [ 1912.004647] LR [3fff86b7319c] 0x3fff86b7319c [ 1912.004647] Call Trace: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733864/+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 1733864] Re: kernel 4.10.0-40 is hanging with a CPU soft lock
Looking in a email thread titled "RCU lockup issues when CONFIG_SOFTLOCKUP_DETECTOR=n - any one else seeing this?"[1] it seems that this problem is very similar to the one in the thread. The final fix seems to be commit id 2fe59f507a65dbd734b990a11ebc7488f6f87a24. [1] http://linuxppc.10917.n7.nabble.com/Re-RCU-lockup-issues-when-CONFIG-SOFTLOCKUP-DETECTOR-n-any-one-else-seeing-this-tt125634.html#none"; -- 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/1733864 Title: kernel 4.10.0-40 is hanging with a CPU soft lock Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Bug description: Kernel 4.10.0-40-generic is causing CPU hung on POWER machines. I got this problem on a POWER8 KVM virtual machine [ 1912.003255] NMI watchdog: BUG: soft lockup - CPU#12 stuck for 24s! [dpkg-deb:31284] [ 1912.004496] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ipt_REJECT nf_reject_ipv4 xfrm_user xfrm_algo xt_addrtype xt_conntrack br_netfilter ebtable_filter ebtables ip6table_filter ip6_tables ib_srpt dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio tcm_qla2xxx qla2xxx vhost_scsi vhost usb_f_tcm tcm_usb_gadget libcomposite udc_core tcm_fc libfc scsi_transport_fc tcm_loop iscsi_target_mod target_core_file target_core_iblock target_core_pscsi target_core_mod ipmi_devintf ipmi_msghandler xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp iptable_filter ip_tables x_tables openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) [ 1912.004575] znvpair(PO) spl(O) bridge 8021q garp mrp stp llc vmx_crypto kvm ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum virtio_blk [ 1912.004624] CPU: 12 PID: 31284 Comm: dpkg-deb Tainted: P O 4.10.0-40-generic #44~16.04.1-Ubuntu [ 1912.004626] task: c00775551e00 task.stack: c007755ac000 [ 1912.004627] NIP: 3fff86b71960 LR: 3fff86b7319c CTR: 002d [ 1912.004628] REGS: c007755afea0 TRAP: 0901 Tainted: P O (4.10.0-40-generic) [ 1912.004629] MSR: 8280f033 [ 1912.004635] CR: 42004442 XER: 2000 [ 1912.004636] CFAR: 3fff86b719b4 SOFTE: 1 GPR00: 00a4 3fffd53f7d70 3fff86ba5008 0040 GPR04: 038a20fc 3fff86467d4b 036c0ed8 002a GPR08: 3fff81c41010 000a20f5 0081 ffec0ed1 GPR12: 00a6 3fff86c8db30 [ 1912.004646] NIP [3fff86b71960] 0x3fff86b71960 [ 1912.004647] LR [3fff86b7319c] 0x3fff86b7319c [ 1912.004647] Call Trace: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733864/+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 1725350] Re: KVM on 17.10 crashes the machine
Hi Joseph, I tested in the mainline kernel, and the problem does not happen. This is a problem we are only seeing in 17.10 at this moment. -- 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/1725350 Title: KVM on 17.10 crashes the machine Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Status in linux source package in Artful: New Bug description: When you start qemu on a 17.10 machine, the whole machine goes down and crashes: [ 90.689627] Unable to handle kernel paging request for data at address 0xf2d3bda0 [ 90.689705] Faulting instruction address: 0xc0361224 [ 90.689840] Oops: Kernel access of bad area, sig: 11 [#1] [ 90.689911] SMP NR_CPUS=2048 [ 90.689912] NUMA [ 90.690053] PowerNV [ 90.690092] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm 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 nf_defrag_ipv6 nf_nat nf_conntrack_netlink nf_conntrack nfnetlink idt_89hpesx snd_hda_codec_hdmi xfs joydev input_leds mac_hid snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundcore ofpart opal_prd cmdlinepart powernv_flash mtd at24 ipmi_powernv ipmi_devintf ipmi_msghandler powernv_rng uio_pdrv_genirq vmx_crypto ibmpowernv uio ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables [ 90.690724] autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage ast crct10dif_vpmsum i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm tg3 ahci libahci [ 90.690937] CPU: 48 PID: 3986 Comm: qemu-system-ppc Not tainted 4.13.0-12-generic #13-Ubuntu [ 90.691001] task: c00b122d8700 task.stack: c00b431cc000 [ 90.691167] NIP: c0361224 LR: c0998960 CTR: c09a19b0 [ 90.691223] REGS: c00bff61b800 TRAP: 0300 Not tainted (4.13.0-12-generic) [ 90.691277] MSR: 90009033 [ 90.691282] CR: 88002844 XER: [ 90.691347] CFAR: c099895c DAR: f2d3bda0 DSISR: 4000 SOFTE: 0 [ 90.691347] GPR00: c0998960 c00bff61ba80 c15e3000 c00b4ef61f20 [ 90.691347] GPR04: c00b44c61680 001f 001f [ 90.691347] GPR08: 001f 02d3bd80 c178e8e8 c00b5a0c26f0 [ 90.691347] GPR12: 28002842 cfadf800 c00b52d07880 c00b44c61680 [ 90.691347] GPR16: 001f 001f c553a560 [ 90.691347] GPR20: 0001 0002 08000553a560 c00b5c62a228 [ 90.691347] GPR24: c5531110 c00b5c632238 0210 [ 90.691347] GPR28: c0998960 c00bff61bc20 c00b4ef61f20 f2d3bd80 [ 90.692089] NIP [c0361224] kfree+0x54/0x270 [ 90.692133] LR [c0998960] xhci_urb_free_priv+0x20/0x40 [ 90.692325] Call Trace: [ 90.692345] [c00bff61ba80] [c00bff61bad0] 0xc00bff61bad0 (unreliable) [ 90.692402] [c00bff61bac0] [c0998960] xhci_urb_free_priv+0x20/0x40 [ 90.692459] [c00bff61bae0] [c099bfc8] xhci_giveback_urb_in_irq.isra.22+0x78/0x190 [ 90.692645] [c00bff61bb40] [c099c350] xhci_td_cleanup+0x130/0x200 [ 90.692702] [c00bff61bbc0] [c09a175c] handle_tx_event+0x74c/0x1380 [ 90.692759] [c00bff61bcc0] [c09a2894] xhci_irq+0x504/0xf20 [ 90.692808] [c00bff61bde0] [c017b110] __handle_irq_event_percpu+0x90/0x300 [ 90.692977] [c00bff61bea0] [c017b3b8] handle_irq_event_percpu+0x38/0x90 [ 90.693038] [c00bff61bee0] [c017b474] handle_irq_event+0x64/0xb0 [ 90.693094] [c00bff61bf10] [c0180da0] handle_fasteoi_irq+0xc0/0x230 [ 90.693155] [c00bff61bf40] [c017972c] generic_handle_irq+0x4c/0x70 [ 90.693332] [c00bff61bf60] [c001767c] __do_irq+0x7c/0x1c0 [ 90.693383] [c00bff61bf90] [c002ab70] call_do_irq+0x14/0x24 [ 90.693431] [c00b431cf9d0] [c001785c] do_IRQ+0x9c/0x130 [ 90.693478] [c00b431cfa20] [c0008ac4] hardware_interrupt_common+0x114/0x120 [ 90.693663] --- interrupt: 501 at __copy_tofrom_user_power7+0x1f4/0x7cc [ 90.693663] LR = _copy_to_user+0x3c/0x60 [ 90.693736] [c00b431cfd10] [c00b431cfdc0] 0xc00b431cfdc0 (unreliable) [ 90.693797] [c00
[Kernel-packages] [Bug 1721070] Re: powerpc/64s: Add workaround for P9 vector CI load issuenext
Joseph, Quick update on this bug. I tested your artful test and: a) It didn't cause any regression. I tested on two P9 with different processor level and P8 and the code runs fine. b) It seems to be fixing the issue that is proposed to fix. c) There are some test cases that are still failing, and might require extra and we will might request those in another bug. -- 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/1721070 Title: powerpc/64s: Add workaround for P9 vector CI load issuenext Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: Triaged Status in linux source package in Artful: In Progress Bug description: -- Problem Description -- POWER9 DD2.1 and earlier has an issue where some cache inhibited vector load will return bad data. The workaround is two part, one firmware/microcode part triggers HMI interrupts when hitting such loads, the other part is this patch which then emulates the instructions in Linux. The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and lxvh8x. When an instruction triggers the HMI, all threads in the core will be sent to the HMI handler, not just the one running the vector load. In general, these spurious HMIs are detected by the emulation code and we just return back to the running process. Unfortunately, if a spurious interrupt occurs on a vector load that's to normal memory we have no way to detect that it's spurious (unless we walk the page tables, which is very expensive). In this case we emulate the load but we need do so using a vector load itself to ensure 128bit atomicity is preserved. Some additional debugfs emulated instruction counters are added also. In order to solve this bug, we need to cherry pick the following patch https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=5080332c2c893118dbc18755f35c8b0131cf0fc4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1721070/+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 1721070] Re: powerpc/64s: Add workaround for P9 vector CI load issuenext
Joseph, Which branch did you use? I can't find the commits at master or master- next: [root@ltc-wspoon9 ubuntu-artful]# git log --oneline js-master | head -n 20 1e3dad9 UBUNTU: Ubuntu-4.13.0-12.13 1f46464 UBUNTU: [Config] CONFIG_I2C_XLP9XX=m 39ae1ca perf/x86: Fix data source decoding for Skylake f473bf9 perf/x86: Move Nehalem PEBS code to flag a8725d5 UBUNTU: [Config] CONFIG_DRM_VBOXVIDEO=n 30d9497 UBUNTU: [Config] Disable CONFIG_IPMMU_VMSA on arm64 806240e scsi: cxlflash: Fix vlun resize failure in the shrink path 69f4910 fs: aio: fix the increment of aio-nr and counting against aio-max-nr 675f3cd UBUNTU: [Config] CONFIG_PINCTRL_DENVERTON=m ebaccf7 libnvdimm, btt: rework error clearing 4bda159 libnvdimm: fix potential deadlock while clearing errors adfc036 libnvdimm, btt: cache sector_size in arena_info b79a931 libnvdimm, btt: ensure that flags were also unchanged during a map_read 45f43c2 libnvdimm, btt: refactor map entry operations with macros 36a7c4e libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path 3f6cafd dax: move all DAX radix tree defs to fs/dax.c 52522e9 dax: remove DAX code from page_cache_tree_insert() 54585e3 dax: use common 4k zero page for dax mmap reads 7b6956d dax: relocate some dax functions a9342b2 mm: add vm_insert_mixed_mkwrite() [root@ltc-wspoon9 ubuntu-artful]# git log --oneline js-master-next | head -n 20 f30326f4 UBUNTU: Start new release ba39ad1 UBUNTU: Ubuntu-4.13.0-15.16 655913c Revert "powerpc/powernv: Add IMC OPAL APIs" 4bab524 Revert "powerpc/powernv: Detect and create IMC device" 192a8d2 Revert "powerpc/perf: Add nest IMC PMU support" 1b9f175 Revert "powerpc/powernv: Add support for powercap framework" 386a56a Revert "powerpc/powernv: Add support to set power-shifting-ratio" 8dc96fd Revert "powerpc/powernv: Enable PCI peer-to-peer" fdea4c4 Revert "powerpc/powernv/vas: Define macros, register fields and structures" 258fa77 Revert "powerpc/powernv: Move GET_FIELD/SET_FIELD to vas.h" efb0381 Revert "powerpc/powernv/vas: Define vas_init() and vas_exit()" 18c0c36 Revert "powerpc/powernv/vas: Define helpers to access MMIO regions" b717098 Revert "powerpc/powernv/vas: Define helpers to init window context" cef2434 Revert "powerpc/powernv/vas: Define helpers to alloc/free windows" 8d6ed22 Revert "powerpc/powernv/vas: Define vas_rx_win_open() interface" 15b835b Revert "powerpc/powernv/vas: Define vas_win_close() interface" 47073e3 Revert "powerpc/powernv/vas: Define vas_tx_win_open()" 5afb9ea Revert "powerpc/powernv/vas: Define copy/paste interfaces" 9cf4ce8 Revert "UBUNTU: [Config] CONFIG_PPC_VAS=y" b22a1be Revert "crypto/nx: Rename nx842_powernv_function as icswx function" -- 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/1721070 Title: powerpc/64s: Add workaround for P9 vector CI load issuenext Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: -- Problem Description -- POWER9 DD2.1 and earlier has an issue where some cache inhibited vector load will return bad data. The workaround is two part, one firmware/microcode part triggers HMI interrupts when hitting such loads, the other part is this patch which then emulates the instructions in Linux. The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and lxvh8x. When an instruction triggers the HMI, all threads in the core will be sent to the HMI handler, not just the one running the vector load. In general, these spurious HMIs are detected by the emulation code and we just return back to the running process. Unfortunately, if a spurious interrupt occurs on a vector load that's to normal memory we have no way to detect that it's spurious (unless we walk the page tables, which is very expensive). In this case we emulate the load but we need do so using a vector load itself to ensure 128bit atomicity is preserved. Some additional debugfs emulated instruction counters are added also. In order to solve this bug, we need to cherry pick the following patch https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=5080332c2c893118dbc18755f35c8b0131cf0fc4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1721070/+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 1721070] Re: powerpc/64s: Add workaround for P9 vector CI load issuenext
Joseph, Do you have a kernel source for this package that I can take a deeper look? -- 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/1721070 Title: powerpc/64s: Add workaround for P9 vector CI load issuenext Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: -- Problem Description -- POWER9 DD2.1 and earlier has an issue where some cache inhibited vector load will return bad data. The workaround is two part, one firmware/microcode part triggers HMI interrupts when hitting such loads, the other part is this patch which then emulates the instructions in Linux. The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and lxvh8x. When an instruction triggers the HMI, all threads in the core will be sent to the HMI handler, not just the one running the vector load. In general, these spurious HMIs are detected by the emulation code and we just return back to the running process. Unfortunately, if a spurious interrupt occurs on a vector load that's to normal memory we have no way to detect that it's spurious (unless we walk the page tables, which is very expensive). In this case we emulate the load but we need do so using a vector load itself to ensure 128bit atomicity is preserved. Some additional debugfs emulated instruction counters are added also. In order to solve this bug, we need to cherry pick the following patch https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=5080332c2c893118dbc18755f35c8b0131cf0fc4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1721070/+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 1718293] Re: [Ubuntu 17.10] POWER9 - Base - Integrate P9 VAS (Virtual Accelerator Switchboard) support in kernel
There is an indication that the tree artful master-next kernel is broken on POWER9 and it seems to be related to this patchset. I am looking at it, maybe we will need to revert 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/1718293 Title: [Ubuntu 17.10] POWER9 - Base - Integrate P9 VAS (Virtual Accelerator Switchboard) support in kernel Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: This feature request is used to submit kernel changes needed for adding VAS (Virtual Accelerator Switchboard) support. VAS interface allows kernel or user space to communicate with any accelerator (Ex: NX). kernel changes will be to open a window/ channel with accelerator and communicate with copy / paste facility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1718293/+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 1707875] Re: include support for Python bindings in "perf"
Hello Canonical, Any update about this bug? Will it make 17.10? Thank you, Breno -- 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/1707875 Title: include support for Python bindings in "perf" Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: == Comment: #0 - Paul A. Clarke - 2017-07-26 09:59:57 == ---Problem Description--- Request to build python bindings support with perf. ---Steps to Reproduce--- Ubuntu-17.04# perf script -g python Python scripting not supported. Install libpython and rebuild perf to enable it. For example: # apt-get install python-dev (ubuntu) # yum install python-devel (Fedora) etc. Userspace tool common name: perf Userspace rpm: linux-tools-common Userspace tool obtained from project website: na == Comment: #2 - MAMATHA INAMDAR - 2017-08-01 05:02:34 == After installing libpython, downloaded ubuntu 17.04 linux source code and compiled perf tool then it works fine. # ./perf script -g python generated Python script: perf-script.py but when I run perf tool without rebuilding after installing libpython it shows an error # perf script -g python Python scripting not supported. Install libpython and rebuild perf to enable it. For example: # apt-get install python-dev (ubuntu) # yum install python-devel (Fedora) etc. root@p8wookie:/home/Mamatha/ubuntu/ubuntu-zesty/tools/perf# perf --version perf version 4.10.17 == Comment: #3 - MAMATHA INAMDAR - 2017-08-01 05:03:44 == Request to build python bindings support with perf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1707875/+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 1700606] Re: POWER9: CAPI2 enablement - Fixes
** Changed in: ubuntu-power-systems Status: In Progress => 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/1700606 Title: POWER9: CAPI2 enablement - Fixes Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: = Comment: #2 - Christophe Lombard - 2017-06-26 11:15:53 == Here are new cxl patches we would like to include on Zesty kernel. These patches bring fixes for the CXL device driver for CAPI and CAPI2. They apply on top of https://bugzilla.linux.ibm.com/show_bug.cgi?id=153737 commit ids: ea9a26d117cf0637c71d3e0076f4a124bf5859df cxl: Force context lock during EEH flow 4f58f0bf155e87dda31a3088b1e107fa9dd79f0e cxl: Route eeh events to all drivers in cxl_pci_error_detected() a715626a8e904e7226915d1bc4885317ea9da141 cxl: Mask slice error interrupts after first occurrence b3aa20ba2ba8072b73bd799605b8c98927b7056c cxl: Avoid double free_irq() for psl,slice interrupts cec422c11caeeccae709e9942058b6b644ce434c cxl: Fix error path on bad ioctl 797625deaedd9a0621376817db2813244b3246e3 cxl: Fixes for Coherent Accelerator Interface Architecture 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1700606/+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 1716924] Re: [Ubuntu 17.10 FEAT] Include cxlflash package in Ubuntu
This is a bug that should be assigned to the foundation team. -- 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/1716924 Title: [Ubuntu 17.10 FEAT] Include cxlflash package in Ubuntu Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Rodrigo R. Rosatti Galvao - 2017-09-12 13:34:52 == CAPI can be thought of as a special tunneling protocol through PCIe that allow PCIe adapters to look like special purpose co-processors which can read or write an application's memory and generate page faults. The cxlflash driver is responsible for the initialization of the Coherent Accelerator (CXL) Flash Adapter, setting up the special path for user space access, and performing error recovery. == Comment: #2 - Rodrigo R. Rosatti Galvao - 2017-09-12 13:35:24 == Hello, Canonical We'd like to include cxlflash package into Artful. There's already a RFS opened for it on Debian (RFS 870909) and it's uploaded into mentors.debian as well. But, since the FeatureFreeze for Artful was on August 24th we'd like to make progress on it directly with Ubuntu. RFS 870909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870909 package on mentors: https://mentors.debian.net/package/cxlflash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1716924/+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 1716491] Re: New PMU fixes for marked events.
Joseph,
Thanks for the kernel. I tested it and it worked.
ubuntu@ltc-wspoon3:~$ uname -a
Linux ltc-wspoon3 4.10.0-33-generic #37~lp1716491 SMP Tue Sep 12 19:34:42 UTC
2017 ppc64le ppc64le ppc64le GNU/Linux
--
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/1716491
Title:
New PMU fixes for marked events.
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Zesty:
In Progress
Bug description:
Dear Canonical,
Please include the following fixes into Ubuntu Zesty (4.10) kernel.
The current kernel does not enable marked events on Power9. And the
following fixes are required:
09539f9b1236 ("powerpc/perf: POWER9 PMU stops after idle workaround")
101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after idle")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1716491/+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 1709784] Re: KVM on 16.04.3 throws an error
Christian, I am looking at 4.4 git repository and version -93 contains exactly the problem described here, it contains the commit# 46a704f8409f79fd66567ad3f8a7304830a84293 (as a97e978574f41ffcf1813c180aba2772d46fbb5b), but it does not include commit# e47057151422a67ce08747176fa21cb3b526a2c9. That said, we probably want to include e47057151422a67ce08747176fa21cb3b526a2c9 into 4.4 series as soon as possible. -- 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/1709784 Title: KVM on 16.04.3 throws an error Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: Won't Fix Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: Invalid Bug description: Problem Description KVM on Ubuntu 16.04.3 throws an error when used ---uname output--- Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8348-21C Habanero ---Steps to Reproduce--- Install 16.04.3 install KVM like: apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils then exit and log back in so virsh will work without sudo then run my spawn script $ cat spawn.sh #!/bin/bash img=$1 qemu-system-ppc64 \ -machine pseries,accel=kvm,usb=off -cpu host -m 512 \ -display none -nographic \ -net nic -net user \ -drive "file=$img" with a freshly downloaded ubuntu cloud image sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img And I get nothing on the output. and errors in dmesg ubuntu@bastion-1:~$ [ 340.180295] Facility 'TM' unavailable, exception at 0xd000148b7f10, MSR=90009033 [ 340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1] [ 340.180513] SMP NR_CPUS=2048 NUMA PowerNV [ 340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c [ 340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 4.4.0-89-generic #112-Ubuntu [ 340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: c01e34ce4000 [ 340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: d000148b7e40 [ 340.181475] REGS: c01e34ce77b0 TRAP: 0f60 Not tainted (4.4.0-89-generic) [ 340.181519] MSR: 90009033 CR: 22024848 XER: [ 340.181629] CFAR: d000148b7ea4 SOFTE: 1 GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc GPR04: c01db9ac c01e34ce7bc0 GPR08: 0001 c01e34c30b50 0001 d000148278f8 GPR12: d000148b7e40 cfb5b500 001f GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 GPR24: 3fffc91fe990 3fff91c10028 c01e37bc GPR28: c01db9ac c01e37bc c01db9ac [ 340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv] [ 340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182394] Call Trace: [ 340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 (unreliable) [ 340.182468] [c01e34ce7b70] [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182522] [c01e34ce7ba0] [d0001481f674] kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm] [ 340.182581] [c01e34ce7be0] [d00014813918] kvm_vcpu_ioctl+0x528/0x7b0 [kvm] [ 340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0 [ 340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0 [ 340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4 [ 340.182766] Instruction dump: [ 340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 e9290108 [ 340.1828
[Kernel-packages] [Bug 1704479] Re: Change CONFIG_IBMVETH to module
Verification done! ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- 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/1704479 Title: Change CONFIG_IBMVETH to module Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Committed Status in linux source package in Artful: Fix Released Bug description: == Comment: #0 - Breno Leitao - 2017-07-14 15:07:47 == Dear Canonical, Please change the CONFIG_IBMVETH=y to module on artful kernel. Thank you, Breno To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1704479/+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 1709784] Re: KVM on 16.04.3 throws an error
I also tested xenial GA kernel: sid ➜ ~ sudo uname -a Linux sid 4.4.0-89-generic #112~lp1709784 SMP Thu Aug 10 19:39:43 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux sid ➜ ~ sudo virsh list IdName State 2 debian running 3 1604 running 4 unstable running sid ➜ ~ sudo virsh console 1604 Connected to domain 1604 Escape character is ^] Ubuntu 16.04.3 LTS 1604 hvc0 1604 login: -- 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/1709784 Title: KVM on 16.04.3 throws an error Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Won't Fix Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Bug description: Problem Description KVM on Ubuntu 16.04.3 throws an error when used ---uname output--- Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8348-21C Habanero ---Steps to Reproduce--- Install 16.04.3 install KVM like: apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils then exit and log back in so virsh will work without sudo then run my spawn script $ cat spawn.sh #!/bin/bash img=$1 qemu-system-ppc64 \ -machine pseries,accel=kvm,usb=off -cpu host -m 512 \ -display none -nographic \ -net nic -net user \ -drive "file=$img" with a freshly downloaded ubuntu cloud image sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img And I get nothing on the output. and errors in dmesg ubuntu@bastion-1:~$ [ 340.180295] Facility 'TM' unavailable, exception at 0xd000148b7f10, MSR=90009033 [ 340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1] [ 340.180513] SMP NR_CPUS=2048 NUMA PowerNV [ 340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c [ 340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 4.4.0-89-generic #112-Ubuntu [ 340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: c01e34ce4000 [ 340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: d000148b7e40 [ 340.181475] REGS: c01e34ce77b0 TRAP: 0f60 Not tainted (4.4.0-89-generic) [ 340.181519] MSR: 90009033 CR: 22024848 XER: [ 340.181629] CFAR: d000148b7ea4 SOFTE: 1 GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc GPR04: c01db9ac c01e34ce7bc0 GPR08: 0001 c01e34c30b50 0001 d000148278f8 GPR12: d000148b7e40 cfb5b500 001f GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 GPR24: 3fffc91fe990 3fff91c10028 c01e37bc GPR28: c01db9ac c01e37bc c01db9ac [ 340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv] [ 340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182394] Call Trace: [ 340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 (unreliable) [ 340.182468] [c01e34ce7b70] [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182522] [c01e34ce7ba0] [d0001481f674] kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm] [ 340.182581] [c01e34ce7be0] [d00014813918] kvm_vcpu_ioctl+0x528/0x7b0 [kvm] [ 340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0 [ 340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0 [ 340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb
[Kernel-packages] [Bug 1709784] Re: KVM on 16.04.3 throws an error
I just tested zesty kernel and it worked fine: # uname -a Linux sid 4.10.0-30-generic #34~lp1709784 SMP Thu Aug 10 20:01:17 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux # sudo virsh list IdName State 1 unstable running 2 debian running 4 1604 running # sudo virsh console 1604 Connected to domain 1604 Escape character is ^] Ubuntu 16.04.3 LTS 1604 hvc0 1604 login: -- 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/1709784 Title: KVM on 16.04.3 throws an error Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Won't Fix Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Bug description: Problem Description KVM on Ubuntu 16.04.3 throws an error when used ---uname output--- Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8348-21C Habanero ---Steps to Reproduce--- Install 16.04.3 install KVM like: apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils then exit and log back in so virsh will work without sudo then run my spawn script $ cat spawn.sh #!/bin/bash img=$1 qemu-system-ppc64 \ -machine pseries,accel=kvm,usb=off -cpu host -m 512 \ -display none -nographic \ -net nic -net user \ -drive "file=$img" with a freshly downloaded ubuntu cloud image sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img And I get nothing on the output. and errors in dmesg ubuntu@bastion-1:~$ [ 340.180295] Facility 'TM' unavailable, exception at 0xd000148b7f10, MSR=90009033 [ 340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1] [ 340.180513] SMP NR_CPUS=2048 NUMA PowerNV [ 340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c [ 340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 4.4.0-89-generic #112-Ubuntu [ 340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: c01e34ce4000 [ 340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: d000148b7e40 [ 340.181475] REGS: c01e34ce77b0 TRAP: 0f60 Not tainted (4.4.0-89-generic) [ 340.181519] MSR: 90009033 CR: 22024848 XER: [ 340.181629] CFAR: d000148b7ea4 SOFTE: 1 GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc GPR04: c01db9ac c01e34ce7bc0 GPR08: 0001 c01e34c30b50 0001 d000148278f8 GPR12: d000148b7e40 cfb5b500 001f GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 GPR24: 3fffc91fe990 3fff91c10028 c01e37bc GPR28: c01db9ac c01e37bc c01db9ac [ 340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv] [ 340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182394] Call Trace: [ 340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 (unreliable) [ 340.182468] [c01e34ce7b70] [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182522] [c01e34ce7ba0] [d0001481f674] kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm] [ 340.182581] [c01e34ce7be0] [d00014813918] kvm_vcpu_ioctl+0x528/0x7b0 [kvm] [ 340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0 [ 340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd
[Kernel-packages] [Bug 1700521] Re: powerpc: Invalidate ERAT on powersave wakeup for POWER9
Tested it on my machine and the original problem was not seen. ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- 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/1700521 Title: powerpc: Invalidate ERAT on powersave wakeup for POWER9 Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Committed Bug description: == Comment: #0 - Breno Leitao - 2017-06-23 13:13:02 == Hello, This is a patch that we need to have on Zesty, including on the 16.04.3 installer. On POWER9 the ERAT may be incorrect on wakeup from some stop states that lose state. This causes random segvs and illegal instructions when these stop states are enabled. This patch invalidates the ERAT on wakeup on POWER9 to prevent this from causing a problem. URL: https://patchwork.ozlabs.org/patch/780365/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1700521/+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 1702159] Re: Opal and POWER9 DD2
I am not able to test this bug on DD2 hardware at this moment, but I tested on DD1 and POWER8 and I didn't see a regression. Marking it as validated. ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- 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/1702159 Title: Opal and POWER9 DD2 Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: That will allow OPAL to configure the CPU in an optimal way. PATCH: http://patchwork.ozlabs.org/patch/783015/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1702159/+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 1705044] Re: Kernel OPAL regression
** Changed in: ubuntu-power-systems Status: New => Invalid ** Changed in: linux (Ubuntu) Status: New => 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/1705044 Title: Kernel OPAL regression Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Invalid Bug description: == Comment: #0 - Breno Leitao - 2017-07-18 07:58:42 == There is a regression caused by patch included on LP#1702159. We would like to have the following fix on top of it: http://patchwork.ozlabs.org/patch/789381/ https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=a70b487b07cf4201bc6702e7f646fa593b23009f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1705044/+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 1700606] Re: POWER9: CAPI2 enablement - Fixes
Canonical is asking us (IBM) to test the kernel in the PPA before proceeding with the patch inclusion. -- 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/1700606 Title: POWER9: CAPI2 enablement - Fixes Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: = Comment: #2 - Christophe Lombard - 2017-06-26 11:15:53 == Here are new cxl patches we would like to include on Zesty kernel. These patches bring fixes for the CXL device driver for CAPI and CAPI2. They apply on top of https://bugzilla.linux.ibm.com/show_bug.cgi?id=153737 commit ids: ea9a26d117cf0637c71d3e0076f4a124bf5859df cxl: Force context lock during EEH flow 4f58f0bf155e87dda31a3088b1e107fa9dd79f0e cxl: Route eeh events to all drivers in cxl_pci_error_detected() a715626a8e904e7226915d1bc4885317ea9da141 cxl: Mask slice error interrupts after first occurrence b3aa20ba2ba8072b73bd799605b8c98927b7056c cxl: Avoid double free_irq() for psl,slice interrupts cec422c11caeeccae709e9942058b6b644ce434c cxl: Fix error path on bad ioctl 797625deaedd9a0621376817db2813244b3246e3 cxl: Fixes for Coherent Accelerator Interface Architecture 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1700606/+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 1702159] Re: Opal and POWER9 DD2
Patch sent to kernel-team mailing list: https://lists.ubuntu.com/archives/kernel-team/2017-July/085402.html -- 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/1702159 Title: Opal and POWER9 DD2 Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: That will allow OPAL to configure the CPU in an optimal way. PATCH: http://patchwork.ozlabs.org/patch/783015/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1702159/+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 1701272] Re: New NVLINK2 patches
Patches sent to the kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2017-June/085279.html
--
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/1701272
Title:
New NVLINK2 patches
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - Breno Leitao - 2017-06-28 16:21:33 ==
Dear Canonical,
These are some important patches we need into 16.04.3. Without these
patches, NVLINK and ATS are broken:
NPU2 requires an extra explicit flush to an active GPU PID when sending
address translation shoot downs (ATSDs) to reliably flush the GPU TLB. This
patch adds just such a flush at the end of each sequence of ATSDs.
We can safely use PID 0 which is always reserved and active on the GPU. PID
0 is only used for init_mm which will never be a user mm on the GPU. To
enforce this we add a check in pnv_npu2_init_context() just in case someone
tries to use PID 0 on the GPU.
http://patchwork.ozlabs.org/patch/778160/
"4c3b89e powerpc/powernv: Add sanity checks to pnv_pci_get_{gpu|npu}_dev"
introduced explicit warnings in pnv_pci_get_npu_dev() when a PCIe device
has no associated device-tree node. However not all PCIe devices have an
of_node and pnv_pci_get_npu_dev() gets indirectly called at least once for
every PCIe device in the system. This results in spurious WARN_ON()'s so
remove it.
http://patchwork.ozlabs.org/patch/775595/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1701272/+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 1700521] Re: powerpc: Invalidate ERAT on powersave wakeup for POWER9
patch sent to kernel-team mailing list: https://lists.ubuntu.com/archives/kernel-team/2017-June/085197.html -- 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/1700521 Title: powerpc: Invalidate ERAT on powersave wakeup for POWER9 Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Breno Leitao - 2017-06-23 13:13:02 == Hello, This is a patch that we need to have on Zesty, including on the 16.04.3 installer. On POWER9 the ERAT may be incorrect on wakeup from some stop states that lose state. This causes random segvs and illegal instructions when these stop states are enabled. This patch invalidates the ERAT on wakeup on POWER9 to prevent this from causing a problem. URL: https://patchwork.ozlabs.org/patch/780365/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1700521/+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 1691477] Re: Hardware transaction memory corruption
I tested this fix and now it is fixed on the proposed kernel. I used the htm torture tool: https://github.com/leitao/htm_torture/tree/master/narrow ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- 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/1691477 Title: Hardware transaction memory corruption Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: There is a bug on hardware transactional memory on Ubuntu 17.04 that is hard to reproduce but I was able to create a testcase that reproduces it easily: https://github.com/leitao/htm_torture/tree/master/narrow The fix for this problem was already accepted in the kernel https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=f48e91e87e67b56bef63393d1a02c6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1691477/+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 1698844] Re: Fix /proc/cpuinfo revision for POWER9 DD2
Sent to the kernel-team mailing list: https://lists.ubuntu.com/archives/kernel-team/2017-June/084927.html -- 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/1698844 Title: Fix /proc/cpuinfo revision for POWER9 DD2 Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Breno Leitao - 2017-06-19 09:44:36 == The P9 PVR bits 12-15 don't indicate a revision but instead different chip configurations. From BookIV we have: Bits Configuration 0 :Scale out 12 cores 1 :Scale out 24 cores 2 :Scale up 12 cores 3 :Scale up 24 cores DD1 doesn't use this but DD2 does. Linux will mostly use the "Scale out 24 core" configuration (ie. SMT4 not SMT8) which results in a PVR of 0x004e1200. The reported revision in /proc/cpuinfo is hence reported incorrectly as "18.0". This patch fixes this to mask off only the relevant bits for the major revision (ie. bits 8-11) for POWER9. Please cherry pick: https://patchwork.ozlabs.org/patch/776052/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1698844/+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 1692580] Re: ATS fix: Fix opal_npu_destroy_context call
Patch sent to the kernel-team mailing list: https://lists.ubuntu.com/archives/kernel-team/2017-May/084305.html -- 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/1692580 Title: ATS fix: Fix opal_npu_destroy_context call Status in linux package in Ubuntu: New Bug description: ATS patches, just included in zesty-next, needs another patch to fix a bug: http://patchwork.ozlabs.org/patch/764857/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692580/+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 1690412] Re: powerpc/powernv: Introduce address translation services for Nvlink2
Patches sent to kernel-team mailing list
https://lists.ubuntu.com/archives/kernel-team/2017-May/084107.html
--
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/1690412
Title:
powerpc/powernv: Introduce address translation services for Nvlink2
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Zesty:
New
Bug description:
== Comment: #0 - Breno Leitao - 2017-05-12
11:44:58 ==
Introduce address translation services for Nvlink2
Nvlink2 supports address translation services (ATS) allowing devices
to request address translations from an mmu known as the nest MMU
which is setup to walk the CPU page tables.
abfe802 powerpc/powernv: Require MMU_NOTIFIER to fix NPU build
1ab66d1 powerpc/powernv: Introduce address translation services for Nvlink2
4c3b89e powerpc/powernv: Add sanity checks to pnv_pci_get_{gpu|npu}_dev
2475a2b drivers/of/base.c: Add of_property_read_u64_index
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1690412/+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 1690412] Re: powerpc/powernv: Introduce address translation services for Nvlink2
Yes. This is targeted against 16.04.3 - 4.10 kernel
--
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/1690412
Title:
powerpc/powernv: Introduce address translation services for Nvlink2
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Zesty:
New
Bug description:
== Comment: #0 - Breno Leitao - 2017-05-12
11:44:58 ==
Introduce address translation services for Nvlink2
Nvlink2 supports address translation services (ATS) allowing devices
to request address translations from an mmu known as the nest MMU
which is setup to walk the CPU page tables.
abfe802 powerpc/powernv: Require MMU_NOTIFIER to fix NPU build
1ab66d1 powerpc/powernv: Introduce address translation services for Nvlink2
4c3b89e powerpc/powernv: Add sanity checks to pnv_pci_get_{gpu|npu}_dev
2475a2b drivers/of/base.c: Add of_property_read_u64_index
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1690412/+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 1691477] Re: Hardware transaction memory corruption
Patch sent to kernel-team at https://lists.ubuntu.com/archives/kernel- team/2017-May/084191.html -- 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/1691477 Title: Hardware transaction memory corruption Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: There is a bug on hardware transactional memory on Ubuntu 17.04 that is hard to reproduce but I was able to create a testcase that reproduces it easily: https://github.com/leitao/htm_torture/tree/master/narrow The fix for this problem was already accepted in the kernel https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=f48e91e87e67b56bef63393d1a02c6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1691477/+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 1690225] Re: nvidia-docker on ppc64le-ubuntu16.04 issue due to cross-thread naming if !PR_DUMPABLE
Patch sent upstream at https://lists.ubuntu.com/archives/kernel- team/2017-May/084092.html -- 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/1690225 Title: nvidia-docker on ppc64le-ubuntu16.04 issue due to cross-thread naming if !PR_DUMPABLE Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Breno Henrique Leitao - 2017-05-11 15:30:52 == The PR_DUMPABLE flag causes the pid related paths of the proc file system to be owned by ROOT. The implementation of pthread_set/getname_np however needs access to /proc//task//comm. If PR_DUMPABLE is false this implementation is locked out. This patch installs a special permission function for the file "comm" that grants read and write access to all threads of the same group regardless of the ownership of the inode. For all other threads the function falls back to the generic inode permission check. Nvidia-docker issue on ppc64le: 1b3044e39a89cb1d4d5313da477e8dfea2b5232d This is fixed by commit 1b3044e39a89cb1d4d5313da477e8dfea2b5232d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1690225/+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 1690155] Re: Fix NVLINK2 TCE route
Patch sent to the mailing list: https://lists.ubuntu.com/archives
/kernel-team/2017-May/084069.html
--
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/1690155
Title:
Fix NVLINK2 TCE route
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - Breno Henrique Leitao -
2017-05-11 09:14:17 ==
Commit 616badd2fb49 ("powerpc/powernv: Use OPAL call for TCE kill on
NVLink2") forced all TCE kills to go via the OPAL call for
NVLink2. However the PHB3 implementation of TCE kill was still being
called directly from some functions which in some circumstances caused
a machine check
The following commit was added into zesty using LP#1667081
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1690155/+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 1686519] Re: POWER9: CAPI2 enablement
Send to the kernel-team mailing list: https://lists.ubuntu.com/archives/kernel-team/2017-April/083808.html -- 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/1686519 Title: POWER9: CAPI2 enablement Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Breno Henrique Leitao - 2017-04-26 15:08:18 == Hello, We would like to include CAPI2 support on the CXL device driver on Zesty kernel. The coherent accelerator interface is designed to allow the coherent connection of accelerators (FPGAs and other devices) to a POWER system. These devices need to adhere to the Coherent Accelerator Interface Architecture (CAIA). This PSL Version 9 provides new features such as: * Interaction with the nest MMU on the P9 chip. * Native DMA support. * Supports sending ASB_Notify messages for host thread wakeup. * Supports Atomic operations. == Comment: #3 - Breno Henrique Leitao - 2017-04-26 15:21:25 == These are the patches we need: f24be42aab37c6d07c05126673138e06223a6399 cxl: Add psl9 specific code d7b1946c7925a270062b2e0718aa57b42ba619c0 cxl: Force psl data-cache flush during device shutdown abd1d99bb3da42d6c7341c14986f5b8f4dcc6bd5 cxl: Isolate few psl8 specific calls 64663f372c72cedeba1b1dc86df9cc159ae5a93d cxl: Rename some psl8 specific functions bdd2e7150644fee4de7167a3e08294ef32eeda11 cxl: Update implementation service layer 6dd2d23403396d8e6d153a6c9db56e1a1012bad8 cxl: Keep track of mm struct associated with a context 66ef20c7834b7df18168b12a57ef01c6ae0d1a81 cxl: Remove unused values in bare-metal environment. aba81433b50350fde68bf80fe9f75d671e15b5ae cxl: Read vsec perst load image 39d40871526627fd0e2cfc1e2fb88500a5049c4c cxl: Fix build when CONFIG_DEBUG_FS=n To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1686519/+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 1681429] Re: POWER9: Improve performance on memory management
Send to the mailing list: https://lists.ubuntu.com/archives/kernel-team/2017-April/083554.html -- 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/1681429 Title: POWER9: Improve performance on memory management Status in linux package in Ubuntu: New Bug description: Please include this two patches for POWER9. They are performance patches and can improve up to 10x some workloads. These patches are limited to arch/powerpc only: https://patchwork.ozlabs.org/patch/746016/ https://patchwork.ozlabs.org/patch/746020/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681429/+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 1680888] Re: Disable CONFIG_HVC_UDBG on ppc64el
Sent to the kernel-team mailing list: https://lists.ubuntu.com/archives/kernel-team/2017-April/083534.html -- 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/1680888 Title: Disable CONFIG_HVC_UDBG on ppc64el Status in linux package in Ubuntu: New Bug description: Canonical, Could you please disable CONFIG_HVC_UDBG on ppc64el config? This is not required, and it is causing some extra timing on the TTY device that is causing some racing condition that is still being debugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680888/+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 1675806] Re: POWER9 Radix mode KVM
I just sent the backported patchset to kernel-team mailing list: https://lists.ubuntu.com/archives/kernel-team/2017-March/083299.html -- 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/1675806 Title: POWER9 Radix mode KVM Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: == Comment: #0 - Breno Henrique Leitao - 2017-03-24 10:06:27 == Hi Canonical, We would like to have the KVM Radix patches integrated into 17.04 kernel. This will allow the KVM to support Radix Page mode in the host. This is the patchset: d3918e7fd4a2 Change interrupt call to reduce scratch space use on HV 7ede531773ea Move 64-bit KVM interrupt handler out from alt section a97a65d53d9f 64-bit CONFIG_RELOCATABLE support for interrupts cc3d2940133d Enable use of radix MMU under hypervisor on POWER9 dbcbfee0c81c More definitions for POWER9 ba9b399aee6f Export pgtable_cache and pgtable_cache_add for KVM 16ed141677c5 Make type of partition table flush depend on partition type bc3551257af8 Allow for relocation-on interrupts from guest to host c92701322711 Add userspace interfaces for POWER9 MMU 468808bd35c4 Set process table for HPT guests on POWER9 ef8c640cb9cc Use ASDR for HPT guests on POWER9 9e04ba69beec Add basic infrastructure for radix guests f4c51f841d2a Modify guest entry/exit paths to handle radix guests 5a319350a465 Page table construction and page faults for radix guests 01756099e0a5 MMU notifier callbacks for radix guests 8f7b79b8379a Implement dirty page logging for radix guests 65dae5403a16 Make HPT-specific hypercalls return error in radix mode a29ebeaf5575 Invalidate TLB on radix guest vcpu movement 53af3ba2e819 Allow guest exit path to have MMU on f11f6f79b606 Invalidate ERAT on guest entry/exit for POWER9 DD1 8cf4ecc0ca9b Enable radix guest support 2337d207288f CONFIG_RELOCATABLE support for hmi interrupts ab9bad0ead9a Remove separate entry for OPAL real mode calls 70cd4c10b290 Fix software walk of guest process page tables 4e5acdc23a3d Don't use ASDR for real-mode HPT faults on POWER9 3deda5e50c89 Don't try to signal cpu -1 8464c8842de2 Fix H_PROD to actually wake the target vcpu 5982f0849e08 Fix error return in kvm_vm_ioctl_create_spapr_tce 7a70d7288c92 Invalidate process table caching after setting process table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675806/+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 1675806] Re: POWER9 Radix mode KVM
Hey Tim, No, let me try to create one, otherwise I will ask internal help. I will let you know when I have something better consumable. -- 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/1675806 Title: POWER9 Radix mode KVM Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: == Comment: #0 - Breno Henrique Leitao - 2017-03-24 10:06:27 == Hi Canonical, We would like to have the KVM Radix patches integrated into 17.04 kernel. This will allow the KVM to support Radix Page mode in the host. This is the patchset: d3918e7fd4a2 Change interrupt call to reduce scratch space use on HV 7ede531773ea Move 64-bit KVM interrupt handler out from alt section a97a65d53d9f 64-bit CONFIG_RELOCATABLE support for interrupts cc3d2940133d Enable use of radix MMU under hypervisor on POWER9 dbcbfee0c81c More definitions for POWER9 ba9b399aee6f Export pgtable_cache and pgtable_cache_add for KVM 16ed141677c5 Make type of partition table flush depend on partition type bc3551257af8 Allow for relocation-on interrupts from guest to host c92701322711 Add userspace interfaces for POWER9 MMU 468808bd35c4 Set process table for HPT guests on POWER9 ef8c640cb9cc Use ASDR for HPT guests on POWER9 9e04ba69beec Add basic infrastructure for radix guests f4c51f841d2a Modify guest entry/exit paths to handle radix guests 5a319350a465 Page table construction and page faults for radix guests 01756099e0a5 MMU notifier callbacks for radix guests 8f7b79b8379a Implement dirty page logging for radix guests 65dae5403a16 Make HPT-specific hypercalls return error in radix mode a29ebeaf5575 Invalidate TLB on radix guest vcpu movement 53af3ba2e819 Allow guest exit path to have MMU on f11f6f79b606 Invalidate ERAT on guest entry/exit for POWER9 DD1 8cf4ecc0ca9b Enable radix guest support 2337d207288f CONFIG_RELOCATABLE support for hmi interrupts ab9bad0ead9a Remove separate entry for OPAL real mode calls 70cd4c10b290 Fix software walk of guest process page tables 4e5acdc23a3d Don't use ASDR for real-mode HPT faults on POWER9 3deda5e50c89 Don't try to signal cpu -1 8464c8842de2 Fix H_PROD to actually wake the target vcpu 5982f0849e08 Fix error return in kvm_vm_ioctl_create_spapr_tce 7a70d7288c92 Invalidate process table caching after setting process table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675806/+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 1667081] Re: Nvlink2: Additional patches
Hi Seth, In which yakkety release do you think we will have these patches integrated? Thank you, Breno -- 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/1667081 Title: Nvlink2: Additional patches Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: In Progress Bug description: Hello Canonical, Could you please integrate the patches to enable NVLink2 in Ubuntu? They are, so far: commit 616badd2fb499320d3ac3b54462f55dededd0e0f Author: Alistair Popple Date: Tue Jan 10 15:41:44 2017 +1100 powerpc/powernv: Use OPAL call for TCE kill on NVLink2 Add detection of NPU2 PHBs. NPU2/NVLink2 has a different register layout for the TCE kill register therefore TCE invalidation should be done via the OPAL call rather than using the register directly as it is for PHB3 and NVLink1. This changes TCE invalidation to use the OPAL call in the case of a NPU2 PHB model. commit 1d0761d2557d1540727723e4f05395d53321d555 Author: Alistair Popple Date: Wed Dec 14 13:36:51 2016 +1100 powerpc/powernv: Initialise nest mmu POWER9 contains an off core mmu called the nest mmu (NMMU). This is used by other hardware units on the chip to translate virtual addresses into real addresses. The unit attempting an address translation provides the majority of the context required for the translation request except for the base address of the partition table (ie. the PTCR) which needs to be programmed into the NMMU. This patch adds a call to OPAL to set the PTCR for the nest mmu in opal_init(). These patches are, still, in the powerpc-next tree. == Comment: #2 - Breno Henrique Leitao - 2017-02-22 13:33:59 == In order to support NVLink2, the memory hotplugs should be applied also, they are: 0d0a4bc powerpc/mm: unstub radix__vmemmap_remove_mapping() 4b5d62c powerpc/mm: add radix__remove_section_mapping() 6cc2734 powerpc/mm: add radix__create_section_mapping() b5200ec powerpc/mm: refactor radix physical page mapping 32b53c0 powerpc/mm: Fix memory hotplug BUG() on radix c3352cb dt: add documentation of "hotpluggable" memory property 41a9ada of/fdt: mark hotpluggable memory 114cf3c mm: enable CONFIG_MOVABLE_NODE on non-x86 arches 39fa104 mm: remove x86-only restriction of movable_node 4a3bac4 powerpc/mm: allow memory hotplug into a memoryless node Note that you need to set CONFIG_MOVABLE_NODE=y. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667081/+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 1671169] Re: POWER9: Improve CAS negotiation
Thanks Tim. I tested it on one of my power9 machines, and the kernel solves this issue. -- 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/1671169 Title: POWER9: Improve CAS negotiation Status in linux package in Ubuntu: Fix Committed Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Committed Bug description: Dear Canonical, Could you please add the following patches into Ubuntu 17.04 and 16.04.2 (4.8) ? It improves Virtualization on POWER9. commit 014d02cbf16b3106dc8e93281d2a9c189751ed5e Author: Suraj Jitindar Singh Date: Tue Feb 28 17:03:48 2017 +1100 powerpc: Update to new option-vector-5 format for CAS commit 12cc9fd6b2d8ee307a735b3b9faed0d17b719463 Author: Suraj Jitindar Singh Date: Tue Feb 28 17:03:47 2017 +1100 powerpc: Parse the command line before calling CAS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671169/+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 1670800] Re: Power9 kernel: add virtualization patches
Hi Tim, Thanks for providing this kernel, I tested it on one of our machines, and it is running fine regarding this issue. Thank you! -- 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/1670800 Title: Power9 kernel: add virtualization patches Status in linux package in Ubuntu: Fix Committed Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Committed Bug description: Dear Canonical, Please add the following patches for POWER9: From powerpc/next tree: cc3d2940133d24000e2866b21e03ce32adfead0a - powerpc/64: Enable use of radix MMU under hypervisor on POWER9 6ae3f8ad2017079292cb49c8959b527bcbcbefed - powerpc: Add POWER9 architected mode to cputable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670800/+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 1656908] Re: In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2)
** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- 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/1656908 Title: In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2) Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: Installed Ubuntu17.04 as PowerVM/KVM or NV , after installation every reboot getting message in console Unable to open file: /etc/keys/x509_ima.der (-2) LOG: Booting Linux via __start() @ 0x0a6c ... -> smp_release_cpus() spinning_secondaries = 7 <- smp_release_cpus() [0.663066] Unable to open file: /etc/keys/x509_ima.der (-2)[0.663129] Unable to open file: /etc/keys/x509_evm.der (-2) [0.792300] sd 0:0:1:0: [sda] Assuming drive cache: write through Ubuntu Zesty Zapus (development branch) ubuntu hvc0 ubuntu login: Maybe this was introduced by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643652 ? Will mirror this over to Launchpad for Canonical to review... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656908/+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 1666197] Re: POWER9 : Enable Stop 0-2 with ESL=EC=0
Tim, we would like to target this bug for Yakkety also, please. Thanks, Breno -- 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/1666197 Title: POWER9 : Enable Stop 0-2 with ESL=EC=0 Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: In Linux 4.10-rc8, the implementation to enable the "stop" instruction has the following shortcomings: a) The code hand-codes the values for ESL, EC, TR, MTL bits of PSSCR and uses only the RL field from the firmware. While this is not incorrect, since the hand-coded values are legitimate, it is not a very flexible design since the firmware has the capability to communicate these values via the "ibm,cpu-idle-state-psscr" and "ibm,cpu-idle-state-psscr-mask" properties. In case where the firmware provides values for these fields that is different from the hand-coded values, the current code will not work as intended. b) Due to issue a), the current code assumes that ESL=EC=1 for all the stop states and hence the wakeup from the stop instruction will happen at 0x100, the system-reset vector which also results in GPR state loss. However, the ISA v3.0 allows the ESL=EC=0 behaviour where the corresponding stop-states lose no GPR state and wakes up from the subsequent instruction. The code in 4.10-rc8 doesn't support these light-weight stop modes. The following commits in the "next" branch of the powerpc-linux git tree (git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git) address these issues. These patches are needed in 17.04 to enable light-weight stop modes 1) commit 823b7bd5156a93872d9561b3f033dfe5cb80204e, powernv:idle: Add IDLE_STATE_ENTER_SEQ_NORET macro 2)commit dd34c74c97b6c3ed1ac7caec0b46267142659aff, powernv:stop: Rename pnv_arch300_idle_init to pnv_power9_idle_init 3)commit 9e9fc6f00a54f7064dc681ac187be6498d566a4f, cpuidle:powernv: Add helper function to populate powernv idle states 4)commit 09206b600c76f20984e80d99f3b5343c79332a97, powernv: Pass PSSCR value and mask to power9_idle_stop 5)commit b48ff52043f489d594b989b318c120ca340a2e41, Documentation:powerpc: Add device-tree bindings for power-mgt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666197/+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 1670800] Re: Power9 kernel: add virtualization patches
Thanks Tim. We would like to target all these POWER9 bugs to yakkety also. Do you think it is feasible? -- 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/1670800 Title: Power9 kernel: add virtualization patches Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: Dear Canonical, Please add the following patches for POWER9: From powerpc/next tree: cc3d2940133d24000e2866b21e03ce32adfead0a - powerpc/64: Enable use of radix MMU under hypervisor on POWER9 6ae3f8ad2017079292cb49c8959b527bcbcbefed - powerpc: Add POWER9 architected mode to cputable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670800/+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 1486152] Re: Kernel WARN @ block/genhd.c:352 with ltp block dev tests
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Taco Screen team (taco-screen-team) -- 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/1486152 Title: Kernel WARN @ block/genhd.c:352 with ltp block dev tests Status in linux package in Ubuntu: New Bug description: == Comment: #0 - SACHIN P. SANT - 2015-08-07 08:28:13 == ---Problem Description--- Kernel WARN @ block/genhd.c:352 with ltp block dev tests Contact Information = Sachin Sant / ss...@in.ibm.com ---uname output--- 3.19.0-26-generic Machine Type = POWER8 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1) Install Ubuntu 14.04.03 running bare-metal 2) Install LTP and compile the code 3) run the ltp_block_dev tests The krenel Warning is displayed on the console during the run Stack trace output: [ 175.365323] ltp_block_dev: Test Case Result: PASS [ 175.365547] ltp_block_dev: Test Case 6: register_blkdev() with name="" [ 175.365550] ltp_block_dev: Test Case Result: PASS [ 175.365615] ltp_block_dev: Test Case 7: unregister_blkdev() with major=0 [ 175.365628] [ cut here ] [ 175.365630] WARNING: at /build/linux-lts-vivid-GlOzk5/linux-lts-vivid-3.19.0/block/genhd.c:352 [ 175.365632] Modules linked in: ltp_block_dev(OE) joydev mac_hid hid_generic ofpart ipmi_powernv cmdlinepart ipmi_msghandler powernv_flash mtd opal_prd powernv_rng at24 usbhid hid ast uio_pdrv_genirq syscopyarea uio sysfillrect sysimgblt nouveau ttm drm_kms_helper drm i2c_algo_bit mlx4_en vxlan ip6_udp_tunnel udp_tunnel uas usb_storage bnx2x mlx4_core lpfc ahci libahci scsi_transport_fc mdio libcrc32c [last unloaded: ltp_block_dev] [ 175.365663] CPU: 133 PID: 4832 Comm: block_dev Tainted: GW OE 3.19.0-26-generic #27~14.04.1-Ubuntu [ 175.365666] task: c00fcebc9140 ti: c00fcec1c000 task.ti: c00fcec1c000 [ 175.365669] NIP: c04eb5cc LR: c04eb574 CTR: c04eb520 [ 175.365671] REGS: c00fcec1f940 TRAP: 0700 Tainted: GW OE (3.19.0-26-generic) [ 175.365673] MSR: 90029033 CR: 28000482 XER: 2000 [ 175.365681] CFAR: c04eb59c SOFTE: 1 [ 175.365681] GPR00: c04eb574 c00fcec1fbc0 c144cc00 [ 175.365681] GPR04: d000190b12c8 000d 636f6c62 0001 [ 175.365681] GPR08: c174db10 c174db10 d000190b10d0 [ 175.365681] GPR12: c04eb520 c7baad00 [ 175.365681] GPR16: [ 175.365681] GPR20: 1000a8a8 10020010 1000a8f0 [ 175.365681] GPR24: 1000a918 1000a9b8 00fb 0001 [ 175.365681] GPR28: d000190b12c8 c1379468 [ 175.365712] NIP [c04eb5cc] unregister_blkdev+0xac/0x160 [ 175.365714] LR [c04eb574] unregister_blkdev+0x54/0x160 [ 175.365716] Call Trace: [ 175.365719] [c00fcec1fbc0] [c04eb574] unregister_blkdev+0x54/0x160 (unreliable) [ 175.365723] [c00fcec1fc00] [d000190b063c] sys_tcase+0x41c/0xb30 [ltp_block_dev] [ 175.365728] [c00fcec1fcc0] [c06431f8] dev_attr_store+0x68/0xa0 [ 175.365732] [c00fcec1fd00] [c035ba30] sysfs_kf_write+0x80/0xb0 [ 175.365735] [c00fcec1fd40] [c035a97c] kernfs_fop_write+0x18c/0x1f0 [ 175.365739] [c00fcec1fd90] [c02b488c] vfs_write+0xdc/0x260 [ 175.365743] [c00fcec1fde0] [c02b573c] SyS_write+0x6c/0x110 [ 175.365747] [c00fcec1fe30] [c0009258] system_call+0x38/0xd0 [ 175.365748] Instruction dump: [ 175.365750] 419e0030 80e90008 7f87f000 409e0018 48c0 815f0008 7f8af000 419e0058 [ 175.365756] 7fe9fb78 ebe9 2fbf 409effe8 <0fe0> 7fa3eb78 3be0 48528871 [ 175.365761] ---[ end trace 02836eb1f955a5cd ]--- Oops output: no System Dump Info: The system is not configured to capture a system dump. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486152/+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 1667081] Re: Nvlink2: Additional patches
Hello Seth, we would like to have this fix on 16.04.2 also, is it possible? -- 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/1667081 Title: Nvlink2: Additional patches Status in linux package in Ubuntu: Fix Committed Bug description: Hello Canonical, Could you please integrate the patches to enable NVLink2 in Ubuntu? They are, so far: commit 616badd2fb499320d3ac3b54462f55dededd0e0f Author: Alistair Popple Date: Tue Jan 10 15:41:44 2017 +1100 powerpc/powernv: Use OPAL call for TCE kill on NVLink2 Add detection of NPU2 PHBs. NPU2/NVLink2 has a different register layout for the TCE kill register therefore TCE invalidation should be done via the OPAL call rather than using the register directly as it is for PHB3 and NVLink1. This changes TCE invalidation to use the OPAL call in the case of a NPU2 PHB model. commit 1d0761d2557d1540727723e4f05395d53321d555 Author: Alistair Popple Date: Wed Dec 14 13:36:51 2016 +1100 powerpc/powernv: Initialise nest mmu POWER9 contains an off core mmu called the nest mmu (NMMU). This is used by other hardware units on the chip to translate virtual addresses into real addresses. The unit attempting an address translation provides the majority of the context required for the translation request except for the base address of the partition table (ie. the PTCR) which needs to be programmed into the NMMU. This patch adds a call to OPAL to set the PTCR for the nest mmu in opal_init(). These patches are, still, in the powerpc-next tree. == Comment: #2 - Breno Henrique Leitao - 2017-02-22 13:33:59 == In order to support NVLink2, the memory hotplugs should be applied also, they are: 0d0a4bc powerpc/mm: unstub radix__vmemmap_remove_mapping() 4b5d62c powerpc/mm: add radix__remove_section_mapping() 6cc2734 powerpc/mm: add radix__create_section_mapping() b5200ec powerpc/mm: refactor radix physical page mapping 32b53c0 powerpc/mm: Fix memory hotplug BUG() on radix c3352cb dt: add documentation of "hotpluggable" memory property 41a9ada of/fdt: mark hotpluggable memory 114cf3c mm: enable CONFIG_MOVABLE_NODE on non-x86 arches 39fa104 mm: remove x86-only restriction of movable_node 4a3bac4 powerpc/mm: allow memory hotplug into a memoryless node Note that you need to set CONFIG_MOVABLE_NODE=y. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667081/+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 1664564] Re: 16.04.2: Extra patches for POWER9
Hi, I was able to test the kernel from proposed (4.8.0-40.43). Marking it as verified. Thanks. ** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- 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/1664564 Title: 16.04.2: Extra patches for POWER9 Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: == Comment: #0 - Breno Henrique Leitao - 2017-02-13 18:21:48 == Other than the initial POWER9 patches made integrated in Bug#149921, there are some other patches we need to have integrated into 16.04.2. These patches are also required to boot POWER9. d7df2443cd5f67fc6ee7c05a88e4996e8177f91b powerpc/mm: Fix spurrious segfaults on radix with autonuma There is also. We are still working on getting these upstream: http://patchwork.ozlabs.org/patch/725916/ http://patchwork.ozlabs.org/patch/725917/ http://patchwork.ozlabs.org/patch/725918/ http://patchwork.ozlabs.org/patch/725919/ http://patchwork.ozlabs.org/patch/725920/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664564/+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 1665447] Re: kernel ppa is building amd64 files inside ppc64el package
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Taco Screen team (taco-screen-team) -- 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/1665447 Title: kernel ppa is building amd64 files inside ppc64el package Status in linux package in Ubuntu: Incomplete Bug description: Kernel PPA contains a files that are compiled against amd64 instead of ppc64el. This makes this kernel unusable: Example: PPA: http://kernel.ubuntu.com/~kernel-ppa/mainline/ Kernel: http://kernel.ubuntu.com/\~kernel-ppa/mainline/v4.10-rc8 /linux- headers-4.10.0-041000rc8-generic_4.10.0-041000rc8.201702121731_ppc64el.deb ➜ ppa dpkg-deb -x linux- headers-4.10.0-041000rc8-generic_4.10.0-041000rc8.201702121731_ppc64el.deb . ➜ ppa find . -name fixdep ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep ➜ ppa file ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=438d1c0255e4943c4af1b9568a4cbe83d9034737, not stripped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665447/+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 1665447] [NEW] kernel ppa is building amd64 files inside ppc64el package
Public bug reported: Kernel PPA contains a files that are compiled against amd64 instead of ppc64el. This makes this kernel unusable: Example: PPA: http://kernel.ubuntu.com/~kernel-ppa/mainline/ Kernel: http://kernel.ubuntu.com/\~kernel-ppa/mainline/v4.10-rc8/linux- headers-4.10.0-041000rc8-generic_4.10.0-041000rc8.201702121731_ppc64el.deb ➜ ppa dpkg-deb -x linux- headers-4.10.0-041000rc8-generic_4.10.0-041000rc8.201702121731_ppc64el.deb . ➜ ppa find . -name fixdep ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep ➜ ppa file ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=438d1c0255e4943c4af1b9568a4cbe83d9034737, not stripped ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: Incomplete ** Package changed: luajit (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/1665447 Title: kernel ppa is building amd64 files inside ppc64el package Status in linux package in Ubuntu: Incomplete Bug description: Kernel PPA contains a files that are compiled against amd64 instead of ppc64el. This makes this kernel unusable: Example: PPA: http://kernel.ubuntu.com/~kernel-ppa/mainline/ Kernel: http://kernel.ubuntu.com/\~kernel-ppa/mainline/v4.10-rc8 /linux- headers-4.10.0-041000rc8-generic_4.10.0-041000rc8.201702121731_ppc64el.deb ➜ ppa dpkg-deb -x linux- headers-4.10.0-041000rc8-generic_4.10.0-041000rc8.201702121731_ppc64el.deb . ➜ ppa find . -name fixdep ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep ➜ ppa file ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=438d1c0255e4943c4af1b9568a4cbe83d9034737, not stripped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665447/+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 1656908] Re: In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2)
Unfortunately this message does not seem as a warning, but, as an error. -- 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/1656908 Title: In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2) Status in linux package in Ubuntu: Won't Fix Bug description: Installed Ubuntu17.04 as PowerVM/KVM or NV , after installation every reboot getting message in console Unable to open file: /etc/keys/x509_ima.der (-2) LOG: Booting Linux via __start() @ 0x0a6c ... -> smp_release_cpus() spinning_secondaries = 7 <- smp_release_cpus() [0.663066] Unable to open file: /etc/keys/x509_ima.der (-2)[0.663129] Unable to open file: /etc/keys/x509_evm.der (-2) [0.792300] sd 0:0:1:0: [sda] Assuming drive cache: write through Ubuntu Zesty Zapus (development branch) ubuntu hvc0 ubuntu login: Maybe this was introduced by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643652 ? Will mirror this over to Launchpad for Canonical to review... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656908/+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 1655002] Re: Move some kernel modules to the main kernel package (part 2)
I just run a sniff test, and all the major modules seem to be included in the linux-image-4.4.0-63-generic package. -- 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/1655002 Title: Move some kernel modules to the main kernel package (part 2) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: Hello Canonical, there are important kernel modules that are required on POWER systems, and they are currently on the linux-image-extra packages. So, in this case, every Power system needs to install the -extra package, which makes the -extra package required. Our suggestion is to add these important modules to the main kernel package, so we do not require the installation of the -extra package. One round of additions was already completed. But we verified some modules we need were missing, so we are hereby requesting a 2nd round of module additions to linux-image main package of Xenial and Yakkety (and all future releases). The list is: (AST stack) 1. ast 2. i2c-core 3. sysfillrect 4. syscopyarea 5. sysimgblt 6. fb_sys_fops 7. drm 8. drm_kms_helper 9. ttm 10. i2c-algo-bit 11. kvm 12. kvm_pr 13. kvm_hv 14. vmx_crypto 15. at24 16. nvmem_core 17. cmdlinepart 18. input_leds 19. uio 20. uio_pdrv_genirq 21. ofpart (USB stack) 22. usb_storage 23. uas 24. hid 25. hid_generic 26. usbhid Thanks in advance, Guilherme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655002/+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 1655041] Re: Xenial update to v4.4.41 stable release
Hello, Any idea when the kernel with this fix will be made available? Thanks -- 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/1655041 Title: Xenial update to v4.4.41 stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.4.41 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.4.41 stable release shall be applied: ssb: Fix error routine when fallback SPROM fails rtlwifi: Fix enter/exit power_save cfg80211/mac80211: fix BSS leaks when abandoning assoc attempts ath9k: Really fix LED polarity for some Mini PCI AR9220 MB92 cards. mmc: sdhci: Fix recovery from tuning timeout regulator: stw481x-vmmc: fix ages old enable error timekeeping_Force_unsigned_clocksource_to_nanoseconds_conversion clk: bcm2835: Avoid overwriting the div info when disabling a pll_div clk thermal: hwmon: Properly report critical temperature in sysfs staging: comedi: ni_mio_common: fix M Series ni_ai_insn_read() data mask staging: comedi: ni_mio_common: fix E series ni_ai_insn_read() data ACPI / video: Add force_native quirk for Dell XPS 17 L702X ACPI / video: Add force_native quirk for HP Pavilion dv6 drm/nouveau/kms: lvds panel strap moved again on maxwell drm/nouveau/bios: require checksum to match for fast acpi shadow method drm/nouveau/ltc: protect clearing of comptags with mutex drm/nouveau/fifo/gf100-: protect channel preempt with subdev mutex drm/nouveau/i2c/gk110b,gm10x: use the correct implementation drm/radeon: Also call cursor_move_locked when the cursor size changes drm/radeon: Hide the HW cursor while it's out of bounds drm/radeon: add additional pci revision to dpm workaround drm/gma500: Add compat ioctl drivers/gpu/drm/ast: Fix infinite loop if read fails mei: request async autosuspend at the end of enumeration block: protect iterate_bdevs() against concurrent close vt: fix Scroll Lock LED trigger name scsi: megaraid_sas: For SRIOV enabled firmware, ensure VF driver waits for 30secs before reset scsi: megaraid_sas: Do not set MPI2_TYPE_CUDA for JBOD FP path for FW which does not support JBOD sequence map scsi: zfcp: fix use-after-"free" in FC ingress path after TMF scsi: zfcp: do not trace pure benign residual HBA responses at default level scsi: zfcp: fix rport unblock race with LUN recovery scsi: avoid a permanent stop of the scsi device's request queue ARC: mm: arc700: Don't assume 2 colours for aliasing VIPT dcache firmware: fix usermode helper fallback loading s390/vmlogrdr: fix IUCV buffer allocation sc16is7xx: Drop bogus use of IRQF_ONESHOT md/raid5: limit request size according to implementation limits KVM: PPC: Book3S HV: Save/restore XER in checkpointed register state KVM: PPC: Book3S HV: Don't lose hardware R/C bit updates in H_PROTECT kvm: nVMX: Allow L1 to intercept software exceptions (#BP and #OF) platform/x86: asus-nb-wmi.c: Add X45U quirk fgraph: Handle a case where a tracer ignores set_graph_notrace IB/mad: Fix an array index check IPoIB: Avoid reading an uninitialized member variable IB/multicast: Check ib_find_pkey() return value IB/cma: Fix a race condition in iboe_addr_get_sgid() media: solo6x10: fix lockup by avoiding delayed register write Input: drv260x - fix input device's parent assignment PCI: Check for PME in targeted sleep state libceph: verify authorize reply on connect nfs_write_end(): fix handling of short copies powerpc/ps3: Fix system hang with GCC 5 builds powerpc: Convert cmp to cmpd in idle enter sequence kconfig/nconf: Fix hang when editing symbol with a long prompt sg_write()/bsg_write() is not fit to be called under KERNEL_DS net: mvpp2: fix dma unmapping of TX buffers for fragments Linux 4.4.41 The following commit was skipped as it was already applied to master- next: ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short jumps to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655041/+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 1656288] Re: Corruption of XER upon a Transaction Failure (Transactional Memory)
We would like to have this fix on both 16.04.2 (4.8) and 16.04.1 (4.4).
In fact, this patch is already in the 4.4 stable tree.
--
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/1656288
Title:
Corruption of XER upon a Transaction Failure (Transactional Memory)
Status in linux package in Ubuntu:
New
Bug description:
Corruption of XER upon a Transaction Failure (Transactional Memory)
Upon a transaction failure the XER register is not being changed back
to the value that should be in the transaction's register checkpoint.
This is occurring when the transaction has been failed in hypervisor
mode.
This require the following commit-id: 0d808df06a44 ("KVM: PPC: Book3S
HV: Save/restore XER in checkpointed register state", 2016-11-07)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656288/+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 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
Hi Mike, In the logs, it seems that you have SMT enabled. KVM does not work with SMT enabled on ppc64el. Would you mind running with SMT=off and rerun and posting the new logs, please? In order to disable SMT, please run: # ppc64_cpu --smt=off -- 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/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https
[Kernel-packages] [Bug 1655379] Re: Bug fixes for IBM VNIC Driver
** Attachment added: "generic.inclusion-list.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655379/+attachment/4802923/+files/generic.inclusion-list.log -- 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/1655379 Title: Bug fixes for IBM VNIC Driver Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: In order to bring the VNIC driver up to date and pull in fixes for all of the bugs we have seen we would need to have the following patches applied. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=12608c260d2fe36746508cb4fa20b6e9a5f9c241 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=87737f8810db445db171ca81ca4cc43bd5b067ce https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=d894be57ca92c8a8819ab544d550809e8731137b https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=9888d7b02c7793cbbcbdd05dd9e14cc0e78d1db7 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=8bf371e6adff29758cc3c57c17df4486513081f8 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=6dbcd8fb5968fda3a5fba019dfb0c80c3139627b https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=b7f193da17fb18b752bef77ce52eb49723299bd8 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=e1fac0adf0f9b2c1eb49e658e6ed070a744bbaef I created a tree based on 16.04.2 kernel and included these commits. https://github.com/leitao/ubuntu-yakkety/tree/vnic I will be generating kernel binaries, so, we can test it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655379/+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 1655379] Re: Bug fixes for IBM VNIC Driver
In Fact, I am not able to find anything useful in these files, other than the error. Take a look ** Attachment added: "generic.depmod.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655379/+attachment/4802922/+files/generic.depmod.log -- 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/1655379 Title: Bug fixes for IBM VNIC Driver Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: In order to bring the VNIC driver up to date and pull in fixes for all of the bugs we have seen we would need to have the following patches applied. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=12608c260d2fe36746508cb4fa20b6e9a5f9c241 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=87737f8810db445db171ca81ca4cc43bd5b067ce https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=d894be57ca92c8a8819ab544d550809e8731137b https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=9888d7b02c7793cbbcbdd05dd9e14cc0e78d1db7 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=8bf371e6adff29758cc3c57c17df4486513081f8 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=6dbcd8fb5968fda3a5fba019dfb0c80c3139627b https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=b7f193da17fb18b752bef77ce52eb49723299bd8 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=e1fac0adf0f9b2c1eb49e658e6ed070a744bbaef I created a tree based on 16.04.2 kernel and included these commits. https://github.com/leitao/ubuntu-yakkety/tree/vnic I will be generating kernel binaries, so, we can test it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655379/+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 1655379] Re: Bug fixes for IBM VNIC Driver
Thanks Tim. I did the backport to generate a internal kernel image to let the testers use it. I will regenerate using your branch. By the way, when I am compiling this kernel on 16.04 using[1], I am facing the following error: "EE: Unresolved module dependencies in base package!". Have you ever seen this? [1] DEB_BUILD_OPTIONS=parallel=20 AUTOBUILD=1 NOEXTRAS=1 skipabi=true fakeroot debian/rules binary" -- 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/1655379 Title: Bug fixes for IBM VNIC Driver Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: In order to bring the VNIC driver up to date and pull in fixes for all of the bugs we have seen we would need to have the following patches applied. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=12608c260d2fe36746508cb4fa20b6e9a5f9c241 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=87737f8810db445db171ca81ca4cc43bd5b067ce https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=d894be57ca92c8a8819ab544d550809e8731137b https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=9888d7b02c7793cbbcbdd05dd9e14cc0e78d1db7 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=8bf371e6adff29758cc3c57c17df4486513081f8 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=6dbcd8fb5968fda3a5fba019dfb0c80c3139627b https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=b7f193da17fb18b752bef77ce52eb49723299bd8 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3&id=e1fac0adf0f9b2c1eb49e658e6ed070a744bbaef I created a tree based on 16.04.2 kernel and included these commits. https://github.com/leitao/ubuntu-yakkety/tree/vnic I will be generating kernel binaries, so, we can test it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655379/+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 1634129] Re: Couldn't emulate instruction 0x7813427c
Tim, I think that the other commit is: https://patchwork.kernel.org/patch/9121881/ It seems to be commit-id 708e75a3ee750dce1072134e630d66c4e6eaf63c -- 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/1634129 Title: Couldn't emulate instruction 0x7813427c Status in linux package in Ubuntu: New Bug description: Couldn't emulate instruction 0x7813427c --- Cannot boot nested VMs in Xenial or Yakkety w/ kvm accel. It worked until Vivid (in spite of not being possible in x86) TCG mode works fine, but very slow. TCG full emulation is the mode in the x86 world for nested virt. However, in Power, we've been using in OpenStack CI w/ kvm accel (native virtualization) to speed up 2nd level VMs. It worked until Vivid. Is the case that kvm accel isn't possible anymore for nested virt (aligned with x86 KVM) ? So full emulation TCG mode is the only possible mode in newer kernels ? qemu-system-ppc64le -machine pseries,accel=kvm,usb=off -m 1G -enable- kvm -cpu POWER8E -display none -nographic cirros-d161007-ppc64le- disk.img lsmod |grep kvm kvm_pr 96452 1 kvm 152984 4 kvm_pr Nested VM console: OF stdout device is: /vdevice/vty@7100 Preparing to boot Linux version 4.4.0-28-generic (buildd@bos01-ppc64el-018) (gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #47-Ubuntu SMP Fri Jun 24 10:09:20 UTC 2016 (Ubuntu 4.4.0-28.47-generic 4.4.13) Detected machine type: 0101 Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done command line: BOOT_IMAGE=/boot/vmlinux-4.4.0-28-generic LABEL=cirros-rootfs ro memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0421 alloc_top: 1000 alloc_top_hi : 4000 rmo_top : 1000 ram_top : 4000 found display : /pci@8002000/vga@0, opening... done instantiating rtas at 0x0daf... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0422 -> 0x04220aa9 Device tree struct 0x0423 -> 0x0424 Quiescing Open Firmware ... Booting Linux via __start() ? /var/log/syslog & /var/log/kern.log Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.186975] kvmppc_handle_exit_pr: emulation at 700 failed (7813427c) Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187023] Couldn't emulate instruction 0x7813427c (op 30 xop 318) Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187066] kvmppc_handle_exit_pr: emulation at 700 failed (7813427c) Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187113] Couldn't emulate instruction 0x7813427c (op 30 xop 318) Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187156] kvmppc_handle_exit_pr: emulation at 700 failed (7813427c) Host: cpu : POWER8E (raw), altivec supported clock : 3690.00MHz revision : 2.1 (pvr 004b 0201) timebase : 51200 platform : PowerNV model : 8247-22L machine : PowerNV 8247-22L firmware : OPAL v3 Guest: Xenial or Yakkety Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety Nested VM: CirrOS http://download.cirros-cloud.net/daily/20161007/cirros-d161007-ppc64le-disk.img This seems to be related https://patchwork.kernel.org/patch/9121881/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634129/+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 1560482] Re: perf: 24x7: Eliminate domain name suffix in event names
Hello Leann, Do you have any update on this bug? -- 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/1560482 Title: perf: 24x7: Eliminate domain name suffix in event names Status in linux package in Ubuntu: Triaged Bug description: Events in the 24x7 counters can belong to different domains like core, chip, virtual CPU home core, etc. To monitor an event, the user must specify the required parameters for the event, which include its name, the chip/core on which to monitor the event as well as the domain. Currently the event is specified to the perf tool as: 'hv_24x7/HPM_0THRD_NON_IDLE_CCYC__PHYS_CORE,core=1/' \ where the event name is 'HPM_0THRD_NON_IDLE_CCYC', the suffix '__PHYS_CORE' specifies the domain, and 'core=1' specifies the core. This is inconsistent in that one parameter is specified as a suffix and the other in a parameter=value format. To simplify the usage, we can eliminate the suffix and let the user specify the domain also in the param=value format. While the domain indices are "well known" or nearly fixed in value, we could display the domain indices in sysfs as a reference for the users: $ cat /sys/bus/event_source/devices/hv_24x7/interface/domains 1: Physical Chip 2: Physical Core 3: VCPU Home Core 4: VCPU Home Chip 5: VCPU Home Node 6: VCPU Remote Node Using these the perf event can now be identified as hv_24x7/HPM_0THRD_NON_IDLE_CCYC,domain=2,core=1 . This feature is implemented by the following commits which have now been merged into mainline: d34171e: powerpc/perf/hv-24x7: Display domain indices in sysfs 8f69dc7: powerpc/perf/24x7: Eliminate domain suffix in event names == Comment: #1 - Sukadev Bhattiprolu - 2016-03-21 15:26:33 == Following two upstream commits are also related 24x7 and could be included in this feature: e5a5886: powerpc/perf/hv-24x7: Fix usage with chip events. 2b206ee: powerpc/perf/hv-24x7: Display change in counter values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1560482/+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 1650263] Re: [16.04.2] POWER9 patches on top of 4.8
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1650263 Title: [16.04.2] POWER9 patches on top of 4.8 Status in linux package in Ubuntu: Confirmed Bug description: This is a Ubuntu 16.04.2 feature to track the inclusions of POWER9 patches on top of kernel 4.8. Ubuntu 16.04.2 is based on kernel 4.8[1], and we want to add support for POWER9 on this kernel. In order to do so, we will need to cherry- pick important patches. What are the commit ids for these patches? Once we have the first batch of commit-ids, we will get this feature mirrored to Canonical. [1] git://kernel.ubuntu.com/ubuntu/ubuntu-yakkety.git Canonical, this is a place holder at this moment. We will start to put the commits that would be required soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650263/+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 1642228] Re: Move some kernel modules to the main kernel package
Thanks for having this fixed. In the meantime, we found some other important modules that are necessary for ppc64el, thus, we would like to include it on the main kernel package also (other than on -extra). We will open a new bug with these new modules. -- 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/1642228 Title: Move some kernel modules to the main kernel package Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: == Comment: #0 - Breno Henrique Leitao - 2016-10-20 08:51:24 == Hello Canonical, There are important kernel modules that are required on POWER systems, and they are currently on the linux-image-extra packages. So, in this case, every Power system needs to install the -extra package, which makes the -extra package required. My suggestion is to add these important modules to the main archive, so, we do not require the installation of the -extra package. We are working on the full list of packages, but I would like to anticipate these modules: 01. lpfc 02. qla2xxx 03. be2net 04. bnx2x 05. i40e 06. igb 07. ixgbe 08. cxl 09. cxlflash 10. jsm 11. ohci-platform 12. xhci 13. aacraid 14. ipr 15. megaraid_sas 16. mpt3sas 17. powernv-rng 18. ipmi_powernv 19. leds-powernv 20. ibmpowernv 21. opal-prd 22. powernv_flash 23. nx-compress-powernv 24. vfio (all modules: vfio.ko, vfio-pci.ko, vfio_iommu_spapr_tce.ko, vfio_virqfd.ko, vfio_spapr_eeh.ko) *Notice* The driver "qlge" is presented in the preliminary list but it's not necessary. Thanks in advance, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642228/+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 1650263] Re: [16.04.2] POWER9 patches on top of 4.8
** 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/1650263 Title: [16.04.2] POWER9 patches on top of 4.8 Status in linux package in Ubuntu: Incomplete Bug description: This is a Ubuntu 16.04.2 feature to track the inclusions of POWER9 patches on top of kernel 4.8. Ubuntu 16.04.2 is based on kernel 4.8[1], and we want to add support for POWER9 on this kernel. In order to do so, we will need to cherry- pick important patches. What are the commit ids for these patches? Once we have the first batch of commit-ids, we will get this feature mirrored to Canonical. [1] git://kernel.ubuntu.com/ubuntu/ubuntu-yakkety.git Canonical, this is a place holder at this moment. We will start to put the commits that would be required soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650263/+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 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build
Hi Canonical, any update on this bug? It is an important fix for 14.04 IMO -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1607894 Title: Unable to analyse vmcore/dump via crash due to bad kernel debug info build Status in crash package in Ubuntu: New Bug description: == Comment: #0 - NAVEED A. UPPINANGADY SALIH - 2016-07-01 02:41:07 == ---Problem Description--- Unable to analyse vmcore/kernel dumpfile generated by 4.4.0-29-generic kernel with ddeb kernel debuginfo available in http://ddebs.ubuntu.com/pool/main/l/linux/ http://ddebs.ubuntu.com/pool/main/l/linux/linux-image-4.4.0-29-generic-dbgsym_4.4.0-29.48_ppc64el.ddeb ---uname output--- 4.4.0-29-generic #48~14.04.1-Ubuntu SMP Wed Jun 29 19:55:03 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = model : 8247-22L machine : PowerNV 8247-22L ---Steps to Reproduce--- # crash /usr/lib/debug/boot/vmlinux-4.4.0-29-generic /var/crash/201606300840/dump.201606300840 crash 7.0.3 ... This GDB was configured as "powerpc64le-unknown-linux-gnu"... crash: invalid kernel virtual address: 61c2555c09c17994 type: "possible" WARNING: cannot read cpu_possible_map crash: invalid kernel virtual address: 8a0f6ddee20c4116 type: "present" WARNING: cannot read cpu_present_map crash: invalid kernel virtual address: 5a09344e320a1886 type: "online" WARNING: cannot read cpu_online_map WARNING: cannot read linux_banner string crash: /usr/lib/debug/boot/vmlinux-4.4.0-29-generic and /var/crash/201606300840/dump.201606300840 do not match! Userspace rpm: linux-image-4.4.0-29-generic- dbgsym_4.4.0-29.48_ppc64el.ddeb == Comment: #5 - Naresh Bannoth - 2016-07-27 04:12:09 == The Latest kernel I am having is as follows root@ltcalpine-lp6:~# uname -a Linux ltcalpine-lp6 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:03:56 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@ltcalpine-lp6:~# >>> the issue same as posted originally. ... This GDB was configured as "powerpc64le-unknown-linux-gnu"... crash: invalid kernel virtual address: 61c2555c09c17994 type: "possible" WARNING: cannot read cpu_possible_map crash: invalid kernel virtual address: 8a0f6ddee20c4116 type: "present" WARNING: cannot read cpu_present_map crash: invalid kernel virtual address: 5a09344e320a1886 type: "online" WARNING: cannot read cpu_online_map WARNING: cannot read linux_banner string crash: /usr/lib/debug/boot/vmlinux-4.4.0-31-generic and /var/crash/201607270248/dump.201607270248 do not match! == Comment: #6 - Hari Krishna Bathini - 2016-07-28 11:49:31 == The kernel is compiled with gcc version 4.8.4 while the vmlinux pulled from http://ddebs.ubuntu.com/pool/main/l/linux/ is compiled with gcc version 5.3.1 which is the source of the issue. Resolved this by pulling the kernel debug symbols package from: deb http://ddebs.ubuntu.com/ -updates main which indeed has the vmlinux compiled with gcc version 4.8.4. But I got this error: crash: invalid structure member offset: module_num_symtab FILE: kernel.c LINE: 3049 FUNCTION: module_init() after the update owning to couple of missing patches listed below: commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61 Author: Dave Anderson Date: Wed Jan 20 09:56:36 2016 -0500 Fix for the changes made to the kernel module structure introduced by this kernel commit for Linux 4.5 and later kernels: commit 7523e4dc5057e157212b4741abd6256e03404cf1 module: use a structure to encapsulate layout. Without the patch, the crash session fails during initialization with the error message: "crash: invalid structure member offset: module_init_text_size". (seb...@linux.vnet.ibm.com) commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66 Author: Dave Anderson Date: Fri Feb 12 14:32:53 2016 -0500 Fix for the changes made to the kernel module structure introduced by this kernel commit for Linux 4.5 and later kernels: commit 8244062ef1e54502ef55f54cced659913f244c3e modules: fix longstanding /proc/kallsyms vs module insertion race. Without the patch, the crash session fails during initialization with the error message: "crash: invalid structure member offset: module_num_symtab". (ander...@redhat.com) Applying the above patches on top of crash tool version 7.0.3-3ubuntu4.4, was able to analyze the dump. The patches apply cleanly.. Thanks Hari == Comment: #8 - Naresh Bannoth - 2016-07-29 06:59:23 == Verified with 4.4.0-31-generic kernel. on Applying the patches mentioned in the #C 6, it is working fine. I took the Compiled Binary attached in the BUG and able to analyse the Dumpfile without any issues. Thanks Naresh == Comment: #9 - Hari Kr
[Kernel-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown
Kernel 4.8 just make 16.04 proposed repository. Does it happen on Ubuntu 16.04 with kernel 4.8? -- 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/1616107 Title: Kernel oops + system freeze on network-bridge shutdown Status in bridge-utils package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in bridge-utils source package in Xenial: Confirmed Status in linux source package in Xenial: Confirmed Status in bridge-utils source package in Yakkety: Confirmed Bug description: A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver. This error does not appear in Ubuntu 14.04 however. The error is reproducible whenever issuing the commands "shutdown", "service networking stop" or "brctl delbr br0". Manually creating the bridge and subsequently bringing it down results in the same error. /var/log/kern.log: [...] Aug 23 15:09:46 base1 kernel: [ 617.996677] device ens1f0 left promiscuous mode Aug 23 15:09:46 base1 kernel: [ 617.996699] br0: port 1(ens1f0) entered disabled state Aug 23 15:09:46 base1 kernel: [ 617.996730] BUG: unable to handle kernel NULL pointer dereference at 00d2 Aug 23 15:09:46 base1 kernel: [ 618.008306] IP: [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.020549] PGD 10374c0067 PUD 1033927067 PMD 0 Aug 23 15:09:46 base1 kernel: [ 618.032773] Oops: 0002 [#1] SMP Aug 23 15:09:46 base1 kernel: [ 618.044434] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio libcrc32c wmi fjes Aug 23 15:09:46 base1 kernel: [ 618.058563] CPU: 3 PID: 4049 Comm: brctl Not tainted 4.4.0-34-generic #53-Ubuntu Aug 23 15:09:46 base1 kernel: [ 618.058564] Hardware name: HP ProLiant DL120 Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016 Aug 23 15:09:46 base1 kernel: [ 618.058574] task: 881030676040 ti: 8810341e4000 task.ti: 8810341e4000 Aug 23 15:09:46 base1 kernel: [ 618.058576] RIP: 0010:[] [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058754] RSP: 0018:8810341e7d68 EFLAGS: 00010206 Aug 23 15:09:46 base1 kernel: [ 618.058769] RAX: RBX: RCX: Aug 23 15:09:46 base1 kernel: [ 618.058774] RDX: 881038470848 RSI: RDI: Aug 23 15:09:46 base1 kernel: [ 618.058775] RBP: 8810341e7d78 R08: R09: 8170d949 Aug 23 15:09:46 base1 kernel: [ 618.058776] R10: ead61340 R11: 8810329d2c00 R12: 00c0 Aug 23 15:09:46 base1 kernel: [ 618.058777] R13: 881030044000 R14: 881038470840 R15: Aug 23 15:09:46 base1 kernel: [ 618.058782] FS: 7f9aebc94700() GS:88107fcc() knlGS: Aug 23 15:09:46 base1 kernel: [ 618.058789] CS: 0010 DS: ES: CR0: 80050033 Aug 23 15:09:46 base1 kernel: [ 618.058790] CR2: 00d2 CR3: 00102fe83000 CR4: 001406e0 Aug 23 15:09:46 base1 kernel: [ 618.058802] Stack: Aug 23 15:09:46 base1 kernel: [ 618.058806] 8810356a4c00 8810341e7d98 c0489258 Aug 23 15:09:46 base1 kernel: [ 618.058822] 8810356a4c00 881038470840 8810341e7dc0 c0479bd8 Aug 23 15:09:46 base1 kernel: [ 618.058825] 881038470838 881038470848 88103847 8810341e7df8 Aug 23 15:09:46 base1 kernel: [ 618.058827] Call Trace: Aug 23 15:09:46 base1 kernel: [ 618.058863] [] nbp_vlan_flush+0x28/0x65 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058870] [] del_nbp+0x98/0x130 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058889] [] br_dev_delete+0x42/0xb0 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058895] [] br_del_bridge+0x4a/0x70 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058911] [] br_ioctl_deviceless_stub+0x153/0x230 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058984] [] ? security_file_alloc+0x33/0x50 Aug 23 15:09:46 base1 kernel: [ 618.059095] [] sock_ioctl+0x215/0x290 Aug 23 15:09:46 base1 kernel: [ 618.059121] [] do_vfs_ioctl+0x29f/0x490 Aug 23 15:09:46 base1 kerne
[Kernel-packages] [Bug 1636330] Re: guest experiencing Transmit Timeouts on CX4
Was the attached patch accepted upstream? -- 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/1636330 Title: guest experiencing Transmit Timeouts on CX4 Status in linux package in Ubuntu: New Bug description: This patch fixes a race condition that was reintroduced in the 4.8 kernel, as part of the P9 changes, after having been originally fixed in 3.19. The effect of the race condition is that a secondary thread can start trying to execute code from the guest while the thread is still in hypervisor mode, so it can cause many different symptoms, one of which seems to be the timebase corruption that leads to the lockup in ktime_get_ts64. It could cause other problems such as CPU cores locking up hard or memory corruption. This patch is only needed on the host. It should be applied to any 4.8 kernel being used as a host, including the Ubuntu 16.10 kernel. Hi Paul I built a kernel with your patch and put at the host and in the guest. I can still see some ktime_get_ts64 at the host. The guest dmesg is clean. This patch fixes another race condition I found in the fastsleep code. Please apply this patch as well and test. Sure will do and provide feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636330/+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 1632045] Re: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA
** Summary changed: - Host OS slowly runs out of available memory after running UbuntuKVM Guest Create/Destroy loop #59 + KVM: PPC: Book3S HV: Migrate pinned pages out of CMA ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Taco Screen team (taco-screen-team) -- 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/1632045 Title: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA Status in linux package in Ubuntu: New Bug description: ---Problem Description--- https://github.com/open-power/supermicro-openpower/issues/59 SW/HW Configuration PNOR image version: 5/3/2016 BMC image version: 0.25 CPLD Version: B2.81.01 Host OS version: Ubuntu 16.04 LTS UbuntuKVM Guest OS version: Ubuntu 14.04.4 LTS HTX version: 394 Processor: 00UL865 * 2 Memory: SK hynix 16GB 2Rx4 PC4-2133P * 16 Summary of Issue Two UbuntuKVM guests are each configured with 8 processors, 64 GB of memory, 1 disk of 128 GB, 1 network interface, and 1 GPU (pass- through'd from the Host OS's K80). The two guests are each put into a Create/Destroy loop, with HTX running on each of the guests (NOT HOST) in between its creation and destruction. The mdt.bu profile is used, and the processors, memory, and the GPU are put under load. The HTX session lasts 9 minutes. While this is running, the amount of available memory (free memory) in the Host OS will slowly decrease, and this can continue until the point wherein there's no more free memory for the Host OS to do anything, including creating the two VM guests. It seems to be that after every cycle, a small portion of the memory that was allocated to the VM guest does not get released back to the Host OS, and eventually, this can and will add up to take up all the available memory in the Host OS. At some point, the VM guest(s) might get disconnected and will display the following error: error: Disconnected from qemu:///system due to I/O error error: One or more references were leaked after disconnect from the hypervisor Then, when the Host OS tries to start the VM guest again, the following error shows up: error: Failed to create domain from guest2_trusty.xml error: internal error: early end of file from monitor, possible problem: Unexpected error in spapr_alloc_htab() at /build/qemu-c3ZrbA/qemu-2.5+dfsg/hw/ppc/spapr.c:1030: 2016-05-23T16:18:16.871549Z qemu-system-ppc64: Failed to allocate HTAB of requested size, try with smaller maxmem The Host OS syslog, as seen HERE, also contains quite some errors. To just list a few: May 13 20:27:44 191-136 kernel: [36827.151228] alloc_contig_range: [3fb800, 3fd8f8) PFNs busy May 13 20:27:44 191-136 kernel: [36827.151291] alloc_contig_range: [3fb800, 3fd8fc) PFNs busy May 13 20:27:44 191-136 libvirtd[19263]: *** Error in `/usr/sbin/libvirtd': realloc(): invalid next size: 0x01000a780400 *** May 13 20:27:44 191-136 libvirtd[19263]: === Backtrace: = May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x8720c)[0x3fffaf6a720c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x96f70)[0x3fffaf6b6f70] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(realloc+0x16c)[0x3fffaf6b87fc] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virReallocN+0x68)[0x3fffaf90ccc8] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0x8ef6c)[0x3fff9346ef6c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0xa826c)[0x3fff9348826c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventPollRunOnce+0x8b4)[0x3fffaf9332b4] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventRunDefaultImpl+0x54)[0x3fffaf931334] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virNetDaemonRun+0x1f0)[0x3fffafad2f70] May 13 20:27:44 191-136 libvirtd[19263]: /usr/sbin/libvirtd(+0x15d74)[0x52e45d74] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x2319c)[0x3fffaf64319c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xb8)[0x3fffaf6433b8] May 13 20:27:44 191-136 libvirtd[19263]: === Memory map: May 13 20:27:44 191-136 libvirtd[19263]: 52e3-52eb r-xp 08:02 65540510 /usr/sbin/libvirtd May 13 20:27:44 191-136 libvirtd[19263]: 52ec-52ed r--p 0008 08:02 65540510 /usr/sbin/libvirtd May 13 20:27:44 191-136 libvirtd[19263]: 52ed-52ee rw-p 0009 08:02 65540510 /usr/sbin/libvirtd M
[Kernel-packages] [Bug 1632466] Re: STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on ubuntu 16.04 guest.
This bug is duplicate of LP #1632462 -- 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/1632466 Title: STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on ubuntu 16.04 guest. Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Application Cdeadmin - 2016-07-26 11:20:20 == == Comment: #1 - Application Cdeadmin - 2016-07-26 11:20:22 == State: Open by: panico on 25 July 2016 18:02:09 Contact Information: Defect Originator: Michael Panico Defect Originator pan...@us.ibm.com Backup: Deepti Umarani Backup ST ID: Deepti S Umarani/India/IBM System Info: Machine Type:8284-22A Card Type:...FSP2_P8LE Current Boot Side:...T Next Boot Side:..T PT_Swap:.1 Current Side Driver:.fips860/b0713a_1630.860 Ubuntu KVM Host: root@iaos1:/tmp# uname -a Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@iaos1:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Codename: yakkety Ubuntu Guest: [htx@iap03] [1m/usr/lpp/htx/bin# [0m uname -a Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux [htx@iap03] [1m/usr/lpp/htx/bin# [0m lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial HTX level on ubuntu 16.04 guest: [htx@iap03] [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu ii htxubuntu 402 ppc64el Problem Description: Running networks (via bridging) on three different guests (other linux, ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on the austin adapter and the shinerT adapter. The shinerT ran for 24 hours and the austin for 72 hours before logging miscompares. From /tmp/htxerr: [htx@iap03] [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr /dev/enp0s6 Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom R(102.1.2.20.50854) connected to W(102.1.1.20.39073) Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 51082 Miscompare at displacement (decimal) = 23876 wbuf = rbuf = For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531 Consecutive prior good reads= 70739865, good bytes read= 2868570843930 /dev/enp0s6 Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom Shutting down testing due to error flag - 1 R(102.1.2.20.50854) connected to W(102.1.1.20.39073) For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531 Consecutive prior good reads=0, good bytes read= 0 /dev/enp0s7 Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom W(102.1.1.20.39073) connected to R(102.1.2.20.50854) Wrote 878 characters, expected 963 Write failed - Connection reset by peer. For stanza 1, TCP connection, bufmin=3, bufmax=2869, bufinc=94 Consecutive prior good writes= 25459432, good bytes written= 35283290616 htx_messages Jul 23 14:29:01 2016 err= sev=1 hxssup hxecom HE program for enp0s6 terminated by exit(0) call. htx_messages Jul 23 16:29:07 2016 err= sev=4 hang_monitor hxecom for enp0s7 is HUNG! Max run time (set in mdt) = 7200 seconds. Current elasped time = 7206 seconds. htx_messages Jul 23 18:29:07 2016 err= sev=4 hang_monitor hxecom for enp0s7 is HUNG! Max run time (set in mdt) = 7200 seconds. Current elasped time = 14406 seconds. htx_messages Jul 23 20:29:07 2016 err= sev=4 hang_monitor hxecom for enp0s7 is HUNG! Max run time (set in mdt) = 7200 seconds. Current elasped time = 21606 seconds. htx_messages Jul 23 22:29:08 2016 err= sev=4 hang_monitor hxecom for enp0s7 is HUNG! Max run time (set in mdt) = 7200 seconds. Current elasped time = 28807 seconds. htx_messages Jul 24 00:29:08 2016 err= sev=4 hang_monitor hxecom for enp0s7 is HUNG! Max run time (set in mdt) = 7200 seconds. Current elasped time = 36007 seconds. /dev/enp0s4 Jul 25 04:56:13 2016 err=00e3 sev=4 hxecom R(103.1.2.20.36665) connected to W(103.1.1.20.40459) Miscompare with packet 0, data size = 3. miscompare_count=0 pakLen = 30020 Miscompare at displacement (decimal) = 17508 wbuf = rbuf = e7f0e114333039373600 For stanza 0, TCP connection, buf
[Kernel-packages] [Bug 1628976] Re: Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running memory_stress_ng.
The fix could be found at https://patchwork.kernel.org/patch/9364805/ -- 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/1628976 Title: Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running memory_stress_ng. Status in linux package in Ubuntu: New Bug description: FYI Canonical: We have been seeing various page handling issues during memory stress in the 4.8 kernels. The following is the most recent issue resulting in system panics on this host after the 4.8.0-17 update: == Comment: #17 - PAVITHRA R. PRAKASH - 2016-09-28 06:26:21 == Hi, Tried running on 4.8.0-17-generic kernel. Getting below call trace and system crashes. Attaching logs. [ 2959.364333] Unable to handle kernel paging request for data at address 0xf2fe4020 [ 2959.364345] Faulting instruction address: 0xc02bb2a0 [ 2959.364356] Oops: Kernel access of bad area, sig: 11 [#1] [ 2959.364364] SMP NR_CPUS=2048 NUMA pSeries [ 2959.364377] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag bnx2x mdio libcrc32c pseries_rng vmx_crypto binfmt_misc ip_tables x_tables autofs4 ibmvscsi crc32c_vpmsum [ 2959.364441] CPU: 13 PID: 108 Comm: oom_reaper Not tainted 4.8.0-17-generic #19-Ubuntu [ 2959.364452] task: c004fbdf9c00 task.stack: c004fbe0 [ 2959.364461] NIP: c02bb2a0 LR: c0300618 CTR: c009ca40 [ 2959.364471] REGS: c004fbe036e0 TRAP: 0300 Not tainted (4.8.0-17-generic) [ 2959.364481] MSR: 80010280b033 CR: 24028844 XER: 200c [ 2959.364526] CFAR: c0300614 DAR: f2fe4020 DSISR: 4000 SOFTE: 1 GPR00: c0300618 c004fbe03960 c14e5e00 f2fe4000 GPR04: 0001 0800 c1665e00 GPR08: f900a196 0001 02fe4000 GPR12: 8800 c1b37500 0008 c1ffe7ff GPR16: c004f62a55f0 3fff9a00 3fff9900 GPR20: c004fbe03b80 c004e0713800 8e017c3302c0 0001 GPR24: c000fb3614c8 c000fce9d990 c000fce9d6e4 96a100f90b40 GPR28: f2fe4000 c000fb3614c8 0001 f2fe4000 [ 2959.364673] NIP [c02bb2a0] page_remove_rmap+0x30/0x4b0 [ 2959.364685] LR [c0300618] zap_huge_pmd+0xf8/0x480 [ 2959.364692] Call Trace: [ 2959.364699] [c004fbe03960] [c004fbe039a0] 0xc004fbe039a0 (unreliable) [ 2959.364714] [c004fbe039a0] [c0300618] zap_huge_pmd+0xf8/0x480 [ 2959.364726] [c004fbe039f0] [c02a68d8] unmap_page_range+0xd08/0xee0 [ 2959.364740] [c004fbe03b20] [c025c474] __oom_reap_task+0x204/0x2c0 [ 2959.364752] [c004fbe03c80] [c025cda8] oom_reaper+0x1e8/0x300 [ 2959.364765] [c004fbe03d80] [c00fd120] kthread+0x110/0x130 [ 2959.364778] [c004fbe03e30] [c00098f0] ret_from_kernel_thread+0x5c/0x6c [ 2959.364788] Instruction dump: [ 2959.364796] 3c4c0123 3842ab90 7c0802a6 fba1ffe8 fbc1fff0 fbe1fff8 f8010010 f821ffc1 [ 2959.364821] 7c7f1b78 7c9e2378 6000 6000 71480001 392a 40820008 [ 2959.364871] ---[ end trace 178b14c6911b70dc ]--- [ 2959.372762] [ 2959.372798] Sending IPI to other CPUs [ 2959.373834] IPI complete Thanks, Pavithra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628976/+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 1543480] Re: ISST-KVM:Ubuntu1510:abakvm: abag3 guest hung while running stress test.
Closing this bug since the patch was already integrated, and available in all the current supported releases. ** Changed in: linux (Ubuntu) Status: New => Fix Released -- 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/1543480 Title: ISST-KVM:Ubuntu1510:abakvm: abag3 guest hung while running stress test. Status in linux package in Ubuntu: Fix Released Bug description: == Comment: #0 == Issue The Ubuntu1510 guest abag3 was running with stress test IO Base and TCP. After 40 hrs it hung , unable to perform ssh and unable to access its console but able to ping the guest. Xmon was enable for guest but it didn't drop there. [root@abakvm ~]# virsh list --all IdName State 11abag6 running 23abag5 running 25abag1 running 27abag2 running 29abag3 running 30abag4 running Logs === [127112.624493] NIP [c05183d8] __blk_mq_run_hw_queue+0x98/0x4c0 [127112.624953] LR [c00d9320] process_one_work+0x1e0/0x560 [127112.625343] Call Trace: [127112.625505] [c00179adbb50] [c1578190] cur_cpu_spec+0x0/0x8 (unreliable) [127112.626079] [c00179adbc50] [c00d9320] process_one_work+0x1e0/0x560 [127112.627154] [c00179adbce0] [c00d9830] worker_thread+0x190/0x660 [127112.627620] [c00179adbd80] [c00e2280] kthread+0x110/0x130 [127112.628084] [c00179adbe30] [c0009538] ret_from_kernel_thread+0x5c/0xa4 [127112.628743] Instruction dump: [127112.629080] 391e0188 eb1e0298 fb810088 fac10078 a12d0008 792ad182 792906a0 794a1f24 [127112.630112] 7d48502a 7d494c36 792907e0 69290001 <0b09> e93e0080 792a07e1 408202c8 [127112.631318] ---[ end trace de34117cdb302980 ]--- XML of abag3 [root@abakvm ~]# virsh dumpxml abag3 abag3 4d73aa99-64f3-4d1d-af02-995abb29cfc5 6291456 6291456 48 4096 /machine hvm power8 destroy restart coredump-restart /usr/bin/qemu-system-ppc64 SYSTEM INFORMATION - HOST KVM BUILD LEVEL: GA3 SP1 build 51 OPAL - FW840.10 - F4_1606A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543480/+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
