June 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1212690] New: kernel BUG at arch/x86/kernel/traps.c:255
by bugzilla_noreply＠suse.com 27 Jun '23

27 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212690 Bug ID: 1212690 Summary: kernel BUG at arch/x86/kernel/traps.c:255 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: wolfgang(a)rosenauer.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When trying to start a VM within Virtualbox it hangs and the log contains the following: Jun 25 21:06:24 ox.rosenauer.org kernel: SUPR0GipMap: fGetGipCpu=0x1b Jun 25 21:06:29 ox.rosenauer.org kernel: traps: Missing ENDBR: 0xffffa88b885f4fe0 Jun 25 21:06:29 ox.rosenauer.org kernel: ------------[ cut here ]------------ Jun 25 21:06:29 ox.rosenauer.org kernel: kernel BUG at arch/x86/kernel/traps.c:255! Jun 25 21:06:29 ox.rosenauer.org kernel: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI Jun 25 21:06:29 ox.rosenauer.org kernel: CPU: 5 PID: 5259 Comm: EMT Tainted: G O 6.3.7-1-default #1 openSUSE Tumbleweed a577eae57964bb7e83477b5a5645a1781df990f0 Jun 25 21:06:29 ox.rosenauer.org kernel: Hardware name: LENOVO 21HMCTO1WW/21HMCTO1WW, BIOS N3XET38W (1.13 ) 04/26/2023 Jun 25 21:06:29 ox.rosenauer.org kernel: RIP: 0010:exc_control_protection+0xb8/0xc0 Jun 25 21:06:29 ox.rosenauer.org kernel: Code: 48 8b 93 80 00 00 00 be fc 00 00 00 48 c7 c7 77 6c 19 a2 e8 4a 55 42 ff e9 7b ff ff ff 48 c7 43 50 00 00 00 00 e9 6e ff ff ff <0f> 0b 66 0f 1f 44 00 00 90 90 9> Jun 25 21:06:29 ox.rosenauer.org kernel: RSP: 0018:ffffa88b882afd68 EFLAGS: 00010002 Jun 25 21:06:29 ox.rosenauer.org kernel: RAX: 0000000000000028 RBX: ffffa88b882afd88 RCX: 0000000000000000 Jun 25 21:06:29 ox.rosenauer.org kernel: RDX: 0000000000000000 RSI: ffff9bfc3f6a74c0 RDI: ffff9bfc3f6a74c0 Jun 25 21:06:29 ox.rosenauer.org kernel: RBP: 0000000000000003 R08: 0000000000000000 R09: ffffa88b882afc28 Jun 25 21:06:29 ox.rosenauer.org kernel: R10: 0000000000000003 R11: ffff9bfc5f6c06e8 R12: 0000000000000000 Jun 25 21:06:29 ox.rosenauer.org kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Jun 25 21:06:29 ox.rosenauer.org kernel: FS: 00007fdaa81fc6c0(0000) GS:ffff9bfc3f680000(0000) knlGS:0000000000000000 Jun 25 21:06:29 ox.rosenauer.org kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 25 21:06:29 ox.rosenauer.org kernel: CR2: 00007fda94568000 CR3: 000000019ceae000 CR4: 0000000000f50ee0 Jun 25 21:06:29 ox.rosenauer.org kernel: PKRU: 55555554 Jun 25 21:06:29 ox.rosenauer.org kernel: Call Trace: Jun 25 21:06:29 ox.rosenauer.org kernel: <TASK> Jun 25 21:06:29 ox.rosenauer.org kernel: ? die+0x36/0x90 Jun 25 21:06:29 ox.rosenauer.org kernel: ? do_trap+0xda/0x100 Jun 25 21:06:29 ox.rosenauer.org kernel: ? exc_control_protection+0xb8/0xc0 Jun 25 21:06:29 ox.rosenauer.org kernel: ? do_error_trap+0x6a/0x90 Jun 25 21:06:29 ox.rosenauer.org kernel: ? exc_control_protection+0xb8/0xc0 Jun 25 21:06:29 ox.rosenauer.org kernel: ? exc_invalid_op+0x50/0x70 Jun 25 21:06:29 ox.rosenauer.org kernel: ? exc_control_protection+0xb8/0xc0 Jun 25 21:06:29 ox.rosenauer.org kernel: ? asm_exc_invalid_op+0x1a/0x20 Jun 25 21:06:29 ox.rosenauer.org kernel: ? exc_control_protection+0xb8/0xc0 Jun 25 21:06:29 ox.rosenauer.org kernel: ? exc_control_protection+0x6e/0xc0 Jun 25 21:06:29 ox.rosenauer.org kernel: asm_exc_control_protection+0x26/0x30 Jun 25 21:06:29 ox.rosenauer.org kernel: RIP: 0010:0xffffa88b885f4fe0 Jun 25 21:06:29 ox.rosenauer.org kernel: Code: 89 da 5b 41 5c 41 5d 5d e9 ad 19 fb ff 48 83 c4 28 b8 8e f8 ff ff 5b 41 5c 41 5d 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 <55> 48 8d 35 18 80 1d 00 48 89 e> Jun 25 21:06:29 ox.rosenauer.org kernel: RSP: 0018:ffffa88b882afe38 EFLAGS: 00010282 Jun 25 21:06:29 ox.rosenauer.org kernel: RAX: ffffa88b885f4fe0 RBX: ffffa88b887f9010 RCX: ffffa88b887e3000 Jun 25 21:06:29 ox.rosenauer.org kernel: RDX: 0000000000000000 RSI: ffff9bf59ceaea90 RDI: ffff9bf5b1814410 Jun 25 21:06:29 ox.rosenauer.org kernel: RBP: ffffa88b882afe88 R08: 0000000000000024 R09: ffffa88b887e3000 Jun 25 21:06:29 ox.rosenauer.org kernel: R10: ffffe1f446e10308 R11: 0000000000000000 R12: 0000000000000000 Jun 25 21:06:29 ox.rosenauer.org kernel: R13: ffffffffc20e23a0 R14: ffff9bf5b1814410 R15: 0000000000000004 Jun 25 21:06:29 ox.rosenauer.org kernel: ? supdrvIOCtl+0x2d20/0x31b0 [vboxdrv d08de03400e80fa9905e861e5fb8375348c52d31] Jun 25 21:06:29 ox.rosenauer.org kernel: ? _copy_from_user+0x4a/0x60 Jun 25 21:06:29 ox.rosenauer.org kernel: ? VBoxDrvLinuxIOCtl_7_0_8+0x151/0x240 [vboxdrv d08de03400e80fa9905e861e5fb8375348c52d31] Jun 25 21:06:29 ox.rosenauer.org kernel: ? __x64_sys_ioctl+0x91/0xd0 Jun 25 21:06:29 ox.rosenauer.org kernel: ? do_syscall_64+0x5d/0x90 Jun 25 21:06:29 ox.rosenauer.org kernel: ? entry_SYSCALL_64_after_hwframe+0x72/0xdc Jun 25 21:06:29 ox.rosenauer.org kernel: </TASK> Jun 25 21:06:29 ox.rosenauer.org kernel: Modules linked in: ccm rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device af_packet vboxnetadp(O) vboxnetflt(O) qrtr vboxdrv(O) cmac algif_hash algif_skcipher a> Jun 25 21:06:29 ox.rosenauer.org kernel: snd_hwdep intel_pmc_bxt pmt_telemetry mei_pxp kvm libarc4 iTCO_vendor_support intel_rapl_msr pmt_class mtd irqbypass snd_pcm ov2740 think_lmi processor_thermal_devi> Jun 25 21:06:29 ox.rosenauer.org kernel: ghash_clmulni_intel xhci_pci i2c_algo_bit sha512_ssse3 xhci_pci_renesas drm_buddy drm_display_helper xhci_hcd cec aesni_intel ucsi_acpi nvme rc_core typec_ucsi inte> Jun 25 21:06:29 ox.rosenauer.org kernel: ---[ end trace 0000000000000000 ]--- Jun 25 21:06:29 ox.rosenauer.org kernel: RIP: 0010:exc_control_protection+0xb8/0xc0 Jun 25 21:06:29 ox.rosenauer.org kernel: Code: 48 8b 93 80 00 00 00 be fc 00 00 00 48 c7 c7 77 6c 19 a2 e8 4a 55 42 ff e9 7b ff ff ff 48 c7 43 50 00 00 00 00 e9 6e ff ff ff <0f> 0b 66 0f 1f 44 00 00 90 90 9> Jun 25 21:06:29 ox.rosenauer.org kernel: RSP: 0018:ffffa88b882afd68 EFLAGS: 00010002 Jun 25 21:06:29 ox.rosenauer.org kernel: RAX: 0000000000000028 RBX: ffffa88b882afd88 RCX: 0000000000000000 Jun 25 21:06:29 ox.rosenauer.org kernel: RDX: 0000000000000000 RSI: ffff9bfc3f6a74c0 RDI: ffff9bfc3f6a74c0 Jun 25 21:06:29 ox.rosenauer.org kernel: RBP: 0000000000000003 R08: 0000000000000000 R09: ffffa88b882afc28 Jun 25 21:06:29 ox.rosenauer.org kernel: R10: 0000000000000003 R11: ffff9bfc5f6c06e8 R12: 0000000000000000 Jun 25 21:06:29 ox.rosenauer.org kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Jun 25 21:06:29 ox.rosenauer.org kernel: FS: 00007fdaa81fc6c0(0000) GS:ffff9bfc3f680000(0000) knlGS:0000000000000000 Jun 25 21:06:29 ox.rosenauer.org kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 25 21:06:29 ox.rosenauer.org kernel: CR2: 00007fda94568000 CR3: 000000019ceae000 CR4: 0000000000f50ee0 Jun 25 21:06:29 ox.rosenauer.org kernel: PKRU: 55555554 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1212601] Cannot emerge from sleep
by bugzilla_noreply＠suse.com 26 Jun '23

26 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212601 https://bugzilla.suse.com/show_bug.cgi?id=1212601#c4 --- Comment #4 from Stuart Nettleton <snettlet(a)gmail.com> --- (In reply to Takashi Iwai from comment #3) > If you can test anything new, please update the information. > TW will switch to 6.4 kernel soon later in anyway, the test with 6.3.9 might > be moot, though. Thanks Takashi ... yesterday it seems to be fixed with 6.3.9-1-default ... much appreciate your help! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212484] radeon/amdgpu: Brief screen corruption on resume after Leap 15.5 update
by bugzilla_noreply＠suse.com 26 Jun '23

26 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212484 https://bugzilla.suse.com/show_bug.cgi?id=1212484#c7 --- Comment #7 from Luigi Baldoni <aloisio(a)gmx.com> --- > Then this should be reported and fixed in the upstream side at first. > Care to report it to the upstream tracker, gitlab.freedesktop.org Issues? Done. https://gitlab.freedesktop.org/drm/amd/-/issues/2656 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212690] kernel BUG at arch/x86/kernel/traps.c:255
by bugzilla_noreply＠suse.com 26 Jun '23

26 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212690 https://bugzilla.suse.com/show_bug.cgi?id=1212690#c2 --- Comment #2 from Wolfgang Rosenauer <wolfgang(a)rosenauer.org> --- Apparently yes, it's a duplicate since ibt=off helped. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212731] New: [Build 20230624] btrfs: openQA test fails in quotacheck
by bugzilla_noreply＠suse.com 26 Jun '23

26 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212731 Bug ID: 1212731 Summary: [Build 20230624] btrfs: openQA test fails in quotacheck Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3380864/modules/quot a/steps/18 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation This error has appeared in openQA since snapshot 0624, which was the update of kernel from 6.3.7 to 6.3.9 quotecheck reports: quotacheck: cannot remount filesystem /tmp/quota read-write: cannot write new quota files Up to snapshot 0623, this passed openQA test code is: https://openqa.opensuse.org/tests/3380864/modules/quota/steps/1/src openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_textmode@64bit fails in [quota](https://openqa.opensuse.org/tests/3380864/modules/quota/steps/18) ## Test suite description Maintainer: slindomansilla(a)suse.de. Mainly post-installation console extra tests. ## Reproducible Fails since (at least) Build [20230509](https://openqa.opensuse.org/tests/3280468) ## Expected result Last good: [20230509](https://openqa.opensuse.org/tests/3279101) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212729] New: Kernel 6.3.9 from snapshot of 24.06.2023 breaks wifi and suspend
by bugzilla_noreply＠suse.com 26 Jun '23

26 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212729 Bug ID: 1212729 Summary: Kernel 6.3.9 from snapshot of 24.06.2023 breaks wifi and suspend 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: silviucc(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, After updating my MicroOS install to snapshot 20230624 my system won't suspend anymore and it may even kernel panic during boot. If it manages to boot then it does not connect to my wifi router. The wifi chip is identified by inxi as Qualcomm Atheros QCA6174 using the ath10k_pci driver I used snapper to rollback snapshot 20230623 and everything works fine. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1212629] All USB ports and attached devices are abruptly disconnected, and data is lost.
by bugzilla_noreply＠suse.com 26 Jun '23

26 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212629 https://bugzilla.suse.com/show_bug.cgi?id=1212629#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(publio.escipion.e | |l.africano(a)gmail.com) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Some packages might tune the parameters for power-saving, and it might change the behavior, too. For example, tlp is notorious about too aggressive setups. Please give the hwinfo output from both working (Live image) and non-working (installed Leap 15.5) systems. Take the dmesg outputs on both, and attach all outputs to Bugzilla. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212601] Cannot emerge from sleep
by bugzilla_noreply＠suse.com 26 Jun '23

26 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212601 https://bugzilla.suse.com/show_bug.cgi?id=1212601#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snettlet(a)gmail.com Flags| |needinfo?(snettlet(a)gmail.co | |m) --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- If you can test anything new, please update the information. TW will switch to 6.4 kernel soon later in anyway, the test with 6.3.9 might be moot, though. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212484] radeon/amdgpu: Brief screen corruption on resume after Leap 15.5 update
by bugzilla_noreply＠suse.com 26 Jun '23

26 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212484 https://bugzilla.suse.com/show_bug.cgi?id=1212484#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Luigi Baldoni from comment #4) > > Could you check the behavior with the latest kernel in OBS Kernel:stable:Backport repo? Just to verify whether it's seen in the recent upstream, too. > > 6.3.8-lp154.5.1.ge044c8e appears to make things worse: now the screen > corruption appears even with "suspend". Then this should be reported and fixed in the upstream side at first. Care to report it to the upstream tracker, gitlab.freedesktop.org Issues? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211898] stress-ng fsize failure on NFSv3
by bugzilla_noreply＠suse.com 26 Jun '23

26 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211898 https://bugzilla.suse.com/show_bug.cgi?id=1211898#c1 --- Comment #1 from Neil Brown <nfbrown(a)suse.com> --- The timeout setting it too small. Use a bigger number. NFSv3 (and NFSv4.1, but not NFSv4.2) does not implement fallocate(). So stress-ng uses a "shim_emulate_fallocate()" instead, which writes data. shim_emulate_fallocate() stops trying to write if keep_stressing_flag() fails. One of the things that causes this to fail is when a SIGALARM is delivered, which happens after the timeout. So after the timeout, a fallocate attempt will appear to succeed. This is arguably a bug in stress-ng. NFS is behaving correctly. stress-ng is not getting an error, because it the way is emulates fallocate is not reliable. -- You are receiving this mail because: You are the assignee for the bug.

1 0