July 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1163120] No mitigations for CPU vulnerabilities
by bugzilla_noreply＠suse.com 29 Jul '20

29 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1163120 https://bugzilla.suse.com/show_bug.cgi?id=1163120#c16 Miroslav Beneš <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |mbenes(a)suse.com Resolution|--- |WORKSFORME Assignee|kernel-maintainers(a)forge.pr |kernel-bugs(a)opensuse.org |ovo.novell.com | Flags|needinfo? | --- Comment #16 from Miroslav Beneš <mbenes(a)suse.com> --- I believe Boris provided exhaustive answers to your questions. Upstream documentation provides all information about the current implementation of all these mitigations. We try really hard to follow upstream here. If I recall correctly, software mitigations were discussed in some cases, but they were not implemented, because of another issues they have (performance, not reliable and such). Boris (or someone else) could add more specific info eventually if they like, but I think we're done here. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1164698] Kernel crash (likely because of Intel graphics card)
by bugzilla_noreply＠suse.com 29 Jul '20

29 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1164698 https://bugzilla.suse.com/show_bug.cgi?id=1164698#c2 Miroslav Beneš <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbenes(a)suse.com Assignee|kernel-maintainers(a)forge.pr |kernel-bugs(a)opensuse.org |ovo.novell.com | --- Comment #2 from Miroslav Beneš <mbenes(a)suse.com> --- Antonio, have you reported the problem upstream? Can you provide the link, please? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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