[Kernel-packages] [Bug 2019011] Re: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver
** Tags added: verification-needed-focal-linux-bluefield -- 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/2019011 Title: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification: == [ Impact ] * The mlx5 driver is causing a Kernel panic with "refcount_t: underflow". * This issue occurs during a recovery when the PCI device is isolated and thus doesn't respond. [ Fix ] * This issue got solved upstream with aaf2e65cac7f aaf2e65cac7f2e1ae729c2fbc849091df9699f96 "net/mlx5: Fix handling of entry refcount when command is not issued to FW" (upstream since 6.1-rc1) * But to get aaf2e65cac7f a backport of b898ce7bccf1 b898ce7bccf13087719c021d829dab607c175246 "net/mlx5: cmdif, Avoid skipping reclaim pages if FW is not accessible" is required on top (upstream since 5.10) [ Test Plan ] * An Ubuntu Server for s390x 20.04 LPAR or z/VM installation is needed that has Mellanox cards (RoCE Express 2.1) assigned, configured and enabled and that runs a 5.4 kernel with mlx5 driver. * Create some network traffic on (one of the) RoCE device (interface ens???[d?]) for testing (e.g. with stress-ng). * Make sure the module/driver mlx5 is loaded and in use. * Trigger a recovery (via the Support Element) that will render the adapter (ports) unresponsive for a moment and should provoke a similar situation. * Alternatively the interface itself can be removed for a moment and re-added again (but this may break further things on top). * Due to the lack of RoCE Express 2.1 hardware, the verification is on IBM. [ Where problems could occur ] * The modifications are limited to the Mellanox mlx5 driver only - no other network driver is affected. * The pre-required commit (aaf2e65cac7f) can have a bad impact on (re-)claiming pages if FW is not accessible, which could cause page leaks in case done wrong. But this commit is pretty save since it's upstream since v5.10. * The fix itself (aaf2e65cac7f) mainly changes the cmd_work_handler and mlx5_cmd_comp_handler functions in a way that instead of pci_channel_offline mlx5_cmd_is_down (introiduced by b898ce7bccf1). * Actually b898ce7bccf1 started with changing from pci_channel_offline to mlx5_cmd_is_down, but looks like a few cases (in the area of refcount increate/decrease) were missed, that are now covered by aaf2e65cac7f. * It fixes now on top refcounts are now always properly increment and decrement to achieve a symmetric state for all flows. * These changes may have an impact on all cases where the mlx5 device is not responding, which can happen in case of an offline channel, interface down, reset or recovery. [ Other Info ] * Looking at the master-next git trees for jammy, kinetic and lunar showed that both fixes are already included, hence only focal is affected. __ ---Problem Description--- Kernel panic with "refcount_t: underflow" in kernel log Contact Information = rijo...@ibm.com, vineeth.vija...@ibm.com ---uname output--- 5.4.0-128-generic Machine Type = s390x ---System Hang--- Kernel panic and stack-trace as below ---Debugger--- A debugger is not configured Stack trace output: [Sat Apr 8 17:52:21 UTC 2023] Call Trace: [Sat Apr 8 17:52:21 UTC 2023] ([<002a5939a286>] refcount_warn_saturate+0xce/0x140) [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f861e>] cmd_ent_put+0xe6/0xf8 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9b6a>] mlx5_cmd_comp_handler+0x102/0x4f0 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9f8a>] cmd_comp_notifier+0x32/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff805fe4fc>] mlx5_eq_async_int+0x13c/0x200 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff8061318e>] mlx5_irq_int_handler+0x2e/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023]
[Kernel-packages] [Bug 2013088] Re: kernel: fix __clear_user() inline assembly constraints
** Attachment removed: "uaccess clear_user() fix" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013088/+attachment/5660553/+files/s390-uaccess.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013088 Title: kernel: fix __clear_user() inline assembly constraints Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification: == [ Impact ] * In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. * The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. [Fix] * For Kinetic and Jammy cherrypick of 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3 "s390/uaccess: add missing earlyclobber annotations to __clear_user()" * For Focal and Bionic a backport of the above commit is needed: https://launchpadlibrarian.net/659551648/s390-uaccess.patch [ Test Plan ] * A test program in C is needed and used for testing. * The test will be done by IBM. [ Where problems could occur ] * The modification is limited to function 'long __clear_user'. * And there, just to one inline assembly constraints line. * This is usually difficult to trace. * A erroneous modification may lead to a wrong behavior in 'long __clear_user', * and maybe returning a wrong size (in uaccess.c). [ Other Info ] * This affects all Ubuntu releases in service, down to 18.04. * Since we are close to 23.04 kernel freeze, I submit a patch request for 23.04 separately, and submit the SRU request for the all other Ubuntu releases later. __ Description: kernel: fix __clear_user() inline assembly constraints Symptom: In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. Problem: The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. Solution: Add missing earlyclobber constraint modifiers. Preventive:yes Upstream-ID: 89aba4c26fae4e459f755a18912845c348ee48f3 Affected Releases: 18.04 20.04 22.04 22.10 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+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 1559194] Re: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver
** Attachment removed: "dmesg for re-run on kernel 4.4.0-33" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4732889/+files/dmesg.log ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4791005/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "dmesg for re-run on kernel 4.4.0-33" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4793785/+files/dmesg.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/1559194 Title: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released 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 Bug description: == Comment: #0 - Dmitry Gorbachev- 2016-03-17 08:52:41 == An error occurs when running zEDC compression/decompression and hotplugging PCI devices. There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled. Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in process genwqe_gunzip pfn:3c275 Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 count:-1 mapcount:0 mapping: (null) index:0x0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0() Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero _count Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) dasd_eckd_mod(E) dasd_mod(E) Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: genwqe_gunzip Tainted: GW E 4.4.0-8-generic #23-Ubuntu Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 20917788 0002 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 209177a0 209177a0 00114182 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 0092345a 03d1000a 000a Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 20917788 20914000 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 00114182 20917788 209177e8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace: Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] show_trace+0xf6/0x148) Mar 14 23:59:01 s8330018 kernel: [ 4972.486929] [<00114136>] show_stack+0x76/0xe8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486934] [<00518c26>] dump_stack+0x6e/0x90 Mar 14 23:59:01 s8330018 kernel: [ 4972.486937] [<0027c376>] bad_page+0xe6/0x148 Mar 14 23:59:01 s8330018 kernel: [ 4972.486938] [<00280516>] get_page_from_freelist+0x49e/0xba8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486940] [<00280ede>] __alloc_pages_nodemask+0x166/0xb00 Mar 14 23:59:01 s8330018 kernel: [ 4972.486941] [<0015635a>] s390_dma_alloc+0x82/0x1a0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486944] [<03ff805ea142>] __genwqe_alloc_consistent+0x7a/0x90 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486947] [<03ff805ea344>] genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486950] [<03ff805e52da>] do_execute_ddcb+0x1da/0x348 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486952] [<03ff805e5964>] genwqe_ioctl+0x51c/0xc20 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486953] [<003145ee>] do_vfs_ioctl+0x3b6/0x518 Mar 14 23:59:01 s8330018 kernel: [ 4972.486955] [<003147f4>] SyS_ioctl+0xa4/0xb8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486956] [<007ad1be>] system_call+0xd6/0x264 Mar 14 23:59:01 s8330018 kernel: [ 4972.486957]
[Kernel-packages] [Bug 1559194] Re: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver
** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4735664/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4788007/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4785403/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4785388/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4785373/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4785022/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4780985/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4780856/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4767763/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4763812/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4759896/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4756819/+files/linux-image-4.4.0-33.52__4.4.0-33.52_-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4756818/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4756788/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4756768/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4755886/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4751793/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4751777/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4739352/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb ** Attachment removed: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559194/+attachment/4736013/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb -- 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/1559194 Title: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released 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 Bug description: == Comment: #0 - Dmitry Gorbachev- 2016-03-17 08:52:41 == An
[Kernel-packages] [Bug 1580951] Re: Upgrade libseccomp from 2.2.3 ->2.3.1
** Package changed: linux (Ubuntu) => account-plugins (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/1580951 Title: Upgrade libseccomp from 2.2.3 ->2.3.1 Status in account-plugins package in Ubuntu: Invalid Bug description: == Comment: #1 - Heinz-Werner Seeck- 2016-05-11 05:09:09 == Please upgrade package libseccomp. The new version 2.3.1 is available on github https://github.com/seccomp/libseccomp/releases == Comment: #2 - Heinz-Werner Seeck - 2016-05-11 05:10:59 == ?Version 2.3.0 - February 29, 2016 ?Added support for the s390 and s390x architectures ?Added support for the ppc, ppc64, and ppc64le architectures ?Update the internal syscall tables to match the Linux 4.5-rcX releases ?Filter generation for both multiplexed and direct socket syscalls on x86 ?Support for the musl libc implementation ?Additions to the API to enable runtime version checking of the library ?Enable the use of seccomp() instead of prctl() on supported systems ?Added additional tests to the regression test suite ?Version 2.3.1 - April 20, 2016 ?Fixed a problem with 32-bit x86 socket syscalls on some systems ?Fixed problems with ipc syscalls on 32-bit x86 ?Fixed problems with socket and ipc syscalls on s390 and s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1580951/+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 1580951] Re: Upgrade libseccomp from 2.2.3 ->2.3.1
Bridge ReTest ** Attachment added: "tt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580951/+attachment/4703262/+files/test.txt -- 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/1580951 Title: Upgrade libseccomp from 2.2.3 ->2.3.1 Status in linux package in Ubuntu: Invalid Bug description: == Comment: #1 - Heinz-Werner Seeck- 2016-05-11 05:09:09 == Please upgrade package libseccomp. The new version 2.3.1 is available on github https://github.com/seccomp/libseccomp/releases == Comment: #2 - Heinz-Werner Seeck - 2016-05-11 05:10:59 == ?Version 2.3.0 - February 29, 2016 ?Added support for the s390 and s390x architectures ?Added support for the ppc, ppc64, and ppc64le architectures ?Update the internal syscall tables to match the Linux 4.5-rcX releases ?Filter generation for both multiplexed and direct socket syscalls on x86 ?Support for the musl libc implementation ?Additions to the API to enable runtime version checking of the library ?Enable the use of seccomp() instead of prctl() on supported systems ?Added additional tests to the regression test suite ?Version 2.3.1 - April 20, 2016 ?Fixed a problem with 32-bit x86 socket syscalls on some systems ?Fixed problems with ipc syscalls on 32-bit x86 ?Fixed problems with socket and ipc syscalls on s390 and s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580951/+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 1580951] Re: Upgrade libseccomp from 2.2.3 ->2.3.1
I want to get 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/1580951 Title: Upgrade libseccomp from 2.2.3 ->2.3.1 Status in linux package in Ubuntu: Invalid Bug description: == Comment: #1 - Heinz-Werner Seeck- 2016-05-11 05:09:09 == Please upgrade package libseccomp. The new version 2.3.1 is available on github https://github.com/seccomp/libseccomp/releases == Comment: #2 - Heinz-Werner Seeck - 2016-05-11 05:10:59 == ?Version 2.3.0 - February 29, 2016 ?Added support for the s390 and s390x architectures ?Added support for the ppc, ppc64, and ppc64le architectures ?Update the internal syscall tables to match the Linux 4.5-rcX releases ?Filter generation for both multiplexed and direct socket syscalls on x86 ?Support for the musl libc implementation ?Additions to the API to enable runtime version checking of the library ?Enable the use of seccomp() instead of prctl() on supported systems ?Added additional tests to the regression test suite ?Version 2.3.1 - April 20, 2016 ?Fixed a problem with 32-bit x86 socket syscalls on some systems ?Fixed problems with ipc syscalls on 32-bit x86 ?Fixed problems with socket and ipc syscalls on s390 and s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580951/+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 1580951] Re: Upgrade libseccomp from 2.2.3 ->2.3.1
Bridge test attachment for LTC bridge ** Attachment added: "Bridge TTT WOW" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580951/+attachment/4703261/+files/test.xml -- 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/1580951 Title: Upgrade libseccomp from 2.2.3 ->2.3.1 Status in linux package in Ubuntu: Invalid Bug description: == Comment: #1 - Heinz-Werner Seeck- 2016-05-11 05:09:09 == Please upgrade package libseccomp. The new version 2.3.1 is available on github https://github.com/seccomp/libseccomp/releases == Comment: #2 - Heinz-Werner Seeck - 2016-05-11 05:10:59 == ?Version 2.3.0 - February 29, 2016 ?Added support for the s390 and s390x architectures ?Added support for the ppc, ppc64, and ppc64le architectures ?Update the internal syscall tables to match the Linux 4.5-rcX releases ?Filter generation for both multiplexed and direct socket syscalls on x86 ?Support for the musl libc implementation ?Additions to the API to enable runtime version checking of the library ?Enable the use of seccomp() instead of prctl() on supported systems ?Added additional tests to the regression test suite ?Version 2.3.1 - April 20, 2016 ?Fixed a problem with 32-bit x86 socket syscalls on some systems ?Fixed problems with ipc syscalls on 32-bit x86 ?Fixed problems with socket and ipc syscalls on s390 and s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580951/+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 1486180] Re: Kernel OOPS during DLPAR operation with Fibre Channel adapter
** Attachment removed: "boot log with lpfc" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486180/+attachment/4548305/+files/boot-log-with-lpfc.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/1486180 Title: Kernel OOPS during DLPAR operation with Fibre Channel adapter Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: In Progress Status in linux source package in Xenial: Fix Committed Bug description: -- Problem Description -- Kernel OOPS during DLPAR operation with Fibre Channel adapter ---uname output--- 4.1.0-1-generic ---Additional Hardware Info--- Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) Machine Type = POWER8 ---Steps to Reproduce--- 1) Install Ubuntu 15.10 on a Power VM LPAR. 2) Configure and start rtas_errd daemon 3) Via HMC try to add a Fibre channel adapter via dynamic partitioning During the operation following OOPS message is observed Oops output: !!! 00E0806 Fcode, Copyright (c) 2000-2012 Emulex !!! Version 3.10x2 !!! 00E0806 Fcode, Copyright (c) 2000-2012 Emulex !!! Version 3.10x2 [ 8696.808703] PCI host bridge /pci@8002020 ranges: [ 8696.808708] MEM 0x0003ff84..0x0003ff847eff -> 0x8000 [ 8696.808716] PCI: I/O resource not set for host bridge /pci@8002020 (domain 1) [ 8696.808761] PCI host bridge to bus 0001:01 [ 8696.808765] pci_bus 0001:01: root bus resource [mem 0x3ff84-0x3ff847eff] (bus address [0x8000-0xfeff]) [ 8696.808768] pci_bus 0001:01: root bus resource [bus 01-ff] [ 8696.897390] rpaphp: Slot [U78C7.001.RCH0042-P1-C8] registered [ 8696.897395] rpadlpar_io: slot PHB 32 added [ 8696.972155] Emulex LightPulse Fibre Channel SCSI driver 10.5.0.0. [ 8696.972157] Copyright(c) 2004-2015 Emulex. All rights reserved. [ 8696.972438] lpfc 0001:01:00.1: enabling device (0140 -> 0142) [ 8696.976145] Unable to handle kernel paging request for data at address 0x000c [ 8696.976174] Faulting instruction address: 0xc0084cc4 [ 8696.976182] Oops: Kernel access of bad area, sig: 11 [#1] [ 8696.976188] SMP NR_CPUS=2048 NUMA pSeries [ 8696.976196] Modules linked in: lpfc(+) scsi_transport_fc rpadlpar_io rpaphp rtc_generic pseries_rng autofs4 [ 8696.976220] CPU: 3 PID: 1426 Comm: systemd-udevd Not tainted 4.1.0-1-generic #1~dogfoodv1-Ubuntu [ 8696.976230] task: c003857737e0 ti: c000fd08c000 task.ti: c000fd08c000 [ 8696.976239] NIP: c0084cc4 LR: c0084ca8 CTR: [ 8696.976247] REGS: c000fd08f0f0 TRAP: 0300 Not tainted (4.1.0-1-generic) [ 8696.976255] MSR: 80019033CR: 8222 XER: 2000 [ 8696.976278] CFAR: c0008468 DAR: 000c DSISR: 4000 SOFTE: 1 GPR00: c0084ca8 c000fd08f370 c14bda00 GPR04: 0001 c000fd08f408 0003 d2c31e60 GPR08: c13bda00 c003873e6b80 d2ca7c98 GPR12: 8800 ce831b00 d29421f8 38ca4522 GPR16: c000fd08fdc0 c000fd08fe04 d2941878 c000fc8054c0 GPR20: d238 d238 d2ccff90 GPR24: c165074c c0038e17e000 c13b5e00 c0038e17e000 GPR28: c13b5e28 ca590600 c13b5df0 c13b5e20 [ 8696.976396] NIP [c0084cc4] enable_ddw+0x254/0x7b0 [ 8696.976405] LR [c0084ca8] enable_ddw+0x238/0x7b0 [ 8696.976411] Call Trace: [ 8696.976419] [c000fd08f370] [c0084ca8] enable_ddw+0x238/0x7b0 (unreliable) [ 8696.976431] [c000fd08f4b0] [c00866d8] dma_set_mask_pSeriesLP+0x218/0x2a0 [ 8696.976444] [c000fd08f540] [c0023528] dma_set_mask+0x58/0xa0 [ 8696.976474] [c000fd08f570] [d2c71280] lpfc_pci_probe_one+0xb0/0xc50 [lpfc] [ 8696.976486] [c000fd08f610] [c05987fc] local_pci_probe+0x6c/0x140 [ 8696.976497] [c000fd08f6a0] [c0598a28] pci_device_probe+0x158/0x1e0 [ 8696.976510] [c000fd08f700] [c067b744] driver_probe_device+0x1c4/0x5a0 [ 8696.976522] [c000fd08f790] [c067bcdc] __driver_attach+0x11c/0x120 [ 8696.976533] [c000fd08f7d0] [c067854c] bus_for_each_dev+0x9c/0x110 [ 8696.976544] [c000fd08f820] [c067adbc] driver_attach+0x3c/0x60 [ 8696.976555] [c000fd08f850] [c067a768] bus_add_driver+0x208/0x320 [ 8696.976565] [c000fd08f8e0] [c067c99c] driver_register+0x9c/0x180 [ 8696.976576] [c000fd08f950] [c05978ec]
[Kernel-packages] [Bug 1486180] Re: Kernel OOPS during DLPAR operation with Fibre Channel adapter
** Attachment removed: "boot log with lpfc" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486180/+attachment/4548034/+files/boot-log-with-lpfc.log ** Attachment removed: "dmesg log captured after DLPAR operation" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486180/+attachment/4548035/+files/dmesg-log-after-dlpar.log ** Attachment removed: "Patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486180/+attachment/4548077/+files/0001-powerpc-eeh-Validate-arch-in-eeh_add_device_early.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1486180 Title: Kernel OOPS during DLPAR operation with Fibre Channel adapter Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: In Progress Status in linux source package in Xenial: Fix Committed Bug description: -- Problem Description -- Kernel OOPS during DLPAR operation with Fibre Channel adapter ---uname output--- 4.1.0-1-generic ---Additional Hardware Info--- Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) Machine Type = POWER8 ---Steps to Reproduce--- 1) Install Ubuntu 15.10 on a Power VM LPAR. 2) Configure and start rtas_errd daemon 3) Via HMC try to add a Fibre channel adapter via dynamic partitioning During the operation following OOPS message is observed Oops output: !!! 00E0806 Fcode, Copyright (c) 2000-2012 Emulex !!! Version 3.10x2 !!! 00E0806 Fcode, Copyright (c) 2000-2012 Emulex !!! Version 3.10x2 [ 8696.808703] PCI host bridge /pci@8002020 ranges: [ 8696.808708] MEM 0x0003ff84..0x0003ff847eff -> 0x8000 [ 8696.808716] PCI: I/O resource not set for host bridge /pci@8002020 (domain 1) [ 8696.808761] PCI host bridge to bus 0001:01 [ 8696.808765] pci_bus 0001:01: root bus resource [mem 0x3ff84-0x3ff847eff] (bus address [0x8000-0xfeff]) [ 8696.808768] pci_bus 0001:01: root bus resource [bus 01-ff] [ 8696.897390] rpaphp: Slot [U78C7.001.RCH0042-P1-C8] registered [ 8696.897395] rpadlpar_io: slot PHB 32 added [ 8696.972155] Emulex LightPulse Fibre Channel SCSI driver 10.5.0.0. [ 8696.972157] Copyright(c) 2004-2015 Emulex. All rights reserved. [ 8696.972438] lpfc 0001:01:00.1: enabling device (0140 -> 0142) [ 8696.976145] Unable to handle kernel paging request for data at address 0x000c [ 8696.976174] Faulting instruction address: 0xc0084cc4 [ 8696.976182] Oops: Kernel access of bad area, sig: 11 [#1] [ 8696.976188] SMP NR_CPUS=2048 NUMA pSeries [ 8696.976196] Modules linked in: lpfc(+) scsi_transport_fc rpadlpar_io rpaphp rtc_generic pseries_rng autofs4 [ 8696.976220] CPU: 3 PID: 1426 Comm: systemd-udevd Not tainted 4.1.0-1-generic #1~dogfoodv1-Ubuntu [ 8696.976230] task: c003857737e0 ti: c000fd08c000 task.ti: c000fd08c000 [ 8696.976239] NIP: c0084cc4 LR: c0084ca8 CTR: [ 8696.976247] REGS: c000fd08f0f0 TRAP: 0300 Not tainted (4.1.0-1-generic) [ 8696.976255] MSR: 80019033CR: 8222 XER: 2000 [ 8696.976278] CFAR: c0008468 DAR: 000c DSISR: 4000 SOFTE: 1 GPR00: c0084ca8 c000fd08f370 c14bda00 GPR04: 0001 c000fd08f408 0003 d2c31e60 GPR08: c13bda00 c003873e6b80 d2ca7c98 GPR12: 8800 ce831b00 d29421f8 38ca4522 GPR16: c000fd08fdc0 c000fd08fe04 d2941878 c000fc8054c0 GPR20: d238 d238 d2ccff90 GPR24: c165074c c0038e17e000 c13b5e00 c0038e17e000 GPR28: c13b5e28 ca590600 c13b5df0 c13b5e20 [ 8696.976396] NIP [c0084cc4] enable_ddw+0x254/0x7b0 [ 8696.976405] LR [c0084ca8] enable_ddw+0x238/0x7b0 [ 8696.976411] Call Trace: [ 8696.976419] [c000fd08f370] [c0084ca8] enable_ddw+0x238/0x7b0 (unreliable) [ 8696.976431] [c000fd08f4b0] [c00866d8] dma_set_mask_pSeriesLP+0x218/0x2a0 [ 8696.976444] [c000fd08f540] [c0023528] dma_set_mask+0x58/0xa0 [ 8696.976474] [c000fd08f570] [d2c71280] lpfc_pci_probe_one+0xb0/0xc50 [lpfc] [ 8696.976486] [c000fd08f610] [c05987fc] local_pci_probe+0x6c/0x140 [ 8696.976497] [c000fd08f6a0] [c0598a28] pci_device_probe+0x158/0x1e0 [ 8696.976510] [c000fd08f700] [c067b744] driver_probe_device+0x1c4/0x5a0 [ 8696.976522] [c000fd08f790] [c067bcdc] __driver_attach+0x11c/0x120 [
[Kernel-packages] [Bug 1430341] Re: [Ubuntu 15.04] Enable perf to exploit 24x7 hardware counters
comment from launchpad, please ignore -- 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/1430341 Title: [Ubuntu 15.04] Enable perf to exploit 24x7 hardware counters Status in linux package in Ubuntu: Fix Released Bug description: == Comment: #0 - Breno Henrique Leitao bren...@br.ibm.com - 2014-11-06 12:52:04 == Enable perf tool to exploit POWER 24x7 hardware counters Parts of the project: a) Some patches upstream and done b) Reset targets on remaining features still to be done (jit support, symbol names) == Comment: #16 - Breno Henrique Leitao bren...@br.ibm.com - 2015-02-24 08:06:45 == Initial patches already accepted by Canonical on 117275. Patchset posted to community, waiting on review. (I had posted a version of the patchset in Dec after fixing minor comments. Waiting to hear back from community ) == Comment: #18 - Sukadev Bhattiprolu s...@us.ibm.com - 2015-02-25 16:18:34 == There are two separate patch sets, one for the perf tool and other for the kernel. They are both available in mainline 3.19-rc4. === Perf tool patches (4) Patch 1/4: http://marc.info/?l=linuxppc-embeddedm=142067974403807w=2 commit 688d4df Author: Cody P Schafer c...@linux.vnet.ibm.com Date: Wed Jan 7 17:13:50 2015 -0800 perf tools: Support parsing parameterized events Patch 2/4: http://marc.info/?l=linux-kernelm=142067973603799w=2 commit aaea361 Author: Cody P Schafer c...@linux.vnet.ibm.com Date: Wed Jan 7 17:13:51 2015 -0800 perf tools: Extend format_alias() to include event parameters Patch 3/4: http://marc.info/?l=linux-kernelm=142067971103796w=2 commit 98a43e0 Author: Cody P Schafer c...@linux.vnet.ibm.com Date: Wed Jan 7 17:13:52 2015 -0800 perf Documentation: Add event parameters Patch 4/4: http://marc.info/?l=linux-kernelm=142067968803787w=2 commit f9ab9c1 Author: Cody P Schafer c...@linux.vnet.ibm.com Date: Wed Jan 7 17:13:53 2015 -0800 perf tools: Document parameterized and symbolic events === Kernel patches(7) Patch 1/7: http://marc.info/?l=linux-kernelm=142265456708471w=2 commit fd979c0 Author: Cody P Schafer c...@linux.vnet.ibm.com Date: Fri Jan 30 13:45:57 2015 -0800 perf: provide sysfs_show for struct perf_pmu_events_attr Patch 2/7: http://marc.info/?l=linux-kernelm=142265448108443w=2 commit f0405b8 Author: Cody P Schafer c...@linux.vnet.ibm.com Date: Fri Jan 30 13:45:58 2015 -0800 perf: add PMU_EVENT_ATTR_STRING() helper Patch 3/7: http://marc.info/?l=linux-kernelm=142265445208433w=2 commit e08e528 Author: suka...@linux.vnet.ibm.com suka...@linux.vnet.ibm.com Date: Fri Jan 30 13:45:59 2015 -0800 perf: define EVENT_DEFINE_RANGE_FORMAT_LITE helper Patch 4/7: http://marc.info/?l=linux-kernelm=142265452008458w=2 commit 5c5cd7b Author: Cody P Schafer c...@linux.vnet.ibm.com Date: Fri Jan 30 13:46:00 2015 -0800 powerpc/perf/hv-24x7: parse catalog and populate sysfs with events Patch 5/7: http://marc.info/?l=linux-kernelm=142265450008450w=2 commit 9e9f601 Author: Cody P Schafer c...@linux.vnet.ibm.com Date: Fri Jan 30 13:46:01 2015 -0800 powerpc/perf/{hv-gpci, hv-common}: generate requests with counters annotated Patch 6/7: http://marc.info/?l=linux-kernelm=142265448408446w=2 commit 97bf264 Author: Cody P Schafer c...@linux.vnet.ibm.com Date: Fri Jan 30 13:46:02 2015 -0800 powerpc/perf/hv-gpci: add the remaining gpci requests Patch 7/7: http://marc.info/?l=linux-kernelm=142265446008435w=2 commit 5c65670 Author: Cody P Schafer c...@linux.vnet.ibm.com Date: Fri Jan 30 13:46:03 2015 -0800 powerpc/perf/hv-24x7: Document sysfs event description entries == Comment: #23 - Sukadev Bhattiprolu s...@us.ibm.com - 2015-02-26 13:22:13 == Never mind. 'git describe' seems to think they are in 3.19-rcX but they are not in 3.19. $ git describe fd979c0 v3.19-rc2-62-gfd979c0 $ git describe aaea361 v3.19-rc4-172-gaaea361 They were merged on Feb 2, so they should be in 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1430341/+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