October 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1204315] New: [RPi3] kernel traces with kernel 6.0
by bugzilla_noreply＠suse.com 14 Oct '22

14 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204315 Bug ID: 1204315 Summary: [RPi3] kernel traces with kernel 6.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/2803022/modules/jour nal_check/steps/10 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, dmueller(a)suse.com, ivan.ivanov(a)suse.com, mbrugger(a)suse.com Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-RPi-aarch64-jeos@RPi3 fails in [journal_check](https://openqa.opensuse.org/tests/2803022/modules/journal_ch… Traces are: Oct 04 00:00:00.983936 localhost kernel: simple-framebuffer simple-framebuffer.0: [drm] *ERROR* could not acquire memory range [mem 0x3eaa9000-0x3ebfafff flags 0x200]: error -16 Oct 04 00:00:07.567844 localhost kernel: Failed to attach USB driver: -22 And also the already known: Oct 04 00:01:11.546090 localhost.localdomain kernel: Bluetooth: hci0: BCM: Reset failed (-110) ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [20220808](https://openqa.opensuse.org/tests/2504844) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 12 Oct '22

12 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c42 --- Comment #42 from Kourosh P. <kourosh(a)pourdanandeh.com> --- (In reply to Felix Miata from comment #41) > (In reply to Kourosh P. from comment #40) > > I have reported this matter at the following link: > > https://gitlab.freedesktop.org/drm/amd/-/issues/1952 > > I just made the following addition there: > > # inxi -S > System: > Host: ab250 Kernel: 5.18.19-200.fc36.x86_64 arch: x86_64 bits: 64 > Desktop: Trinity v: R14.0.12 Distro: Fedora release 36 (Thirty Six) > # > > If I keep my second display's cable disconnected, I get this: > # grep onnec /var/log/Xorg.0.log > [ 5.313] (II) modeset(0): Output DP-1 connected > [ 5.313] (II) modeset(0): Output HDMI-1 disconnected > [ 5.313] (II) modeset(0): Output HDMI-2 disconnected > [ 5.313] (II) modeset(0): Output HDMI-3 disconnected > [ 5.313] (II) modeset(0): Output DP-2 disconnected > # > Or this: > # grep onnec /var/log/Xorg.0.log > [ 5.544] (II) modeset(0): Output DP-1 disconnected > [ 5.544] (II) modeset(0): Output HDMI-1 disconnected > [ 5.544] (II) modeset(0): Output HDMI-2 connected > [ 5.544] (II) modeset(0): Output HDMI-3 disconnected > [ 5.544] (II) modeset(0): Output DP-2 disconnected > # > > It may surprise many that if I keep my second display's signal cable > connected > from the PC, but with it powered off, I get this on booting instead: > # grep onnec /var/log/Xorg.0.log > [ 5.412] (II) modeset(0): Output DP-1 connected > [ 5.412] (II) modeset(0): Output HDMI-1 disconnected > [ 5.412] (II) modeset(0): Output HDMI-2 connected > [ 5.412] (II) modeset(0): Output HDMI-3 disconnected > [ 5.412] (II) modeset(0): Output DP-2 disconnected > # > Or this: > # grep onnec /var/log/Xorg.0.log > [ 5.451] (II) modeset(0): Output DP-1 connected > [ 5.451] (II) modeset(0): Output HDMI-1 disconnected > [ 5.451] (II) modeset(0): Output HDMI-2 connected > [ 5.451] (II) modeset(0): Output HDMI-3 disconnected > [ 5.451] (II) modeset(0): Output DP-2 disconnected > # > > So, at "connection" time, the secondary display isn't providing any > information > about it's capability, only the cable connection is "reporting" something is > connected. Some may want to rethink their definition of "connected", and not > boot > with an external display attached but un-powered.[/quote] > > It would be nice to know what MX Linux is doing that it doesn't present the > problem. Thank you. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191954] btrfs fiemap results are inconsistent compared to XFS
by bugzilla_noreply＠suse.com 12 Oct '22

12 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1191954 https://bugzilla.suse.com/show_bug.cgi?id=1191954#c6 --- Comment #6 from David Disseldorp <ddiss(a)suse.com> --- (In reply to Filipe Manana from comment #5) > (In reply to David Disseldorp from comment #3) > > I (In reply to David Disseldorp from comment #2) > > > Reassigning to Filipe, who appears to have also run into this issue (and has > > > a fix). @Filipe: I'd be happy to rerun my tests if you can point me at your > > > fix. > > > > I spent some time running my dracut workload (will attach script) atop > > current Tumbleweed (5.19.8 + dracut 057+suse.309.gb71946f6-1.3) with and > > without Filipe's v1 fiemap patches ([PATCH 00/10] btrfs: make lseek and > > fiemap much more efficient). I did notice improvements in fiemap performance > > for reflinked initramfs images with many shared extents, but was > > unfortunately no longer seeing inconsistent fiemap values, so can't confirm > > whether it's fixed with these changes. > > Unfortunately? > Shouldn't it be fortunately :) Hehe yeah, just unfortunate because I wasn't able to reproduce with the 5.19.8 *before* applying your patches. > Btw, there's a couple old bugs I found recently that could make fiemap > incorrectly report some extents as shared despite not being shared anymore. > It's the first two patches from this set: > > https://lore.kernel.org/linux-btrfs/cover.1665490018.git.fdmanana@suse.com/ Thanks, I'll give these another spin when I get a chance :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191954] btrfs fiemap results are inconsistent compared to XFS
by bugzilla_noreply＠suse.com 12 Oct '22

12 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1191954 https://bugzilla.suse.com/show_bug.cgi?id=1191954#c5 --- Comment #5 from Filipe Manana <fdmanana(a)suse.com> --- (In reply to David Disseldorp from comment #3) > I (In reply to David Disseldorp from comment #2) > > Reassigning to Filipe, who appears to have also run into this issue (and has > > a fix). @Filipe: I'd be happy to rerun my tests if you can point me at your > > fix. > > I spent some time running my dracut workload (will attach script) atop > current Tumbleweed (5.19.8 + dracut 057+suse.309.gb71946f6-1.3) with and > without Filipe's v1 fiemap patches ([PATCH 00/10] btrfs: make lseek and > fiemap much more efficient). I did notice improvements in fiemap performance > for reflinked initramfs images with many shared extents, but was > unfortunately no longer seeing inconsistent fiemap values, so can't confirm > whether it's fixed with these changes. Unfortunately? Shouldn't it be fortunately :) Btw, there's a couple old bugs I found recently that could make fiemap incorrectly report some extents as shared despite not being shared anymore. It's the first two patches from this set: https://lore.kernel.org/linux-btrfs/cover.1665490018.git.fdmanana@suse.com/ > > The kernel backport (with minimal delta) is at > https://gitlab.suse.de/dmdiss/linux/-/tree/tw_stable_btrfs_fiemap . I think > this ticket can be closed - I'll reopen it if I see it again. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204042] New: Missing modules with kernel-defaults-base
by bugzilla_noreply＠suse.com 11 Oct '22

11 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204042 Bug ID: 1204042 Summary: Missing modules with kernel-defaults-base 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: jlopez(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Th package kernel-defaults-base does not include some kernel modules that are needed for some basic operations like creating a podmain container checkpoint: $ podman container checkpoint distracted_babbage ERRO[0000] container still running ERRO[0000] criu failed: type NOTIFY errno 0 log file: /var/lib/containers/storage/btrfs-containers/ee203bab8fadb391481ec3179657eccd3970e3f9acc087ab8869890cd7938239/userdata/dump.log Error: `/usr/bin/runc checkpoint --image-path /var/lib/containers/storage/btrfs-containers/ee203bab8fadb391481ec3179657eccd3970e3f9acc087ab8869890cd7938239/userdata/checkpoint --work-path /var/lib/containers/storage/btrfs-containers/ee203bab8fadb391481ec3179657eccd3970e3f9acc087ab8869890cd7938239/userdata ee203bab8fadb391481ec3179657eccd3970e3f9acc087ab8869890cd7938239` failed: exit status 1 This was detected in the context of ALP, see https://bugzilla.suse.com/show_bug.cgi?id=1203854. Right now we have two images for ALP (non-encrypted and encrypted). The non-encrypted one includes kernel-defaults-base, and the encrypted one uses kernel-defaults. With the encrypted image criu does not complain when creating a podman container checkpoint. These *diag modules are missing with kernel-defaults-base: raw_diag, tcp_diag, udp_diag, unix_diag. This issue is relevant even for TW in virtual environments (where you don��t need all drivers). Probably we will need to fix the packaging of kernel to include those missing modules with kernel-defaults-base. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1203800] Recent Kernel Updates (likely) broke backintime
by bugzilla_noreply＠suse.com 11 Oct '22

11 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1203800 https://bugzilla.suse.com/show_bug.cgi?id=1203800#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dsims(a)usa.com, | |tiwai(a)suse.com Flags| |needinfo?(dsims(a)usa.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Are you sure that it's a kernel regression? Please try to boot with the previous kernel and confirm that it's working again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203800] Recent Kernel Updates (likely) broke backintime
by bugzilla_noreply＠suse.com 11 Oct '22

11 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1203800 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1170696] Dell Latitude 7490 freezes with 15.2
by bugzilla_noreply＠suse.com 11 Oct '22

11 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1170696 http://bugzilla.opensuse.org/show_bug.cgi?id=1170696#c26 Luciano Santos <luc14n0(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |luc14n0(a)opensuse.org Resolution|--- |INVALID --- Comment #26 from Luciano Santos <luc14n0(a)opensuse.org> --- Leap 15.2 has reached end of Lifetime on January 4th, 2022. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204155] Unable to login into any virtual console second appearing
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204155 https://bugzilla.suse.com/show_bug.cgi?id=1204155#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Component|Kernel |Basesystem Assignee|kernel-bugs(a)opensuse.org |screening-team-bugs(a)suse.de --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- This doesn't appear to be a kernel bug. Let's try to reassign. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202571] kernel 5.19.1 shuts down after waking from suspend
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1202571 https://bugzilla.suse.com/show_bug.cgi?id=1202571#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- OK, then let's close the bug. Feel free to reopen if you still encounters the problem again. -- You are receiving this mail because: You are the assignee for the bug.

1 0