September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1190146] [Build N.199.1] toolbox: Error: cannot setup namespace using newuidmap: exit status 1
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190146 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190146] [Build N.199.1] toolbox: Error: cannot setup namespace using newuidmap: exit status 1
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190146 https://bugzilla.suse.com/show_bug.cgi?id=1190146#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|rbrown(a)suse.com |mvetter(a)suse.com --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- The problem: /etc/subuid and /etc/subgid contain both: <name>:0:0 if I change both files to <name>:100000:65536 it works. Account was created as root with "useradd -m <name>". Michael, why are there on '0' in the files? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185268] EDITOR env var not set
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1185268 https://bugzilla.suse.com/show_bug.cgi?id=1185268#c6 Danilo Spinella <danilo.spinella(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #6 from Danilo Spinella <danilo.spinella(a)suse.com> --- I cannot reproduce this bug with a clean installation of Tumbleweed, closing. Please reopen this bug if you face this issue again. Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190567] vmlinuz is no longer present on /boot/ breaking separate boot partitions
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190567 https://bugzilla.suse.com/show_bug.cgi?id=1190567#c9 --- Comment #9 from Michal Suchanek <msuchanek(a)suse.com> --- So far I am not aware of any difference between rPi and any other EFI system. The EFI partition contains the bootloader, and the /boot partition (if any) contains the kernel and ramdisk. The extra part on rPi is that the firmware needs to be stored on the disk for version 3 and earlier, and depending on the disk layout the same partition can be used for EFI and firmware. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182761] New: workqueue lockup in xfs in Google Compute Engine
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1182761 Bug ID: 1182761 Summary: workqueue lockup in xfs in Google Compute Engine Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: maciek.borzecki(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: Community User Blocker: --- We are trying to use the Tumbleweed snapshots in our CI, but whenever govendor sync is executed with a larger number of dependencies, the GCE nodes stop responding. We are using the JeOS Tumbleweed Snapshot from https://download.opensuse.org/tumbleweed/appliances/ add the build dependencies and Cloud:Tools repository. I believe this is the last snapshot we have tried: https://download.opensuse.org/tumbleweed/appliances/openSUSE-Tumbleweed-JeO… I was able to collect the following backtrace: Feb 25 14:34:54 feb251430-278071 systemd[1]: Stopped User Runtime Directory /run/user/12345. Feb 25 14:34:54 feb251430-278071 systemd[1]: Removed slice User Slice of UID 12345. Feb 25 14:35:06 feb251430-278071 kernel: ------------[ cut here ]------------ Feb 25 14:35:06 feb251430-278071 kernel: kernel BUG at mm/filemap.c:1499! Feb 25 14:35:06 feb251430-278071 kernel: invalid opcode: 0000 [#1] SMP PTI Feb 25 14:35:06 feb251430-278071 kernel: CPU: 0 PID: 85 Comm: kworker/0:2 Not tainted 5.10.16-1-default #1 openSUSE Tumbleweed Feb 25 14:35:06 feb251430-278071 kernel: Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Feb 25 14:35:06 feb251430-278071 kernel: Workqueue: xfs-conv/sda3 xfs_end_io [xfs] Feb 25 14:35:06 feb251430-278071 kernel: RIP: 0010:end_page_writeback+0xbb/0xc0 Feb 25 14:35:06 feb251430-278071 kernel: Code: 34 83 e0 07 83 f8 04 75 e8 48 8b 45 08 8b 40 68 83 e8 01 83 f8 01 77 d9 48 89 ef 5d e9 2e e5 00 00 48 89 ef 5d e9 75 e4 00 00 <0f> 0b 0f 1f 00 0f 1f 44 00 00 41 54 55 48 89 fd 53 89 d3 40 84 f6 Feb 25 14:35:06 feb251430-278071 kernel: RSP: 0018:ffffb15640153d80 EFLAGS: 00010246 Feb 25 14:35:06 feb251430-278071 kernel: RAX: 0000000000000000 RBX: 000000000000008f RCX: 0000000000000000 Feb 25 14:35:06 feb251430-278071 kernel: RDX: 0000000000000000 RSI: ffff9ddb6ffe8000 RDI: 0000000000000000 Feb 25 14:35:06 feb251430-278071 kernel: RBP: ffffd554c4421a80 R08: 0000000000001000 R09: 0000000000000001 Feb 25 14:35:06 feb251430-278071 kernel: R10: ffff9ddb6ffe8000 R11: 0000000000000020 R12: 0000000000000000 Feb 25 14:35:06 feb251430-278071 kernel: R13: 0000000000000000 R14: ffff9ddb59dd4800 R15: ffffd554c4421a80 Feb 25 14:35:06 feb251430-278071 kernel: FS: 0000000000000000(0000) GS:ffff9ddb6c000000(0000) knlGS:0000000000000000 Feb 25 14:35:06 feb251430-278071 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 25 14:35:06 feb251430-278071 kernel: CR2: 0000559245e6b000 CR3: 0000000101a46001 CR4: 00000000001706f0 Feb 25 14:35:06 feb251430-278071 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Feb 25 14:35:06 feb251430-278071 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Feb 25 14:35:06 feb251430-278071 kernel: Call Trace: Feb 25 14:35:06 feb251430-278071 kernel: iomap_finish_ioend+0x127/0x250 Feb 25 14:35:06 feb251430-278071 kernel: iomap_finish_ioends+0x41/0x90 Feb 25 14:35:06 feb251430-278071 kernel: xfs_end_ioend+0x6d/0x110 [xfs] Feb 25 14:35:06 feb251430-278071 kernel: xfs_end_io+0xac/0xe0 [xfs] Feb 25 14:35:06 feb251430-278071 kernel: process_one_work+0x1df/0x370 Feb 25 14:35:06 feb251430-278071 kernel: worker_thread+0x50/0x400 Feb 25 14:35:06 feb251430-278071 kernel: ? process_one_work+0x370/0x370 Feb 25 14:35:06 feb251430-278071 kernel: kthread+0x11b/0x140 Feb 25 14:35:06 feb251430-278071 kernel: ? __kthread_bind_mask+0x60/0x60 Feb 25 14:35:06 feb251430-278071 kernel: ret_from_fork+0x22/0x30 Feb 25 14:35:06 feb251430-278071 kernel: Modules linked in: dm_mod af_packet iscsi_ibft iscsi_boot_sysfs button nls_iso8859_1 nls_cp437 vfat fat drm configfs xfs libcrc32c crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd virtio_net cryptd glue_helper net_failover virtio_scsi failover sg virtio_rng Feb 25 14:35:06 feb251430-278071 kernel: ---[ end trace d087eea0f8414966 ]--- Feb 25 14:35:06 feb251430-278071 kernel: RIP: 0010:end_page_writeback+0xbb/0xc0 Feb 25 14:35:06 feb251430-278071 kernel: Code: 34 83 e0 07 83 f8 04 75 e8 48 8b 45 08 8b 40 68 83 e8 01 83 f8 01 77 d9 48 89 ef 5d e9 2e e5 00 00 48 89 ef 5d e9 75 e4 00 00 <0f> 0b 0f 1f 00 0f 1f 44 00 00 41 54 55 48 89 fd 53 89 d3 40 84 f6 Feb 25 14:35:06 feb251430-278071 kernel: RSP: 0018:ffffb15640153d80 EFLAGS: 00010246 Feb 25 14:35:06 feb251430-278071 kernel: RAX: 0000000000000000 RBX: 000000000000008f RCX: 0000000000000000 Feb 25 14:35:06 feb251430-278071 kernel: RDX: 0000000000000000 RSI: ffff9ddb6ffe8000 RDI: 0000000000000000 Feb 25 14:35:06 feb251430-278071 kernel: RBP: ffffd554c4421a80 R08: 0000000000001000 R09: 0000000000000001 Feb 25 14:35:06 feb251430-278071 kernel: R10: ffff9ddb6ffe8000 R11: 0000000000000020 R12: 0000000000000000 Feb 25 14:35:06 feb251430-278071 kernel: R13: 0000000000000000 R14: ffff9ddb59dd4800 R15: ffffd554c4421a80 Feb 25 14:35:06 feb251430-278071 kernel: FS: 0000000000000000(0000) GS:ffff9ddb6c000000(0000) knlGS:0000000000000000 Feb 25 14:35:06 feb251430-278071 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 25 14:35:06 feb251430-278071 kernel: CR2: 0000559245e6b000 CR3: 0000000101a46001 CR4: 00000000001706f0 Feb 25 14:35:06 feb251430-278071 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Feb 25 14:35:06 feb251430-278071 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Feb 25 14:36:07 feb251430-278071 kernel: BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 60s! Feb 25 14:36:07 feb251430-278071 kernel: Showing busy workqueues and worker pools: Feb 25 14:36:07 feb251430-278071 kernel: workqueue events: flags=0x0 Feb 25 14:36:07 feb251430-278071 kernel: pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=5/256 refcnt=6 Feb 25 14:36:07 feb251430-278071 kernel: pending: vmstat_shepherd, netstamp_clear, check_corruption, ima_keys_handler, free_work Feb 25 14:36:07 feb251430-278071 kernel: workqueue events_power_efficient: flags=0x80 Feb 25 14:36:07 feb251430-278071 kernel: pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=3/256 refcnt=4 Feb 25 14:36:07 feb251430-278071 kernel: pending: fb_flashcursor, neigh_periodic_work, neigh_periodic_work Feb 25 14:36:07 feb251430-278071 kernel: workqueue mm_percpu_wq: flags=0x8 Feb 25 14:36:07 feb251430-278071 kernel: pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=2/256 refcnt=4 Feb 25 14:36:07 feb251430-278071 kernel: pending: vmstat_update, lru_add_drain_per_cpu BAR(27) Feb 25 14:36:07 feb251430-278071 kernel: workqueue writeback: flags=0x4a Feb 25 14:36:07 feb251430-278071 kernel: pwq 2: cpus=0 flags=0x4 nice=0 active=1/256 refcnt=3 Feb 25 14:36:07 feb251430-278071 kernel: in-flight: 298:wb_workfn Feb 25 14:36:07 feb251430-278071 kernel: workqueue xfs-buf/sda3: flags=0xc Feb 25 14:36:07 feb251430-278071 kernel: pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/1 refcnt=320 Feb 25 14:36:07 feb251430-278071 kernel: pending: xfs_buf_ioend_work [xfs] Feb 25 14:36:07 feb251430-278071 kernel: delayed: xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs] Feb 25 14:36:07 feb251430-278071 kernel: , xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs] Feb 25 14:36:07 feb251430-278071 kernel: , xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs] Feb 25 14:36:07 feb251430-278071 kernel: , xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs] Feb 25 14:36:07 feb251430-278071 kernel: , xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs] Feb 25 14:36:07 feb251430-278071 kernel: , xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs] Feb 25 14:36:07 feb251430-278071 kernel: , xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs] Feb 25 14:36:07 feb251430-278071 kernel: , xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs] Feb 25 14:36:07 feb251430-278071 kernel: , xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs], xfs_buf_ioend_work [xfs] Feb 25 14:36:07 feb251430-278071 kernel: workqueue xfs-conv/sda3: flags=0xc Feb 25 14:36:07 feb251430-278071 kernel: pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=12/256 refcnt=13 Feb 25 14:36:07 feb251430-278071 kernel: in-flight: 85:xfs_end_io [xfs] Feb 25 14:36:07 feb251430-278071 kernel: pending: xfs_end_io [xfs], xfs_end_io [xfs], xfs_end_io [xfs], xfs_end_io [xfs], xfs_end_io [xfs], xfs_end_io [xfs], xfs_end_io [xfs], xfs_end_io [xfs], xfs_end_io [xfs], xfs_end_io [xfs], xfs_end_io [xfs] Feb 25 14:36:07 feb251430-278071 kernel: workqueue xfs-reclaim/sda3: flags=0xc Feb 25 14:36:07 feb251430-278071 kernel: pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 Feb 25 14:36:07 feb251430-278071 kernel: pending: xfs_reclaim_worker [xfs] Feb 25 14:36:07 feb251430-278071 kernel: workqueue xfs-eofblocks/sda3: flags=0xc Feb 25 14:36:07 feb251430-278071 kernel: pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 Feb 25 14:36:07 feb251430-278071 kernel: pending: xfs_eofblocks_worker [xfs] Feb 25 14:36:07 feb251430-278071 kernel: workqueue xfs-sync/sda3: flags=0x4 Feb 25 14:36:07 feb251430-278071 kernel: pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 Feb 25 14:36:07 feb251430-278071 kernel: pending: xfs_log_worker [xfs] Feb 25 14:36:07 feb251430-278071 kernel: pool 0: cpus=0 node=0 flags=0x0 nice=0 hung=60s workers=3 idle: 5 1056 Feb 25 14:36:07 feb251430-278071 kernel: pool 2: cpus=0 flags=0x4 nice=0 hung=42s workers=3 idle: 250 87 Feb 25 14:36:38 feb251430-278071 kernel: BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 91s! -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1190567] vmlinuz is no longer present on /boot/ breaking separate boot partitions
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190567 https://bugzilla.suse.com/show_bug.cgi?id=1190567#c8 --- Comment #8 from Ludwig Nussel <lnussel(a)suse.com> --- (In reply to Marcus Schaefer from comment #7) > That's fine by me. So /boot will go away from Linux ? > > That's the driver right ? In this case I'm still confused were the value > is in such a change, or in other words what is wrong with /boot and why > did it harm users to have data in /boot such that it has to move to /usr Users can put whatever they like in /boot of course :-) It's just not for rpm to touch. The content of /boot depends on the bootloader. EFI systems or a RPi for example don't strictly need /boot the way we know it. They use a FAT partition to boot with potentially different layout. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190609] Bluetooth dongle always "on"
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190609 https://bugzilla.suse.com/show_bug.cgi?id=1190609#c1 Michal Filka <mfilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Kernel Assignee|yast2-maintainers(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de --- Comment #1 from Michal Filka <mfilka(a)suse.com> --- Nothing for yast in my POV -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190648] Yast crashes on package installation/update
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190648 https://bugzilla.suse.com/show_bug.cgi?id=1190648#c1 Michal Filka <mfilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ivano.mercuri(a)yahoo.it Flags| |needinfo?(ivano.mercuri@yah | |oo.it) --- Comment #1 from Michal Filka <mfilka(a)suse.com> --- thanks for detailed description. However, we would need complete yast logs not only last few lines. You can obtain them using save_y2logs tool -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190633] New: Failure to reboot guests consistently at least 100 times
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190633 Bug ID: 1190633 Summary: Failure to reboot guests consistently at least 100 times Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: luis.chamberlain(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Upstream kdevops [0] has a workflow test called "reboot-limit". The goal is to spawn a guest and then reboot it and confirm each reboot at least 100 times. If that fails the test fails. On to of this, the real goal is to run this simple test 100 times, so for a full set of 10,000 reboots. This is called achieving steady state for the reboot-limit kdevops test. To spawn guests vagrant is used. Right now I'm using this to vagrant with libvirt, and so behind the scenes this is all libvirt. I've been following Tumbleweed for a while now and in all releases so far I've only been able to accomplish a successful reboot-limit test only once, and so it would seem it might just be chance. kdevops uses ansible to control guests. There are 3 simple steps to the reboot: 1) ansible reboot module will first ssh to the guest and query /proc/sys/kernel/random/boot_id and saves this random UUID. 2) Ansible will ssh to the guest and issue '/sbin/shutdown -r 0 ' to reboot the guest 3) Yet again ansible will try to loop trying to ssh to the guest for up to 600 seconds, and once it logs in it will query again /proc/sys/kernel/random/boot_id. If the UUIDs match then the reboot is determined to have failed. Now, using /proc/sys/kernel/random/boot_id does not change in containers, and so on ansible 2.10 boot_time_command was added to the reboot module to allow you to specify another check. But for guests, this should work fine. OpenSUSE Tumbleweed is running ansible-2.9.24-1.1.noarch. With this the reboot-failure can't pass more than 100 reboots easily, sometimes maybe it reaches 200 or 500 but that's it. A workaround I noticed was to use: diff --git a/playbooks/roles/reboot-limit/tasks/do-reboot.yml b/playbooks/roles/reboot-limit/tasks/do-reboot.yml index a6876d2..2841bf6 100644 --- a/playbooks/roles/reboot-limit/tasks/do-reboot.yml +++ b/playbooks/roles/reboot-limit/tasks/do-reboot.yml @@ -12,6 +12,7 @@ become: yes become_method: sudo reboot: + post_reboot_delay: 10 when: - reboot_limit_test_type == "ansible" tags: [ 'run_tests' ] I've had to merge the above fix to kdevops because otherwise this test fails easily... With this we are able to get 10,000 reboots on OpenSUSE Tumbleweed. But, on Debian testing using ansible 2.10.7 and linux-next, I'm easily able to get 1,000,0000 reboots and without the above hack. Which begs the question: where is the issue? I checked ansible with verbose (ansible-playbook -vvv) for the test and it would seem everything checks out except the timeout really happens. But the odd thing is that you are able to still ssh to the host when you go and check to see what the hell happened. Which would seem to indicate the issue might be something else. [0] https://github.com/mcgrof/kdevops -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 536846] rebuild RPM DB automatically and silently when necessary
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=536846 http://bugzilla.opensuse.org/show_bug.cgi?id=536846#c9 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Andreas.Stieger(a)gmx.de --- Comment #9 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- Some considerations: Rebuilding "automatically and silently" hides the underlying problem and and will leads to bugs that are worde e.g. those when rebuilding does not fix the issue. Tumbleweed rpm >= 4.16 now offers sqlite and ndb backends which are more resilient. The Tumbleweed package also disables the bdb backend from the original report and defaults to ndb. This happened in October 2020. The original issue can hence no longer occur. This bug should be closed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0