[Kernel-packages] [Bug 1926960] Re: [Ubuntu 21.04] - OpenSSL 1.1.1g function EC_KEY_set_group() causes illegal instruction SIGILL in file crypto/ec/ec_key:477 (openssl-ibmca)
** Package changed: linux (Ubuntu) => openssl-ibmca (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926960 Title: [Ubuntu 21.04] - OpenSSL 1.1.1g function EC_KEY_set_group() causes illegal instruction SIGILL in file crypto/ec/ec_key:477 (openssl- ibmca) Status in openssl-ibmca package in Ubuntu: New Bug description: Problem Description: Loading and initializing the OpenSSL configuration twice causes ibmca to prematurely destroy global data. This then causes crashes in applications that do this. It might happen if an application first initializes OpenSSls libcrypto and then libssl. Solution: Please backport https://github.com/juergenchrist/openssl-ibmca/commit/40928425d848827fa8427d677e37178ab3b57e50 to fix this problem. focal (20.04LTS) (libs): 2.1.0-0ubuntu1 [ports]: s390x groovy (20.10) (libs): 2.1.1-0ubuntu1 [ports]: s390x hirsute (21.04) (libs): 2.1.1-0ubuntu1 [ports]: s390x git commit applies here cleanly. impish (libs): 2.1.2-0ubuntu1 [ports]: s390x git commit should already be contained in this. So no need for another patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl-ibmca/+bug/1926960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908371] Re: [UBUNTU 20.04] - zipl command doesn't work correctly with -M option (s390utils/s390-tools?)
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1908371
Title:
[UBUNTU 20.04] - zipl command doesn't work correctly with -M option
(s390utils/s390-tools?)
Status in s390-tools package in Ubuntu:
New
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1908371/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906384] Re: [UBUNTU 18.04] lvm boot failure
** Summary changed: - lvm boot failure + [UBUNTU 18.04] lvm boot failure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906384 Title: [UBUNTU 18.04] lvm boot failure Status in linux package in Ubuntu: New Bug description: ---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 de
[Kernel-packages] [Bug 1896726] Re: [UBUNTU 20.04.1]Secure guest (qemu) crash during boot (mostly) but also while running workload (rare) (secure execution)
** Summary changed: - Secure guest (qemu) crash during boot (mostly) but also while running workload (rare) (secure execution) + [UBUNTU 20.04.1]Secure guest (qemu) crash during boot (mostly) but also while running workload (rare) (secure execution) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896726 Title: [UBUNTU 20.04.1]Secure guest (qemu) crash during boot (mostly) but also while running workload (rare) (secure execution) Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Secure Execution with Ubuntu 20.04, secure guest crash during boot from time to time, crashed guest went into Shufoff state instead of Crashed state (preserve is set), so I can't get a dump. libvirt log file: 2020-04-21T16:35:39.382999Z qemu-system-s390x: Guest says index 19608 is available 2020-04-21 16:35:44.831+: shutting down, reason=crashed ---uname output--- Linux ubu204uclg1002 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:05:32 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = z15 8561 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- I have a setup with 72 KVM guests which I can start in secure or non-secure mode. Starting all of them in secure mode back to back results in a number of guests (4..8) in Shutoff state and reason=crashed in the libvirt log. I can manually start the guest again no problem. Different guests are failing. Host and guests are on latest Ubuntu 20.04. The supposed fix (kernel memory management) has landed in Andrew Mortons mm tree https://lore.kernel.org/mm-commits/20200916003608.ib4ln%25a...@linux-foundation.org/T/#u Please note: while this was found with secure execution, the bug is actually present for non-KVM workloads as well. The complete patch is this: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a338e69ba37286c0fc300ab7e6fa0227e6ca68b1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893027] Re: [UBUNTU 20.04] lscpumf display raw event number incorrectly
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893027 Title: [UBUNTU 20.04] lscpumf display raw event number incorrectly Status in s390-tools package in Ubuntu: New Bug description: Fix wrong output of lscpumf when device cpum_cf has different type than 4 Please apply to ubuntu 20.04 (s390-tools version 2.12) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1893027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892350] Re: [UBUNTU 20.04]zipl boot loader should check for secure IPL feature before looking up data (was: PV: guest fails to reboot from a disk)
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) ** Summary changed: - [UBUNTU 20.04]zipl boot loader should check for secure IPL feature before looking up data (was: PV: guest fails to reboot from a disk) + [UBUNTU 20.04] zipl boot loader should check for secure IPL feature before looking up data (was: PV: guest fails to reboot from a disk) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892350 Title: [UBUNTU 20.04] zipl boot loader should check for secure IPL feature before looking up data (was: PV: guest fails to reboot from a disk) Status in s390-tools package in Ubuntu: New Bug description: Problem description: Sometimes a PV guest fails to reboot from a disk. # How to reproduce? Try to reboot a PV guest multiple times. Or using hades (bb/mhartmay/pv branch): $ for i in $(seq 1 100); do nose2 -v --early-debug tests.test_pv.PVChreiplTestCase; done # Host kernel used: 5.6.0-rc2-00041-g0c1beb8db4fc # Host cmdline used: kvm.nested=1 nokaslr crashkernel=196M selinux=0 root=/dev/disk/by-path/ccw-0.0.1000-part1 rd.dasd=0.0.1000 cio_ignore=all,!condev LANG=en_US.UTF-8 prot_virt=1 # QEMU used: QEMU emulator version 4.2.50 (v4.2.0-1246-g3d17206cbf41-dirty) # Guest kernel used: 5.6.0-rc2-00041-g0c1beb8db4fc # Guest cmdline used: enforcing=0 console=ttyS0 swiotlb=256000 STARTUP=sshd.sh PV This is a list of commits that are required to entirely resolve this bug on top of s390tools-2.12 These commits are zipl related only. c91d8bd5f9102cb91ba6839cf98c40dd26521cd3 fb62cc9e14591c7f84944148d48ac98114a26d46 f4f2220693ffe2efadfd41e0036f6971aabc1fdd e0ffb3c584f57783538773b3eda5f48caefc e67f6300862d939d212d79c4ce5e1249102ddcd3 c4a0933165c7093c2ca52c9ee94e4b074fc9f3f7 cb11d6baec41f14c3e8f6832a13ea0020dcf907d 6c04f977734f55b862b9900abfc325e1db98acd0 ce65c39e18a62743bf65eeec92eaedbe22d035da 19f747847ffb39cb2df43376ff569bf18a026362 eb4e806cdc0801718e3d74b2062700d57f6f4b5a 93a0cb254efe45b5e291283af69d74f531cdc40d 2fe5f27975785a3af91d0b24f88962c7ae82ed44 cc069af26d1c35e35bca9d7db4ee4d8a0f8f5440 0843b7db36af3e30c97fd8be8173debe9f5510b7 1a150b2fe05627adc43cc00dd2291acfff30735a 9a68a25ab609146e0c22ae882a2f80c6da714761 4eea67cd6f100e7db7b71a03495e97a8db96490a 0ac7ce964ed089a2614dbfcffb89bd6c4175992b 0c583ec1a68e998f5ed775a97d7f046aad5df28a 1b65b23b43985cb8a1da2ef399ec6def31bbcc69 454f1427d3edcd94c2e25fe7165d392bcc97567a 71b36d17f019c9e2cf218351520d5b55a6c2d479 41fae58ecd8d0099ce2802f43e6b998eecc818c7 3217e0438fd8ba602706eda8adbb23e74f2f54ad ae66f795124fb3b5e57637ff002edbf45f05ccbd d7b816ff58baed404b5406a7c25e390804ff1a76 c367a6bb6529f04bdcb6264ede99439a756dfa3e 943c5dc51d493fd89f8c1b0760656446d5653be6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1892350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888231] Re: [UBUNTU 20.04] zipl: Fix KVM IPL without bootindex
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888231 Title: [UBUNTU 20.04] zipl: Fix KVM IPL without bootindex Status in s390-tools package in Ubuntu: New Bug description: Description: zipl: Fix KVM IPL without bootindex Symptom: Failed IPL on KVM when no bootindex is specified. Problem: Without bootindex specified there is no IPL parmblock on KVM which can be read by the stage3 loader. Solution: In case diag308 gives a response code 0x102 the stage3 loader can safely assume that no secure IPL is required since no IPL report block exists. Reproduction: IPL on KVM without 'bootindex=' attached. Upstream-ID: c9066bf5497300db5e0ba11bf111683ea225d8c8 b7f1977d3f9332f82e7f388fb18076b89b83944e Component: s390-tools 2.14 Should also be integrated into 20.04, where secure boot is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1888231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887777] Re: [UBUNTU 20.04] Failed to install ubuntu 20.04 on FBA disk on a zvm guest
** Summary changed:
- Failed to install ubuntu 20.04 on FBA disk on a zvm guest
+ [UBUNTU 20.04] Failed to install ubuntu 20.04 on FBA disk on a zvm guest
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/188
Title:
[UBUNTU 20.04] Failed to install ubuntu 20.04 on FBA disk on a zvm
guest
Status in linux package in Ubuntu:
New
Bug description:
Failed to install ubuntu 20.04 on FBA disk on a zvm guest
---uname output---
Linux ubuntu-server 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:27:17 UTC
2020 s390x s390x s390x GNU/Linux
Machine Type = z14
---boot type---
CDROM / ISO image
---Install repository type---
CDROM
---Point of failure---
Failed during boot of installer
I'm installing a ubuntu focal server on a zvm guest with one single
DASD-FBA disk and use the default one single partition mode on the
page of selecting partition.
After the partition selection and continue, the installer aborted.
Following errors can be found in /var/log/curtin/install.log:
Checking if dasd 0.0.0100 needs formatting
Running command ['dasdview', '--extended', '/dev/dasda'] with allowed
return codes [0] (capture=True)
An error occured handling 'dasd-dasda': ValueError - dasdview output
has fewer than 52 lines, cannot parse
finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL:
configuring dasd: dasd-dasda
TIMED BLOCK_META: 18.075
finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL:
curtin command block-meta
Traceback (most recent call last):
File
"/snap/subiquity/1937/lib/python3.6/site-packages/curtin/commands/main.py",
line 202, in main
ret = args.func(args)
File
"/snap/subiquity/1937/lib/python3.6/site-packages/curtin/log.py", line 97, in
wrapper
return log_time("TIMED %s: " % msg, func, *args, **kwargs)
File
"/snap/subiquity/1937/lib/python3.6/site-packages/curtin/log.py", line 79, in
log_time
return func(*args, **kwargs)
File
"/snap/subiquity/1937/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 111, in block_meta
return meta_custom(args)
File
"/snap/subiquity/1937/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 1911, in meta_custom
handler(command, storage_config_dict)
File
"/snap/subiquity/1937/lib/python3.6/site-packages/curtin/commands/block_meta.py",
line 564, in dasd_handler
disk_layout, label)):
File
"/snap/subiquity/1937/lib/python3.6/site-packages/curtin/block/dasd.py", line
561, in needs_formatting
if layout != self.disk_layout():
File
"/snap/subiquity/1937/lib/python3.6/site-packages/curtin/block/dasd.py", line
519, in disk_layout
view = dasdview(self.devname)
File
"/snap/subiquity/1937/lib/python3.6/site-packages/curtin/block/dasd.py", line
65, in dasdview
return _parse_dasdview(out)
File
"/snap/subiquity/1937/lib/python3.6/site-packages/curtin/block/dasd.py", line
226, in _parse_dasdview
'dasdview output has fewer than 52 lines, cannot parse')
ValueError: dasdview output has fewer than 52 lines, cannot parse
dasdview output has fewer than 52 lines, cannot parse
root@ubuntu-server:/# uname -a
Linux ubuntu-server 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:27:17 UTC
2020 s390x s390x s390x GNU/Linux
root@ubuntu-server:/# cat /proc/cmdline
ip=9.152.85.241::9.152.84.1:255.255.252.0:u20:enc1000:none:9.152.120.241
url=ftp://9.123.155.79/pub/ubuntu-20-daily/focal-live-server-s390x.iso --- quiet
root@ubuntu-server:/#
== Comment: #1 - Dong Yan Yang - 2020-07-01 05:20:54 ==
From this comment in another bug:
https://bugzilla.linux.ibm.com/show_bug.cgi?id=185885#c10
it says: FBA support is in the works
Are there any documentation mentioned this?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/188/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881096] Re: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf
** Summary changed: - Deflate counters reported by lscpumf are not valid or available with perf + [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881096 Title: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable with perf stat -e ---uname output--- Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = z15 8561 ---Steps to Reproduce--- lscpumf -c gives a list of available counters, but a few of them are not usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR perf list is also not offering these counters. A solution will be a backport to 20.04, and tried to made available for next SRU , code needed before 06-12. Addl Info from Dev: I have downloaded the following repository https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal and checked out branch master-next. Both patches appended apply without warning and the compilation showed no error. For the perf tool: e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM z15 For the s390 kernel d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15 All accepted for kernel 5.7 rc1 Please include both patches into Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1881096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879286] Re: [UBUNTU 20.04] Netplan configuration fails to apply in subiquity installer
** Summary changed:
- Netplan configuration fails to apply in subiquity installer
+ [UBUNTU 20.04] Netplan configuration fails to apply in subiquity installer
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879286
Title:
[UBUNTU 20.04] Netplan configuration fails to apply in subiquity
installer
Status in linux package in Ubuntu:
New
Bug description:
I'm installing Ubuntu 20.04 with a nocloud-net installation source on
a z/VM guest. I'm currently limited to seeing installation output only
through webhook reporter, because I cannot access shell on the target
system during installation.
Kernel command-line:
cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
autoinstall ds=nocloud-net;s=http://t35lp37.lnxne.boe:8080/cfg/
#cloud-config
autoinstall:
version: 1
reporting:
remote:
type: webhook
endpoint: http://t35lp37.lnxne.boe:8080/log/
refresh-installer:
update: yes
apt:
primary:
- arches: [s390x]
uri: http://us.ports.ubuntu.com/ubuntu-ports
identity: {hostname: m8330038, password:
.ueYA4yxzICWX9/.wxG7epPimsn.FM/CuMQMqjgbBbawyn5T3zYyGc5Io4ZNRcvItBWojzpO1S8bkTpthJRPc4Q.,
realname: user, username: user}
keyboard: {layout: us, variant: ''}
locale: en_US
network:
ethernets:
encbdf0:
addresses: [172.18.76.38/15]
gateway4: 172.18.0.1
nameservers:
addresses: [172.18.0.1]
version: 2
ssh:
allow-pw: true
authorized-keys: []
install-server: true
storage:
version: 1
layout:
name: direct
I get the following otuput on the webhook:
curtin start subiquity/Welcome/apply_autoinstall_config:
curtin finish subiquity/Welcome/apply_autoinstall_config:
curtin finish subiquity/Welcome: completed
curtin start subiquity/Refresh/apply_autoinstall_config:
curtin start subiquity/Refresh/check_for_update:
curtin finish subiquity/Network/apply_config: Command '['netplan', 'apply']'
returned non-zero exit status 1.
curtin start subiquity/Error/1589791025.945954323.network_fail/add_info:
curtin start subiquity/Error/1589791025.951922417.ui/add_info:
curtin finish subiquity/Error/1589791025.951922417.ui/add_info: written to
/var/crash/1589791025.951922417.ui.crash
Configuration seems to be working fine when applied on a manually
installed system.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879286/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
** Summary changed: - installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf + [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876715] Re: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects
** Summary changed: - zfcpdump-kernel package has different name for dumpkernel image than zipl expects + [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876715 Title: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects Status in linux package in Ubuntu: New Bug description: Under Ubuntu 20.04 I wanted to prepare a SCSI dump disk: root@t35lp25:/~# apt install zfcpdump-kernel Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: zfcpdump-kernel 0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded. Need to get 1655 kB of archives. After this operation, 1757 kB of additional disk space will be used. Get:1 http://de.ports.ubuntu.com/ubuntu-ports focal/universe s390x zfcpdump-kernel s390x 4.13-0ubuntu1 [1655 kB] Fetched 1655 kB in 1s (1803 kB/s) Selecting previously unselected package zfcpdump-kernel. (Reading database ... 53866 files and directories currently installed.) Preparing to unpack .../zfcpdump-kernel_4.13-0ubuntu1_s390x.deb ... Unpacking zfcpdump-kernel (4.13-0ubuntu1) ... Setting up zfcpdump-kernel (4.13-0ubuntu1) ... root@t35lp25:/~# zipl -d /dev/disk/by-id/scsi-36005076303ffd3274609-part1 Error: Need external file '/lib/s390-tools/zfcpdump/zfcpdump-image' for partition dump: No such file or directory root@t35lp25:~# ls /lib/s390-tools/zfcpdump/ zfcpdump-initrd zfcpdump_part.image root@t35lp25:~# As you can see, zipl expects "zfcpdump-image", but "zfcpdump_part.image" is available. with paramater -d, zipl does NOT accept -i to override the image name. Thus I renamed zfcpdump_part.image to zfcpdump-image: root@t35lp25:~# cd /lib/s390-tools/zfcpdump root@t35lp25:/lib/s390-tools/zfcpdump# mv zfcpdump_part.image zfcpdump-image root@t35lp25:/lib/s390-tools/zfcpdump# zipl -d /dev/disk/by-id/scsi-36005076303ffd3274609-part1 Building bootmap directly on partition '/dev/disk/by-id/scsi-36005076303ffd3274609-part1' Adding dump section initial ramdisk...: /lib/s390-tools/zfcpdump/zfcpdump-initrd 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-0x001b9fff parmline: 0x001ba000-0x001ba1ff initial ramdisk.: 0x001c-0x0020edff Preparing boot device: sde. Done. root@t35lp25:/lib/s390-tools/zfcpdump# === Hi, zfcpdump_part.image got renamed to zfcpdump-image upstream with s390-tools v2.7.0. For me it looks like the old name is hard coded somewhere in the packaging/installation routines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874058] Re: [UBUNTU 20.04] mlx5: alloc_pages_nodemask stack trace
** Summary changed: - Ubuntu 20.04 mlx5: alloc_pages_nodemask stack trace + [UBUNTU 20.04] mlx5: alloc_pages_nodemask stack trace -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874058 Title: [UBUNTU 20.04] mlx5: alloc_pages_nodemask stack trace Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874058/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874055] Re: [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available
** Summary changed: - s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available + [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874055 Title: [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO instructions are available Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] Re: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter
** Summary changed: - s390x/pci: enumerate pci functions per physical adapter + [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874057] Re: [UBUNTU 20.04] s390x/pci: do not allow to create more pci functions than configured via CONFIG_PCI_NR_FUNCTIONS
** Summary changed: - s390x/pci: do not allow to create more pci functions than configured via CONFIG_PCI_NR_FUNCTIONS + [UBUNTU 20.04] s390x/pci: do not allow to create more pci functions than configured via CONFIG_PCI_NR_FUNCTIONS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874057 Title: [UBUNTU 20.04] s390x/pci: do not allow to create more pci functions than configured via CONFIG_PCI_NR_FUNCTIONS Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868113] Re: [Ubuntu 20.04] Striding RQ as Default for ConnectX-4
** Summary changed: - [Ubuntu 20.04] Striding RQ als Default für ConnectX-4 in Distros + [Ubuntu 20.04] Striding RQ as Default for ConnectX-4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868113 Title: [Ubuntu 20.04] Striding RQ as Default for ConnectX-4 Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: ello, Within our Network Performance runs in the RoCE Express 2(.1) area, we noticed a performance regression with streaming workloads which could be mitigated by using an ethtool setting. The Commit which switched the default value from "Striding RQ" to "Legacy RQ" for ConnectX-4 devices (RoCE Express 2(.1)) is attached here: commit 5ffd81943d7a57423f204cd5844bf430b5634472 (refs/bisect/bad) Author: Tariq Toukan Date: Tue Feb 20 15:17:54 2018 +0200 net/mlx5e: RX, Always prefer Linear SKB configuration Prefer the linear SKB configuration of Legacy RQ over the non-linear one of Striding RQ. This implies that ConnectX-4 LX now uses legacy RQ by default, as it does not support the linear configuration of Striding RQ. Signed-off-by: Tariq Toukan Signed-off-by: Saeed Mahameed diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c index 2c634e50d051..333d4ed52b94 100644 --- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c @@ -4405,9 +4405,16 @@ void mlx5e_build_nic_params(struct mlx5_core_dev *mdev, MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_CQE_COMPRESS, params->rx_cqe_compress_def); /* RQ */ - if (mlx5e_striding_rq_possible(mdev, params)) - MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, - !slow_pci_heuristic(mdev)); + /* Prefer Striding RQ, unless any of the following holds: +* - Striding RQ configuration is not possible/supported. +* - Slow PCI heuristic. +* - Legacy RQ would use linear SKB while Striding RQ would use non-linear. +*/ + if (!slow_pci_heuristic(mdev) && + mlx5e_striding_rq_possible(mdev, params) && + (mlx5e_rx_mpwqe_is_linear_skb(mdev, params) || +!mlx5e_rx_is_linear_skb(mdev, params))) + MLX5E_SET_PFLAG(params, MLX5E_PFLAG_RX_STRIDING_RQ, true); mlx5e_set_rq_type(mdev, params); mlx5e_init_rq_type_params(mdev, params); We have modified the upstream-kernel to allow us running of measurements and compare differences between Legacy RQ vs Striding RQ. Here is an example below: Kernel used: 5.4.0-rc7 The measurements run on a dedicated machine (z14) using uperf with streaming profiles (MTU size 1500). Example throughput drop: (traffic via a shared card, i.e. client and server using VFs from the same ConnectX-4) -- | |Legacy RQ| Striding RQ | -- |str-writex30k (1 connection) |24.62Gb/s| 33.47Gb/s| -- Additionaly, two tests with transactional workload using the ethtool proposed switch: -- | |Legacy RQ| Striding RQ | -- | rr1c-200x30k---1 | 4.12Gb/s|5.66Gb/s| -- | rr1c-200x30k--10 |15.10Gb/s| 20.77Gb/s| -- As concluded in the communication with Mellanox, there is a possibility to use a simple ethtool command to switch between the queuing methods, allowing us to avoid kernel code changes: ethtool --set-priv-flags DEVNAME rx_striding_rq on (To list the available settings you may use: ethtool --show-priv-flags DEVNAME) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1868113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865032] Re: [UBUNTU] zipl/libc: Fix potential buffer overflow in printf
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865032 Title: [UBUNTU] zipl/libc: Fix potential buffer overflow in printf Status in s390-tools package in Ubuntu: New Bug description: Description: zipl/libc: Fix potential buffer overflow in printf Symptom: Crash of the zipl boot loader during boot. Problem: The zipl boot loaders have their own minimalistic libc implementation. In it printf and sprintf use vsprintf for string formatting. Per definition vsprintf assumes that the buffer it writes to is large enough to contain the formatted string and performs no size checks. This is problematic for the boot loaders because the buffer they use are often allocated on the stack. Thus even small changes to the string format can potentially cause buffer overflows on the stack. Solution: Implement vsnprintf and make use of it. Reproduction: Use printf to print a string with >81 characters (exact number depends on the stack layout/compiler used). Upstream commit(s) for s390-tools: 6fe9e6c55c69c14971dca1009f5060418aae 8874b908254c47c8a6fd7a1aca2c7371c11035c4 f7430027b41d5ad6220e962a179c2a5213330a44 36fed0e6c6590631c4ce1707c8fe3c3397bcce4d Problem was introduced with version 1.24. Therefore these patches need to be applied to all distros in service. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1865032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864433] Re: [Ubuntu 20.04] boost library requires addl. patches
** Package changed: linux (Ubuntu) => boost1.71 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864433 Title: [Ubuntu 20.04] boost library requires addl. patches Status in boost1.71 package in Ubuntu: New Bug description: Currently Ubuntu 20.04 contains an updated version of boost, which is "FIX RELEASED" via BZ: https://bugzilla.linux.ibm.com/show_bug.cgi?id=182852 LP: https://bugs.launchpad.net/ubuntu/+source/boost1.71/+bug/1859941 While trying to backport the upstream implementation for older boost library versions IBM found the current version to be broken and have new patch was provided. IBM provided some fixes ontop of the current implementation: https://github.com/boostorg/context/pull/133 The pull request has just been accepted. Please also pick up the following patch for Ubuntu 20.04: https://github.com/boostorg/context/commit/e0ba57928d681c9f8e0b28eef2a17973950b9e8b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost1.71/+bug/1864433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862187] Re: [UBUNTU 20.04] zkey: Fix display of XTS attribute for validate command
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862187 Title: [UBUNTU 20.04] zkey: Fix display of XTS attribute for validate command Status in s390-tools package in Ubuntu: New Bug description: Description: zkey: Fix display of XTS attribute for validate command Symptom: The 'zkey validate' command shows an invalid value for the XTS attribute. Problem: Due to a use after free of the secure key, the XTS attribute is not determined correctly, and is displayed incorrectly. Function is_xts_key() is called with a secure key that has already been freed and thus most likely returns false. This bug has been introduced with feature SEC1717 "Cipher key support" with commit 298fab68fee8 "zkey: Preparations for introducing a new key type" Solution: Free the secure key only after the last use. Reproduction: Generate an XTS key of type CCA-AESDATA or CCA-AESCIPHER and then run 'zkey validate'. Upstream Commit ID: f75f4aff8f6e4ae148bde858ee1cb7f1066f5f23 https://github.com/ibm-s390-tools/s390-tools/commit/f75f4aff8f6e4ae148bde858ee1cb7f1066f5f23 Need to be applied on top of 2.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1862187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861984] Re: [Comm] IBM JDK 8.0.6.5 integration into Ubuntu
** Package changed: linux (Ubuntu) => ibm-java71 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861984 Title: [Comm] IBM JDK 8.0.6.5 integration into Ubuntu Status in ibm-java71 package in Ubuntu: New Bug description: ~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr6fp5_20200111_02_ocdc.tar.gz local: 80sr6fp5_20200111_02_ocdc.tar.gz remote: 80sr6fp5_20200111_02_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr6fp5_20200111_02_ocdc.tar.gz 226 Transfer successful. 658783435 bytes sent in 122.72 secs (5242.6 kB/s) Status of providing SNAPS: We were not able to create SNAPS for this release due to other priorities. We will try to generate Package in SNAPS for next release. Thanks !!! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibm-java71/+bug/1861984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852550] Re: libica fix required : x25519, x448: fix handling of non-canonical values
** Package changed: linux (Ubuntu) => libica (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852550 Title: libica fix required : x25519,x448: fix handling of non-canonical values Status in libica package in Ubuntu: New Bug description: libica 3.6.1 has just been released at https://github.com/opencryptoki/libica/releases/tag/v3.6.1 It contains the following fix: https://github.com/opencryptoki/libica/commit/a3b36ef136e304a1e2dc12ef7b96686202cbd00d The patch applies cleanly to libica 3.6.0. Thanks for your support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libica/+bug/1852550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842436] Re: [UBUNTU] Avoid creation of mixed-blocksize PV on LVM volume groups
** Package changed: linux (Ubuntu) => lvm2 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842436 Title: [UBUNTU] Avoid creation of mixed-blocksize PV on LVM volume groups Status in lvm2 package in Ubuntu: New Bug description: efault blocksize of a file-system seems to be dependent on the volume-size. Big volume (at least ext4) does have 4k blk-size, even the underlaying devise with a smaller phyiscal blk-size. The patch, avoiding define mixed-sized volume groups is now upstream in the master branch of LVM2 https://sourceware.org/git/?p=lvm2.git;a=commit;h=0404539edb25e4a9d3456bb3e6b402aa2767af6b Using this patch within the distribution is for sanity reasons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1842436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841427] Re: [Comm] IBM JDK 8.0.5.40 integration into Ubuntu
** Package changed: linux (Ubuntu) => ibm-java71 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841427 Title: [Comm] IBM JDK 8.0.5.40 integration into Ubuntu Status in ibm-java71 package in Ubuntu: New Bug description: ---Problem Description--- ~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> set prompt off ?Invalid command ftp> prompt off Interactive mode off. ftp> put 80sr5fp40_20190807_01_ocdc.tar.gz local: 80sr5fp40_20190807_01_ocdc.tar.gz remote: 80sr5fp40_20190807_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp40_20190807_01_ocdc.tar.gz 226 Transfer successful. 656958051 bytes sent in 328.72 secs (1951.7 kB/s) ---uname output--- Linux 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:50:31 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibm-java71/+bug/1841427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841032] Re: [UBUNTU] 19.04 - Packaging problem with smc-tools 1.2.0
** Package changed: linux (Ubuntu) => smc-tools (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841032 Title: [UBUNTU] 19.04 - Packaging problem with smc-tools 1.2.0 Status in smc-tools package in Ubuntu: New Bug description: The shared library libsmc-preload.so (shipped with smc-tools) is installed in the wrong place: root@m3545040:~# smc_run ls ERROR: ld.so: object 'libsmc-preload.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. root@m3545040:~# dpkg -L smc-tools /. /usr /usr/bin /usr/bin/smc_dbg /usr/bin/smc_pnet /usr/bin/smc_rnics /usr/bin/smc_run /usr/bin/smcss /usr/lib64 /usr/lib64/libsmc-preload.so /usr/share /usr/share/doc /usr/share/doc/smc-tools /usr/share/doc/smc-tools/changelog.Debian.gz /usr/share/doc/smc-tools/copyright /usr/share/lintian /usr/share/lintian/overrides /usr/share/lintian/overrides/smc-tools /usr/share/man /usr/share/man/man7 /usr/share/man/man7/af_smc.7.gz /usr/share/man/man8 /usr/share/man/man8/smc_pnet.8.gz /usr/share/man/man8/smc_rnics.8.gz /usr/share/man/man8/smc_run.8.gz /usr/share/man/man8/smcss.8.gz root@m3545040:~# mv /usr/lib64/libsmc-preload.so /usr/lib/s390x-linux-gnu/ root@m3545040:~# ldconfig root@m3545040:~# smc_run ls root@m3545040:~# It is currently packaged to install to /usr/lib64/libsmc-preload.so, which is not a search path for shared libraries. It should rather install to /usr/lib/s390x-linux-gnu/ instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smc-tools/+bug/1841032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827037] Re: [Comm] IBM JDK 8.0.5.35 integration into Ubuntu
** Package changed: linux (Ubuntu) => ibm-java71 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827037 Title: [Comm] IBM JDK 8.0.5.35 integration into Ubuntu Status in Ubuntu on IBM z Systems: Triaged Status in ibm-java71 package in Ubuntu: New Bug description: Info: Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp35_20190418_01_ocdc.tar.gz local: 80sr5fp35_20190418_01_ocdc.tar.gz remote: 80sr5fp35_20190418_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp35_20190418_01_ocdc.tar.gz 226 Transfer successful. 656732151 bytes sent in 522.25 secs (1228.0 kB/s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1827037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818799] Re: [Comm] IBM JDK 8.0.5.30 integration into Ubuntu
** Package changed: linux (Ubuntu) => ibm-java71 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818799 Title: [Comm] IBM JDK 8.0.5.30 integration into Ubuntu Status in ibm-java71 package in Ubuntu: New Bug description: x@xxx:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp30_20190207_01_ocdc.tar.gz local: 80sr5fp30_20190207_01_ocdc.tar.gz remote: 80sr5fp30_20190207_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp30_20190207_01_ocdc.tar.gz 226 Transfer successful. 653799760 bytes sent in 489.77 secs (1303.6 kB/s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibm-java71/+bug/1818799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805792] Re: [Comm] IBM JDK 8.0.5.25 integration into Ubuntu
** Package changed: linux (Ubuntu) => ibm-java71 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805792 Title: [Comm] IBM JDK 8.0.5.25 integration into Ubuntu Status in Ubuntu on IBM z Systems: Triaged Status in ibm-java71 package in Ubuntu: New Bug description: foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp25_20181030_01_ocdc.tar.gz local: 80sr5fp25_20181030_01_ocdc.tar.gz remote: 80sr5fp25_20181030_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp25_20181030_01_ocdc.tar.gz 226 Transfer successful. 649123994 bytes sent in 396.74 secs (1597.8 kB/s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805160] Re: problem when trying to build atlas from source
** Package changed: linux (Ubuntu) => atlas (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805160 Title: problem when trying to build atlas from source Status in atlas package in Ubuntu: New Bug description: issue when trying to build atlas (libatlas.so) from sources. ---Steps to Reproduce--- apt-get source atlas, extract, follow README.Debian When running on EC12: cc1: error: hardware vector support not available on zEC12 make[4]: *** [IRunCComp] Error 1 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 When running on z13 or z14: /root/atlas-3.10.3/build/..//include/atlas_simd.h:385:29: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'double' #define ATL_VTYPE vector double gcc: error: liblapack_atlas.a: No such file or directory gcc: error: libf77blas.a: No such file or directory Linux weather 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:57:21 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = EC12 and z14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atlas/+bug/1805160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803958] Re: [UBUNTU] zkey: Fails to run commands generated by 'zkey cryptsetup'
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803958 Title: [UBUNTU] zkey: Fails to run commands generated by 'zkey cryptsetup' Status in s390-tools package in Ubuntu: New Bug description: Description: zkey: Fails to run commands generated by 'zkey cryptsetup' Symptom: Fails to run commands generated by 'zkey cryptsetup'. Problem: When using 'zkey cryptsetup' with --run option the execution of the generated commands may fail, when the executable to be run is located in '/sbin'. Solution: Include /sbin into PATH when executing commands. Reproduction: Use 'zkey cryptsetup' with option --run on a distribution where 'cryptsetup' is located in '/sbin'. Upstream commit: https://github.com/ibm-s390-tools/s390-tools/commit/9100327092c470c2e5b5819087c8094822a1c751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1803958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798312] Re: LP1792533 : [Comm] IBM JDK 8.0.5.22 integration into Ubuntu
** Package changed: linux (Ubuntu) => ibm-java71 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798312 Title: LP1792533 : [Comm] IBM JDK 8.0.5.22 integration into Ubuntu Status in Ubuntu on IBM z Systems: Triaged Status in ibm-java71 package in Ubuntu: New Bug description: ---Problem Description--- foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> quit 221 Goodbye. foreman@cit7r02:~/sandbox/binary$ foreman@cit7r02:~/sandbox/binary$ foreman@cit7r02:~/sandbox/binary$ foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp22_20180919_01_ocdc.tar.gz local: 80sr5fp22_20180919_01_ocdc.tar.gz remote: 80sr5fp22_20180919_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp22_20180919_01_ocdc.tar.gz 226 Transfer successful. 649431788 bytes sent in 457.58 secs (1386.0 kB/s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1798312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790831] Re: [Ubuntu] lstape, lsluns: handle non-zfcp; lin_tape multiple paths
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) ** Summary changed: - [Ubuntu] lstape, lsluns: handle non-zfcp; lin_tape multiple paths + lstape, lsluns: handle non-zfcp; lin_tape multiple paths -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790831 Title: lstape, lsluns: handle non-zfcp; lin_tape multiple paths Status in s390-tools package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1790831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775641] Re: [Comm] IBM JDK 8.0.5.16 integration into Ubuntu
** Package changed: linux (Ubuntu) => ibm-java71 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775641 Title: [Comm] IBM JDK 8.0.5.16 integration into Ubuntu Status in ibm-java71 package in Ubuntu: New Bug description: foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp16_20180524_01_ocdc.tar.gz local: 80sr5fp16_20180524_01_ocdc.tar.gz remote: 80sr5fp16_20180524_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp16_20180524_01_ocdc.tar.gz 226 Transfer successful. 651496332 bytes sent in 377.03 secs (1687.5 kB/s) ftp> quit 221 Goodbye. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibm-java71/+bug/1775641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771575] Re: [Comm] IBM JDK 8.0.5.15 integration into Ubuntu
** Package changed: linux (Ubuntu) => ibm-java71 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771575 Title: [Comm] IBM JDK 8.0.5.15 integration into Ubuntu Status in ibm-java71 package in Ubuntu: New Bug description: Uploaded the Debian packages onto the Canonical FTP Server for 8.0.5.15 foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp15_20180502_01_ocdc.tar.gz local: 80sr5fp15_20180502_01_ocdc.tar.gz remote: 80sr5fp15_20180502_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp15_20180502_01_ocdc.tar.gz 226 Transfer successful. 651526537 bytes sent in 413.46 secs (1538.9 kB/s) ftp> quit 221 Goodbye. foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for file list 226 Transfer successful. ftp> quit 221 Goodbye. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibm-java71/+bug/1771575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk
** Summary changed: - cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk + [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762353 Title: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Problem Description: Environment: z14 VM Guest system with one CEX6C CCA coprocessor in toleration mode (i.e. CEX6 HW presented as CEX5) OS: Ubuntu 18.04 Prerelease Setting up a second dm-crypt device using protected CCA paes-xts keys fails. The problem is reproducible. Details === Setting up two or more plain end-to-end encrypted disks using 'cryptsetup' fails when using a cipher based on the protected key mechanism. The setup needs the paes and pkey modules loaded, the former providing the paes-xts-plain64 cipher (cat /proc/crpyto |grep paes). A second attempt to establish an end-to-end encrypted disk fails with : "device-mapper: reload ioctl on failed: No such file or directory." The problem is independent of the second encrypted disk being based on a second DASD or second partition on one DASD. ---uname output--- Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- 1.) The following cryptsetup statement works, and is the first one I issued. cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1 2.) After this successful statement, I issued the following: cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2 device-mapper: reload ioctl on failed: No such file or directory. See attached patch (comment #1) as fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761491] Re: [Comm] IBM JDK 8.0.5.11 integration into Ubuntu
** Package changed: linux (Ubuntu) => ibm-java71 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761491 Title: [Comm] IBM JDK 8.0.5.11 integration into Ubuntu Status in ibm-java71 package in Ubuntu: New Bug description: Uploaded the Debian packages onto the Canonical FTP Server for 8.0.5.11 foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> ftp> bin 200 Type set to Binary. ftp> prompt Interactive mode off. ftp> put 80sr5fp11_20180326_01_ocdc.tar.gz local: 80sr5fp11_20180326_01_ocdc.tar.gz remote: 80sr5fp11_20180326_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp11_20180326_01_ocdc.tar.gz 226 Transfer successful. 651713704 bytes sent in 347.10 secs (1833.6 kB/s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibm-java71/+bug/1761491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750782] Re: [Comm] IBM JDK >=8.0.5.10 integration into Ubuntu
** Package changed: linux (Ubuntu) => ibm-java71 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750782 Title: [Comm] IBM JDK >=8.0.5.10 integration into Ubuntu Status in ibm-java71 package in Ubuntu: New Bug description: Uploaded the Debian packages onto the Canonical FTP Server for 8.0.5.10 foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt Interactive mode off. ftp> put 80sr5fp10_20180214_01_ocdc.tar.gz local: 80sr5fp10_20180214_01_ocdc.tar.gz remote: 80sr5fp10_20180214_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp10_20180214_01_ocdc.tar.gz 226 Transfer successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibm-java71/+bug/1750782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750568] Re: qeth: check not more than 16 SBALEs on the completion queue
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750568 Title: qeth: check not more than 16 SBALEs on the completion queue Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1750568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750388] Re: 17.10 - BPF test tool build with errors
** Summary changed: - 17.10 - BPF package build with errors + 17.10 - BPF test tool build with errors -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1750388 Title: 17.10 - BPF test tool build with errors Status in linux package in Ubuntu: New Bug description: Rebuild problem of BPFC test tool with Ubuntu 17.10 uname -a Linux s8360046 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:33:05 UTC 2017 s390x s390x s390x GNU/Linux cat ./etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.10 DISTRIB_CODENAME=artful DISTRIB_DESCRIPTION="Ubuntu 17.10" root@s8360046:/# When I compile file test_pkt_access.c in directory linux/tools/testing/selftest/bpf I get a compile error. root@s8360046:~/linux/tools/testing/selftests/bpf# clang -I. -I./include/uapi -I../../../include/uapi -Wno-compare-distinct-pointer-types -O2 -target bpf -emit-llvm -c test_pkt_access.c -o - In file included from test_pkt_access.c:8: /usr/include/string.h:26:10: fatal error: 'bits/libc-header-start.h' file not found #include ^~ 1 error generated. # File bits/libc-header-start.h is located in directory /usr/include/s390x-linux-gnu which is not part of the include directory list: # find /usr/ -name libc-header-start.h /usr/include/s390x-linux-gnu/bits/libc-header-start.h # When I add this directory to the include pathes of the compile, I get another error: # clang -I. -I./include/uapi -I../../../include/uapi -I/usr/include/s390x-linux-gnu -Wno-compare-distinct-pointer-types -O2 -target bpf -emit-llvm -c test_pkt_access.c -o - In file included from test_pkt_access.c:12: In file included from /usr/include/linux/ip.h:20: In file included from /usr/include/s390x-linux-gnu/asm/byteorder.h:4: In file included from /usr/include/linux/byteorder/big_endian.h:12: In file included from /usr/include/linux/swab.h:6: /usr/include/s390x-linux-gnu/asm/swab.h:52:5: error: invalid output constraint '=&d' in asm : "=&d" (result) : "Q" (*x) : "cc"); ^ /usr/include/s390x-linux-gnu/asm/swab.h:80:5: error: invalid output constraint '=&d' in asm : "=&d" (result) : "Q" (*x) : "cc"); ^ 2 errors generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1719297] Re: [18.04 FEAT] KVM: CPU Model z14
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1719297 Title: [17.10 FEAT] KVM: CPU Model z14 Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Bug description: Kernel team, could you please consider cherrypicking the below commit into the linux kernel for Artful? commit b697e435aeee99b7f5b2d8f8dbb51f791be99b16 Author: Jason J. Herne Date: Fri Feb 24 10:01:30 2017 -0500 KVM: s390: Support Configuration z/Architecture Mode This is related to the following feature: Enable non transparent hardware functions for KVM guests (crypto CPACF functions) Commit-ID will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1719297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value
** Package changed: linux (Ubuntu) => kvm (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1717224 Title: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value Status in kvm package in Ubuntu: New Bug description: Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with the following error: root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038 error: Failed to start domain zs93kag70038 error: internal error: process exited while connecting to monitor: 2017-07-26T01:48:26.352534Z qemu-kvm: -drive file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native: Could not open backing file: Could not set AIO state: Inappropriate ioctl for device The previous 17 guests started fine: root@zm93k8# virsh start zs93kag70020 Domain zs93kag70020 started root@zm93k8# virsh start zs93kag70021 Domain zs93kag70021 started . . root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036 Domain zs93kag70036 started We ended up fixing the issue by adding the following line to /etc/sysctl.conf : fs.aio-max-nr = 4194304 ... then, reload the sysctl config file: root@zm93k8:/etc# sysctl -p /etc/sysctl.conf fs.aio-max-nr = 4194304 Now, we're able to start more guests... root@zm93k8:/etc# virsh start zs93kag70036 Domain zs93kag70036 started The default value was originally set to 65535: root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr 65536 Note, we chose the 4194304 value, because this is what our KVM on System Z hypervisor ships as its default value. Eg. on our zKVM system: [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr 4194304 ubuntu@zm93k8:/etc$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial ubuntu@zm93k8:/etc$ ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version Version: 1:2.5+dfsg-5ubuntu10.8 Is something already documented for Ubuntu KVM users warning them about the low default value, and some guidance as to how to select an appropriate value? Also, would you consider increasing the default aio-max-nr value to something much higher, to accommodate significantly more virtual guests? Thanks! ---uname output--- ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux Machine Type = z14 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- See Problem Description. The problem was happening a week ago, so this may not reflect that activity. This file was collected on Aug 7, one week after we were hitting the problem. If I need to reproduce the problem and get fresh data, please let me know. /var/log/messages doesn't exist on this system, so I provided syslog output instead. All data have been collected too late after the problem was observed over a week ago. If you need me to reproduce the problem and get new data, please let me know. That's not a problem. Also, we would have to make special arrangements for login access to these systems. I'm happy to run traces and data collection for you as needed. If that's not sufficient, then we'll explore log in access for you. Thanks... - Scott G. I was able to successfully recreate the problem and captured / attached new debug docs. Recreate procedure: # Started out with no virtual guests running. ubuntu@zm93k8:/home/scottg$ virsh list IdName State # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in /etc/sysctl.conf ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf fs.aio-max-nr = 65536 ## sysctl -a shows: fs.aio-max-nr = 4194304 ## Reload sysctl. ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf fs.aio-max-nr = 65536 ubuntu@zm93k8:~$ ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr fs.aio-max-nr = 65536 ubuntu@zm93k8:~$ cat /proc/sys/fs/aio-max-nr 65536 # Attempt to start more than 17 qcow2 virtual guests on the Ubuntu host. Fails on the 18th XML. Script used to start guests.. ubuntu@zm93k8:/home/scottg$ date;./start_privs.sh Wed Aug 23 13:21:25 EDT 2017 virsh start zs93kag70015 Domain zs93kag70015 started Started zs93kag70015 succesfully ... virsh start zs93kag70020 Domain zs93kag70020 started Started zs93kag70020 succesfully ... virsh start zs93kag70021 Domain zs93kag70021 started Started zs93kag70021 succesfully ... virsh start zs93kag70022 Domain zs93kag70022 started
[Kernel-packages] [Bug 1612224] Re: [17.04 FEAT] Extend cpu topology to support drawers
** Summary changed: - [16.10 FEAT] Extend cpu topology to support drawers + [17.04 FEAT] Extend cpu topology to support drawers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1612224 Title: [17.04 FEAT] Extend cpu topology to support drawers Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Bug description: kernel 4.8: Add support for the additional scheduling layer within the kernel and util-linux. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1612224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642639] Re: libica crashes with illegal instruction on zEC12-GA1
** Package changed: linux (Ubuntu) => libica (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642639 Title: libica crashes with illegal instruction on zEC12-GA1 Status in libica package in Ubuntu: New Bug description: Please backport libica upstream commit: Fix msa level detection Fixed problem in library constructor that was leading to false positive msa level detection resulting in illegal instruction. See also: https://sourceforge.net/p/opencryptoki/libica/ci/eeb40e5aea7dd36580629e6b17cd7f03fb62549c/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libica/+bug/1642639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1565841] Re: [FEAT] Provide zfcpdump-infrastructure with Ubuntu 16.04
** Summary changed: - Provide zfcpdump-infrastructure with Ubuntu 16.04 + [FEAT] Provide zfcpdump-infrastructure with Ubuntu 16.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1565841 Title: [FEAT] Provide zfcpdump-infrastructure with Ubuntu 16.04 Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Status in s390-tools package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in s390-tools source package in Xenial: Confirmed Status in linux source package in Yakkety: Confirmed Status in s390-tools source package in Yakkety: Confirmed Bug description: == Comment: #0 - Heinz-Werner Seeck - 2016-04-04 10:59:10 == Please provide the zfcpdump infrastructure to Ubuntu 16.04 , to enhance RAS capabilities and better Service enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1565841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
