June 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1226232] Going to sleep and Hibernate often fails with black screen
by bugzilla_noreply＠suse.com 21 Jun '24

21 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226232 https://bugzilla.suse.com/show_bug.cgi?id=1226232#c17 --- Comment #17 from Gui Do <guidopro(a)mailbox.org> --- (In reply to Takashi Iwai from comment #16) > Ah sorry, I missed that information. So it's something in user-space, or > some subtle change that was applied to BIOS or whatever. Tough. > > In the case of user-space, it's often such like tlp, tuned or such package > that adjust the PM behavior. Maybe, bu I have no such a package. tlp and tuned are not installed, BIOS settings did not changed an are the same as in Leap 15.5. I did a fresh installation of Leap 15.6 on my old testing laptop thinkpad T61 with BIOS boot, LUKS1 encryption for root partition an not-encrypted swap partiton. Problem is the same: no automatically hibernation. So it is not a hardware problem but 15.6 release issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1226646] Reboot freezes after multiple sleep/wake cycles
by bugzilla_noreply＠suse.com 21 Jun '24

21 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226646 https://bugzilla.suse.com/show_bug.cgi?id=1226646#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Do you have any crash trace? If LED is flashing, it's usually a kernel panic, and we have a chance to catch it via kdump, too. Care to set up and try to get the crash data? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1226646] New: Reboot freezes after multiple sleep/wake cycles
by bugzilla_noreply＠suse.com 20 Jun '24

20 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226646 Bug ID: 1226646 Summary: Reboot freezes after multiple sleep/wake cycles Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aleksey.rukhlenko(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- If I sleep/wake the laptop multiple times (more than 2-3), then laptop freezes when I try to reboot it or shut it down. Sometimes caps lock is blinking when the laptop is frozen this way. I have to perform force shut down to make it work again. Hardware: Dell XPS 17 9700 OS: Fresh install of OpenSUSE 15.6 64-bit. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224434] Page cache invalidation failure during direct I/O write
by bugzilla_noreply＠suse.com 20 Jun '24

20 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224434 https://bugzilla.suse.com/show_bug.cgi?id=1224434#c1 Jan Kara <jack(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdmanana(a)suse.com --- Comment #1 from Jan Kara <jack(a)suse.com> --- Since this is on btrfs, we should involve someone from btrfs team. Filipe, can you have a look? Feel free to reassign if somebody else is a better fit. Checking the kernel logs I agree the iomap code is complaining about failure to invalide page cache *after* a direct write. I can also see LTP is declaring the test as broken because fsync(2) after writing the file has failed with EIO: tst_test.c:1734: TINFO: LTP version: 20240524 tst_test.c:1618: TINFO: Timeout per run is 0h 30m 30s aiocp.c:211: TINFO: Maximum AIO blocks: 65536 tst_device.c:545: TINFO: Use BTRFS specific strategy aiocp.c:250: TINFO: Fill srcfile.bin with random data aiocp.c:279: TINFO: Copy srcfile.bin -> dstfile.bin aiocp.c:115: TBROK: fsync(4) failed: EIO (5) And this is weird because it shouldn't be caused by the page cache invalidation. Now I suspect this is connected with the fact that PowerPC64 where this is happening has page size of 64k and so all the failing cases are not page aligned and so individual IOs are going to use the same page and if we fall back to buffered IO for some reason, conflicts between buffered and direct IO can happen. But since this is not happening with SLE15-SP6, something must have changed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225968] New: Since kernel 6.9, applications running on only 1 core
by bugzilla_noreply＠suse.com 20 Jun '24

20 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225968 Bug ID: 1225968 Summary: Since kernel 6.9, applications running on only 1 core Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ivan.topolsky(a)isb-sib.ch QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875310 --> https://bugzilla.suse.com/attachment.cgi?id=875310&action=edit excerpt of the journal on kernel 6.9.1 (based on forum thread: https://forums.opensuse.org/t/since-kernel-6-9-running-on-only-1-core/175460) Since updating my openSUSE Tumbleweed install from kernel 6.8.9 to kernels 6.9.x, all my applications (such as firefox) run on mostly only 1 core of the CPU. CPU is AMD FX 8350 8 core (as 4 modules of 2 half-cores which share their FPU) Motherboard is GA-990FXA-UD7 (rev 1.x) (firmware is BIOS with some EFI compatibility layer. Not UEFI like rev 3.x) on kernels 6.9.1 and 6.9.3, while smpboot is initialising the other cores, I get a bunch of errors, which disappear if I boot into version 6.8.9 instead (See linked thread / attachment). This is then followed by: > boot.6.9.txt:jun 03 10:02:33 saturn kernel: mtrr: your CPUs had inconsistent variable MTRR settings > boot.6.9.txt:jun 03 10:02:33 saturn kernel: mtrr: probably your BIOS does not setup all CPUs. > boot.6.9.txt:jun 03 10:02:33 saturn kernel: mtrr: corrected configuration. What would be the next best step to gather information useful to understand bug? -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1224434] New: Page cache invalidation failure during direct I/O write
by bugzilla_noreply＠suse.com 19 Jun '24

19 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224434 Bug ID: 1224434 Summary: Page cache invalidation failure during direct I/O write Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 URL: https://openqa.opensuse.org/tests/4202483/modules/AD03 3/steps/8 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: avinesh.kumar(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-ltp_aiodio_part1@ppc64le fails in [AD033](https://openqa.opensuse.org/tests/4202483/modules/AD033/steps/8) ## Test suite description LTP_ENV=TMPDIR=/var/tmp is to test on btrfs instead of tmpfs ## Reproducible Fails since (at least) Build [20240131](https://openqa.opensuse.org/tests/3907534) Last good: Unknown ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64le&distri=opensu… -------- LTP Test - https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/io/l… we run this test with various combinations of write block size and I/O numbers (https://github.com/linux-test-project/ltp/blob/master/runtest/ltp-aiodio.pa…) failing scenarios on ppc64le: AD033 aiocp -b 4k -n 4 -f DIRECT AD035 aiocp -b 4k -n 8 -f DIRECT AD037 aiocp -b 4k -n 16 -f DIRECT (few times doesn't fail) AD039 aiocp -b 4k -n 32 -f DIRECT (few times doesn't fail) AD047 aiocp -b 8k -n 4 -f DIRECT AD049 aiocp -b 8k -n 8 -f DIRECT AD051 aiocp -b 8k -n 16 -f DIRECT (few times doesn't fail) AD061 aiocp -b 16k -n 4 -f DIRECT AD063 aiocp -b 16k -n 8 -f DIRECT AD075 aiocp -b 32k -n 4 -f DIRECT dmesg log during each of these failures: OpenQA::run_ltp.pm: Starting AD032 OpenQA::run_ltp.pm: Starting AD033 [ 48.470444][ T62] Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O! [ 48.471404][ T62] File: /var/tmp/LTP_aioTBsaEH/dstfile.bin PID: 62 Comm: kworker/1:1 OpenQA::run_ltp.pm: Starting AD034 OpenQA::run_ltp.pm: Starting AD035 This issue is not present on aarch64 and x86_64 tumbleweed builds. And on SLE15-SP6, we are not seeing this on ppc64le also. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1223131] New: Disable WAN drivers
by bugzilla_noreply＠suse.com 19 Jun '24

19 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223131 Bug ID: 1223131 Summary: Disable WAN drivers 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- We do not provide WAN in SLE at all (it lives in the -optional subpackage, so is Leap only). Provided: * no our customer apparently uses this, * is poorly maintained upstream (hdlc in particular), * it's unlikely TW/Leap users run this (but not impossible), * we diverge from SLE configs, we should consider disabling whole WAN in TW and Leap too. The proposed config change is: @@ -4217,20 +4217,7 @@ CONFIG_QTNFMAC=m CONFIG_QTNFMAC_PCIE=m CONFIG_MAC80211_HWSIM=m CONFIG_VIRT_WIFI=m -CONFIG_WAN=y -CONFIG_HDLC=m -CONFIG_HDLC_RAW=m -CONFIG_HDLC_RAW_ETH=m -CONFIG_HDLC_CISCO=m -CONFIG_HDLC_FR=m -CONFIG_HDLC_PPP=m -CONFIG_HDLC_X25=m -CONFIG_FRAMER=m -CONFIG_PCI200SYN=m -CONFIG_WANXL=m -CONFIG_PC300TOO=m -CONFIG_FARSYNC=m -CONFIG_LAPBETHER=m +# CONFIG_WAN is not set CONFIG_IEEE802154_DRIVERS=m CONFIG_IEEE802154_FAKELB=m # CONFIG_IEEE802154_AT86RF230 is not set @@ -4658,7 +4645,7 @@ CONFIG_SERIAL_MCTRL_GPIO=y CONFIG_SERIAL_NONSTANDARD=y # CONFIG_MOXA_INTELLIO is not set CONFIG_MOXA_SMARTIO=m -CONFIG_N_HDLC=m +# CONFIG_N_HDLC is not set CONFIG_IPWIRELESS=m CONFIG_N_GSM=m CONFIG_NOZOMI=m -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1226302] Leap 15.6 cannot boot up successfully on RPi 4
by bugzilla_noreply＠suse.com 19 Jun '24

19 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226302 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1226302] Leap 15.6 cannot boot up successfully on RPi 4
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226302 https://bugzilla.suse.com/show_bug.cgi?id=1226302#c15 Zaoliang Luo <zluo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #15 from Zaoliang Luo <zluo(a)suse.com> --- now I found the cause of this issue. comparing with Tumbleweed boot I got warning about low voltage. The adapter used might be broken, so I use a different one and Leap can boots up. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1226302] Leap 15.6 cannot boot up successfully on RPi 4
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226302 https://bugzilla.suse.com/show_bug.cgi?id=1226302#c14 --- Comment #14 from Zaoliang Luo <zluo(a)suse.com> --- Created attachment 875561 --> https://bugzilla.suse.com/attachment.cgi?id=875561&action=edit boot output -- You are receiving this mail because: You are the assignee for the bug.

1 0