[Bug 1901528] Comment bridged from LTC Bugzilla
--- Comment From i...@de.ibm.com 2021-01-20 05:23 EDT--- s390x build of gzip 1.10-2ubuntu1.1 fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901528 Title: [Ubuntu 20.10] - When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB (gzip) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1901528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907421] Comment bridged from LTC Bugzilla
--- Comment From mjros...@us.ibm.com 2021-01-19 15:52 EDT--- The associated commit is now available in 5.4 stable as of 5.4.90 -- the commit ID from the 5.4.y stable branch is 5597557244d44989a7310755d0a8ec40ae603acb 'vfio iommu: Add dma available capability' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907421 Title: [UBUNTU 21.04] vfio: pass DMA availability information to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1907421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903984] debdiff_focal.diff
Default Comment by Bridge ** Attachment added: "debdiff_focal.diff" https://bugs.launchpad.net/bugs/1903984/+attachment/5454587/+files/debdiff_focal.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903984 Title: [UBUNTU 20.04] Cannot run zcryptstats in the Hosting Appliance To manage notifications about this bug go to: https://bugs.launchpad.net/s390-tools/+bug/1903984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903984] debdiff_groovy.diff
Default Comment by Bridge ** Attachment added: "debdiff_groovy.diff" https://bugs.launchpad.net/bugs/1903984/+attachment/5454567/+files/debdiff_groovy.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903984 Title: [UBUNTU 20.04] Cannot run zcryptstats in the Hosting Appliance To manage notifications about this bug go to: https://bugs.launchpad.net/s390-tools/+bug/1903984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903984] debdiff_hirsute.diff
Default Comment by Bridge ** Attachment added: "debdiff_hirsute.diff" https://bugs.launchpad.net/bugs/1903984/+attachment/5454565/+files/debdiff_hirsute.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903984 Title: [UBUNTU 20.04] Cannot run zcryptstats in the Hosting Appliance To manage notifications about this bug go to: https://bugs.launchpad.net/s390-tools/+bug/1903984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850294] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-01-19 08:59 EDT--- IBM Bugzilla status->closed, Fix Released by all requested Distros -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850294 Title: ICA HW token missing after the package update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1850294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850294] Re: ICA HW token missing after the package update
** Tags removed: targetmilestone-inin1804 ** Tags added: targetmilestone-inin2004 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850294 Title: ICA HW token missing after the package update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1850294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850294] Re: ICA HW token missing after the package update
** Tags removed: targetmilestone-inin2004 ** Tags added: targetmilestone-inin1804 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850294 Title: ICA HW token missing after the package update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1850294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850294] Comment bridged from LTC Bugzilla
--- Comment From patrick.ste...@de.ibm.com 2021-01-19 05:54 EDT--- The fixes are not needed for 3.9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850294 Title: ICA HW token missing after the package update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1850294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903984] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-01-19 04:55 EDT--- The git commit should apply to all requested levels. If tested is also required for non-hirsuite levels, please provide a PPA, at least for focal.. thx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903984 Title: [UBUNTU 20.04] Cannot run zcryptstats in the Hosting Appliance To manage notifications about this bug go to: https://bugs.launchpad.net/s390-tools/+bug/1903984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907656] Re: [UBUNTU 21.04] s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset
--- Comment From heinz-werner_se...@de.ibm.com 2021-01-19 04:52 EDT--- IBM Bugzilla status-> closed, Fix Released with all requested distros ** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2104 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907656 Title: [UBUNTU 21.04] s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1907656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904585] Re: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd))
--- Comment From hegdevas...@in.ibm.com 2021-01-18 09:32 EDT--- (In reply to comment #28) > What about verification of the bionic packages? I only see tags for groovy, > focal and xenial updated, but I assume bionic has also been verified? > Could someone confirm? Done. I missed to update the keyword. -Vasant ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904585 Title: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903984] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-01-18 05:57 EDT--- @Canonical, please provide an update for this update request. Many thx in advance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903984 Title: [UBUNTU 20.04] Cannot run zcryptstats in the Hosting Appliance To manage notifications about this bug go to: https://bugs.launchpad.net/s390-tools/+bug/1903984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906384] Comment bridged from LTC Bugzilla
--- Comment From y...@cn.ibm.com 2021-01-18 04:38 EDT--- Thanks! We will try this out and see if that works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906384 Title: [UBUNTU 18.04] lvm boot failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1906384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902179] Comment bridged from LTC Bugzilla
--- Comment From jjhe...@us.ibm.com 2021-01-15 08:35 EDT--- (In reply to comment #82) > Is the NVMe drive with or without nvme-multipath support? > Does it help to disable multipath? > > Please see the below pullrequest from Canonical employee in efivar project > that explains the issue a bit, and the various paths that the NVMe devices > can have. > > https://github.com/rhboot/efivar/pull/158 > > This also affected efibootmgr project for the EFI platforms with newer > kernels, as shipped in focal. > > You can also try booting with the following kernel cmdline option appended > in the param file i.e. `nvme_core.multipath=N` to get the "non-multipath > nvme0 nodes in the sysfs". > > BTW > https://www.ibm.com/support/knowledgecenter/STSLR9_8.3.1/com.ibm.fs9100_831. > doc/svc_fc_nvme_multipathconfighosts.html has an excellent summary of nvme > multipath situation in various distros. Yes, multipath is the problem here. When multipath is enabled we have a different sysfs structure. I'll have to work up a fix. Can you move ahead with the code as it is, and then we can provide a bug fix patch when ready? This chreipl bug should not impede NVMe installation or a normal boot process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902179 Title: [20.04 FEAT] Support/enhancement of NVMe IPL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1902179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904585] Comment bridged from LTC Bugzilla
--- Comment From hegdevas...@in.ibm.com 2021-01-15 01:23 EDT--- (In reply to comment #24) > Vasant, thanks for the verification on this bug. > Could you also check the other opal-prd bug which also needs verification, > please: > > ``` > "Ubuntu 20.04: opal-prd fails to start on 20.04" > https://bugs.launchpad.net/bugs/1905393 > ``` I have updated that above defect. Thanks! -Vasant -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904585 Title: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905393] Re: Ubuntu 20.04: opal-prd fails to start on 20.04
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905393 Title: Ubuntu 20.04: opal-prd fails to start on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1905393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902179] Comment bridged from LTC Bugzilla
--- Comment From jjhe...@us.ibm.com 2021-01-14 09:00 EDT--- chreipl currently fails on Ubuntu 20.04 when given a device node (e.g. chreipl /dev/nvme0n1p1). This is because chreipl cannot find the expected sysfs directory structure. We are investigating the best way to fix this. If the Ubuntu installer can still complete an install to NVMe devices without this particular invocation of chreipl then we recommend going forward with the code as-is and we can provide a bug fix at a later date. I suspect this should be fine, as chreipl should only affect the reboot following OS installation. It should be noted that chreipl works when given the devices function id (FID) parameter instead of the device node. It only fails when it needs to look up the device's FID given the device node. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902179 Title: [20.04 FEAT] Support/enhancement of NVMe IPL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1902179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906384] Comment bridged from LTC Bugzilla
--- Comment From y...@cn.ibm.com 2021-01-14 04:48 EDT--- Thanks! I remember that the system was installed on a single path. Later on, more paths were added. And no initramfs was rebuilt. I think that's the case. Is there any procedure for Ubuntu to deal with such case for boot LVM device? Thanks! (In reply to comment #15) > Do you remember what happened just prior to the reboot - have you been > upgrading the system with a new kernel and/or updated packages? > (Btw. the kernel 4.15.0-91 is a bit outdated, current is 4.15.0-124.) > There's maybe a file /etc/lvm/lvm.conf.dpkg-dist available from a previous > upgrade. > > Or have you added more or changed FCP or iSCSI disks to the system, that may > have let to a name clash or device (path) discovery order issues? > And was the initramfs rebuild? > > Such an issue can also happen due to temporarily unavailable paths or > devices, and there seem to be some of them in that system. > Do you have LUN masking (zoning) in your SAN in place, so that the host can > only see the LUNs it's supported to see? > > Btw. I think in your filter rule you also want to accept the sd* (SCSI/FCP) > devices, so: > filter = [ "a|/dev/sd*|", "a|/dev/mapper/mpath*|", "r|.*|" ] > and you may add the same as global filter: > global_filter = [ "a|/dev/sd*|", "a|/dev/mapper/mpath*|", "r|.*|" ] > for system level scans. > According to the logs the system seems to expect '/dev/mapper/ISVCL1--vg', > so looks you have LVM on top of multipath? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906384 Title: [UBUNTU 18.04] lvm boot failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1906384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906250] Comment bridged from LTC Bugzilla
--- Comment From s...@de.ibm.com 2021-01-13 10:19 EDT--- I've just installed libc-bin/groovy-proposed,now 2.32-0ubuntu3.1 amd64 [installed,automatic] libc6/groovy-proposed,now 2.32-0ubuntu3.1 amd64 [installed,automatic] and /etc/ld.so.cache contains the flags = cache_file_new_flags_endian_little = 2. Which libc6-s390x-cross groovy package version is based on libc6-2.32-0ubuntu3.1 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906250 Title: Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using qemu-s390x on x86_64. To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1906250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876715] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1877089 *** https://bugs.launchpad.net/bugs/1877089 --- Comment From heinz-werner_se...@de.ibm.com 2021-01-13 09:54 EDT--- IBM Bugzilla status-> closed , Fix Released by Canonical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876715 Title: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1876715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881109] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-01-13 09:51 EDT--- IBM Bugzilla -> closed, Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881109 Title: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1881109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908371] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-01-13 09:19 EDT--- In addition following git.commit need also be applied on both levels https://github.com/ibm-s390-tools/s390-tools/commit/37348ef662a7052dae798e500ca8c9b769fff3e6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908371 Title: [UBUNTU 20.04] - zipl command doesn't work correctly with -M option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1908371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906250] Re: Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using qemu-s390x on x86_64.
** Tags removed: targetmilestone-inin--- verification-done verification-done-focal verification-done-groovy ** Tags added: targetmilestone-inin2004 verification-needed verification-needed-focal verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906250 Title: Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using qemu-s390x on x86_64. To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1906250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904585] Re: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd))
--- Comment From hegdevas...@in.ibm.com 2021-01-13 05:23 EDT--- (In reply to comment #20) > Hello bugproxy, or anyone else affected, > > Accepted skiboot into groovy-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/skiboot/6.5.2-1ubuntu0.20.10.1 in a few > hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to > enable and use -proposed. Your feedback will aid us getting this update out > to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested, what testing has been > performed on the package and change the tag from verification-needed-groovy > to verification-done-groovy. If it does not fix the bug for you, please add > a comment stating that, and change the tag to verification-failed-groovy. In > either case, without details of your testing we will not be able to proceed. We have verified above package and fixes looks good. We verified whether daemon starts fine or not. Also whether it spawns separate child to handle page offlining process. -Vasant --- Comment From hegdevas...@in.ibm.com 2021-01-13 05:24 EDT--- (In reply to comment #21) > Hello bugproxy, or anyone else affected, > > Accepted skiboot into xenial-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/skiboot/5.4.3-1ubuntu0.16.04.2 in a few > hours, and then in the -proposed repository. We have verified above package and fixes looks good. -Vasant ** Tags removed: verification-needed-focal verification-needed-groovy verification-needed-xenial ** Tags added: verification-done-focal verification-done-groovy verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904585 Title: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906250] Comment bridged from LTC Bugzilla
--- Comment From s...@de.ibm.com 2021-01-12 05:22 EDT--- (In reply to comment #13) > Yes this is a different fix in Focal, but it fixes the actual endianness > problem rather than improving the corruption check. In my testing that > resolved the reported issue, please give a try to the newly build cross > packages. I've just updated to these packages: libc-bin/focal-proposed,now 2.31-0ubuntu9.2 amd64 [installed,automatic] libc6/focal-proposed,now 2.31-0ubuntu9.2 amd64 [installed,automatic] libc6-s390x-cross/focal-proposed,focal-proposed,now 2.31-0ubuntu9.2cross1 all [installed] And checked that ldconfig has written /etc/ld.so.cache with flags = cache_file_new_flags_endian_little = 2. And successfully run a s390x binary: $ qemu-s390x -L /usr/s390x-linux-gnu ./helloworld-s390x Hello world Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906250 Title: Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using qemu-s390x on x86_64. To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1906250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905393] Re: Ubuntu 20.04: opal-prd fails to start on 20.04
--- Comment From hegdevas...@in.ibm.com 2021-01-12 01:25 EDT--- (In reply to comment #20) > Hello bugproxy, or anyone else affected, > > Accepted skiboot into groovy-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/skiboot/6.5.2-1ubuntu0.20.10.1 in a few > hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to > enable and use -proposed. Your feedback will aid us getting this update out > to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested, what testing has been > performed on the package and change the tag from verification-needed-groovy > to verification-done-groovy. If it does not fix the bug for you, please add > a comment stating that, and change the tag to verification-failed-groovy. In > either case, without details of your testing we will not be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance for helping! > > N.B. The updated package will be released to -updates after the bug(s) fixed > by this package have been verified and the package has been in -proposed for > a minimum of 7 days. Thanks! Changes looks good. With this change we are able to start opal-prd daemon and co-worker fix also working fine. -Vasant ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905393 Title: Ubuntu 20.04: opal-prd fails to start on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1905393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904585] Re: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd))
** Tags removed: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904585 Title: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907656] Comment bridged from LTC Bugzilla
--- Comment From mjros...@us.ibm.com 2021-01-08 15:26 EDT--- I installed the focal qemu-system-s390x package (1:4.2-3ubuntu6.11) as well as the groovy package (1:5.0-5ubuntu9.3) via the -proposed repositories. In both cases, I tested using a vfio-pci passthrough device on a single guest and the same method described above (kexec in the guest) to trigger the subsystem reset event in QEMU -- With both of these QEMU versions, I verified that the PCI device is now appropriately available after the reset event. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907656 Title: [UBUNTU 21.04] s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1907656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881109] Comment bridged from LTC Bugzilla
--- Comment From max.bend...@ibm.com 2020-12-21 10:42 EDT--- We have re-run our test suite that originally produces this bug consistently and again were unable to reproduce. It looks like this issue has been fixed on the latest kernel. ``` bender@zt93ke:~$ uname -a Linux zt93ke 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:13:08 UTC 2020 s390x s390x s390x GNU/Linux bender@zt93ke:~$ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.1 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.1 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ``` @Heinz-Werner Seeck good to close +1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881109 Title: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1881109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908756] [NEW] Ubuntu 20.10 - elfutils unwinding broken for s390 compat
Public bug reported:
---Problem Description---
libdw unwinding fails for 32 bit binaries.
Elfutils biarch test currently fails on s390x doing unwinding for a 32 bit
process.
FAIL: run-backtrace-native-biarch.sh
0x557e7000 0x557eb000 /root/elfutils/tests/backtrace-child-biarch
0x7dba4000 0x7dd51000 /usr/lib/libc-2.32.so
0x7dd53000 0x7dd7 /usr/lib/libpthread-2.32.so
0x7dd7f000 0x7dda6000 /usr/lib/ld-2.32.so
TID 376858:
# 0 0x7dd6668a raise
# 1 0x7fd0ef60 - 1
/root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information
found
backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL &&
strcmp (symname, "sigusr2") == 0' failed.
./test-subr.sh: line 84: 376822 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-biarch: no main
FAIL run-backtrace-native-biarch.sh (exit status: 1)
Patch has already been posted and upstream committed:
https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html
Please pick up the following commit for the next release:
commit e4d985a3c1c873f77d20fa0cd421458cc2824996
Author: Andreas Krebbel
Date: Thu Nov 19 20:32:24 2020 +0100
IBM Z: Fix endianess problem in pid_memory_read
The cached reads lack the big endian adjustments done in the fallback
path.
Signed-off-by: Andreas Krebbel
The patch applies cleanly ontop of elfutils_0.181-1.
strace right now is not built with unwinding support for IBM Z although both
variants should work - libdw and libunwind.
Other distros use libdw from elfutils while Ubuntu on x86 appears to use
libunwind. libdw and libunwind do support IBM Z.
It would be good to build strace with unwinding support for Z.
** Affects: elfutils (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-190488 severity-medium
targetmilestone-inin2104
** Tags added: architecture-s39064 bugnameltc-190488 severity-medium
targetmilestone-inin2104
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => elfutils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908756
Title:
Ubuntu 20.10 - elfutils unwinding broken for s390 compat
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1908756/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2020-12-17 23:45 EDT--- Squeezing in right before the end of the year! I tested this with my pseries secure boot setup. I built the key from the PPA into grub and signed grub with the testing key which I built into SLOF. I was then able to boot 5.10.0-9-generic in secure boot mode under P8 KVM. The kernel correctly detected secure boot mode and entered lockdown: [0.00] Secure boot mode enabled [0.00] Kernel is locked down from PowerNV Secure Boot mode; see man kernel_lockdown.7 (The text is a bit of a misnomer, but that's of no consequence.) Lockdown appears to work as expected, I can't open /dev/mem for example. Given LP: #1903288 / BZ 189099, I didn't test kexec. In summary, I don't see anything from booting with secure boot on or off that would prevent you promoting 5.10 for hirsute. Enjoy your end of year break! Kind regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903288] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2020-12-17 19:59 EDT--- I checked out LP: #1643652. I don't know why we asked for IMA_X509_PATH there, we don't need it for OpenPower secure boot. For guest secure boot, the end goal of my request here is to get the pieces in place to enable signed kexec - at least for the kdump case. Under secure boot, only signed kernels can be kexeced. The kernel will verify the appended signature against the .platform and .ima keyrings. The .platform keyring is fine on OpenPower secure boot and UEFI secure boot because the keyring gets populated by keys out of firmware. However, at the moment pseries firmware doesn't have any mechanism to expose trusted keys (this will change with the full key management solution!), so nothing ends up in .platform. So we want to get a key into the .ima keychain instead. IMA_X509_PATH purports to achieve this, but unfortunately just setting it isn't quite sufficient. The key will only be loaded into the .ima keychain if it's signed by a key already trusted by the kernel, that is, in .builtin_trusted_keys. (I discovered recently that it's also possible to load a key into .ima at runtime with keyctl, so loading the key as part of the kexec scripts could be an alternative. However, this also requires that the key being loaded into .ima be trusted by the kernel.) So, what I think I need is: - the key that signs the kernel on the filesystem so that it can be loaded by IMA_X509_PATH or keyctl. - the CA key that signs the kernel-signing key to be trusted by the kernel by being included in the .pem file that gets loaded by CONFIG_SYSTEM_TRUSTED_KEYS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906250] Comment bridged from LTC Bugzilla
--- Comment From s...@de.ibm.com 2020-12-17 09:42 EDT---
The build of the cross-packages is not finished yet:
https://launchpad.net/ubuntu/+source/cross-toolchain-base/43ubuntu3.1
See "Builds"
Focal: (Icon: currently building) amd64
But I had a look into glibc 2.31-0ubuntu9.2 source package
and recognized Florians patch:
debian/ubuntu/git-elf-Add-endianness-markup-to-ld.so.cache-bug-27008.patch
But compared to upstream, elf/dl-cache.c:_dl_load_cache_lookup():
if (file != MAP_FAILED && cachesize > sizeof *cache_new
&& memcmp (file, CACHEMAGIC_VERSION_NEW,
sizeof CACHEMAGIC_VERSION_NEW - 1) == 0)
### Missing the "Check for corruption, avoiding overflow." here. ###
{
if (! cache_file_new_matches_endian (file))
{
This check was introduced in a different patch. See my former comment:
On glibc upstream > glibc-2.31 && < glibc-2.32,
there is the following commit which adds a further check for corruption,
avoiding overflow:
"ld.so: Check for new cache format first and enhance corruption check"
https://sourceware.org/git/?p=glibc.git;a=commit;h=e221c512c74ec42fd47b71de2981a475b38110a4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906250
Title:
Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using
qemu-s390x on x86_64.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1906250/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904419] Comment bridged from LTC Bugzilla
--- Comment From s...@de.ibm.com 2020-12-17 08:50 EDT--- I've updated to libc6/groovy-proposed,now 2.32-0ubuntu3.1 (s390x and amd64) and have successfully run the strace-testsuite (especially ipc_msg/ipc_shm tests), glibc-tests which were added by the mentioned commits and the test attached to glibc-Bugzilla 26636 for 64bit and -m32 / -m31. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904419 Title: Upgrade glibc 2.32 by required upstream patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903341] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-16 06:58 EDT--- IBM Bugzilla status->closed, Fix Released with all requested distros -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903341 Title: Partitions of a DASD (that is passed as virtio-block device to a KVM guest) are not recognized with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908371] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-16 04:08 EDT--- For 2.12 patch 2nd is not needed because the prerequisit is not there... So the following patches should be applied: 2.14: (1) https://github.com/ibm-s390-tools/s390-tools/commit/fa7a4dafa3d89b2e8787de102e4362e895d44b05 (2) https://github.com/ibm-s390-tools/s390-tools/commit/aa8c2945cc7b047c626e75817c6a3e3924413023 (3) https://github.com/ibm-s390-tools/s390-tools/commit/6802b86414b48c4f118da09c7bf7ee142a459fa0 2.12: (1) https://github.com/ibm-s390-tools/s390-tools/commit/fa7a4dafa3d89b2e8787de102e4362e895d44b05 (2) - (3) https://github.com/ibm-s390-tools/s390-tools/commit/6802b86414b48c4f118da09c7bf7ee142a459fa0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908371 Title: [UBUNTU 20.04] - zipl command doesn't work correctly with -M option (s390utils/s390-tools?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908371] [NEW] [UBUNTU 20.04] - zipl command doesn't work correctly with -M option (s390utils/s390-tools?)
Public bug reported:
Zipl command doesn't work correctly with -M option.
There is an error at preparing of multi-volume dump taking because of Bus-ID
for 1st disk partition listed in file dump_conf (DEVLIST) isn't found. At the
same time LSDASD command shows this Bus-ID and ZIPL command with -d option
works correctly.
[root@t8375009 ~]# lsdasd
Bus-IDStatusName Device Type BlkSz Size Blocks
0.0.2c58 activedasda 94:0ECKD 4096 21129MB 5409180
0.0.2c5b activedasdb 94:4ECKD 4096 21129MB 5409180
0.0.2c59 activedasdc 94:8ECKD 4096 21129MB 5409180
0.0.2c5a activedasdd 94:12 ECKD 4096 21129MB 5409180
[root@t8375009 ~]#
[root@t8375009 ~]# systemctl stop kdump.service
[root@t8375009 ~]# lsdasd | tail -n +5 | awk '{ print "/dev/" $3 "1" }' >
dump_conf
[root@t8375009 ~]# cat dump_conf
/dev/dasdc1
/dev/dasdd1
[root@t8375009 ~]# zipl -M dump_conf
Error: Could not find bus-ID for '/dev/dasdc1'
[root@t8375009 ~]#
[root@t8375009 ~]# zipl -d /dev/dasdc1
Dump target: partition '/dev/dasdc1' with a size of 21129 MB.
Warning: All information on partition '/dev/dasdc1' will be lost!
Do you want to continue creating a dump partition (y/n)?yes
Done.
[root@t8375009 ~]#
[root@t8375009 ~]# zipl -M dump_conf
Error: Could not find bus-ID for '/dev/dasdc1'
---Steps to Reproduce---
[root@t8375009 ~]# lsdasd | tail -n +5 | awk '{ print "/dev/" $3 "1" }' >
dump_conf
[root@t8375009 ~]# cat dump_conf
/dev/dasdc1
/dev/dasdd1
[root@t8375009 ~]# zipl -M dump_conf
Stack trace output:
no
Oops output:
Error: Could not find bus-ID for '/dev/dasdc1'
System Dump Info:
The system is not configured to capture a system dump.
Fix provided upstream with
https://github.com/ibm-s390-tools/s390-tools/releases/tag/v2.15.1
Commits:
https://github.com/ibm-s390-tools/s390-tools/commit/fa7a4dafa3d89b2e8787de102e4362e895d44b05
https://github.com/ibm-s390-tools/s390-tools/commit/aa8c2945cc7b047c626e75817c6a3e3924413023
https://github.com/ibm-s390-tools/s390-tools/commit/6802b86414b48c4f118da09c7bf7ee142a459fa0
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-187221 severity-medium
targetmilestone-inin2004
** Tags added: architecture-s39064 bugnameltc-187221 severity-medium
targetmilestone-inin2004
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908371
Title:
[UBUNTU 20.04] - zipl command doesn't work correctly with -M option
(s390utils/s390-tools?)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908371/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908280] [NEW] Ubuntu 20.04: scapy fails to load BPF program
Public bug reported:
The scapy sniff() function loads a BPF program into the kernel which apparently
fails to load on s390x (Ubuntu 20.04).
Contact Information = Alexander Schmidt
---uname output---
Linux pok1-qz1-sr1-rk011-s21 5.4.0-51-generic #56-Ubuntu SMP Mon Oct 5 14:25:32
UTC 2020 s390x s390x s390x GNU/Linux
Machine Type = 8562
---Steps to Reproduce---
root@e4943f38d89b:/# cat /bin/tlb.py
#!/usr/bin/env python
import argparse
from scapy.all import scapy, sniff, Ether, IP, TCP
def tlb_sniff_cb(dip, dport):
def send_pkt_to_target_vm(x):
x[Ether].src = x[Ether].dst
x[Ether].dst = None
del x[IP].chksum
x[IP].dst = dip
if x.haslayer(TCP):
del x[TCP].chksum
x[TCP].dport = dport
scapy.sendrecv.sendp(x)
return send_pkt_to_target_vm
def main():
parser = argparse.ArgumentParser(description="TLB Simulator")
parser.add_argument("dip", help="IP address of the target VM")
parser.add_argument("dport", type=int, help="Dst port")
parser.add_argument("lport", type=int, help="lb listener port")
args = parser.parse_args()
sniff(filter="dst port " + str(args.lport),
prn=tlb_sniff_cb(args.dip, args.dport))
if __name__ == "__main__":
main()
root@e4943f38d89b:/# python /bin/tlb.py 191.168.100.100 81 2001
Traceback (most recent call last):
File "/bin/tlb.py", line 33, in
main()
File "/bin/tlb.py", line 29, in main
sniff(filter="dst port " + str(args.lport), prn=tlb_sniff_cb(args.dip,
args.dport))
File "/usr/lib/python2.7/dist-packages/scapy/sendrecv.py", line 731, in sniff
*arg, **karg)] = iface
File "/usr/lib/python2.7/dist-packages/scapy/arch/linux.py", line 578, in
__init__
attach_filter(self.ins, filter, iface)
File "/usr/lib/python2.7/dist-packages/scapy/arch/linux.py", line 165, in
attach_filter
s.setsockopt(socket.SOL_SOCKET, SO_ATTACH_FILTER, bp)
File "/usr/lib/python2.7/socket.py", line 229, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 22] Invalid argument
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
*Additional Instructions for Alexander Schmidt:
-Attach sysctl -a output output to the bug.
Upstream is fixed:
https://github.com/secdev/scapy/commit/474eb1f6930601e444227445f9e315b35c06a996.
It's a bit more complicated than s/int/ushort/, because that would break
FreeBSD.
This should be picked up by Canonical
** Affects: scapy (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-188965 severity-medium
targetmilestone-inin20041
** Tags added: architecture-s39064 bugnameltc-188965 severity-medium
targetmilestone-inin20041
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => scapy (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908280
Title:
Ubuntu 20.04: scapy fails to load BPF program
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/scapy/+bug/1908280/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905393] This is a debdiff for the Focal SRU
Default Comment by Bridge ** Attachment added: "This is a debdiff for the Focal SRU" https://bugs.launchpad.net/bugs/1905393/+attachment/5443865/+files/skiboot_6.5.2-1_6.5.2-1ubuntu0.20.04.1.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905393 Title: Ubuntu 20.04: opal-prd fails to start on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1905393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905393] This is a debdiff for the Groovy SRU
Default Comment by Bridge ** Attachment added: "This is a debdiff for the Groovy SRU" https://bugs.launchpad.net/bugs/1905393/+attachment/5443864/+files/skiboot_6.5.2-1_6.5.2-1ubuntu0.20.10.1.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905393 Title: Ubuntu 20.04: opal-prd fails to start on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1905393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907265] Re: [UBUNTU 21.04] s390/pci: vfio-pci mmio being disabled erroneously
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2104 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907265 Title: [UBUNTU 21.04] s390/pci: vfio-pci mmio being disabled erroneously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1907265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854148] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-15 08:28 EDT--- IBM Bugzilla status->closed. Fix Released for all requested distros -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854148 Title: [UBUNTU] openCryptoki: pkcsep11_migrate: Fix re-encryption of EP11 key blobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1854148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2020-12-14 19:40 EDT--- Hi, Thanks for your patience. I tested 5.10.0-8-generic. /boot/config-5.10.0-8-generic contains: # CONFIG_RCU_SCALE_TEST is not set It boots fine in a P9 kvm guest, both when loaded by kexec and when loaded by grub. There is no secure-boot in these tests. Please let me know if you need anything else. Kind regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904585] Comment bridged from LTC Bugzilla
--- Comment From hegdevas...@in.ibm.com 2020-12-14 06:24 EDT--- (In reply to comment #11) > Excellent. > > Finally Can you verify the latest update for bionic and xenial on this ppa. > Once confirmed we should be able to formally release everything Looks good. > > Also in preparation for the SRU, it is required to have some steps to > reproduce the problem and explain how to confirm it is resolved, Can you > provide me those steps? This is bit tricky to verify on customer environment. In lab we inject errors and verify whether memory offlining worked fine or not, and also verify whether it created forked processor or not. -Vasant -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904585 Title: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905393] Comment bridged from LTC Bugzilla
--- Comment From hegdevas...@in.ibm.com 2020-12-14 06:20 EDT--- (In reply to comment #10) > Created attachment 146860 [details] > skiboot_6.6.2-1_6.6.2-1ubuntu1.diff > > default comment Looks good. -Vasant -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905393 Title: Ubuntu 20.04: opal-prd fails to start on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1905393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904419] Re: Upgrade glibc 2.32 by required upstream patches
--- Comment From s...@de.ibm.com 2020-12-11 10:43 EDT--- It has nothing to do with a performance improvement. It's just broken. Thus your Ubuntu 20.10 has a regression compared to Ubuntu 20.04! The issues were reported via glibc-upstream bugzillas: - "Bug 26636 - 32-bit shmctl(IPC_INFO) crashes when shminfo struct is at the end of a memory mapping ": ... Compile attached test program: gcc -m32 -o ~/tmp/test ~/tmp/test.c It should print something like "max=2147483647". With the above glibc commit, it crashes. ... This causes an rr test failure: https://github.com/mozilla/rr/issues/2681 - "Bug 26639 - msgctl IPC_INFO and MSG_INFO return garbage " Starting with commit glibc-2.31.9000-687-g3283f71113 aka glibc-2.32~83, both IPC_INFO and MSG_INFO commands of msgctl return garbage because their argument of type "struct msginfo" is converted using kmsqid64_to_msqid64. This bug was found by strace test suite. - "Bug 26637 - semctl SEM_STAT_ANY fails to pass the buffer specified by the caller to the kernel" The kernel receives garbage instead of union semun.buf address specified by the caller. ... (As Dimitry has reported this bug on the same day as Bug 26639, I assume he also found it by strace test suite.) The glibc-commits have added new testcaes which are run with "make check" while building the libc6 package. I assume you are monitoring those testfails. ** Bug watch added: github.com/mozilla/rr/issues #2681 https://github.com/mozilla/rr/issues/2681 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904419 Title: Upgrade glibc 2.32 by required upstream patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877089] Comment bridged from LTC Bugzilla
--- Comment From thorsten.di...@de.ibm.com 2020-12-11 03:37 EDT--- Hi Dimitri, now I understood. As mentioned in LP1876715 (LTC 185713) in my last recent comments, the naming problem is fixed with zfcpdump-kernel 5.4-0ubuntu1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877089 Title: zfcpdump kernel can not be IPLed, wrong file name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876715] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1877089 *** https://bugs.launchpad.net/bugs/1877089 --- Comment From thorsten.di...@de.ibm.com 2020-12-11 03:34 EDT--- Version of zfcpdump-kernel is 5.4-0ubuntu1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876715 Title: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1876715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904419] Comment bridged from LTC Bugzilla
--- Comment From s...@de.ibm.com 2020-12-11 03:37 EDT--- Yes you are right, in this case send_dg() from glibc is not invoked. Thus from my side, you can exclude commit "resolv: Handle transaction ID collisions in parallel queries (bug 26600)" for groovy. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904419 Title: Upgrade glibc 2.32 by required upstream patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904585] Comment bridged from LTC Bugzilla
--- Comment From hegdevas...@in.ibm.com 2020-12-11 00:22 EDT--- (In reply to comment #9) > Excellent, Can you also validate the solution for groovy and focal from this > ppa? Looks good. -Vasant -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904585 Title: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905393] Comment bridged from LTC Bugzilla
--- Comment From hegdevas...@in.ibm.com 2020-12-11 00:22 EDT--- (In reply to comment #7) > Excellent, Can you also validate the solution for groovy and focal from this > ppa? Looks good. -Vasant -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905393 Title: Ubuntu 20.04: opal-prd fails to start on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1905393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877089] Comment bridged from LTC Bugzilla
--- Comment From thorsten.di...@de.ibm.com 2020-12-10 13:43 EDT--- I updated to https://launchpad.net/ubuntu/focal/+queue?queue_state=3_text=zfcpdump-kernel as of focal-proposed. Then I zipled the SCSI dump LUN: root@t35lp25:~# zipl -d /dev/disk/by-id/scsi-36005076303ffd3274609-part1 Building bootmap directly on partition '/dev/disk/by-id/scsi-36005076303ffd3274609-part1' Adding dump section kernel image..: /lib/s390-tools/zfcpdump/zfcpdump-image kernel parmline...: 'root=/dev/ram0 dump_mem=1 possible_cpus=1 cgroup_disable=memory ' component address: heap area...: 0x2000-0x5fff stack area..: 0xf000-0x internal loader.: 0xa000-0xdfff parameters..: 0x9000-0x91ff kernel image: 0x0001-0x001b7fff parmline: 0x001b8000-0x001b81ff Preparing boot device: sdi. Done. ... and dumped from LUN with secure boot enabled. But it still shows the same symptom: ... Running 'ZBootLoader' version '2.1.4' level 'D41C.D41C_0020'. MLOLOA6269064E Secure IPL: There are no signed components available on device HB A=0.0.1800, WWPN=500507630309D327, LUN=40464009. IPL failed (110). I zipled again with additional switch --secure=1, but that didn't help either. Please change the tag to verification-failed-focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877089 Title: zfcpdump kernel can not be IPLed, wrong file name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876715] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1877089 *** https://bugs.launchpad.net/bugs/1877089 --- Comment From thorsten.di...@de.ibm.com 2020-12-10 13:33 EDT--- Still not fixed with focal updates as of 2020-12-10. Then I updated to https://launchpad.net/ubuntu/focal/+queue?queue_state=3_text=zfcpdump-kernel as of focal-proposed. Found /lib/s390-tools/zfcpdump/zfcpdump-image with its correct name on the correct place. Waiting for release into focal-updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876715 Title: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1876715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904419] Re: Upgrade glibc 2.32 by required upstream patches
--- Comment From s...@de.ibm.com 2020-12-10 10:23 EDT--- The sysvipc related bugs were introduced with glibc 2.32 and are fixed upstream and will be included in upcoming glibc 2.33 release. In addition those commits were also cherry-picked to the release/2.32/master branch. Therefore no updates required for focal. As mentioned earlier, the hirsute libc6 2.32-0ubuntu5 package contains those commits (see debian/patches/git-updates.diff). Only the groovy libc6 2.32-0ubuntu3 package is affected. Those bugs are observable with the strace testsuite or the rr testsuite: commit "sysvipc: Fix IPC_INFO and SHM_INFO handling [BZ #26636]" (https://sourceware.org/git/?p=glibc.git;a=commit;h=0b9460d22e285432d232f42c7442a3226e1bf830) "Bug 26636 - 32-bit shmctl(IPC_INFO) crashes when shminfo struct is at the end of a memory mapping " (https://sourceware.org/bugzilla/show_bug.cgi?id=26636) commit "sysvipc: Fix IPC_INFO and MSG_INFO handling [BZ #26639]" (https://sourceware.org/git/?p=glibc.git;a=commit;h=c4aeedea598a1bd80f52ca9ebd07fe447680d491) "Bug 26639 - msgctl IPC_INFO and MSG_INFO return garbage " (https://sourceware.org/bugzilla/show_bug.cgi?id=26639) commit "sysvipc: Fix SEM_STAT_ANY kernel argument pass [BZ #26637]" (https://sourceware.org/git/?p=glibc.git;a=commit;h=9b139b6b81a5def91bec01f30301acc95fbf0289) "Bug 26637 - semctl SEM_STAT_ANY fails to pass the buffer specified by the caller to the kernel " (https://sourceware.org/bugzilla/show_bug.cgi?id=26637) The DNS lookup can be slow downed as the A and queries times out after 5s before retrying. This is fixed upstream and will be included in upcoming glibc 2.33 release and it is also cherry-picked to the release/2.32/master branch. As mentioned earlier, the hirsute libc6 2.32-0ubuntu5 package contains this commit (see debian/patches/git-updates.diff). commit "resolv: Handle transaction ID collisions in parallel queries (bug 26600)" (https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=2dfa659a66f20facc4082207884c20e986ddecee) "Bug 26600 - Transaction ID collisions cause slow DNS lookups in getaddrinfo" (https://sourceware.org/bugzilla/show_bug.cgi?id=26600) "Bug 1868106 - glibc: Transaction ID collisions cause slow DNS lookups in getaddrinfo" (https://bugzilla.redhat.com/show_bug.cgi?id=1868106) ** Bug watch added: Sourceware.org Bugzilla #26636 https://sourceware.org/bugzilla/show_bug.cgi?id=26636 ** Bug watch added: Sourceware.org Bugzilla #26639 https://sourceware.org/bugzilla/show_bug.cgi?id=26639 ** Bug watch added: Sourceware.org Bugzilla #26637 https://sourceware.org/bugzilla/show_bug.cgi?id=26637 ** Bug watch added: Sourceware.org Bugzilla #26600 https://sourceware.org/bugzilla/show_bug.cgi?id=26600 ** Bug watch added: Red Hat Bugzilla #1868106 https://bugzilla.redhat.com/show_bug.cgi?id=1868106 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904419 Title: Upgrade glibc 2.32 by required upstream patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907656] Comment bridged from LTC Bugzilla
--- Comment From mjros...@us.ibm.com 2020-12-10 10:05 EDT--- (In reply to comment #10) > This is in qemu 5.2 which I'm already working on for hirsute. > So -devel should be fixed soon (althrough testing on 5.2 will consume a few > days). > > Three questions for the following SRU as this was flagged for Focal and > Groovy as well. > > 1. How urgent/severe is it, do we need to move heaven and earth to get this > completed before the Christmas downtime or can this be SRU released in > January? No, this can be released in January. > > 2. I see you said for repro "kexec on an s390x guest with PCI devices". But > I'm sure you already have a script and or guest xmls and whatever else that > is related. Anything I don't have to come up from-scratch will make handling > this faster. > > 3. Do I need any special HW and/or configuration to achieve "s390x guest > with PCI devices" like real PCI ?!? - or is it enough to try to force e.g. > virtio-net-pci in? Again sample XMls and commands will help. The issue was originally hit with vfio-pci passthrough (which would indeed require special hardware), but can also be recreated using emulated devices such as virtio-net-pci. I just did so on focal using an XML entry that looks like this for a guest: I will also attach a minimal guest XML entry that I used, you should be able to re-use just this with a different boot disk. I don't have a script, but the process to reproduce is short and straightforward: 1) start the guest with the virtio-net-pci device 2) In the guest, 'lspci' to view the available PCI devices, you should see: 0001:00:00.0 Ethernet controller: Red Hat, Inc. Virtio network device 3) In the guest, kexec to a different kernel, example: kexec -l /path/to/image --initrd=/path/to/initrd --append="$(cat /proc/cmdline)" kexec -e 4) lspci after to view the available PCI devices - this time, there will be none listed; reboot of the guest is required to restore PCI devices. With the fix applied, lspci would show the same results as in step 2 above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907656 Title: [UBUNTU 21.04] s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1907656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907656] Sample Guest XML
--- Comment (attachment only) From mjros...@us.ibm.com 2020-12-10 10:07 EDT--- ** Attachment added: "Sample Guest XML" https://bugs.launchpad.net/bugs/1907656/+attachment/5442524/+files/kexec-test.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907656 Title: [UBUNTU 21.04] s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1907656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892367] Comment bridged from LTC Bugzilla
--- Comment From vineeth.vija...@ibm.com 2020-12-10 08:39 EDT--- Unfortunately .defval="1" functionality doesnt work for this case. Instead, what we do is, we modify the root_check() function in root.c,such a way that, the required functionality of zdev:early=1 is enabled by default, based on a MACRO. The new MACRO will be build-time configurable, which will then be used by Canonical while building the chzdev. The patch is being developed and will push to s390-tools upstream once it is ready. Which can then be used by Canonical. So, we dont need a Canonical-only change in the code; But the change is only the MACRO- definition passed during the build-time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892367 Title: [UBUNTU 20.04] udev rule change did not get applied To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2020-12-10 08:44 EDT--- Hi, We've had some good progress with debugging upstream: https://lore.kernel.org/lkml/20201209202732.5896-1-ure...@gmail.com/t/#u fixes the issue properly. Would you prefer to take that and leave the config unchanged? It'll almost certainly end up in stable trees soon anyway... Kind regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854148] Comment bridged from LTC Bugzilla
--- Comment From jschm...@de.ibm.com 2020-11-26 04:03 EDT--- Verified successfully on 18.04.5 LTS: # pkcsep11_migrate -slot 4 -adapter 16 -domain 76 Using slot #4... Enter the USER PIN: Card ID 0x10, domain ID 76 has committed pending(next) WK going to reencrpyt key 0 with blob len 240: 'myeckey' reencryption success obj: 0 myeckey: going to reencrpyt key 1 with blob len 970: 'myrsakey' reencryption success obj: 1 myrsakey: going to reencrpyt key 2 with blob len db: 'myeckey' reencryption success obj: 2 myeckey: going to reencrpyt key 3 with blob len 1a6: 'myrsakey' reencryption success obj: 3 myrsakey: all keys successfully reencrypted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854148 Title: [UBUNTU] openCryptoki: pkcsep11_migrate: Fix re-encryption of EP11 key blobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1854148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907656] [NEW] [UBUNTU 21.04] s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset
Public bug reported: Description: s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset Symptom: PCI devices are unavailable after a subsystem reset Problem: When a subsystem reset event occurs (e.g. via kexec) PCI devices are not being reset and are therefore in an unexpected state when the guest attempts to enable them again after the subsystem reset. This results in the devices being unavailable to the guest until a reboot. Solution: Add the s390 PCI host bridge to the list of devices to be reset during a subsystem reset event Reproduction: kexec on an s390x guest with PCI devices db08244a3a7e s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset This fix need to be applied to qemu for focal (20.04) and groovy (20.10). ** Affects: qemu (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-190224 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-190224 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => qemu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907656 Title: [UBUNTU 21.04] s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1907656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903817] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-10 04:58 EDT--- IBM Bugzilla status->closed, Fix Released with hirsuite -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903817 Title: Clustalo 1.2.4-6 segfaults on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904585] Comment bridged from LTC Bugzilla
--- Comment From hegdevas...@in.ibm.com 2020-12-10 02:01 EDT--- (In reply to comment #7) > Hello, > I've uploaded a new version of skiboot for hirsute to this ppa > ppa:mclemenceau/distro-work > Can you confirm this resolve the issue on this LP and I'll start release > process for hirsute and other impacted series > Thanks > Matthieu Looks good. -Vasant -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904585 Title: opal-prd: Have a worker process handle page offlining (Fixes "PlatServices: dyndealloc memory_error() failed" is getting reported in error log (opal-prd)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905393] Comment bridged from LTC Bugzilla
--- Comment From hegdevas...@in.ibm.com 2020-12-10 01:17 EDT--- (In reply to comment #5) > Hello, > I've uploaded a new version of skiboot for hirsute to this ppa > ppa:mclemenceau/distro-work > Can you confirm this resolve the issue on this LP and I'll start release > process for hirsute and other impacted series > Thanks > Matthieu Looks good. Thanks! -Vasant -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905393 Title: Ubuntu 20.04: opal-prd fails to start on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1905393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892824] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-09 08:56 EDT--- IBM Bugzilla status->closed, Fix Released with hirsuite -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892824 Title: [21.04 FEAT] NVMe stand-alone dump support - s390-tools part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1892824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825343] Comment bridged from LTC Bugzilla
--- Comment From ar...@de.ibm.com 2020-12-09 08:09 EDT--- The Valgrind z14 support is upstream now: https://sourceware.org/git/?p=valgrind.git;a=commit;h=159f132289160ab1a5a5cf4da14fb57ecdb248ca -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825343 Title: [21.04 FEAT] Valgrind add new hardware support for z Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1825343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907421] [NEW] [UBUNTU 21.04] vfio: pass DMA availability information to userspace
Public bug reported: Description: vfio: pass DMA availability information to userspace Symptom: vfio-pci device on s390 enters error state Problem: Commit 492855939bdb added a limit to the number of concurrent DMA requests for a vfio container. However, lazy unmapping in s390 can in fact cause quite a large number of outstanding DMA requests to build up prior to being purged, potentially the entire guest DMA space. This results in unexpected errors seen in qemu such as 'VFIO_MAP_DMA failed: No space left on device' Solution: The solution requires a change to both kernel and qemu - For the kernel, add the ability to provide the number of allowable DMA requests via the VFIO_IOMMU_GET_INFO ioctl. Reproduction: Put a vfio-pci device on s390 under I/O load Upstream-ID: a717072007e8aedd3f951726d8cf55454860b30d 7d6e1329652ed971d1b6e0e7bea66fba5044e271 Need also to be integrated into 20.10 and 20.04. OK, just to clarify we don't need to fix bionic for this one, but rather focal (20.04) and groovy (20.10). Furthermore, for 20.04, 20.10 and 21.04 ONLY commit 7d6e1329652ed971d1b6e0e7bea66fba5044e271 is needed, the other was a pre-req that is already present. ** Affects: ubuntu-z-systems Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-190211 severity-high targetmilestone-inin2104 ** Tags added: architecture-s39064 bugnameltc-190211 severity-high targetmilestone-inin2104 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907421 Title: [UBUNTU 21.04] vfio: pass DMA availability information to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1907421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907265] Comment bridged from LTC Bugzilla
--- Comment From mjros...@us.ibm.com 2020-12-08 17:39 EDT--- Thanks! I tested the provided focal build and was able to verify that it resolves the issue. Re: groovy -- Sorry, my mistake I was not looking at the latest versions of groovy/focal when listing which patches needed backporting. I did also just now verify your assertion that this issue is already resolved in the latest groovy as well, so thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907265 Title: [UBUNTU 21.04] s390/pci: vfio-pci mmio being disabled erroneously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1907265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907265] [NEW] [UBUNTU 21.04] s390/pci: vfio-pci mmio being disabled erroneously
Public bug reported: Description: s390/pci: vfio-pci mmio being disabled erroneously Symptom: PCI virtual functions passed through via vfio-pci are unusable Problem: The fix for CVE-2020-12888 'abafbc551fdd vfio-pci: Invalidate mmaps and block MMIO access on disabled memory' introduced an issue which prevented PCI Virtual Functions from being passed- through via vfio-pci as VFs are not allowed to have the PCI_COMMAND_MEMORY bit enabled per spec. This issue was initially thought to be fixed via 'ebfa440ce38b vfio/pci: Fix SR-IOV VF handling with MMIO blocking' which removes the PCI_COMMAND_MEMORY requirement for VFs but this did not solve the issue for virtual functions on s390 that are first passed through to an LPAR without their associated physical function as they are not identified as VFs in the traditional sense (there is no PF available to the host kernel to link to). As a result, when passing these devices through to a guest via vfio-pci, these devices do not trigger the check added by ebfa440ce38b which results in MMIO access from the guest being blocked because the PCI_COMMAND_MEMORY bit is off. Solution: Identify devices beyond traditional linked VFs that vfio must consider memory-enabled. Reproduction: Pass a PCI Virtual Function to a qemu-kvm guest via vfio-pci Upstream-ID: 12856e7acde4702b7c3238c15fcba86ff6aa507f 08b6e22b850c28b6032da1e4d767a33116e23dfb 515ecd5368f1510152fa4f9b9ce55b66ac56c334 These patches need to be applied for 20.10 and 20.04. The git-commits will apply cleanly on the dedicated kernels. Manx thx ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-190039 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-190039 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907265 Title: [UBUNTU 21.04] s390/pci: vfio-pci mmio being disabled erroneously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-12-07 05:17 EDT--- (In reply to comment #23) > Could someone try to put the attached script into /etc/kernel/postinst.d and > let me know whether that make installkernel work? Thanks. I can confirm this works with installkernel and the previously described workflow on Ubuntu 20.04.1! Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2020-12-03 11:51 EDT--- There is not a mechanism to give direct access to this systems, we understand that this makes thing much more difficult but is another method of debug that we could use? like forcing a crash dump? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896575 Title: [UBUNTU 20.04] syslog daemon stop running unexpectedly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2020-12-02 12:13 EDT--- is it any update about this? We still have the issue, is there anything else that we could do to help this keep moving? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896575 Title: [UBUNTU 20.04] syslog daemon stop running unexpectedly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904884] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-02 08:27 EDT--- Verified -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904884 Title: s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865032] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-02 03:32 EDT--- IBM Bugzilla status->closed, Fix Released by all requested distros -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865032 Title: [UBUNTU] zipl/libc: Fix potential buffer overflow in printf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1865032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902254] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-02 03:36 EDT--- IBM Bugzilla status-> closed, Fix Released by Canonical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902254 Title: Bionic: btrfs: kernel BUG at /build/linux- eTBZpZ/linux-4.15.0/fs/btrfs/ctree.c:3233! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1902254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2020-12-01 23:08 EDT--- No worries, let me know if you'd like me to test another spin. We continue to look into the issue upstream: https://lore.kernel.org /linuxppc-dev/87eekfh80a@dja-thinkpad.axtens.net/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865032] Comment bridged from LTC Bugzilla
--- Comment From pr...@de.ibm.com 2020-12-01 12:25 EDT--- verified on bionic (zipl 2.3.0-build-20201124)and xenial (zipl 1.34.0-build-20201124) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865032 Title: [UBUNTU] zipl/libc: Fix potential buffer overflow in printf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1865032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902179] Comment bridged from LTC Bugzilla
--- Comment From jjhe...@us.ibm.com 2020-12-01 08:05 EDT--- (In reply to comment #74) > @Jason, seems to be some build failures. Can you please have a look. It looks like there are two versions of this patch applied: [PATCH] s390-tools: zipl: Fix NVMe partition and base device detection Not sure how this happened. Here is the compiler output: disk.c:174:12: error: redefinition of ?blkext_get_partnum? 174 | static int blkext_get_partnum(dev_t dev) |^~ disk.c:92:12: note: previous definition of ?blkext_get_partnum? was here 92 | static int blkext_get_partnum(dev_t dev) |^~ disk.c:199:12: error: redefinition of ?blkext_is_base_device? 199 | static int blkext_is_base_device(dev_t dev) |^ disk.c:117:12: note: previous definition of ?blkext_is_base_device? was here 117 | static int blkext_is_base_device(dev_t dev) |^ disk.c:213:12: error: redefinition of ?blkext_get_base_dev? 213 | static int blkext_get_base_dev(dev_t dev, dev_t *base_dev) |^~~ disk.c:131:12: note: previous definition of ?blkext_get_base_dev? was here 131 | static int blkext_get_base_dev(dev_t dev, dev_t *base_dev) |^~~ Can someone on Canonical's end manually verify this,and perhaps exclude the above patch from their build if it seems to already be present? I created the backport patches on top of the following repo/branch: git://git.launchpad.net/ubuntu/+source/s390-tools focal-proposed And on this branch, this patch was missing, which is why I included it here. Was I using the wrong repo/branch for this backport? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902179 Title: [20.04 FEAT] Support/enhancement of NVMe IPL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1902179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904884] Comment bridged from LTC Bugzilla
--- Comment From geral...@de.ibm.com 2020-12-01 09:14 EDT--- Verified -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904884 Title: s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903682] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-12-01 08:55 EDT--- (In reply to comment #19) > Well, that's a pity, because it means that a manual kernel SRU is needed now. > It's needed to make sure that someone who has the fix in focal and upgrades > to groovy will not run into a regression situation. > > I think the 'plan' for hirsute is still 5.11 - but it of course depends a > lot on upstream. > For the interim (aka non-LTS releases) we are not that super keen on LTS > kernels, since interim releases are only supported for up to 9 month anyway > and we want to offer the latest goodies (the story is of course different > for LTS releases though). :-( yeah.. On the bright side I have just verified that this is working now in focal proposed. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903682 Title: NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903682] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-12-01 06:51 EDT--- Ahh, got it 5.8 stable is already EOL according to https://www.kernel.org/ By the way, is the plan for 21.04 LTS still to go with v5.11, seeing as Greg announced that v5.10 will be the next long term stable kernel, picking 5.11 seems a little less ideal. I'd think it might be easier and give better quality if an the Ubuntu LTS coincides with one of Greg's longterm stable kernels. Then again, personally I have 2 tiny NVMe driver cleanups queued for 5.11 and those would be my first actual changes to run on almost all architectures (besides a tiny SR-IOV change but people don't have that on their laptops :D). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903682 Title: NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903682] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-12-01 06:43 EDT--- (In reply to comment #16) > Hi Niklas, > I found the ticket upstream accepted with hash 0b2ca2c7d0c9 > and the provenance in 'git show 0b2ca2c7d0c9' mentions: > Cc: # 5.8 > So I'm expecting that in 5.8 (rather than in 5.9) stable - and 5.8 is the > kernel used in groovy/20.10. > So I was looking - and couldn't find the patch - in 5.8 stable yet. Good point, I only got Greg's mail about inclusion in 5.9 stable... hmm let me see if I can find out why it's not in 5.8 stable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903682 Title: NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867118] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-01 05:26 EDT--- IBM Bugzilla status->closed, Fix Released by all requested distros -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867118 Title: dasd_fba io error and kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896216] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-01 05:27 EDT--- IBM Bugzilla status->closed, Fix Released by all requested distros -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896216 Title: [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906384] lvm.conf file
Default Comment by Bridge ** Attachment added: "lvm.conf file" https://bugs.launchpad.net/bugs/1906384/+attachment/5439973/+files/lvm.conf.1120 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906384 Title: [UBUNTU 18.04] lvm boot failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906384] console-log during boot
Default Comment by Bridge ** Attachment added: "console-log during boot" https://bugs.launchpad.net/bugs/1906384/+attachment/5439972/+files/isvcl1-cons2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906384 Title: [UBUNTU 18.04] lvm boot failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906384] [NEW] [UBUNTU 18.04] lvm boot failure
Public bug reported: ---Problem Description--- boot failure with LVM root disk ---uname output--- 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:07:52 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = 8561 LT1 ---System Hang--- Boot failure with LVM root disk and enter emergency shell ---Debugger--- A debugger is not configured ---Steps to Reproduce--- boot the system *Additional Instructions for Chee Ye/y...@cn.ibm.com: -Attach: /proc/partitions /proc/mounts/ /etc/lvm/lvm.conf dmsetup ls dmsetup table dmsetup targets dmsetup version lvm version During boot, got below error message and then entered emergency shell. I am attaching part of the console log from HMC. "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah be" "cause device was seen first." "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah be" "cause device was seen first." "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah be" "cause device was seen first." "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 be" "cause device was seen first." "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 be" "cause device was seen first." "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 be" "cause device was seen first." "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn be" "cause device was seen first." "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn be" "cause device was seen first." "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn be" "cause device was seen first." "Cannot activate LVs in VG ISVCL1-vg while PVs appear on duplicate devices." done. "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: error opening /dev/md?*: No such file or directory" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" done. "Gave up waiting for root file system device. Common problems:" "- Boot args (cat /proc/cmdline)" "- Check rootdelay= (did the system wait long enough?)" "- Missing modules (cat /proc/modules; ls /dev)" "chvt: can't open console" "ALERT! /dev/mapper/ISVCL1--vg-root does not exist. Dropping to a shell!" "Couldn't get a file descriptor referring to the console" "/scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o" "r address" "/scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or" address "/scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or" address "/scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or" address "/scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or" address "/scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or" address "/scripts/panic/console_setup: line 1: can't open
[Bug 1903682] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-12-01 04:45 EDT--- @Frank Heinz-Werner said you had trouble finding the upstream stable commit for this. The original upstream commit is 0b2ca2c7d0c9e2731d01b6c862375d44a7e13923 s390/pci: fix hot-plug of PCI function missing bus This was pulled into 5.9 stable as part of the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable- queue.git/commit/?id=c7a8c5e06c4e554a91eeb2df5202e56a9e2acd83 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903682 Title: NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896726] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-01 04:29 EDT--- IBM Bugzilla status->closed, Fix Released by all requested Distros -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896726 Title: [UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic page table folding issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899582] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-01 04:31 EDT--- IBM Buzgilla status->closed, Fix Released by all requested distros -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899582 Title: ceph: fix inode number handling on arches with 32-bit ino_t To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1899582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902870] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-11-30 07:50 EDT--- For addl. info only: https://linux-on-z.blogspot.com/2020/11/new-release-qclib-v221.html https://github.com/ibm-s390-tools/qclib. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902870 Title: [21.04 FEAT] Upgrade qclib to latest version ( at least version 2.2.1 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1902870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904899] Re: pixel color access delivers wrong data on s390x (e.g., tests/color_test.py)
--- Comment From heinz-werner_se...@de.ibm.com 2020-11-30 07:41 EDT--- IBM Bugzilla status-> closed, Fix Released by Canonical ** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2010 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904899 Title: pixel color access delivers wrong data on s390x (e.g., tests/color_test.py) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wand/+bug/1904899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904899] Re: pixel color access delivers wrong data on s390x (e.g., tests/color_test.py)
** Tags added: architecture-s3903164 bugnameltc-190018 severity-low targetmilestone-inin--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904899 Title: pixel color access delivers wrong data on s390x (e.g., tests/color_test.py) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wand/+bug/1904899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906255] [NEW] [UBUNTU 20.10] Applications runing in QEMU/KVM get translation faults
Public bug reported:
commit 0b0ed657fe ("s390: remove critical section cleanup from entry.S")
introduced a problem where FPU registers were not properly restored when
entering SIE. This leads to crashes of applications runnning inside kvm,
as most of the programs in use nowdays are using FPU registers for
backing of general register content.
Fix is upstream:
author Sven Schnelle 2020-11-20 14:17:52 +0100
committer Heiko Carstens 2020-11-23 11:52:13
+0100
commit 1179f170b6f0af7bb0b3b7628136eaac450ddf31 (patch)
tree19e8acb64e0968b41de4899cc1315c41b002839e /arch/s390/kernel/entry.S
parent 78d732e1f326f74f240d416af9484928303d9951 (diff)
downloadlinux-1179f170b6f0af7bb0b3b7628136eaac450ddf31.tar.gz
s390: fix fpu restore in entry.S
We need to disable interrupts in load_fpu_regs(). Otherwise an
interrupt might come in after the registers are loaded, but before
CIF_FPU is cleared in load_fpu_regs(). When the interrupt returns,
CIF_FPU will be cleared and the registers will never be restored.
The entry.S code usually saves the interrupt state in __SF_EMPTY on the
stack when disabling/restoring interrupts. sie64a however saves the pointer
to the sie control block in __SF_SIE_CONTROL, which references the same
location. This is non-obvious to the reader. To avoid thrashing the sie
control block pointer in load_fpu_regs(), move the __SIE_* offsets eight
bytes after __SF_EMPTY on the stack.
Cc: # 5.8
Fixes: 0b0ed657fe00 ("s390: remove critical section cleanup from entry.S")
Reported-by: Pierre Morel
Signed-off-by: Sven Schnelle
Acked-by: Christian Borntraeger
Reviewed-by: Heiko Carstens
Signed-off-by: Heiko Carstens
** Affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-189961 severity-critical
targetmilestone-inin---
** Tags added: architecture-s39064 bugnameltc-189961 severity-critical
targetmilestone-inin---
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906255
Title:
[UBUNTU 20.10] Applications runing in QEMU/KVM get translation faults
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1906255/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906250] [NEW] Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using qemu-s390x on x86_64.
Public bug reported:
---Problem Description---
On a x86_64 machine with Ubuntu 20.04, running a s390x (or ppc64) binary with
qemu leads to a segmentation fault in ld.so while lookup in /etc/ld.so.cache.
Contact Information = via bugzilla
---uname output---
Linux 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64 x86_64
x86_64 GNU/Linux
---Steps to Reproduce---
- apt-get install -y --no-install-recommends gcc-s390x-linux-gnu
libc6-dev-s390x-cross qemu-user
- apt list --installed "libc6*"
libc6/focal-updates,now 2.31-0ubuntu9.1 amd64 [installed,automatic]
libc6-s390x-cross/focal,focal,now 2.31-0ubuntu7cross1 all [installed,automatic]
...
- echo 'int main(void) { puts("Hello, world!"); }' | s390x-linux-gnu-gcc
-o helloworld-s390x -x c -
- qemu-s390x -strace -L /usr/s390x-linux-gnu ./helloworld-s390x
18392 brk(NULL) = 0x00403000
18392 uname(0x4000803402) = 0
18392 access("/etc/ld.so.preload",R_OK) = -1 errno=2 (No such file or directory)
18392 openat(AT_FDCWD,"/etc/ld.so.cache",O_RDONLY|O_CLOEXEC) = 3
18392 fstat(3,0x004000802720) = 0
18392 mmap(0x004000802648,65784,PROT_READ,MAP_PRIVATE,3,0x82d140) =
0x00400082e000
18392 close(3) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=1, si_addr=0x004300a6e000} ---
Segmentation fault (core dumped)
- qemu-s390x -L /usr/s390x-linux-gnu -g 12345 ./helloword-s390x
- gdb-multiarch ./helloword-s390x
target remote localhost:12345
c
Program received signal SIGSEGV, Segmentation fault.
0x00400081c572 in ?? ()
Dump of assembler code from 0x400081c500 to 0x400081c600:
...
0x00400081c564: l %r4,216(%r11)
0x00400081c568: agr %r10,%r1
0x00400081c56c: sllg%r10,%r10,3
=> 0x00400081c572: l %r1,52(%r10,%r6)
0x00400081c576: lgdr%r2,%f8
0x00400081c57a: algfr %r3,%r1
0x00400081c57e: clrjnh %r4,%r1,0x400081c5a0
0x00400081c584: brasl %r14,0x400081c290
This happens in /elf/dl-cache.c:_dl_load_cache_lookup():
ld.so.cache is mmaped with:
void *file = _dl_sysdep_read_whole_file (LD_SO_CACHE, , PROT_READ);
And this check is true:
if (file != MAP_FAILED && cachesize > sizeof *cache_new
&& memcmp (file, CACHEMAGIC_VERSION_NEW,
sizeof CACHEMAGIC_VERSION_NEW - 1) == 0)
{
cache_new = file;
cache = file;
}
The segmentation fault happens in SEARCH_CACHE macro which is also defined in
elf/dl-cache.c:
if (cache_new != (void *) -1)
{
...
SEARCH_CACHE (cache_new);
}
#define SEARCH_CACHE(cache)
...
left = 0;
right = cache->nlibs - 1;
middle = (left + right) / 2;
key = cache->libs[middle].key;
...
(gdb) p/x *((struct cache_file_new *) $r6)
$5 = {magic = {0x67, 0x6c, 0x69, 0x62, 0x63, 0x2d, 0x6c, 0x64, 0x2e, 0x73,
0x6f, 0x2e, 0x63, 0x61, 0x63, 0x68, 0x65}, version = {0x31, 0x2e,
0x31}, nlibs = 0x5e00, len_strings = 0x4813, unused = {0x0, 0x0,
0x0, 0x0, 0x0}, libs = 0x3fffdf00030}
(gdb) ptype cache_new
type = struct cache_file_new {
char magic[17];
char version[3];
uint32_t nlibs;
uint32_t len_strings;
uint32_t unused[5];
struct file_entry_new libs[0];
} *
As /etc/ld.so.cache is generated by x86_64 (little endian) code, we get
a huge number for nlibs on s390x (big endian).
The segfault happens while:
l %r1,52(%r10,%r6)
=> key = cache->libs[middle].key;
(gdb) i r r6
r6 0x3fffdf0 => cache_new
(gdb) p &(((struct cache_file_new *) $r6)->libs[0])
$17 = (struct file_entry_new *) 0x3fffdf00030
(gdb) p &(((struct cache_file_new *) $r6)->libs[0].key)
$18 = (uint32_t *) 0x3fffdf00034
=> 0x3fffdf00034 - 0x3fffdf0 = 0x34 = 52
On glibc upstream > glibc-2.31 && < glibc-2.32,
there is the following commit which adds a further check for corruption,
avoiding overflow:
"ld.so: Check for new cache format first and enhance corruption check"
https://sourceware.org/git/?p=glibc.git;a=commit;h=e221c512c74ec42fd47b71de2981a475b38110a4
I've recognized that the libc6-2.31-0ubuntu9.1 package contains the patch
debian/patches/any/submitted-ld.so-cache-new-format.diff
which already patches elf/dl-cache.c in _dl_load_cache_lookup().
Therefore the mentioned commit does not apply.
For testing, I've added this patch and just rebuild the libc6-s390x-cross
package:
cat glibc-ldsocache-corruption.diff
--- glibc-2.31/elf/dl-cache.c 2020-11-26 15:36:33.963032580 +0100
+++ glibc-2.31/elf/dl-cache.c 2020-11-26 15:39:13.866894100 +0100
@@ -202,13 +202,16 @@
PROT_READ);
/* We can handle three different cache file formats here:
+- only the new format
- the old libc5/glibc2.0/2.1 format
- the old format with the new format in it
-- only the new format
The following checks if the cache contains any of these formats. */
if (file != MAP_FAILED && cachesize > sizeof *cache_new
- && memcmp (file, CACHEMAGIC_VERSION_NEW,
- sizeof CACHEMAGIC_VERSION_NEW - 1) == 0)
+ &&
[Bug 1904906] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2020-11-25 21:40 EDT--- Ok, so sadly I cannot find a tarball with the patches not already applied, which is very frustrating. However, it turns out I don't need that because, as it turns out... Doing an upstream checkout of v5.10-rc4 and building with config-5.10.0-4-generic also fails to boot under qemu. Previously I hadn't tested upstream with a Canoni-config, so I thought it was an ubuntu-specific bug, which clearly it is not. Apologies about that. It also affects 5.10-rc5 and powerpc/fixes, so I'm trying to get some eyes on it internally. Kind regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2020-11-25 06:47 EDT--- Hi, Thanks, I'll look at sources tarball, hopefully tomorrow. (I'm in AU, so no thanksgiving here!) Have you tested this on any of your local systems? I can't get it to work much on P9, even on stock hardware/qemu without any secure-boot features. Indeed, it even fails on qemu TCG (so you don't actually need a Power system at all!): qemu-system-ppc64 -M pseries -m 1G -nographic -vga none -smp 4 -cpu power9 -kernel dbg/usr/lib/debug/boot/vmlinux-5.10.0-4-generic Actually, the failure matrix is really interesting: Power8 host + KVM + grub -> boots Power9 host bare metal (kexec) -> fails Power9 host + KVM + grub -> fails Power9 host + KVM + qemu -kernel -> boots qemu TCG + power9 cpu-> fails qemu TCG + power8 cpu-> fails I'm assuming the tarball includes the debian/patches directory, in which case it should be easy to apply and git bisect. Kind regards, Daniel (IBMers: is there someone outside the security team that we should pull in? It doesn't seem at all to be a security-related issue.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2020-11-25 00:34 EDT--- Hi, Looks like it fails to boot on a p9 qemu/kvm guest even out of grub: hangs trying to bring up SMP. That's probably what we saw in bare-metal too, the console probably just didn't catch up. I will continue investigating, but I'm not sure what kernel tree you're using: git://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/hirsute has something based on linux-5.8. What tree are you building from? Kind regards, Daniel Loading Linux 5.10.0-4-generic ... Loading initial ramdisk ... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 5.10.0-4-generic (buildd@bos02-ppc64el-008) (gcc (Ubuntu 10.2.0-17ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #5-Ubuntu SMP Mon Nov 16 09:41:59 UTC 2020 (Ubuntu 5.10.0-4.5-generic 5.10.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/boot/vmlinux-5.10.0-4-generic root=UUID=19b72275-8385-4e0e-8001-62baacf410e3 ro console=hvc0 earlyprintk xmon=rw Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0657 alloc_top: 1000 alloc_top_hi : 0004 rmo_top : 1000 ram_top : 0004 instantiating rtas at 0x0daf... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0658 -> 0x06580b32 Device tree struct 0x0659 -> 0x065a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0200 ... [0.00] radix-mmu: Page sizes from device-tree: [0.00] radix-mmu: Page size shift = 12 AP=0x0 [0.00] radix-mmu: Page size shift = 16 AP=0x5 [0.00] radix-mmu: Page size shift = 21 AP=0x1 [0.00] radix-mmu: Page size shift = 30 AP=0x2 [0.00] radix-mmu: Activating Kernel Userspace Execution Prevention [0.00] radix-mmu: Activating Kernel Userspace Access Prevention [0.00] radix-mmu: Mapped 0x-0x0200 with 2.00 MiB pages (exec) [0.00] radix-mmu: Mapped 0x0200-0x0004 with 2.00 MiB pages [0.00] lpar: Using radix MMU under hypervisor [0.00] Linux version 5.10.0-4-generic (buildd@bos02-ppc64el-008) (gcc (Ubuntu 10.2.0-17ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #5-Ubuntu SMP Mon Nov 16 09:41:59 UTC 2020 (Ubuntu 5.10.0-4.5-generic 5.10.0-rc4) [0.00] Secure boot mode disabled [0.00] Found initrd at 0xc470:0xc656fbfa [0.00] Using pSeries machine description [0.00] printk: bootconsole [udbg0] enabled [0.00] Partition configured for 24 cpus. [0.00] CPU maps initialized for 1 thread per core [0.00] - [0.00] phys_mem_size = 0x4 [0.00] dcache_bsize = 0x80 [0.00] icache_bsize = 0x80 [0.00] cpu_features = 0x0001c07b8f4f91a7 [0.00] possible= 0x000ffbfbcf5fb1a7 [0.00] always = 0x0003800081a1 [0.00] cpu_user_features = 0xdc0065c2 0xeff0 [0.00] mmu_features = 0xbc007441 [0.00] firmware_features = 0x0085455a445f [0.00] vmalloc start = 0xc008 [0.00] IO start = 0xc00a [0.00] vmemmap start = 0xc00c [0.00] - [0.00] numa: NODE_DATA [mem 0x3ffd24900-0x3ffd2bfff] [0.00] rfi-flush: fallback displacement flush available [0.00] count-cache-flush: flush disabled. [0.00] link-stack-flush: flush disabled. [0.00] stf-barrier: eieio barrier available [0.00] PCI host bridge /pci@8002000 ranges: [0.00] IO 0x2000..0x2000 -> 0x [0.00] MEM 0x20008000..0x2000 -> 0x8000 [0.00] MEM 0x2100..0x21ff -> 0x2100 [0.00] PPC64 nvram contains 65536 bytes [0.00] barrier-nospec: using ORI speculation barrier [0.00] Zone ranges: [0.00] Normal [mem 0x-0x0003] [0.00] Device empty [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x-0x0003] [0.00] Initmem setup node 0 [mem 0x-0x0003] [0.00] percpu: Embedded 11 pages/cpu s628760 r0 d92136 u720896 [0.00] Built 1 zonelists, mobility grouping on. Total pages: 261888 [0.00] Policy zone: Normal [0.00] Kernel command line:
[Bug 1905393] [NEW] Ubuntu 20.04: opal-prd fails to start on 20.04
Public bug reported: == Comment: #0 - VASANT HEGDE - 2020-11-23 23:23:22 == ---Problem Description--- opal-prd fails to start on 20.04 Contact Information = Vasant hegde ---uname output--- Ubuntu 20.04 Machine Type = All Power System ---Steps to Reproduce--- opal-prd fails to start on 20.04 Userspace tool common name: opal-prd The userspace tool has the following bit modes: 64bit Userspace rpm: opal-prd This is fixed in upstream by below commit. Please backport this patch to 20.04 LTS release. Also applicable for 20.10. commit 47005e8d4c9aeda5826c17c4a013cfbda1a3f2de Author: Georgy Yakovlev Date: Mon Oct 12 14:29:17 2020 -0700 opal-prd: handle devtmpfs mounted with noexec On systems using recent versions of systemd /dev (devtmpfs) is mounted with noexec option. Such mount prevents mapping HBRT image code region as RWX from /dev. This commit, as suggested in github PR linked below, attempts to work around the situation by copying HBRT image to anon mmaped memory region and sets mprotect rwx on it, allowing opal-prd to sucessfully execute the code region. Having memory region set as RWX is not ideal for security, but fixing that is a separate and hard to solve problem. Original code also mmaped region as RWX, so this PR does not make things worse at least. Closes: https://github.com/open-power/skiboot/issues/258 Signed-off-by: Georgy Yakovlev Reviewed-by: Vasant Hegde [oliver: whitespace fix, add a comment, reflow commit message] Signed-off-by: Oliver O'Halloran -Vasant ** Affects: ubuntu-power-systems Importance: Undecided Status: New ** Affects: opal (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-189959 severity-critical targetmilestone-inin20041 ** Tags added: architecture-ppc64le bugnameltc-189959 severity-critical targetmilestone-inin20041 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => opal (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905393 Title: Ubuntu 20.04: opal-prd fails to start on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1905393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2020-11-24 02:07 EDT--- Hi, Ok, I have been experimenting with the hirsute kernel: 5.10.0-4-generic #5-Ubuntu It boots without issue on a pseries guest with secure boot both on and off. However, this doesn't exercise booting out of kexec. Booting on a machine with no OS secure-boot support also fails coming out of kexec, so something is going wrong with kexec. I will see if this can be replicated under qemu and try a bisect over the next couple of days. In the mean time, here's the log of a boot with `earlyprintk` and without `quiet`. Kind regards, Daniel [ 182.160030] kexec_core: Starting new kernel [0.00] dt-cpu-ftrs: setup for ISA 3000 [0.00] dt-cpu-ftrs: final cpu/mmu features = 0x0001f86b8f5fb1a7 0x3c007041 [0.00] radix-mmu: Page sizes from device-tree: [0.00] radix-mmu: Page size shift = 12 AP=0x0 [0.00] radix-mmu: Page size shift = 16 AP=0x5 [0.00] radix-mmu: Page size shift = 21 AP=0x1 [0.00] radix-mmu: Page size shift = 30 AP=0x2 [0.00] radix-mmu: Activating Kernel Userspace Execution Prevention [0.00] radix-mmu: Activating Kernel Userspace Access Prevention [0.00] radix-mmu: Mapped 0x-0x4000 with 1.00 GiB pages (exec) [0.00] radix-mmu: Mapped 0x4000-0x0008 with 1.00 GiB pages [0.00] radix-mmu: Mapped 0x2000-0x2008 with 1.00 GiB pages [0.00] radix-mmu: Initializing Radix MMU [0.00] Linux version 5.10.0-4-generic (buildd@bos02-ppc64el-008) (gcc (Ubuntu 10.2.0-17ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubun tu) 2.35.1) #5-Ubuntu SMP Mon Nov 16 09:41:59 UTC 2020 (Ubuntu 5.10.0-4.5-generic 5.10.0-rc4) [0.00] Secure boot mode disabled [0.00] Found initrd at 0xc490:0xc66f0cf4 [0.00] OPAL: Found memory mapped LPC bus on chip 0 [0.00] Using PowerNV machine description [0.00] printk: bootconsole [udbg0] enabled [0.00] CPU maps initialized for 4 threads per core [0.00] - [0.00] phys_mem_size = 0x10 [0.00] dcache_bsize = 0x80 [0.00] icache_bsize = 0x80 [0.00] cpu_features = 0x0001f86b8f5fb1a7 [0.00] possible= 0x000ffbfbcf5fb1a7 [0.00] always = 0x0003800081a1 [0.00] cpu_user_features = 0xdc0065c2 0xaef0 [0.00] mmu_features = 0xbc007441 [0.00] firmware_features = 0x00011000 [0.00] vmalloc start = 0xc008 [0.00] IO start = 0xc00a [0.00] vmemmap start = 0xc00c [0.00] - [0.00] kvm_cma_reserve: reserving 3276 MiB for global area [0.00] cma: Reserved 3280 MiB at 0x20072f00 [0.00] numa: NODE_DATA [mem 0x7ffd44900-0x7ffd4bfff] [0.00] numa: NODE_DATA [mem 0x2007ff438900-0x2007ff43] [0.00] rfi-flush: mttrig type flush available [0.00] count-cache-flush: flush disabled. [0.00] link-stack-flush: software flush enabled. [0.00] stf-barrier: eieio barrier available [0.00] Initializing IODA2 PHB (/pciex@600c3c000) [0.00] PCI host bridge /pciex@600c3c000 (primary) ranges: [0.00] MEM 0x000600c0..0x000600c07ffe -> 0x8000 [0.00] ioremap() called early from pnv_pci_init_ioda_phb+0x360/0x968. Use early_ioremap() instead [0.00] MEM 0x0006..0x0006003f -> 0x0006 (M64 #1..31) [0.00] Using M64 #31 as default window [0.00] 512 (511) PE's M32: 0x8000 [segment=0x40] [0.00] M64: 0x40 [segment=0x2000] [0.00] Allocated bitmap for 4088 MSIs (base IRQ 0xfe000) [0.00] Initializing IODA2 PHB (/pciex@600c3c010) [0.00] PCI host bridge /pciex@600c3c010 ranges: [0.00] MEM 0x000600c08000..0x000600c0fffe -> 0x8000 [0.00] ioremap() called early from pnv_pci_init_ioda_phb+0x360/0x968. Use early_ioremap() instead [0.00] MEM 0x00060040..0x0006007f -> 0x00060040 (M64 #1..15) [0.00] Using M64 #15 as default window [0.00] 256 (255) PE's M32: 0x8000 [segment=0x80] [0.00] M64: 0x40 [segment=0x4000] [0.00] Allocated bitmap for 2040 MSIs (base IRQ 0xfd800) [0.00] Initializing IODA2 PHB (/pciex@600c3c020) [0.00] PCI host bridge /pciex@600c3c020 ranges: [0.00] MEM 0x000600c1..0x000600c17ffe -> 0x8000 [0.00] ioremap() called early from pnv_pci_init_ioda_phb+0x360/0x968. Use early_ioremap() instead [0.00] MEM
