July 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1167306] ACPI Error
by bugzilla_noreply＠suse.com 29 Jul '20

29 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1167306 Miroslav Beneš <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-maintainers(a)forge.pr |kernel-bugs(a)opensuse.org |ovo.novell.com | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1174505] rsync and mv command fails: "File exists" on cifs mount on kernel >= 5.7.8 with SMB protocol version 1.0
by bugzilla_noreply＠suse.com 28 Jul '20

28 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1174505 https://bugzilla.suse.com/show_bug.cgi?id=1174505#c2 --- Comment #2 from Ian Mepham <ianmepham(a)gmail.com> --- The legacy systems only support smb version 1.0 but I can work around it though. To be honest, I wasn't sure if this was just another one of those things as the technology gap increases between old retro PCs and newer PCs. I must confess that a lot (most actually) of the technical aspects where way over my head, but finding that it wasn't just an oddity at my end I thought I'd better report it and see what others think. I understand that to properly fix the problem it will take a lot of time, especially for an old unsupported protocol, and for my simple needs I can easily work around it. Thank you for your time. Ian. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1174505] rsync and mv command fails: "File exists" on cifs mount on kernel >= 5.7.8 with SMB protocol version 1.0
by bugzilla_noreply＠suse.com 28 Jul '20

28 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1174505 https://bugzilla.suse.com/show_bug.cgi?id=1174505#c1 --- Comment #1 from Aurelien Aptel <aaptel(a)suse.com> --- This was reverted upstream but the patch did fix some wrong behaviour for smb2 which is the supported version of the protocol. Is there any reason you have to keep on using smb version 1.0? Could you try 2.1 or 3.0? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172670] kdump: fails to create dump as dump-capture kernel boots into systemd emergency mode
by bugzilla_noreply＠suse.com 28 Jul '20

28 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1172670 Shung-Hsi Yu <shung-hsi.yu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |shung-hsi.yu(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172670] kdump: fails to create dump as dump-capture kernel boots into systemd emergency mode
by bugzilla_noreply＠suse.com 28 Jul '20

28 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1172670 https://bugzilla.suse.com/show_bug.cgi?id=1172670#c7 Shung-Hsi Yu <shung-hsi.yu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #7 from Shung-Hsi Yu <shung-hsi.yu(a)suse.com> --- (In reply to Shung-Hsi Yu from comment #6) > (In reply to Shung-Hsi Yu from comment #5) > > kdump-save.service is not listed as a dependency of initrd.target, not sure > > if this is the intended behavior. > > > > $ systemctl list-dependencies initrd.target > > initrd.target > > ● ├─dev-disk-by\x2duuid-BEE5\x2dF873.device > > ● ├─dracut-cmdline-ask.service > > [...snip...] > > According to /usr/lib/dracut/modules.d/99kdump/module-setup.sh:277 there > should be a $systemdsystemunitdir"/initrd.target.wants/kdump-save.service > symbolic link to the kdump-save.service, however I don't see such symbolic > link in my kdump initrd. Adding a `mkdir -p "$initdir/$systemdsystemunitdir/initrd.target.wants"` in /usr/lib/dracut/modules.d/99kdump/module-setup.sh does the magic, kdump now works. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172670] kdump: fails to create dump as dump-capture kernel boots into systemd emergency mode
by bugzilla_noreply＠suse.com 28 Jul '20

28 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1172670 https://bugzilla.suse.com/show_bug.cgi?id=1172670#c6 --- Comment #6 from Shung-Hsi Yu <shung-hsi.yu(a)suse.com> --- (In reply to Shung-Hsi Yu from comment #5) > kdump-save.service is not listed as a dependency of initrd.target, not sure > if this is the intended behavior. > > $ systemctl list-dependencies initrd.target > initrd.target > ● ├─dev-disk-by\x2duuid-BEE5\x2dF873.device > ● ├─dracut-cmdline-ask.service > ● ├─dracut-cmdline.service > ● ├─dracut-initqueue.service > ● ├─dracut-mount.service > ● ├─dracut-pre-mount.service > ● ├─dracut-pre-pivot.service > ● ├─dracut-pre-trigger.service > ● ├─dracut-pre-udev.service > ● ├─initrd-parse-etc.service > ● ├─basic.target > ● │ ├─tmp.mount > ● │ ├─paths.target > ● │ ├─slices.target > ● │ │ ├─-.slice > ● │ │ └─system.slice > ● │ ├─sockets.target > ● │ │ ├─systemd-journald-dev-log.socket > ● │ │ ├─systemd-journald.socket > ● │ │ ├─systemd-udevd-control.socket > ● │ │ └─systemd-udevd-kernel.socket > ● │ ├─sysinit.target > ● │ │ ├─kmod-static-nodes.service > ● │ │ ├─systemd-ask-password-console.path > ● │ │ ├─systemd-journald.service > ● │ │ ├─systemd-modules-load.service > ● │ │ ├─systemd-sysctl.service > ● │ │ ├─systemd-tmpfiles-setup-dev.service > ● │ │ ├─systemd-tmpfiles-setup.service > ● │ │ ├─systemd-udev-trigger.service > ● │ │ ├─systemd-udevd.service > ● │ │ ├─local-fs.target > ● │ │ │ ├─kdump-mnt0.mount > ● │ │ │ └─kdump-mnt1-var.mount > ● │ │ └─swap.target > ● │ └─timers.target > ● ├─initrd-fs.target > ● ├─initrd-root-device.target > ● └─initrd-root-fs.target > ● ├─ostree-prepare-root.service > ● └─sysroot.mount According to /usr/lib/dracut/modules.d/99kdump/module-setup.sh:277 there should be a $systemdsystemunitdir"/initrd.target.wants/kdump-save.service symbolic link to the kdump-save.service, however I don't see such symbolic link in my kdump initrd. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172670] kdump: fails to create dump as dump-capture kernel boots into systemd emergency mode
by bugzilla_noreply＠suse.com 28 Jul '20

28 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1172670 https://bugzilla.suse.com/show_bug.cgi?id=1172670#c5 --- Comment #5 from Shung-Hsi Yu <shung-hsi.yu(a)suse.com> --- kdump-save.service is not listed as a dependency of initrd.target, not sure if this is the intended behavior. $ systemctl list-dependencies initrd.target initrd.target ● ├─dev-disk-by\x2duuid-BEE5\x2dF873.device ● ├─dracut-cmdline-ask.service ● ├─dracut-cmdline.service ● ├─dracut-initqueue.service ● ├─dracut-mount.service ● ├─dracut-pre-mount.service ● ├─dracut-pre-pivot.service ● ├─dracut-pre-trigger.service ● ├─dracut-pre-udev.service ● ├─initrd-parse-etc.service ● ├─basic.target ● │ ├─tmp.mount ● │ ├─paths.target ● │ ├─slices.target ● │ │ ├─-.slice ● │ │ └─system.slice ● │ ├─sockets.target ● │ │ ├─systemd-journald-dev-log.socket ● │ │ ├─systemd-journald.socket ● │ │ ├─systemd-udevd-control.socket ● │ │ └─systemd-udevd-kernel.socket ● │ ├─sysinit.target ● │ │ ├─kmod-static-nodes.service ● │ │ ├─systemd-ask-password-console.path ● │ │ ├─systemd-journald.service ● │ │ ├─systemd-modules-load.service ● │ │ ├─systemd-sysctl.service ● │ │ ├─systemd-tmpfiles-setup-dev.service ● │ │ ├─systemd-tmpfiles-setup.service ● │ │ ├─systemd-udev-trigger.service ● │ │ ├─systemd-udevd.service ● │ │ ├─local-fs.target ● │ │ │ ├─kdump-mnt0.mount ● │ │ │ └─kdump-mnt1-var.mount ● │ │ └─swap.target ● │ └─timers.target ● ├─initrd-fs.target ● ├─initrd-root-device.target ● └─initrd-root-fs.target ● ├─ostree-prepare-root.service ● └─sysroot.mount -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172670] kdump: fails to create dump as dump-capture kernel boots into systemd emergency mode
by bugzilla_noreply＠suse.com 28 Jul '20

28 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1172670 https://bugzilla.suse.com/show_bug.cgi?id=1172670#c4 --- Comment #4 from Shung-Hsi Yu <shung-hsi.yu(a)suse.com> --- The issue is still present after upgrading to Tumbleweed 20200720, with the following (possibly) issue-related packages: * dracut-050+suse.67.g28be2f36-1.1.x86_64 * kernel-default-5.7.9-1.1.x86_64 * kexec-tools-2.0.20-5.2.x86_64 * kdump-0.9.0-13.2.x86_64 * systemd-245.6-2.1.x86_64 After some poking around I found that manual dump succeed with the following commands: systemctl start kdump-mnt1-var.mount bash -c 'source /lib/kdump/save_dump.sh' # From kdump-save.service However, manually starting `systemctl start kdump-save.service` will not work, it just brings me back the the rescue mode prompt. This leads me to think that perhaps the issue is not initrd-switch-root.service, rather, the issue is that kdump-save (or its dependencies) somehow fail to start. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173449] New: WiFi Device not working for BCM-43142,even after the installation of boradcom-wl from packman.
by bugzilla_noreply＠suse.com 27 Jul '20

27 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173449 Bug ID: 1173449 Summary: WiFi Device not working for BCM-43142,even after the installation of boradcom-wl from packman. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: 64bit OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: avaish92(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Not getting an option to turn wifi on in openSuse 15.2 Steps to reproduce : 1. Install opensuse leap 15.2. 2. add packman repo. 3. install broadcom-wl and reboot. lspci output : 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04) 01:00.0 3D controller: NVIDIA Corporation GK208M [GeForce GT 740M] (rev a1) 07:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01) 08:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01) 0e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) -- You are receiving this mail because: You are the assignee for the bug.

1 7

[kernel-bugs] [Bug 1173870] Internal error: synchronous parity or ECC error - while building on obs-arm-2/3 (ThunderX)
by bugzilla_noreply＠suse.com 27 Jul '20

27 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173870 https://bugzilla.suse.com/show_bug.cgi?id=1173870#c8 --- Comment #8 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Dirk Mueller from comment #5) > do you have the exact timestamp? No, I don't. -- You are receiving this mail because: You are the assignee for the bug.

1 0