July 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1177800] New: [Ten64] getsysinfo caused kernel error (synchronous external abort)
by bugzilla_noreply＠suse.com 08 Jul '22

08 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177800 Bug ID: 1177800 Summary: [Ten64] getsysinfo caused kernel error (synchronous external abort) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: afaerber(a)suse.com QA Contact: qa-bugs(a)suse.de CC: matt(a)traverse.com.au, snwint(a)suse.com, yousaf.kaukab(a)suse.com Found By: --- Blocker: --- Running `getsysinfo` (via ssh) on Tumbleweed 20201011 with kernel-default 5.9.0 from Kernel:HEAD repository caused a kernel error, with ssh getting stuck and reconnections failing. Serial login still worked. zehn:~ # getsysinfo /proc/bus/input /proc/cpuinfo /proc/device-tree /proc/devices /proc/fb /proc/filesystems /proc/interrupts /proc/iomem /proc/ioports /proc/meminfo /proc/modules /proc/net/dev /proc/partitions /proc/scsi /proc/tty /proc/version /sys /usr/sbin/getsysinfo: line 23: 2761 Segmentation fault cp -x -a --parents "$i" "$dir/$host" 2> /dev/null /var/lib/hardware/udi /proc/mounts System data written to: /tmp/zehn.tar.gz zehn:~ # [ 544.956478] Internal error: synchronous external abort: 96000210 [#1] SMP [ 544.963295] Modules linked in: af_packet ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter xt_tcpudp ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security iscsi_ibft iscsi_boot_sysfs ip_set nfnetlink ebtable_filter ebtables rfkill ip6table_filter ip6_tables iptable_filter ip_tables x_tables fsl_dpaa2_ptp ptp_qoriq fsl_dpaa2_eth phylink xgmac_mdio hid_generic fsl_mc_dpio usbhid cdc_acm i2c_mux_pca954x i2c_mux tpm_i2c_atmel spi_fsl_qspi qoriq_thermal leds_gpio optee tee uio_pdrv_genirq uio qoriq_cpufreq nls_iso8859_1 nls_cp437 vfat fat drm xhci_plat_hcd xhci_hcd usbcore caam_jr mmc_block libdes authenc caamhash_desc caamalg_desc crypto_engine rtc_ds1307 mp886x aes_ce_blk crypto_simd cryptd aes_ce_cipher crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce dpaa2_console nvme nvme_core dwc3 sdhci_of_esdhc caam sdhci_pltfm ulpi [ 544.963547] error sdhci udc_core roles mmc_core i2c_imx btrfs blake2b_generic libcrc32c xor xor_neon raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 545.066303] CPU: 0 PID: 2761 Comm: cp Not tainted 5.9.0-1.g11733e1-default #1 openSUSE Tumbleweed (unreleased) [ 545.076303] Hardware name: traverse ten64/ten64, BIOS 2020.07-rc1-g1d4a3d9d5c 07/28/2020 [ 545.084393] pstate: 60000085 (nZCv daIf -PAN -UAO BTYPE=--) [ 545.089967] pc : dw_pcie_read+0x48/0xc0 [ 545.093799] lr : dw_pcie_access_other_conf.isra.0+0xc4/0x120 [ 545.099452] sp : ffff800012203bf0 [ 545.102759] x29: ffff800012203bf0 x28: 0000000000000400 [ 545.108067] x27: ffff00833e683400 x26: ffff008348240000 [ 545.113375] x25: ffff800010085000 x24: 0000000000000000 [ 545.118683] x23: ffff00834b239880 x22: ffff800012203cc4 [ 545.123991] x21: 0000000000000004 x20: 0000000000000400 [ 545.129299] x19: ffff00834b2398a8 x18: 0000000000000000 [ 545.134607] x17: 0000000000000000 x16: ffffafadaf1be170 [ 545.139915] x15: 0000000000000000 x14: 0000000000000000 [ 545.145222] x13: 0000000000000000 x12: 0000000000000040 [ 545.150530] x11: ffff00834bd8c920 x10: 0000000000000000 [ 545.155837] x9 : ffffafadaf12e8f4 x8 : 0000000002080000 [ 545.161145] x7 : 0000000000000000 x6 : ffff800010f00000 [ 545.166452] x5 : 0000000000000000 x4 : 0000000000000908 [ 545.171759] x3 : 0000000000000003 x2 : ffff800012203cc4 [ 545.177066] x1 : 0000000000000004 x0 : ffff800010085400 [ 545.182374] Call trace: [ 545.184816] dw_pcie_read+0x48/0xc0 [ 545.188298] dw_pcie_rd_conf+0x11c/0x150 [ 545.192217] pci_user_read_config_dword+0xa8/0x190 [ 545.197004] pci_read_config+0x1f8/0x264 [ 545.200923] sysfs_kf_bin_read+0x78/0xa0 [ 545.204840] kernfs_file_direct_read+0x90/0x220 [ 545.209365] kernfs_fop_read+0x44/0x50 [ 545.213111] vfs_read+0xb8/0x1e4 [ 545.216334] ksys_read+0x78/0x110 [ 545.219643] __arm64_sys_read+0x28/0x34 [ 545.223476] el0_svc_common.constprop.0+0x84/0x230 [ 545.228261] do_el0_svc+0x30/0xa0 [ 545.231572] el0_svc+0x18/0x50 [ 545.234621] el0_sync_handler+0x90/0x254 [ 545.238538] el0_sync+0x158/0x180 [ 545.241849] Code: 528010e0 d50323bf b900005f d65f03c0 (b9400001) [ 545.247941] ---[ end trace 68383e7eecaae870 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1201114] mount fails after umount -R, then unplug/re-plug external drive
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201114 http://bugzilla.opensuse.org/show_bug.cgi?id=1201114#c4 --- Comment #4 from Gene Snider <genes1122(a)gmail.com> --- "What happens if you do rmdir /mnt/chroot after unplug, but before replug?" Bad things happen. Commands first, then journal entries follow: > sudo umount -v -R /mnt/chroot umount: /mnt/chroot/sys/kernel/security unmounted umount: /mnt/chroot/sys/fs/cgroup (cgroup2) unmounted umount: /mnt/chroot/sys/fs/pstore unmounted umount: /mnt/chroot/sys/firmware/efi/efivars unmounted umount: /mnt/chroot/sys/fs/bpf (bpf) unmounted umount: /mnt/chroot/sys/kernel/debug unmounted umount: /mnt/chroot/sys/kernel/tracing (tracefs) unmounted umount: /mnt/chroot/sys/fs/fuse/connections (fusectl) unmounted umount: /mnt/chroot/sys/kernel/config unmounted umount: /mnt/chroot/sys unmounted umount: /mnt/chroot unmounted Jul 07 16:50:27 Mobile-PC sudo[3031]: gene : TTY=pts/1 ; PWD=/home/gene ; USER=root ; COMMAND=/usr/bin/umount -v -R /mnt/chroot Jul 07 16:50:27 Mobile-PC sudo[3031]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Jul 07 16:50:27 Mobile-PC sudo[3031]: pam_unix(sudo:session): session closed for user root Jul 07 16:50:27 Mobile-PC systemd[1]: mnt-chroot-sys-fs-bpf.mount: Deactivated successfully. Jul 07 16:50:27 Mobile-PC systemd[1]: mnt-chroot-sys-firmware-efi-efivars.mount: Deactivated successfully. Jul 07 16:50:27 Mobile-PC systemd[1]: mnt-chroot-sys-fs-pstore.mount: Deactivated successfully. Jul 07 16:50:27 Mobile-PC systemd[1]: mnt-chroot-sys-fs-cgroup.mount: Deactivated successfully. Jul 07 16:50:27 Mobile-PC systemd[1]: mnt-chroot-sys-kernel-security.mount: Deactivated successfully. Jul 07 16:50:27 Mobile-PC systemd[1]: mnt-chroot-sys-kernel-config.mount: Deactivated successfully. Jul 07 16:50:27 Mobile-PC systemd[1]: mnt-chroot-sys-fs-fuse-connections.mount: Deactivated successfully. Jul 07 16:50:27 Mobile-PC systemd[1]: mnt-chroot-sys-kernel-tracing.mount: Deactivated successfully. Jul 07 16:50:27 Mobile-PC systemd[1]: mnt-chroot-sys-kernel-debug.mount: Deactivated successfully. Jul 07 16:50:27 Mobile-PC systemd[1]: mnt-chroot-sys.mount: Deactivated successfully. Jul 07 16:50:27 Mobile-PC systemd[1]: mnt-chroot.mount: Deactivated successfully. Jul 07 16:50:32 Mobile-PC chronyd[1118]: Selected source 162.159.200.1 (2.opensuse.pool.ntp.org) Jul 07 16:50:36 Mobile-PC kernel: usb 2-1: USB disconnect, device number 2 Jul 07 16:50:36 Mobile-PC systemd[1]: Stopping Sabrent-Samsung temperature monitor daemon, started by udev rule... Jul 07 16:50:36 Mobile-PC systemd[1]: Sabrent-Samsung-tempd.service: Deactivated successfully. Jul 07 16:50:36 Mobile-PC systemd[1]: Stopped Sabrent-Samsung temperature monitor daemon, started by udev rule. Jul 07 16:50:36 Mobile-PC kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache Jul 07 16:50:36 Mobile-PC kernel: sd 2:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > sudo rmdir /mnt/chroot Jul 07 16:50:49 Mobile-PC sudo[3070]: gene : TTY=pts/1 ; PWD=/home/gene ; USER=root ; COMMAND=/usr/bin/rmdir /mnt/chroot Jul 07 16:50:49 Mobile-PC sudo[3070]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Jul 07 16:50:49 Mobile-PC kernel: BTRFS error (device sdb2): bdev /dev/sdb2 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0 Jul 07 16:50:49 Mobile-PC kernel: BTRFS error (device sdb2): bdev /dev/sdb2 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0 Jul 07 16:50:49 Mobile-PC kernel: BTRFS error (device sdb2): bdev /dev/sdb2 errs: wr 0, rd 3, flush 0, corrupt 0, gen 0 Jul 07 16:50:49 Mobile-PC kernel: BTRFS error (device sdb2): bdev /dev/sdb2 errs: wr 0, rd 4, flush 0, corrupt 0, gen 0 Jul 07 16:50:49 Mobile-PC kernel: BTRFS error (device sdb2): bdev /dev/sdb2 errs: wr 0, rd 5, flush 0, corrupt 0, gen 0 Jul 07 16:50:49 Mobile-PC kernel: BTRFS error (device sdb2): bdev /dev/sdb2 errs: wr 0, rd 6, flush 0, corrupt 0, gen 0 Jul 07 16:50:49 Mobile-PC kernel: BTRFS error (device sdb2): bdev /dev/sdb2 errs: wr 0, rd 7, flush 0, corrupt 0, gen 0 Jul 07 16:50:49 Mobile-PC kernel: BTRFS error (device sdb2): bdev /dev/sdb2 errs: wr 0, rd 8, flush 0, corrupt 0, gen 0 Jul 07 16:50:49 Mobile-PC kernel: BTRFS error (device sdb2): bdev /dev/sdb2 errs: wr 0, rd 9, flush 0, corrupt 0, gen 0 Jul 07 16:50:49 Mobile-PC kernel: BTRFS error (device sdb2): bdev /dev/sdb2 errs: wr 0, rd 10, flush 0, corrupt 0, gen 0 Jul 07 16:50:49 Mobile-PC kernel: BTRFS: error (device sdb2: state A) in add_to_free_space_tree:1051: errno=-5 IO failure Jul 07 16:50:49 Mobile-PC kernel: BTRFS info (device sdb2: state EA): forced readonly Jul 07 16:50:49 Mobile-PC kernel: BTRFS: error (device sdb2: state EA) in do_free_extent_accounting:2874: errno=-5 IO failure Jul 07 16:50:49 Mobile-PC kernel: BTRFS: error (device sdb2: state EA) in btrfs_run_delayed_refs:2151: errno=-5 IO failure Jul 07 16:50:49 Mobile-PC kernel: BTRFS warning (device sdb2: state EA): Skipping commit of aborted transaction. Jul 07 16:50:49 Mobile-PC kernel: BTRFS: error (device sdb2: state EA) in cleanup_transaction:1982: errno=-5 IO failure Jul 07 16:50:49 Mobile-PC kernel: BTRFS error (device sdb2: state EA): commit super ret -5 Jul 07 16:50:49 Mobile-PC sudo[3070]: pam_unix(sudo:session): session closed for user root The kernel BTRFS driver is very confused at this point. Gene -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201114] mount fails after umount -R, then unplug/re-plug external drive
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201114 http://bugzilla.opensuse.org/show_bug.cgi?id=1201114#c3 --- Comment #3 from Stanislav Brabec <sbrabec(a)suse.com> --- This is very strange: Jul 07 13:52:20 Mobile-PC kernel: BTRFS warning: duplicate device /dev/sdc2 devid 1 generation 6733 scanned by mount (4717) It looks that even if everything was correctly unmounted, something in the kernel still holds a record for /dev/sdb2, which prevents it from releasing. Just a dumb idea: What happens if you do rmdir /mnt/chroot after unplug, but before replug. It seems, that something becomes bound to this directory, but it is not a mounted volume. Does the bug happens then? Does the device get name sdb2 or sdc2 then? In any case, it looks like a kernel problem that has nothing to do with mount/libmount. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201114] mount fails after umount -R, then unplug/re-plug external drive
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201114 http://bugzilla.opensuse.org/show_bug.cgi?id=1201114#c2 --- Comment #2 from Gene Snider <genes1122(a)gmail.com> --- After the first > sudo umount -v -R /mnt/chroot: > ll /mnt/chroot total 0 -rw-r--r-- 1 root root 0 Jul 7 13:26 nothing_is_mounted > mount proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) devtmpfs on /dev type devtmpfs (rw,nosuid,size=4096k,nr_inodes=1048576,mode=755,inode64) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,size=3141212k,nr_inodes=819200,mode=755,inode64) cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) /dev/nvme0n1p4 on / type btrfs (rw,relatime,ssd,space_cache=v2,subvolid=504,subvol=/(a)/.snapshots/239/snapshot) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=25704) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,nr_inodes=1048576,inode64) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) /dev/nvme0n1p4 on /.snapshots type btrfs (rw,relatime,ssd,space_cache=v2,subvolid=265,subvol=/(a)/.snapshots) /dev/nvme0n1p4 on /boot/grub2/x86_64-efi type btrfs (rw,relatime,ssd,space_cache=v2,subvolid=263,subvol=/@/boot/grub2/x86_64-efi) /dev/nvme0n1p4 on /boot/grub2/i386-pc type btrfs (rw,relatime,ssd,space_cache=v2,subvolid=264,subvol=/@/boot/grub2/i386-pc) /dev/nvme0n1p4 on /home type btrfs (rw,relatime,ssd,space_cache=v2,subvolid=262,subvol=/@/home) /dev/sda1 on /mnt/backups type btrfs (rw,relatime,ssd,space_cache,subvolid=5,subvol=/) /dev/nvme0n1p4 on /srv type btrfs (rw,relatime,ssd,space_cache=v2,subvolid=259,subvol=/@/srv) /dev/nvme0n1p4 on /root type btrfs (rw,relatime,ssd,space_cache=v2,subvolid=260,subvol=/@/root) /dev/nvme0n1p4 on /opt type btrfs (rw,relatime,ssd,space_cache=v2,subvolid=261,subvol=/@/opt) /dev/nvme0n1p4 on /var type btrfs (rw,relatime,ssd,space_cache=v2,subvolid=257,subvol=/@/var) /dev/nvme0n1p4 on /usr/local type btrfs (rw,relatime,ssd,space_cache=v2,subvolid=258,subvol=/@/usr/local) /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1570604k,nr_inodes=392651,mode=700,uid=1000,gid=1000,inode64) gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) > cat /proc/mounts proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 devtmpfs /dev devtmpfs rw,nosuid,size=4096k,nr_inodes=1048576,mode=755,inode64 0 0 securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev,inode64 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,nodev,size=3141212k,nr_inodes=819200,mode=755,inode64 0 0 cgroup2 /sys/fs/cgroup cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot 0 0 pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0 bpf /sys/fs/bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 0 0 /dev/nvme0n1p4 / btrfs rw,relatime,ssd,space_cache=v2,subvolid=504,subvol=/(a)/.snapshots/239/snapshot 0 0 systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=25704 0 0 mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0 hugetlbfs /dev/hugepages hugetlbfs rw,relatime,pagesize=2M 0 0 debugfs /sys/kernel/debug debugfs rw,nosuid,nodev,noexec,relatime 0 0 tracefs /sys/kernel/tracing tracefs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /tmp tmpfs rw,nosuid,nodev,nr_inodes=1048576,inode64 0 0 fusectl /sys/fs/fuse/connections fusectl rw,nosuid,nodev,noexec,relatime 0 0 configfs /sys/kernel/config configfs rw,nosuid,nodev,noexec,relatime 0 0 /dev/nvme0n1p4 /.snapshots btrfs rw,relatime,ssd,space_cache=v2,subvolid=265,subvol=/(a)/.snapshots 0 0 /dev/nvme0n1p4 /boot/grub2/x86_64-efi btrfs rw,relatime,ssd,space_cache=v2,subvolid=263,subvol=/@/boot/grub2/x86_64-efi 0 0 /dev/nvme0n1p4 /boot/grub2/i386-pc btrfs rw,relatime,ssd,space_cache=v2,subvolid=264,subvol=/@/boot/grub2/i386-pc 0 0 /dev/nvme0n1p4 /home btrfs rw,relatime,ssd,space_cache=v2,subvolid=262,subvol=/@/home 0 0 /dev/sda1 /mnt/backups btrfs rw,relatime,ssd,space_cache,subvolid=5,subvol=/ 0 0 /dev/nvme0n1p4 /srv btrfs rw,relatime,ssd,space_cache=v2,subvolid=259,subvol=/@/srv 0 0 /dev/nvme0n1p4 /root btrfs rw,relatime,ssd,space_cache=v2,subvolid=260,subvol=/@/root 0 0 /dev/nvme0n1p4 /opt btrfs rw,relatime,ssd,space_cache=v2,subvolid=261,subvol=/@/opt 0 0 /dev/nvme0n1p4 /var btrfs rw,relatime,ssd,space_cache=v2,subvolid=257,subvol=/@/var 0 0 /dev/nvme0n1p4 /usr/local btrfs rw,relatime,ssd,space_cache=v2,subvolid=258,subvol=/@/usr/local 0 0 /dev/nvme0n1p1 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=1570604k,nr_inodes=392651,mode=700,uid=1000,gid=1000,inode64 0 0 gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0 portal /run/user/1000/doc fuse.portal rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0 I didn't see any references to /dev/sdb or /mnt/chroot with grep for either command. The journal says the umount was successful: Jul 07 13:42:48 Mobile-PC sudo[3403]: gene : TTY=pts/0 ; PWD=/home/gene ; USER=root ; COMMAND=/usr/bin/umount -v -R /mnt/chroot Jul 07 13:42:48 Mobile-PC sudo[3403]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Jul 07 13:42:48 Mobile-PC sudo[3403]: pam_unix(sudo:session): session closed for user root Jul 07 13:42:48 Mobile-PC systemd[1]: mnt-chroot-sys-kernel-security.mount: Deactivated successfully. Jul 07 13:42:48 Mobile-PC systemd[1]: mnt-chroot-sys-kernel-config.mount: Deactivated successfully. Jul 07 13:42:48 Mobile-PC systemd[1]: mnt-chroot-sys-fs-fuse-connections.mount: Deactivated successfully. Jul 07 13:42:48 Mobile-PC systemd[1]: mnt-chroot-sys-kernel-tracing.mount: Deactivated successfully. Jul 07 13:42:48 Mobile-PC systemd[1]: mnt-chroot-sys-kernel-debug.mount: Deactivated successfully. Jul 07 13:42:48 Mobile-PC systemd[1]: mnt-chroot-sys-fs-bpf.mount: Deactivated successfully. Jul 07 13:42:48 Mobile-PC systemd[1]: mnt-chroot-sys-firmware-efi-efivars.mount: Deactivated successfully. Jul 07 13:42:48 Mobile-PC systemd[1]: mnt-chroot-sys-fs-pstore.mount: Deactivated successfully. Jul 07 13:42:48 Mobile-PC systemd[1]: mnt-chroot-sys-fs-cgroup.mount: Deactivated successfully. Jul 07 13:42:48 Mobile-PC systemd[1]: mnt-chroot-sys.mount: Deactivated successfully. Jul 07 13:42:48 Mobile-PC systemd[1]: mnt-chroot.mount: Deactivated successfully. Check out what happens when I run journalctl -f and umplug/replug the drive: Jul 07 13:50:31 Mobile-PC kernel: usb 2-1: USB disconnect, device number 2 Jul 07 13:50:31 Mobile-PC systemd[1]: Stopping Sabrent-Samsung temperature monitor daemon, started by udev rule... Jul 07 13:50:31 Mobile-PC systemd[1]: Sabrent-Samsung-tempd.service: Deactivated successfully. Jul 07 13:50:31 Mobile-PC systemd[1]: Stopped Sabrent-Samsung temperature monitor daemon, started by udev rule. Jul 07 13:50:31 Mobile-PC systemd[1]: Sabrent-Samsung-tempd.service: Consumed 5.075s CPU time. Jul 07 13:50:32 Mobile-PC kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache Jul 07 13:50:32 Mobile-PC kernel: sd 2:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK Jul 07 13:50:38 Mobile-PC kernel: usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 3 using xhci_hcd Jul 07 13:50:38 Mobile-PC kernel: usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01 Jul 07 13:50:38 Mobile-PC kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jul 07 13:50:38 Mobile-PC kernel: usb 2-1: Product: Sabrent Jul 07 13:50:38 Mobile-PC kernel: usb 2-1: Manufacturer: Sabrent Jul 07 13:50:38 Mobile-PC kernel: usb 2-1: SerialNumber: 012345678930 Jul 07 13:50:38 Mobile-PC kernel: scsi host3: uas Jul 07 13:50:38 Mobile-PC mtp-probe[4457]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb2/2-1" Jul 07 13:50:38 Mobile-PC mtp-probe[4457]: bus: 2, device: 3 was not an MTP device Jul 07 13:50:38 Mobile-PC kernel: scsi 3:0:0:0: Direct-Access Sabrent 1.00 PQ: 0 ANSI: 6 Jul 07 13:50:38 Mobile-PC mtp-probe[4458]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb2/2-1" Jul 07 13:50:38 Mobile-PC mtp-probe[4458]: bus: 2, device: 3 was not an MTP device Jul 07 13:50:38 Mobile-PC kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0 Jul 07 13:50:38 Mobile-PC systemd[1]: Started Sabrent-Samsung temperature monitor daemon, started by udev rule. Jul 07 13:50:38 Mobile-PC kernel: sd 3:0:0:0: [sdc] 1000215216 512-byte logical blocks: (512 GB/477 GiB) Jul 07 13:50:38 Mobile-PC kernel: sd 3:0:0:0: [sdc] Write Protect is off Jul 07 13:50:38 Mobile-PC kernel: sd 3:0:0:0: [sdc] Mode Sense: 37 00 00 08 Jul 07 13:50:38 Mobile-PC kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 07 13:50:38 Mobile-PC kernel: sd 3:0:0:0: [sdc] Optimal transfer size 33553920 bytes Jul 07 13:50:38 Mobile-PC kernel: sdc: sdc1 sdc2 Jul 07 13:50:38 Mobile-PC kernel: sd 3:0:0:0: [sdc] Attached SCSI disk Jul 07 13:50:38 Mobile-PC kernel: BTRFS warning: duplicate device /dev/sdc2 devid 1 generation 6733 scanned by systemd-udevd (4456) Notice that it reattached as /dev/sdc2. I get the same message when the mount fails: Jul 07 13:52:20 Mobile-PC sudo[4716]: gene : TTY=pts/1 ; PWD=/home/gene ; USER=root ; COMMAND=/usr/bin/mount -v UUID=4c96a0c2-f72f-4827-b023-83ba000b2fd2 /mnt/chroot Jul 07 13:52:20 Mobile-PC kernel: BTRFS warning: duplicate device /dev/sdc2 devid 1 generation 6733 scanned by mount (4717) Jul 07 13:52:20 Mobile-PC sudo[4716]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Jul 07 13:52:20 Mobile-PC sudo[4716]: pam_unix(sudo:session): session closed for user root Let me know if you need more info. An aside, this only seems to happen for --rbind and --make-rslave. Just mounting the root drive doesn't cause a problem. Thanks, Gene -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201114] mount fails after umount -R, then unplug/re-plug external drive
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201114 https://bugzilla.suse.com/show_bug.cgi?id=1201114#c1 Stanislav Brabec <sbrabec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |genes1122(a)gmail.com, | |kernel-bugs(a)opensuse.org Flags| |needinfo?(genes1122(a)gmail.c | |om) --- Comment #1 from Stanislav Brabec <sbrabec(a)suse.com> --- Could you provide an output from mount command and contents of /proc/mounts after the first successful umount? And eventually output of dmesg and journalctl. And could you verify that nothing remains in the directory /mnt/chroot? (You can test "touch /mnt/chroot/nothing_is_mounted" before starting your experiments. You should see this file again when everything is unmounted.) It seems that something is still holding the old mount. It looks more like a kernel issue, as mount command is only a intermediary between user and kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201112] New: WiFi not available on pinebook pro
by bugzilla_noreply＠suse.com 06 Jul '22

06 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201112 Bug ID: 1201112 Summary: WiFi not available on pinebook pro 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On Tumbleweed there is no WiFi when booted on Pinebook Pro. Other distributions manage fine. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1200647] TW 20220614: MT7921K (RZ608) Wi-Fi (14c3:0608) fails to initialize with "probe of 0000:06:00.0 failed with error -5"
by bugzilla_noreply＠suse.com 06 Jul '22

06 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200647 https://bugzilla.suse.com/show_bug.cgi?id=1200647#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- OK, then it has something to do with the power management. Upon the warm boot, it's possibly set in the power down state and the driver couldn't initialize properly... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200947] Error message on resume
by bugzilla_noreply＠suse.com 06 Jul '22

06 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200947 https://bugzilla.suse.com/show_bug.cgi?id=1200947#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aloisio(a)gmx.com, | |tiwai(a)suse.com Flags| |needinfo?(aloisio(a)gmx.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Do you happen to have installed tlp package? If yes, try to uninstall it. In anyway, please give the full dmesg output and the output of hwinfo. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200923] shut down during update hang system
by bugzilla_noreply＠suse.com 06 Jul '22

06 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200923 https://bugzilla.suse.com/show_bug.cgi?id=1200923#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gio_6b(a)yahoo.it, | |tiwai(a)suse.com Flags| |needinfo?(gio_6b(a)yahoo.it) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Is the problem reproducible? It doesn't sound like a kernel problem, per se. In anyway, if you can see the problem again, please upload the dmesg output. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200919] System is freeze on X loading
by bugzilla_noreply＠suse.com 06 Jul '22

06 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200919 https://bugzilla.suse.com/show_bug.cgi?id=1200919#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hillwoodroc(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(hillwoodroc@gmail | |.com) --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Could you try to boot with the old Leap 15.3 kernel and see whether it works? If zypper or rpm complains dependency, ignore it and forcibly install. -- You are receiving this mail because: You are the assignee for the bug.

1 0