[Bug 1899582] Re: ceph: fix inode number handling on arches with 32-bit ino_t
--- Comment From tuan.hoa...@ibm.com 2020-11-23 06:18 EDT--- Hello, I tested the latest kernel 5.4.0.55.58 (#61) in 'proposed-focal' and it seems to work just fine. ** Tags removed: verification-needed-focal ** Tags added: 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/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 1903814] for 18.04
--- Comment on attachment From i...@de.ibm.com 2020-11-23 11:20 EDT--- The attached patch applies cleanly to binutils-2_30 tag and binutils_2.30-21ubuntu1~18.04.4ubuntu1. ** Attachment added: "for 18.04" https://bugs.launchpad.net/bugs/1903814/+attachment/5437266/+files/patch-binutils-2_30 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903814 Title: [binutils] Prevent GOT access rewrite for certain symbols To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903814/+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 0x000600800
[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-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: BOOT_IMAGE=/boot/vmlinux-5.
[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 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 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, &cachesize, 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 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 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 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 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 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 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 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 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 /dev
[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] 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 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 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 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 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 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 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 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 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 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 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 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 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 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 1825343] deb-diff_hirsute-devel.diff
Default Comment by Bridge ** Attachment added: "deb-diff_hirsute-devel.diff" https://bugs.launchpad.net/bugs/1825343/+attachment/5465942/+files/deb-diff_hirsute-devel.diff -- 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 1892824] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-02-23 06:13 EDT--- Due to the fact, that the package version is invalid. This feature will be moved to 21.10 by another ticket. Please drop that from Release Notes of 21.04. -- 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 1906369] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-02-23 06:19 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/1906369 Title: [21.04 FEAT[ Upgrade openCryptoki to latest version (3.15.1) + additional patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1906369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904558] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1906369 *** https://bugs.launchpad.net/bugs/1906369 --- Comment From heinz-werner_se...@de.ibm.com 2021-02-23 06:22 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/1904558 Title: [21.04 FEAT] openCryptoki: PKCS #11 3.0 - baseline provider support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915689] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1906369 *** https://bugs.launchpad.net/bugs/1906369 --- Comment From heinz-werner_se...@de.ibm.com 2021-02-23 08:52 EDT--- IBM Bugzilla status->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/1915689 Title: [UBUNTU 21.04] Opencryptoki 3.15: token_specific_sha_update() causes segmentation fault in main_arena () from /usr/lib64/libc.so.6 (opencryptoki) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1915689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913395] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-02-23 08:51 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/1913395 Title: [UBUNTU 21.04] qemu s390x/pci: Honor vfio DMA limiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913395/+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 heinz-werner_se...@de.ibm.com 2021-02-24 05:15 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/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 1906255] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-02-24 05:16 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/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 1903682] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-02-24 05:17 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/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 1889070] Comment bridged from LTC Bugzilla
--- Comment From bw...@de.ibm.com 2021-02-24 05:32 EDT--- I have done some rudimentary tests with the package on Ubuntu 20.04.1. # 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 # apt info fence-agents Package: fence-agents Version: 4.5.2-1ubuntu1~ppa2 Priority: optional Section: admin Maintainer: Ubuntu Developers Original-Maintainer: Debian HA Maintainers Installed-Size: 839 kB Depends: python3:any, libc6 (>= 2.15), python3-boto3, python3-googleapi, python3-pycurl, python3-pexpect, python3-requests, python3-suds Recommends: libnet-telnet-perl, openssh-client, sg3-utils, snmp Suggests: python3-adal, python3-azure, python3-keystoneauth1, python3-keystoneclient, python3-novaclient Breaks: cman (<= 3.0.12-2ubuntu4) Replaces: cman (<= 3.0.12-2ubuntu4) Download-Size: 236 kB APT-Manual-Installed: yes APT-Sources: http://ppa.launchpad.net/lucaskanashiro/ha-stack-ibm/ubuntu focal/main s390x Packages Description: Fence Agents for Red Hat Cluster Red Hat Fence Agents is a collection of scripts to handle remote power management for several devices. They allow failed or unreachable nodes to be forcibly restarted and removed from the cluster. # fence_ibmz --ip= --username= --password= --plug=M46/m46lp64 -o status Status: ON # fence_ibmz --ip= --username= --password= --plug=M46/m46lp64 -o off Success: Powered OFF # fence_ibmz --ip= --username= --password= --plug=M46/m46lp64 -o status Status: OFF # fence_ibmz --ip= --username= --password= --plug=M46/m46lp64 -o on Success: Powered ON # fence_ibmz --ip= --username= --password= --plug=M46/m46lp64 -o status Status: ON # fence_ibmz --ip=localhost --username=sysprog --password=o8cpav4u --plug=M46/m46lp64 -o list-status [long list of all CECs and LPARs on the HMC] Life-cycle changes/reporting seems to be working fine. I am not sure how the other actions (monitor/validate-all) are supposed to work, let me know if you need me to verify this as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889070 Title: [20.10 FEAT] Add LPAR fence agent to Pacemaker (fence-agents) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916230] Comment bridged from LTC Bugzilla
--- Comment From jakob.nau...@ibm.com 2021-02-24 08:44 EDT--- LGTM & works for me. Awesome, thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916230 Title: [Ubuntu 21.04] QEMU is missing virtio-9p-ccw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1916230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916230] Comment bridged from LTC Bugzilla
--- Comment From jakob.nau...@ibm.com 2021-02-24 09:04 EDT--- Sorry, I was unaware the address would be hidden. LGTM & works for me. Awesome, thank you! Jakob Naucke -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916230 Title: [Ubuntu 21.04] QEMU is missing virtio-9p-ccw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1916230/+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 heinz-werner_se...@de.ibm.com 2021-02-25 07:33 EDT--- IBM Bugzilla status->closed Fix Released with 20.04 -- 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-release-notes/+bug/1902179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903814] Comment bridged from LTC Bugzilla
--- Comment From i...@de.ibm.com 2021-02-25 07:36 EDT---
binutils-s390x-linux-gnu s390x 2.30-21ubuntu1~18.04.5 works fine.
Tested as follows:
#include
char a __attribute((aligned(1)));
char b __attribute((aligned(1)));
int main() { printf("%p %p\n", &a, &b); }
prints the following:
0x2aa00c02014 0x2aa00c02014
on the latest bionic (the pointers are the same - bad).
After the upgrade to bionic-proposed it prints:
0x2aa2ed82015 0x2aa2ed82014
(the pointers are different - good).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903814
Title:
[binutils] Prevent GOT access rewrite for certain symbols
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903814/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2021-02-25 10:28 EDT--- (In reply to comment #25) > For netplan yaml of: > > network: > version: 2 > ethernets: > enc8f00: > dhcp4: yes > > It would be interesting to see if L3 dhcp starts to work if one does: > > $ sudo mkdir -p /etc/systemd/network/10-netplan-enc8f00.network.d > $ cat < /etc/systemd/network/10-netplan-enc8f00.network.d/30-request-broadcast.conf > [DHCPv4] > RequestBroadcast=yes > EOF > > $ sudo networkctl reconfigure enc8f00 > > (or chzdev -d 0.0.8f00; chzdev -e 0.0.8f00 or reboot, whatever is easier to > make networkd force renew). Thank you xnox. I confirm that this works with chzdev -d/-e and with reboot. @Asha, this is a better solution for you. --- Comment From wint...@de.ibm.com 2021-02-25 10:36 EDT--- (In reply to comment #26) > My preference would be to fix networkd, if that fails netplan, and isc-dhcp > only if there is syntax to online the device in the right l2/l3 state via > kernel cmdline and that one needs to complete install over it. > > For example, does automatic chzdev device enablement provides > autoconfiguration for hipersockets in l3? in that case it would be neat for > ip=dhcp to just do the right thing. > Yes, 'chzdev -e' defaults to Layer3 unless you explicitely specify 'chzdev -e layer2=1'. Note that chzdev creates a udev rule to make this setting persistent. > Would turning on RequestBroadcast=yes for ID_NET_DRIVER=qeth_l3 interfaces > be good enough in networkd? Yes, that sounds good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905412] Re: LVM install broken if other disks have meta-data on the VG name already
--- Comment From dougm...@us.ibm.com 2021-02-22 08:37 EDT--- Is this a regression? It's been a long time since I installed Ubuntu, but don't recall any issues when installing multiple instances on a lab machine. Perhaps I never chose LVM, though. Other distros do ensure that the LVM volume name is unique, for example by appending digits such as "001", "002", "003", ... until it is unique. ** Tags added: architecture-ppc64le bugnameltc-191598 severity-high 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/1905412 Title: LVM install broken if other disks have meta-data on the VG name already To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1905412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2021-03-01 02:53 EDT--- This is the setup I use as DHCP client: root@s83lp72:~# cat /etc/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 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 So if you can provide a fix for focal fossa (plus instructions how to install it), I can give it a try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914574] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-03-01 03:41 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/1914574 Title: [21.04 FEAT] Upgrade s390-tools to latest version (2.16.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914574/+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 heinz-werner_se...@de.ibm.com 2021-03-01 03:44 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/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 1906384] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-03-01 03:50 EDT--- IBM Bugzilla status->closed, Problem could currently not reproduced. Therefore -> close. If problem reoccur a new ticket will be opened. -- 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 1913266] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-03-01 06:23 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/1913266 Title: [UBUNTU 20.04] Vsock can't be used with Secure Execution, required argument not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903814] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-03-01 06:32 EDT--- IBM Bugzilla status->closed, Fix Release 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/1903814 Title: [binutils] Prevent GOT access rewrite for certain symbols To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] dhcp_broadcast_qeth_l3.patch
Default Comment by Bridge ** Attachment added: "dhcp_broadcast_qeth_l3.patch" https://bugs.launchpad.net/bugs/1914740/+attachment/5471482/+files/dhcp_broadcast_qeth_l3.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889070] Comment bridged from LTC Bugzilla
--- Comment From bw...@de.ibm.com 2021-03-01 10:45 EDT--- # cat /etc/os-release NAME="Ubuntu" VERSION="18.04.5 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.5 LTS" VERSION_ID="18.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=bionic UBUNTU_CODENAME=bionic # apt show fence-agents Package: fence-agents Version: 4.0.25-2ubuntu1.3~ppa2 Priority: optional Section: admin Maintainer: Ubuntu Developers Original-Maintainer: Debian HA Maintainers Installed-Size: 686 kB Depends: python:any (>= 2.7.5-5~), libc6 (>= 2.15), python-pycurl, python-pexpect Recommends: libnet-telnet-perl, openssh-client, sg3-utils, snmp Suggests: python-requests, python-suds, python-boto3 Conflicts: cman (<= 3.0.12-2ubuntu4) Replaces: cman (<= 3.0.12-2ubuntu4) Download-Size: 198 kB APT-Manual-Installed: yes APT-Sources: http://ppa.launchpad.net/lucaskanashiro/ha-stack-ibm/ubuntu bionic/main s390x Packages Description: Fence Agents for Red Hat Cluster Red Hat Fence Agents is a collection of scripts to handle remote power management for several devices. They allow failed or unreachable nodes to be forcibly restarted and removed from the cluster. I've ran the same commands on Ubuntu 18.04.5 without issues. The only thing that I had to do was manually install python-requests. There's probably a package dependency missing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889070 Title: [20.10 FEAT] Add LPAR fence agent to Pacemaker (fence-agents) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2021-03-01 12:00 EDT--- Works like a charm, thank you xnox! I tested L2 and L3 HiperSockets during reboot. L2 got the IP@ via unicast reply L3 got its IP@ via broadcast reply. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915517] debdiff_groovy.diff
Default Comment by Bridge ** Attachment added: "debdiff_groovy.diff" https://bugs.launchpad.net/bugs/1915517/+attachment/5471572/+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/1915517 Title: [UBUNTU 21.04] openCryptoki: pkcscca migration fails with usr/sb2 is not a valid slot ID To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1915517/+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 heinz-werner_se...@de.ibm.com 2021-03-03 03:55 EDT--- Tested the latest ubuntu21.04 root@m35lp41:~# cat /proc/version Linux version 5.10.0-14-generic (buildd@bos02-s390x-005) (gcc (Ubuntu 10.2.1-6ubuntu2) 10.2.1 20210121, GNU ld (GNU Binutils for Ubuntu) 2.36) #15-Ubuntu SMP Fri Jan 29 15:04:37 UTC 2021 root@m35lp41:~# ls /sys/devices/qeth/0.0.bd00/buffer_count /sys/devices/qeth/0.0.bd00/buffer_count root@m35lp41:~# cat /sys/devices/qeth/0.0.bd00/buffer_count 64 root@m35lp41:~# chzdev qeth bd00 -p layer2=1 buffer_count=128 Configuring devices in the persistent configuration only QETH device 0.0.bd00:0.0.bd01:0.0.bd02 configured Note: The initial RAM-disk must be updated for these changes to take effect: - QETH device 0.0.bd00:0.0.bd01:0.0.bd02 update-initramfs: Generating /boot/initrd.img-5.10.0-14-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Preparing boot device: dasda (af8a). Done. root@m35lp41:~# root@m35lp41:~# cat /sys/devices/qeth/0.0.bd00/buffer_count 64 root@m35lp41:~# reboot packet_write_wait: Connection to UNKNOWN port 65535: Broken pipe [vineeth.vijayan@oc6887364776 ~]$ ssh m35lp41.lnxne.boe r...@m35lp41.lnxne.boe's password: Welcome to Ubuntu Hirsute Hippo (development branch) (GNU/Linux 5.10.0-14-generic s390x) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage System information as of Wed Mar 3 08:23:18 AM UTC 2021 System load: 0.16 Memory usage: 2% Processes: 204 Usage of /: 7.5% of 20.18GB Swap usage: 0% Users logged in: 0 => There were exceptions while processing one or more plugins. See /var/log/landscape/sysinfo.log for more information. 22 updates can be installed immediately. 0 of these updates are security updates. To see these additional updates run: apt list --upgradable Last login: Wed Mar 3 08:14:55 2021 from 172.18.0.1 root@m35lp41:~# root@m35lp41:~# cat /sys/devices/qeth/0.0.bd00/buffer_count 128 Looks good to me. -- 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 1925452] Comment bridged from LTC Bugzilla
--- Comment From alexs...@de.ibm.com 2021-05-17 10:30 EDT--- Verified successfully on 5.4.0-74, with adapter in eswitch mode and adapter firmware 16.27.2008. Thank you! alexschm@pok1-qz1-sr1-rk011-s21:~$ uname -a Linux pok1-qz1-sr1-rk011-s21 5.4.0-74-generic #83 SMP Mon May 17 09:04:32 EDT 2021 s390x s390x s390x GNU/Linux alexschm@pok1-qz1-sr1-rk011-s21:~$ ping 172.31.22.170 PING 172.31.22.170 (172.31.22.170) 56(84) bytes of data. 64 bytes from 172.31.22.170: icmp_seq=1 ttl=0 time=0.217 ms 64 bytes from 172.31.22.170: icmp_seq=2 ttl=0 time=0.162 ms 64 bytes from 172.31.22.170: icmp_seq=3 ttl=0 time=0.191 ms ^C --- 172.31.22.170 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2052ms rtt min/avg/max/mdev = 0.162/0.190/0.217/0.022 ms -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925452 Title: [Ubuntu 21.04] net/mlx5: Fix HW spec violation configuring uplink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925452/+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 2021-05-17 10:50 EDT--- I just did an "apt update && apt upgrade" on a KVM guest with Ubuntu 20.04 that I had previously used installkernel on with an early version of your updated script: Setting up linux-image-5.4.0-73-generic (5.4.0-73.82) ... I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.12.0-rc8-07595-g446009324fa8 I: /boot/initrd.img.old is now a symlink to initrd.img-5.12.0-rc8-07595-g446009324fa8 I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-73-generic I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-73-generic Setting up alsa-utils (1.2.2-1ubuntu2.1) ... alsa-restore.service is a disabled or a static unit not running, not starting it. alsa-state.service is a disabled or a static unit not running, not starting it. Setting up procps (2:3.3.16-1ubuntu2.1) ... Setting up bind9-dnsutils (1:9.16.1-0ubuntu2.8) ... Setting up cloud-init (21.1-19-gbad84ad4-0ubuntu1~20.04.2) ... Setting up linux-modules-extra-5.4.0-73-generic (5.4.0-73.82) ... Setting up linux-image-generic (5.4.0.73.76) ... Setting up linux-generic (5.4.0.73.76) ... Setting up python3-distupgrade (1:20.04.32) ... Setting up ubuntu-release-upgrader-core (1:20.04.32) ... Setting up python3-update-manager (1:20.04.10.7) ... Setting up update-manager-core (1:20.04.10.7) ... Setting up update-notifier-common (3.192.30.7) ... Processing triggers for libc-bin (2.31-0ubuntu9.2) ... Processing triggers for rsyslog (8.2001.0-1ubuntu1.1) ... Processing triggers for systemd (245.4-4ubuntu3.6) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for dbus (1.12.16-2ubuntu2.1) ... Processing triggers for initramfs-tools (0.136ubuntu6.4) ... update-initramfs: Generating /boot/initrd.img-5.12.0-rc8-07595-g446009324fa8 <--- this is the currently running kernel installed with installkernel Not invoking zipl: initrd doesn't exist yet Processing triggers for linux-image-5.4.0-73-generic (5.4.0-73.82) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-73-generic Not invoking zipl: initrd doesn't exist yet /etc/kernel/postinst.d/zz-zipl: Not invoking zipl: initrd doesn't exist yet <--- but above it said it generated ?it!? So usually I would expect that upgrading the kernel after having used installkernel will afterwards use the new distro kernel. Am I correct in that assumption? It might also be that this system is somehow in a weird state but would like confirmation either way. -- 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 1925452] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-05-18 04:19 EDT--- Verified also on groovy and hirsuite.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925452 Title: [Ubuntu 21.04] net/mlx5: Fix HW spec violation configuring uplink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926584] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-05-18 05:04 EDT--- IBM Bugzilla status->closed, Fix Released with impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926584 Title: [21.10 FEAT] Upgrade openssl-ibmca to latest version (crypto) (version 2.1.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1926584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928780] [NEW] [UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is valid
Public bug reported: The Opencryptoki Soft token does not check if an EC key is valid when an EC key is created via C_CreateObject, nor when C_DeriveKey is used with ECDH public data. This may allow one to perform Invalid Curve Attacks. Fix: https://github.com/opencryptoki/opencryptoki/commit/4e3b43c3d8844402c04a66b55c6c940f965109f0 (SOFT: Check the EC Key on C_CreateObject and C_DeriveKey) This commit should apply smooth on top of OCK 3.16.0, but also on OCK 3.15.0 or 3.15.1. EC support has been introduced in the Soft token with OCK 3.15.0. So all OCK versions >= 3.15.0 are affected. Earlier OCK releases are not affected. This problem need only to be fixed with 21.04 wherer 3.15.1 is included. ** Affects: opencryptoki (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-192742 severity-high targetmilestone-inin2104 ** Tags added: architecture-s39064 bugnameltc-192742 severity-high targetmilestone-inin2104 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => opencryptoki (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928780 Title: [UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is valid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencryptoki/+bug/1928780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921498] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-05-18 06:27 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/1921498 Title: [Ubuntu 21.04] s390/vtime: fix increased steal time accounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921104] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-05-19 02:18 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/1921104 Title: net/mlx5e: Add missing capability check for uplink follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928780] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-05-19 02:22 EDT--- Also to be added to 3.16 (impish) . I missed that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928780 Title: [UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is valid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1928780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925211] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-05-19 07:18 EDT--- IBM Response: Yes. this makes sense. Previously Canonical reverted the "s390/cio: remove pm support from ccw bus driver" patch because of the issue. Right solution is to unrevert the revert-patch and add "s390/cio: remove invalid condition on IO_SCH_UNREG" patch. Which makes both available in the kernel. So, we agree on this. In stable 5.13-rc1, we have both the patches. Which is same as 5.11.20 for hirsute. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925211/+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 naynj...@ibm.com 2021-05-19 16:51 EDT--- (In reply to comment #28) > @Nayna Jain @Daniel > > Hm but we have CONFIG_LOAD_PPC_KEYS=y already which I would expect to be > the only thing that loads keys into .platform keyring which was enabled as > part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866909 > LTC-184073 . Which keys are present in firmware / get loaded into .platform > because of that? I would have expected canonical keys to be loaded by that > into the .platform keyring, or is that not the case? Hi, Yes you are right that CONFIG_LOAD_PPC_KEYS enables loading of keys into .platform keyring from firmware at runtime. However, as Daniel has mentioned in his comment dated 2020-12-17 , that the .platform keyring is currently not loaded in pseries firmware as it is static keys based solution and at the moment doesn't have any mechanism to expose trusted keys (this will change with the full key management solution). > > Can you please share contents of "powerpc:db"? Ideally it should contain > Canonical's two OPAL signing certs. > > If canonical keys are not in "powerpc:db", does it make sense to then add > the two Canonical keys to the .builtin_trusted_keys_keyring, and then link > the whole keyring into .ima keyring? > > I will attach the two Canonical OPAL signing keys here, and the ESL for them. The final conclusion was to add a config option for PLATFORM KEYRING similar to SYSTEM_TRUSTED_KEYS mechanism. It would allow loading additional keys compiled into the kernel to be loaded only to .platform keyring. This would be in addition to the existing support for loading firmware keys at runtime on the platfom keyring. It aligns with xnox comment dated "2012-03-18". At some point we will probably close the loop hole that allows self signed certificates loaded onto the builtin keyring to be loaded onto the IMA keyring. It's better to define a mechanism for loading additional certs on the platform keyring that would work today and will continue to work in the future. I am supposed to start looking at the patches. I would be starting to look at them in June timeframe. Thanks & Regards, - Nayna -- 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 1828187] Re: ibm, dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic)
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin18042 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828187 Title: ibm,dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] [NEW] [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
Public bug reported: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition enP50s3832 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition enP50s3832 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition enP53p0s0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition enP53p0s0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0.160 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0.160 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdc0.150 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdc0.150 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition enP50s3832.170 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: Netwo
[Bug 1929790] [NEW] Request to backport fix for endianness issue in TigerVNC vncviewer
Public bug reported: ---Problem Description--- TigerVNC 1.11.0 contains a regression that causes vncviewer to display incorrect colors when vncviewer and X11 server use different endianness (e.g., when using X11 forwarding via SSH between an x86-64 desktop and a Linux system on s390x). The regression was originally reported in github issue https://github.com/TigerVNC/tigervnc/issues/1073 and fixed in github pull request https://github.com/TigerVNC/tigervnc/pull/1084 The regression caused vncviewer to always use the system byte order for pixel values instead of the byte order required by the X11 display. With the fix, vncviewer queries the X11 display for the required byte order. As of now, the fix has not made it into a release yet. Please consider backporting the fix (upstream commit 7ab92639848). I confirmed that this commit cleanly applies on top of release 1.11.0 and fixes the regression. ---uname output--- Linux s390x Machine Type = x15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- See also https://github.com/TigerVNC/tigervnc/issues/1252 - From a Linux x86 system, connect to a Linux system on s390x via SSH with X forwarding - Start a Xvnc session on that Linux system tigervncserver :0 -geometry 800x600 -depth 32 - Start vncviewer on the same Linux system xtigervncviewer :0 - On vncviewer's window on your origin X session, observe incorrect colors. - Optionally, start X11 programs such as xlogo, xclock, or xeyes to make the problem obvious - Optionally, connect to the vnc session directly (i.e., with a vnc client on the origin system) to compare Userspace tool common name: vncviewer The userspace tool has the following bit modes: 64-bit Userspace rpm: tigervnc-viewer Userspace tool obtained from project website: na ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-192826 severity-medium targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-192826 severity-medium 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/1929790 Title: Request to backport fix for endianness issue in TigerVNC vncviewer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926960] Comment bridged from LTC Bugzilla
--- Comment From juergen.chr...@ibm.com 2021-05-27 07:05 EDT--- Please backport https://github.com/opencryptoki/openssl-ibmca/commit/40928425d848827fa8427d677e37178ab3b57e50 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926960 Title: OpenSSL 1.1.1g function EC_KEY_set_group() causes illegal instruction SIGILL in file crypto/ec/ec_key:477 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1926960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929825] [NEW] [Ubuntu 21.04] OSA Device doesn't get enabled if a vlan is specified on the kernel cmdline for the installer
Public bug reported:
The OSA Device doesn't get enabled if a vlan is specified on the kernel
cmdline for the installer.
with the cmdline
`ip=10.1.8.74::10.1.10.1:255.255.252.0::enc800.300:none nameserver=10.1.9.101
vlan=enc800.300:enc800
url=http://10.1.9.101:1002/iso/ubuntu-21.04-live-server-s390x.iso quiet ---`
the boot fails with this message and drops to a shell:
```
BusyBox v1.30.1 (Ubuntu 1:1.30.1-6ubuntu2) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) [6n
ip: SIOCGIFFLAGS: No such device
ip: can't find device 'enc800'
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
ipconfig: enc800.300: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
no search or nameservers found in /run/net-enc800.300.conf /run/net-*.conf /run/
net6-*.conf
Connecting to 10.1.9.101:1002 (10.1.9.101:1002)
wget: can't connect to remote host (10.1.9.101): Network is unreachable
Unable to find a live file system on the network
```
It the zdev 800 doesn't get enabled.
```
ip addr
1: lo: mtu 65536 qdisc noop qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
(initramfs) [6n
lszdev | grep 0.0.0800
qeth 0.0.0800:0.0.0801:0.0.0802 no no
```
But I can enable it manually:
```
chzdev -e 800
QETH device 0.0.0800:0.0.0801:0.0.0802 configured
Note: The initial RAM-disk must be updated for these changes to take effect:
- QETH device 0.0.0800:0.0.0801:0.0.0802
A manual update of the initial RAM-disk is required.
(initramfs) [6n
ip addr
1: lo: mtu 65536 qdisc noop qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enc800: mtu 1500 qdisc noop qlen 1000
link/ether f2:ae:7d:de:88:a0 brd ff:ff:ff:ff:ff:ff
```
The same cmdline (adjusted for the iso url) works on 20.04.
Between 20.04 and 21.04 the line 318 `echo "${VLAN}" | grep -q "${dev}" &&
continue` was added to /scripts/functions in the initrd.ubuntu. If I remove
this line and repack the ramdisk the network boot works as expected like on
ubuntu 20.04
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-192957 severity-high
targetmilestone-inin2104
** Tags added: architecture-s39064 bugnameltc-192957 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/1929825
Title:
[Ubuntu 21.04] OSA Device doesn't get enabled if a vlan is specified
on the kernel cmdline for the installer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929825/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929921] Core dump lines from journal
Default Comment by Bridge ** Attachment added: "Core dump lines from journal" https://bugs.launchpad.net/bugs/1929921/+attachment/5500848/+files/journalextract.log ** 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/1929921 Title: Ubuntu 20.04.2 - OPENSSL_cleanse() fails with segmentation fault in eddsa_test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929921] [NEW] Ubuntu 20.04.2 - OPENSSL_cleanse() fails with segmentation fault in eddsa_test
Public bug reported: ---Problem Description--- === IBM z15 with D41C Bundle S39a and z/VM 7.2.0 guest with crypto cards attached OS: Ubuntu 20.04.2 (focal fossa) with 5.4.0-73-generic and libica 3.6.1 installed Core dump when running the eddsa_test from libica Details === The available openSSL version is: OpenSSL 1.1.1f 31 Mar 2020 The ibmca engine was installed, but not defined into the openssl.cnf file, openssl engine displayed the default line: (dynamic) Dynamic engine loading support The segmentation fault was generated by `./eddsa_test'. Program terminated with signal SIGSEGV, Segmentation fault in openSSL (gdb) bt #0 0x03ff896e50be in OPENSSL_cleanse () from /lib/s390x-linux-gnu/libcrypto.so.1.1 #1 0x03ff898a26fa in ica_ed25519_ctx_del (ctx=0x3fff9b7e010) at ica_api.c:1897 #2 0x02aa28986f14 in ed25519_stress () at eddsa_test.c:441 #3 0x02aa289831bc in main (argc=0x1, argv=0x3fff9b7eaf8) at eddsa_test.c:66 See https://wiki.ubuntu.com/Debug%20Symbol%20Packages about how to define debug repositories apt install libica3-dbgsym #0 0x03ff896e50be in OPENSSL_cleanse () from /lib/s390x-linux-gnu/libcrypto.so.1.1 (gdb) bt # coredumpctl dump 158582 > eddsa.core PID: 158582 (eddsa_test) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Wed 2021-05-26 19:52:28 CEST (15h ago) Command Line: ./eddsa_test Executable: /root/crypto/libica-3.6.1/test/eddsa_test Control Group: /user.slice/user-0.slice/session-9.scope Unit: session-9.scope Slice: user-0.slice Session: 9 Owner UID: 0 (root) Boot ID: 6a7a23240f464a0d9f2d3fa3e82be73e Machine ID: c933ae494f9a4c6e8d82625c952945d5 Hostname: t3514002.lnxne.boe Storage: /var/lib/systemd/coredump/core.eddsa_test.0.6a7a23240f464a0d9f2d3fa3e82be73e.158582.1622051548.lz4 Message: Process 158582 (eddsa_test) of user 0 dumped core. Stack trace of thread 158582: #0 0x03ff896e50be OPENSSL_cleanse (libcrypto.so.1.1 + 0x1650be) ---uname output--- Linux system 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = Manufacturer: IBM Type: 8561 Model:703 T01 ---Debugger--- A debugger was configured, however the system did not enter into the debugger ---Steps to Reproduce--- 1.) install the github libica 3.6.1 package and build the test cases 2.) cd .../libica-3.6.1 3.) ./bootstrap.sh; configure --enable-coverage 4.) make coverage Watch the segmentation fault to happen Userspace tool common name: eddsa_test The userspace tool has the following bit modes: 64bit Userspace rpm: libica3 Userspace tool obtained from project website: na The problem could be reproduced with libica 3.6.1, however, it does not show up with libica 3.8.0. Looks like the problem was fixed by commit https://github.com/opencryptoki/libica/commit/b40d0d2ad4a2aac088cf47befbddd8b3b9fca1c5 After applying this fix on top of 3.6.1, the segfault does not occur anymore. It's sufficient to apply the 4 changes in eddsa_test.c. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-192953 severity-high targetmilestone-inin20042 ** Tags added: architecture-s39064 bugnameltc-192953 severity-high targetmilestone-inin20042 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929921 Title: Ubuntu 20.04.2 - OPENSSL_cleanse() fails with segmentation fault in eddsa_test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929921] compressed eddsa core file
Default Comment by Bridge ** Attachment added: "compressed eddsa core file" https://bugs.launchpad.net/bugs/1929921/+attachment/5500847/+files/eddsa.core.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929921 Title: Ubuntu 20.04.2 - OPENSSL_cleanse() fails with segmentation fault in eddsa_test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929923] [NEW] [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function
Public bug reported: ---Problem Description--- kernel panic rq_qos_wake_function ---uname output--- Linux version 5.4.0-71-generic Machine Type = s390x ---Debugger--- A debugger is not configured Stack trace output: May 15 20:21:04 data1 kernel: Call Trace: May 15 20:21:04 data1 kernel: ([<00234091e670>] 0x234091e670) May 15 20:21:04 data1 kernel: [<003e10047e3a>] rq_qos_wake_function+0x8a/0xa0 May 15 20:21:04 data1 kernel: [<003e0fbec482>] __wake_up_common+0xa2/0x1b0 May 15 20:21:04 data1 kernel: [<003e0fbec984>] __wake_up_common_lock+0x94/0xe0 May 15 20:21:04 data1 kernel: [<003e0fbec9fa>] __wake_up+0x2a/0x40 May 15 20:21:04 data1 kernel: [<003e1005ee70>] wbt_done+0x90/0xe0 May 15 20:21:04 data1 kernel: [<003e10047f42>] __rq_qos_done+0x42/0x60 May 15 20:21:04 data1 kernel: [<003e10033cb0>] blk_mq_free_request+0xe0/0x140 May 15 20:21:04 data1 kernel: [<003e101d46f0>] dm_softirq_done+0x140/0x230 May 15 20:21:04 data1 kernel: [<003e100326c0>] blk_done_softirq+0xc0/0xe0 May 15 20:21:04 data1 kernel: [<003e103fc084>] __do_softirq+0x104/0x360 May 15 20:21:04 data1 kernel: [<003e0fb9da1e>] irq_exit+0x9e/0xc0 May 15 20:21:04 data1 kernel: [<003e0fb28ae8>] do_IRQ+0x78/0xb0 May 15 20:21:04 data1 kernel: [<003e103fb588>] ext_int_handler+0x130/0x134 May 15 20:21:04 data1 kernel: [<003e101d4416>] dm_mq_queue_rq+0x36/0x1d0 May 15 20:21:04 data1 kernel: Last Breaking-Event-Address: May 15 20:21:04 data1 kernel: [<003e0fbce75e>] wake_up_process+0xe/0x20 May 15 20:21:04 data1 kernel: Kernel panic - not syncing: Fatal exception in interrupt Oops output: no System Dump Info: The system was configured to capture a dump, however a dump was not produced. -Attach sysctl -a output output to the bug. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-192966 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-192966 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/1929923 Title: [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929926] [NEW] [UBUNTU 21.10] qemu: target/s390x: Fix translation exception on illegal instruction
Public bug reported: --Problem Description--- Using an uretprobe in QEMU without hardware acceleration causes a SIGSEGV. ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Run attach_probe eBPF testcase in QEMU. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/testing/selftests/bpf/prog_tests/attach_probe.c?h=v5.12#n73 Userspace tool common name: na The userspace tool has the following bit modes: 64-bit Userspace rpm: na Userspace tool obtained from project website: na Fix: https://git.qemu.org/?p=qemu.git;a=commit;h=86131c71b13257e095d8c4f4453d52cbc6553c07 Package qemu focal (20.04LTS) 1:4.2-3ubuntu6.14 groovy (20.10) 1:5.0-5ubuntu9.6 hirsute (21.04)1:5.2+dfsg-9ubuntu2 impish (metapackages): 1:5.2+dfsg-9ubuntu3 It would be good to have this fix in 20.04 and the later ones. The patch applies cleanly to all levels. ** Affects: qemu (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-all bugnameltc-192947 severity-medium targetmilestone-inin2110 ** Tags added: architecture-all bugnameltc-192947 severity-medium targetmilestone-inin2110 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** 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/1929926 Title: [UBUNTU 21.10] qemu: target/s390x: Fix translation exception on illegal instruction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1929926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929921] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-05-28 05:09 EDT--- Please close this ticket. The problem only occurs in the testsuite not in the production package... Many thanks --- Comment From heinz-werner_se...@de.ibm.com 2021-05-28 05:10 EDT--- IBM Bugzilla status->closed, Not a bug ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929921 Title: Ubuntu 20.04.2 - OPENSSL_cleanse() fails with segmentation fault in eddsa_test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929923] Re: [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function
** Tags removed: severity-high ** Tags added: severity-critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929923 Title: [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929926] Comment bridged from LTC Bugzilla
--- Comment From i...@de.ibm.com 2021-06-01 09:37 EDT---
Here is a small test that doesn't require installing extra tools or building
code:
echo "r:bash_readline /bin/bash:0x$(nm -D /bin/bash | awk '/T readline$/ {print
$1}')" >/sys/kernel/debug/tracing/uprobe_events
echo 1 >/sys/kernel/debug/tracing/events/uprobes/bash_readline/enable
cat /sys/kernel/debug/tracing/trace
With the unfixed qemu you will lose your shell (provided it's bash)
after step 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929926
Title:
[UBUNTU 21.10] qemu: target/s390x: Fix translation exception on
illegal instruction
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1929926/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] lshw
--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-01 13:30 EDT--- ** Attachment added: "lshw" https://bugs.launchpad.net/bugs/1929657/+attachment/5501728/+files/lshw.rtf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-01 13:57 EDT--- This is the actual configuration of HBA assigned to the Host: root@ilabg13:~# znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.0e0f,0.0.0e10,0.0.0e11 1731/01 OSD_1000 EE qeth ence0f online 0.0.0dc0,0.0.0dc1,0.0.0dc2 1731/01 OSD_25GIG DA qeth encdc0 online 0.0.0db0,0.0.0db1,0.0.0db2 1731/01 OSD_25GIG D9 qeth encdb0 online root@ilabg13:~# lspci 0032:00:00.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function] 0035:00:00.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function] The RoCE adapters are: enP50s3832 <- working ok enP53p0s0 <- vLan not getting IP assigned The full output of lshw is in the attachments, here the reduced output for network class: root@ilabg13:~# lshw -class network *-network:0 description: Ethernet interface product: MT27710 Family [ConnectX-4 Lx Virtual Function] vendor: Mellanox Technologies physical id: 5 bus info: pci@0032:00:00.0 logical name: enP50s3832 version: 00 serial: 82:0c:9b:a8:a1:b2 capacity: 25Gbit/s width: 64 bits clock: 33MHz capabilities: pciexpress msix bus_master cap_list ethernet physical fibre 1000bt-fd 1bt-fd 25000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=mlx5_core driverversion=5.0-0 duplex=full firmware=14.25.1020 (IBM16) ip=11.111.112.214 latency=0 link=yes multicast=yes port=fibre resources: iomemory:d-c irq:0 memory:8000-800f *-network:1 description: Ethernet interface product: MT27710 Family [ConnectX-4 Lx Virtual Function] vendor: Mellanox Technologies physical id: 6 bus info: pci@0035:00:00.0 logical name: enP53p0s0 version: 00 serial: 82:0c:9b:c9:78:f8 capacity: 25Gbit/s width: 64 bits clock: 33MHz capabilities: pciexpress msix bus_master cap_list ethernet physical fibre 1000bt-fd 1bt-fd 25000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=mlx5_core driverversion=5.0-0 duplex=full firmware=14.25.1020 (IBM16) ip=11.111.112.215 latency=0 link=yes multicast=yes port=fibre resources: iomemory:fc000-fbfff irq:0 memory:8001-8001000f *-device:7 description: Ethernet interface product: 1732/01 physical id: 8 bus info: ccw@0.0.0db0 logical name: encdb0 serial: 02:76:54:00:00:03 capabilities: ethernet physical fibre autonegotiation configuration: autonegotiation=on broadcast=yes driver=qeth_l2 driverversion=1.0 duplex=full firmware=0165 ip=11.111.114.213 link=yes multicast=yes port=fibre *-device:8 description: OSA-Express QDIO channel product: 1732/01 physical id: 9 bus info: ccw@0.0.0db1 configuration: driver=qeth *-device:9 description: OSA-Express QDIO channel product: 1732/01 physical id: a bus info: ccw@0.0.0db2 configuration: driver=qeth *-device:10 description: Ethernet interface product: 1732/01 physical id: b bus info: ccw@0.0.0dc0 logical name: encdc0 serial: 02:76:54:00:00:04 capabilities: ethernet physical fibre autonegotiation configuration: autonegotiation=on broadcast=yes driver=qeth_l2 driverversion=1.0 duplex=full firmware=0165 ip=11.111.112.213 link=yes multicast=yes port=fibre *-device:11 description: OSA-Express QDIO channel product: 1732/01 physical id: c bus info: ccw@0.0.0dc1 configuration: driver=qeth *-device:12 description: OSA-Express QDIO channel product: 1732/01 physical id: d bus info: ccw@0.0.0dc2 configuration: driver=qeth *-device:13 description: Ethernet interface product: 1732/01 physical id: e bus info: ccw@0.0.0e0f logical name: ence0f serial: 02:76:54:00:00:08 size: 1Gbit/s capacity: 1Gbit/s capabilities: ethernet physical fibre 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=qeth_l2 driverversion=1.0 duplex=full firmware=0165 ip=9.11.116.213 link=yes multicast=yes port=fibre speed=1Gbit/s *-device:14 description: OSA-Express QDIO channel product: 1732/01 physical id: f bus info: ccw@0.0.0e10 configuration: driver=qeth *-device:15 description: OSA-Express QDIO channel product: 1732/01 physical id: 10 bus info: ccw@0.0.0e11 configuration: driver=qeth *-device:16 description: Network adapter product: 1732/03 physical id: 11 bus info: ccw@0.0.100d configuration: driver=zfcp *-device:17 description: Network adapter product: 1732/03 physical id: 12 bus info: ccw@0.0.110d configuration: driver=zfcp *-device:18 description: Network adapter product: 1732/03 physical id: 13 bus info: ccw@0.0.120d configuration: driver=zfcp *-device:19 description: Network adapter product: 1732/03 physical id: 14 bus info: ccw@0.0.130d configuration: driver=zfcp *-network:0 description: Ethernet interface physical id: 5b logical name: enP53p0s0.171 serial: 82:0c:9b:
[Bug 1926960] Comment bridged from LTC Bugzilla
--- Comment From juergen.chr...@ibm.com 2021-06-04 04:47 EDT--- Test successful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926960 Title: OpenSSL 1.1.1g function EC_KEY_set_group() causes illegal instruction SIGILL in file crypto/ec/ec_key:477 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1926960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931063] [NEW] Include powerpc port upstream fixes to librpmem 1.10 on pmdk package
Public bug reported: == Comment: #0 - Lucas Alexandre Mello Magalhaes - 2021-06-04 14:06:47 == On PPC64LE there is an issue on librpmem check for RPMEM_RAW_BUFF_SIZE. This is fixed upstream already. Please include the follow commits to include the fix. 652659830 rpmem: Fix RPMEM_RAW_BUFF_SIZE and LANE_ALIGN_SIZE for powerpc64le e672c09d9 common: Move page_size.h from common to core The following patches are fixes to the unity test. Please include them if you need for testing. bc048c7e4 test: Fix obj_rpmem_heap_state for ppc64le 736e42b1d test: Fix pmempool_sync_remote for ppc64 2e1a6a1da test: fix rpmem_basic for ppc64le 74e3ca419 test: Add create_recovery_file_absolute ffeb20d6c test: Fix rpmemd_obc POOL_DESC_SIZE redefinition aa7aae2b4 test: Fix tools/fip includes ** Affects: kernel-package (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-193088 severity-medium targetmilestone-inin--- ** Tags added: architecture-ppc64le bugnameltc-193088 severity-medium targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => kernel-package (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931063 Title: Include powerpc port upstream fixes to librpmem 1.10 on pmdk package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1931063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931063] Comment bridged from LTC Bugzilla
--- Comment From tuli...@br.ibm.com 2021-06-07 10:25 EDT--- > I think this affects pmdk (rather the Linux kernel). Correct. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931063 Title: Include powerpc port upstream fixes to librpmem 1.10 on pmdk package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1931063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-07 13:56 EDT--- Could you provide a place to upload the system.journal file? it pass the limit of 51200 KB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] system.journal
--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-07 14:39 EDT--- ** Attachment added: "system.journal" https://bugs.launchpad.net/bugs/1929657/+attachment/5502962/+files/system.journal.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-07 14:49 EDT--- Compressed and attached system.journal. Frank, I have other systems with similar configurations but not exactly the same. It is another ubuntu host but Native linux installed in its own Lpar, and have some other hosts in a zVM bug with different OS. All of them with 2 OSA adapters and 2 RoCE. This is the first time that this issue is seen we have being using this host for at least 6 moths without doing OS reinstallation or changing the adapters and was working correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] joutnalctl
--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-07 16:08 EDT--- ** Attachment added: "joutnalctl" https://bugs.launchpad.net/bugs/1929657/+attachment/5502963/+files/dump-of-journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-07 16:13 EDT--- Just executed netplan try and netplan apply and take snapshot of journalctl. It is attached now! - The configuration has not being touched for long time - Correct is the only one presenting this problem - Correct all of the host has RoCe v2.X installed Could you explain what do you mean with setup the vLan using the IP commands? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From stefan.ra...@de.ibm.com 2021-06-09 05:41 EDT--- Hi Frank, Do we know which component is supposed to set the IP address in Mario's case? Probably netplan...?! It's debug log doesn't say anything about IP addresses being set, which is unfortunate. So here's a couple of oddities(?) / shots in the dark: (1) Mario's config file has no "renderer" statement - maybe add one? (2) "version: 2" appears at the end - that's what netplan, according to its log, does anyway - but on my system, that's at the top of the file, not at the end. Maybe move it up? I.e. my config file looks like this: network: version: 2 renderer: networkd ethernets: (3) enP53p0s0.171 is the final interface listed in the config file. Can you move to a different position to check if that makes a difference? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-09 11:27 EDT--- Attached the output of journalctl -o verbose Also did some changes int he netplan config file and the result was the same: config file: network: version: 2 ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : macaddress: 82:0c:9b:a8:a1:b2 enP53p0s0: macaddress: 82:0c:9b:c9:78:f8 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 configuration result: root@ilabg13:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: encdb0: mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 02:76:54:00:00:03 brd ff:ff:ff:ff:ff:ff inet 11.111.114.213/22 brd 11.111.115.255 scope global encdb0 valid_lft forever preferred_lft forever inet6 fe80::76:54ff:fe00:3/64 scope link valid_lft forever preferred_lft forever 3: encdc0: mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 02:76:54:00:00:04 brd ff:ff:ff:ff:ff:ff inet 11.111.112.213/22 brd 11.111.115.255 scope global encdc0 valid_lft forever preferred_lft forever inet6 fe80::76:54ff:fe00:4/64 scope link valid_lft forever preferred_lft forever 4: ence0f: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 02:76:54:00:00:08 brd ff:ff:ff:ff:ff:ff inet 9.11.116.213/24 brd 9.11.116.255 scope global ence0f valid_lft forever preferred_lft forever inet6 2002:90b:e006:116:76:54ff:fe00:8/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 2591965sec preferred_lft 604765sec inet6 fe80::76:54ff:fe00:8/64 scope link valid_lft forever preferred_lft forever 5: enP50s3832: mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 82:0c:9b:a8:a1:b2 brd ff:ff:ff:ff:ff:ff inet6 fe80::800c:9bff:fea8:a1b2/64 scope link valid_lft forever preferred_lft forever 6: enP53p0s0: mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 82:0c:9b:c9:78:f8 brd ff:ff:ff:ff:ff:ff inet6 fe80::800c:9bff:fec9:78f8/64 scope link valid_lft forever preferred_lft forever 7: enP53p0s0.171@enP53p0s0: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether 82:0c:9b:c9:78:f8 brd ff:ff:ff:ff:ff:ff inet6 fe80::800c:9bff:fec9:78f8/64 scope link valid_lft forever preferred_lft forever 8: enP50s3832.170@enP50s3832: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether 82:0c:9b:a8:a1:b2 brd ff:ff:ff:ff:ff:ff inet 192.168.170.53/24 brd 192.168.170.255 scope global enP50s3832.170 valid_lft forever preferred_lft forever inet6 fe80::800c:9bff:fea8:a1b2/64 scope link valid_lft forever preferred_lft forever 9: encdc0.150@encdc0: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether 02:76:54:00:00:04 brd ff:ff:ff:ff:ff:ff inet 192.168.150.53/24 brd 192.168.150.255 scope global encdc0.150 valid_lft forever preferred_lft forever inet6 fe80::76:54ff:fe00:4/64 scope link valid_lft forever preferred_lft forever 10: encdb0.160@encdb0: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether 02:76:54:00:00:03 brd ff:ff:ff:ff:ff:ff inet 192.168.160.53/24 brd 192.168.160.255 scope global encdb0.160 valid_lft forever preferred_lft forever inet6 fe80::76:54ff:fe00:3/64 scope link valid_lft forever preferred_lft forever -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] journalctl verbose
--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-09 11:22 EDT--- ** Attachment added: "journalctl verbose" https://bugs.launchpad.net/bugs/1929657/+attachment/5503579/+files/journalctl_verbose.txt.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-09 11:37 EDT--- Adding another journalctl to trace the setup with ip command I proceded to execute: root@ilabg13:~# ip addr add 192.168.171.53/24 dev enP53p0s0.171 And that get the ip assigned: root@ilabg13:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: encdb0: mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 02:76:54:00:00:03 brd ff:ff:ff:ff:ff:ff inet 11.111.114.213/22 brd 11.111.115.255 scope global encdb0 valid_lft forever preferred_lft forever inet6 fe80::76:54ff:fe00:3/64 scope link valid_lft forever preferred_lft forever 3: encdc0: mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 02:76:54:00:00:04 brd ff:ff:ff:ff:ff:ff inet 11.111.112.213/22 brd 11.111.115.255 scope global encdc0 valid_lft forever preferred_lft forever inet6 fe80::76:54ff:fe00:4/64 scope link valid_lft forever preferred_lft forever 4: ence0f: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 02:76:54:00:00:08 brd ff:ff:ff:ff:ff:ff inet 9.11.116.213/24 brd 9.11.116.255 scope global ence0f valid_lft forever preferred_lft forever inet6 2002:90b:e006:116:76:54ff:fe00:8/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 2591957sec preferred_lft 604757sec inet6 fe80::76:54ff:fe00:8/64 scope link valid_lft forever preferred_lft forever 5: enP50s3832: mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 82:0c:9b:a8:a1:b2 brd ff:ff:ff:ff:ff:ff inet6 fe80::800c:9bff:fea8:a1b2/64 scope link valid_lft forever preferred_lft forever 6: enP53p0s0: mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 82:0c:9b:c9:78:f8 brd ff:ff:ff:ff:ff:ff inet6 fe80::800c:9bff:fec9:78f8/64 scope link valid_lft forever preferred_lft forever 7: enP53p0s0.171@enP53p0s0: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether 82:0c:9b:c9:78:f8 brd ff:ff:ff:ff:ff:ff inet 192.168.171.53/24 scope global enP53p0s0.171 valid_lft forever preferred_lft forever inet6 fe80::800c:9bff:fec9:78f8/64 scope link valid_lft forever preferred_lft forever 8: enP50s3832.170@enP50s3832: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether 82:0c:9b:a8:a1:b2 brd ff:ff:ff:ff:ff:ff inet 192.168.170.53/24 brd 192.168.170.255 scope global enP50s3832.170 valid_lft forever preferred_lft forever inet6 fe80::800c:9bff:fea8:a1b2/64 scope link valid_lft forever preferred_lft forever 9: encdc0.150@encdc0: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether 02:76:54:00:00:04 brd ff:ff:ff:ff:ff:ff inet 192.168.150.53/24 brd 192.168.150.255 scope global encdc0.150 valid_lft forever preferred_lft forever inet6 fe80::76:54ff:fe00:4/64 scope link valid_lft forever preferred_lft forever 10: encdb0.160@encdb0: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether 02:76:54:00:00:03 brd ff:ff:ff:ff:ff:ff inet 192.168.160.53/24 brd 192.168.160.255 scope global encdb0.160 valid_lft forever preferred_lft forever inet6 fe80::76:54ff:fe00:3/64 scope link valid_lft forever preferred_lft forever -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] journalctl vlan setup whit ip cmd
--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-09 11:34 EDT--- ** Attachment added: "journalctl vlan setup whit ip cmd" https://bugs.launchpad.net/bugs/1929657/+attachment/5503581/+files/journalctl_ipcmd.txt.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-09 11:50 EDT--- Did another experiment and removed the IP assigned to both RoCE adapters vLans using ip command and ran the netplan apply. The issue was recreated only one of the vLans gets the ip assigned the other one didn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-09 15:04 EDT--- Steeps followed... Updated systemd-networkd loglevel: root@ilabg13:~# cat /etc/systemd/system/systemd-networkd.service.d/override.conf [Service] Environment=SYSTEMD_LOG_LEVEL=debug root@ilabg13:~# systemctl restart systemd-networkd Removed manually the IP: ip addr del 192.168.171.53/24 dev enP53p0s0.171 Configure network using netplan: root@ilabg13:~# netplan apply root@ilabg13:~# networkctl status enP53p0s0.171 --no-pager ? 7: enP53p0s0.171 Link File: n/a Network File: n/a Type: vlan State: degraded (pending) HW Address: 82:0c:9b:c9:78:f8 MTU: 9000 (max: 65535) Queue Length (Tx/Rx): 1/1 Auto negotiation: yes Speed: 25Gbps Duplex: full Port: fibre Address: fe80::800c:9bff:fec9:78f8 Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Link 7 added Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: link pending udev initialization... Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: netdev has index 7 Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Saved original MTU: 9000 Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Remembering foreign address: fe80::800c:9bff:fec9:78f8/64 (valid forever) Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Gained IPv6LL Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Remembering route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a, scope: glob? multicast Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Remembering route: dst: fe80::800c:9bff:fec9:78f8/128, src: n/a, gw: n/a, pref?ype: local Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Remembering route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a, scope: glo?e: unicast Manually adding IP: root@ilabg13:~# ip addr add 192.168.171.53/24 dev enP53p0s0.171 root@ilabg13:~# networkctl status enP53p0s0.171 --no-pager ? 7: enP53p0s0.171 Link File: n/a Network File: n/a Type: vlan State: routable (pending) HW Address: 82:0c:9b:c9:78:f8 MTU: 9000 (max: 65535) Queue Length (Tx/Rx): 1/1 Auto negotiation: yes Speed: 25Gbps Duplex: full Port: fibre Address: 192.168.171.53 fe80::800c:9bff:fec9:78f8 Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Remembering foreign address: fe80::800c:9bff:fec9:78f8/64 (valid forever) Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Gained IPv6LL Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Remembering route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a, scope: glob? multicast Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Remembering route: dst: fe80::800c:9bff:fec9:78f8/128, src: n/a, gw: n/a, pref?ype: local Jun 09 11:59:40 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Remembering route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a, scope: glo?e: unicast Jun 09 12:02:03 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Remembering foreign address: 192.168.171.53/24 (valid forever) Jun 09 12:02:03 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Remembering route: dst: 192.168.171.53/32, src: n/a, gw: n/a, prefsrc: 192.168?ype: local Jun 09 12:02:03 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Remembering route: dst: 192.168.171.0/24, src: n/a, gw: n/a, prefsrc: 192.168.?e: unicast Jun 09 12:02:03 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Remembering route: dst: 192.168.171.0/32, src: n/a, gw: n/a, prefsrc: 192.168.? broadcast Jun 09 12:02:03 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2801696]: enP53p0s0.171: Remembering route: dst: 192.168.171.255/32, src: n/a, gw: n/a, prefsrc: 192.16? broadcast -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-09 17:17 EDT--- Attaching output of 'journalctl -b -u systemd-networkd --no-pager' after 'systemctl daemon-reload && systemctl restart systemd-networkd' execution File -> journalctl_deamon-reload -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] journalctl_deamon-reload
--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-09 17:14 EDT--- ** Attachment added: "journalctl_deamon-reload" https://bugs.launchpad.net/bugs/1929657/+attachment/5503691/+files/journalctl_daemon-reload.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
