December 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 12 Dec '22

12 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c12 --- Comment #12 from Philippe Cond� <conde.philippe(a)skynet.be> --- I have build 3 bisect kernel: the problem occurs still but I need more and more time to have the lock.( last build the lock occured after 2 days testing. I tested this morning with kernel 6.0.12 and the lock occurs immediately or after some minuutes. I have the feeling that the locks occur more and more rapidely when going from kernel 6.0.8 -> 6.0.9 -> 6.0.10 -> 6.0.12 I had 3 locks with kernel 6.0.12 but only the first gives a general protection fault in journalctl. I attach the journalctl outputs for 6.0.12 here my hardware # inxi -Ga --cpu CPU: Info: model: Intel Xeon E5-2620 0 socket: LGA2011 (Proc 2) note: check bits: 64 type: MT SMP arch: Sandy Bridge level: v2 built: 2010-12 process: Intel 32nm family: 6 model-id: 0x2D (45) stepping: 7 microcode: 0x710 Topology: cpus: 1x cores: 1 tpc: 12 threads: 12 smt: enabled cache: L1: 2x 64 KiB (128 KiB) desc: d-1x32 KiB; i-1x32 KiB L2: 2x 256 KiB (512 KiB) desc: 1x256 KiB L3: 2x 15 MiB (30 MiB) desc: 1x15 MiB Speed (MHz): avg: 1995 min/max: N/A base/boost: 2000/4800 volts: 1.4 V ext-clock: 200 MHz cores: 1: 1995 2: 1995 3: 1995 4: 1995 5: 1995 6: 1995 7: 1995 8: 1995 9: 1995 10: 1995 11: 1995 12: 1995 bogomips: 47879 Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported Type: l1tf mitigation: PTE Inversion Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown Type: meltdown status: Unknown (XEN PV detected, hypervisor mitigation required) Type: mmio_stale_data status: Unknown: No mitigations Type: retbleed status: Not affected Type: spec_store_bypass status: Vulnerable Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: NVIDIA GK104GL [Quadro K4200] driver: nouveau v: kernel non-free: series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Kepler code: GKxxx process: TSMC 28nm built: 2012-18 pcie: gen: 2 speed: 5 GT/s lanes: 16 ports: active: DP-1,DVI-I-1 empty: DP-2 bus-ID: 0a:00.0 chip-ID: 10de:11b4 class-ID: 0300 temp: 44.0 C Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5 compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa alternate: nouveau,nv,nvidia dri: nouveau gpu: nouveau display-ID: :0 screens: 1 Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22") s-diag: 1055mm (41.54") Monitor-1: DP-1 pos: right model: Asus VG248 serial: F2LMQS017700 built: 2015 res: 1920x1080 hz: 60 dpi: 92 gamma: 1.2 size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes: max: 1920x1080 min: 720x400 Monitor-2: DVI-I-1 pos: primary,left model: Asus VG248 serial: F5LMQS077420 built: 2015 res: 1920x1080 hz: 60 dpi: 92 gamma: 1.2 size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes: max: 1920x1080 min: 720x400 API: OpenGL v: 4.3 Mesa 22.2.4 renderer: NVE4 direct render: Yes hpprol2:~ # -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206084] pynfs fails in test nfs4.0 on x86-64 and aarch64
by bugzilla_noreply＠suse.com 12 Dec '22

12 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206084 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(yosun(a)suse.com) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206084] pynfs fails in test nfs4.0 on x86-64 and aarch64
by bugzilla_noreply＠suse.com 12 Dec '22

12 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206084 https://bugzilla.suse.com/show_bug.cgi?id=1206084#c4 Neil Brown <nfbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(nfbrown(a)suse.com) | --- Comment #4 from Neil Brown <nfbrown(a)suse.com> --- This failure could be related to Commit 4271c2c08875 ("NFSD: limit the number of v4 clients to 1024 per 1GB of system memory") which landed in Linux 6.0. The Linux NFS server now limits the number of active clients to 1024 per gigabyte of memory. It is possible that the pynfs test suite creates lots of clients without cleaning them up properly You can see how many active clients there are by looking in /proc/fs/nfsd/clients on the NFS server. There will be one directory for each client. Yong Sun: can you modify the test hardness to check /proc/fs/nfsd/clients when the failure happens? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202950] radeon [Radeon 6450] Blank screen (Kernel driver regression on Leap 15.4)
by bugzilla_noreply＠suse.com 11 Dec '22

11 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202950 http://bugzilla.opensuse.org/show_bug.cgi?id=1202950#c25 Jacobs <opensuse(a)jackbonet.eu> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(opensuse@jackbone | |t.eu) | --- Comment #25 from Jacobs <opensuse(a)jackbonet.eu> --- Hello, I downloaded the latest file from "https://get.opensuse.org/leap/15.4/" named " openSUSE-Leap-15.4-CR-DVD-x86_64-Build19.2-Media.iso". Copied the file to an USB-stick and tried to start without any changes on the boot options. But behavior is just the same. There is no remote access available when I try the update. dmesg log can only be provided when I start using textmode or the "nomodeset"-workaround as far as I can see. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1206084] pynfs fails in test nfs4.0 on x86-64 and aarch64
by bugzilla_noreply＠suse.com 10 Dec '22

10 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206084 https://bugzilla.suse.com/show_bug.cgi?id=1206084#c3 --- Comment #3 from Yong Sun <yosun(a)suse.com> --- btw, it has only 1 commit in 4 months in testsuite pynfs. And I tried the previous commit(818e7e1c102c2c5ccc90f2f8c7beaaf0c683d359) also fails in the same way. So I think it's not because of test script update. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206084] pynfs fails in test nfs4.0 on x86-64 and aarch64
by bugzilla_noreply＠suse.com 10 Dec '22

10 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206084 https://bugzilla.suse.com/show_bug.cgi?id=1206084#c2 Yong Sun <yosun(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(yosun(a)suse.com) | --- Comment #2 from Yong Sun <yosun(a)suse.com> --- (In reply to Jiri Slaby from comment #1) > @Yong: is this now or you simply started running this test recently? I.e. is > this a regression? I'm not sure if it's regression or not. I just found it fails, and check all previous tests fails like that[1](the most early one is build20221101). I remember I checked it two months before and it's passed. But o3 doesn't have that long record to see the last good. [1]https://openqa.opensuse.org/tests/2927483#next_previous -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206042] New: [Build 20221204] zdup from 15.4 to Tumbleweed falls on removing 15.4 kernel
by bugzilla_noreply＠suse.com 09 Dec '22

09 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206042 Bug ID: 1206042 Summary: [Build 20221204] zdup from 15.4 to Tumbleweed falls on removing 15.4 kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2929149/modules/zdup /steps/166 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 Found By: openQA Blocker: Yes ## Observation (1580/2514) Removing kernel-default-optional-5.14.21-150400.22.1.x86_64 [...[ 580.054161] [RPM][8690]: Transaction ID 638df844 started [ 580.120327] [RPM][8690]: erase kernel-default-optional-5.14.21-150400.22.1.x86_64: success /var/tmp/rpm-tmp.RH7ho2: line 1: /usr/lib/module-init-tools/kernel-scriptlets/inkmp-preun: No such file or directory [ 580.131156] [RPM][8690]: scriptlet %preun(kernel-default-optional-5.14.21-150400.22.1.x86_64) failure: 2 [ 580.132144] [RPM][8690]: erase kernel-default-optional-5.14.21-150400.22.1.x86_64: failure [ 580.132880] [RPM][8690]: 1 elements failed, 1 scripts failed Upgrades from 15.3 to TW do not have this problem openQA test in scenario opensuse-Tumbleweed-NET-x86_64-zdup-Leap-15.4-gnome@64bit fails in [zdup](https://openqa.opensuse.org/tests/2929149/modules/zdup/steps/166) ## Test suite description ## Reproducible Fails since (at least) Build [20221204](https://openqa.opensuse.org/tests/2929000) ## Expected result Last good: (unknown) (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 17

[Bug 1189946] New: [trackerbug] Ancient patch cleanup
by bugzilla_noreply＠suse.com 09 Dec '22

09 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1189946 Bug ID: 1189946 Summary: [trackerbug] Ancient patch cleanup 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: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jeffm(a)suse.com, mkubecek(a)suse.com Found By: --- Blocker: --- This is the tracker bug for cleaning up old patches in the master branch. -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 1206224] Dell notebook drains battery during sleep
by bugzilla_noreply＠suse.com 09 Dec '22

09 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206224 https://bugzilla.suse.com/show_bug.cgi?id=1206224#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo?(msvec(a)suse.com) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Could you check with the latest TW backport kernel whether the problem persists? It's available in OBS Kernel:stable:Backport repo. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206084] pynfs fails in test nfs4.0 on x86-64 and aarch64
by bugzilla_noreply＠suse.com 09 Dec '22

09 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206084 https://bugzilla.suse.com/show_bug.cgi?id=1206084#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com, | |nfbrown(a)suse.com, | |yosun(a)suse.com Flags| |needinfo?(yosun(a)suse.com), | |needinfo?(nfbrown(a)suse.com) --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- @Neil: any ideas? @Yong: is this now or you simply started running this test recently? I.e. is this a regression? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205891] System freeze
by bugzilla_noreply＠suse.com 09 Dec '22

09 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205891 https://bugzilla.suse.com/show_bug.cgi?id=1205891#c11 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |FIXED --- Comment #11 from Jiri Slaby <jslaby(a)suse.com> --- So if you see the issue, feel free to reopen. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206224] Dell notebook drains battery during sleep
by bugzilla_noreply＠suse.com 09 Dec '22

09 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206224 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 1205891] System freeze
by bugzilla_noreply＠suse.com 08 Dec '22

08 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205891 https://bugzilla.suse.com/show_bug.cgi?id=1205891#c10 --- Comment #10 from Branislav Klocok <branislav.klocok(a)orava.sk> --- Tested again today with delay and seems working fine. Just as a remark, form hibernation was working fine, problem was sleeping. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202950] radeon [Radeon 6450] Blank screen (Kernel driver regression on Leap 15.4)
by bugzilla_noreply＠suse.com 08 Dec '22

08 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202950 http://bugzilla.opensuse.org/show_bug.cgi?id=1202950#c24 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags|needinfo?(kernel-bugs@opens |needinfo?(opensuse@jackbone |use.org) |t.eu) --- Comment #24 from Takashi Iwai <tiwai(a)suse.com> --- Could you verify whether the problem still persists with the latest Leap 15.4 update kernel (after removing the blacklist or nomodeset workaround)? If the problem persists, please give the dmesg output from the bad working state (I suppose you can still access via remote login?). -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1203519] New: floating shutdown problem on pinebook pro
by bugzilla_noreply＠suse.com 08 Dec '22

08 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203519 Bug ID: 1203519 Summary: floating shutdown problem on pinebook pro Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: werwolf131313(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- intermittent shutdown problem on pinebook pro, the problem is expressed as follows: after the laptop is turned off (it doesn��t matter by the button in the menu or via sudo systemctl shutdown), a regular shutdown occurs, the service stop log is visible and everything is as it should be, BUT, after the screen goes blank, the board remains on. this can be checked if you try to turn it on, pressing the button does not work. only a long press of the power key (to completely turn off) for 7-10 seconds, and a second press (to turn it on) allows you to turn on the pinebook. the problem is not observed in other distributions (tried on manjaro, armbian, gentoo) and is specific to opensuse. in my case, the installation differs from the typical one in that the operating system is installed on a microsd card (due to the death of emmc), can this affect? but in other distributions, even installed on the same microsd card, the problem is not observed. I'm using opensuse tumbleweed installed from the openSUSE-Tumbleweed-ARM-KDE-pinebookpro.aarch64.raw.xz image. at the moment there are all the latest updates, but the problem has existed for quite a long time. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1202950] radeon [Radeon 6450] Blank screen (Kernel driver regression on Leap 15.4)
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202950 http://bugzilla.opensuse.org/show_bug.cgi?id=1202950#c23 Jacobs <opensuse(a)jackbonet.eu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kernel-bugs(a)opensuse.org Flags| |needinfo?(kernel-bugs@opens | |use.org) --- Comment #23 from Jacobs <opensuse(a)jackbonet.eu> --- Hi there, is there any progress with this issue? Any ideas how to solve the problem or how to be able to perform the upgrade? Thanks. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

needinfo requested: [Bug 1202950] radeon [Radeon 6450] Blank screen (Kernel driver regression on Leap 15.4)
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

Jacobs <opensuse(a)jackbonet.eu> has asked openSUSE Kernel Bugs <kernel-bugs(a)opensuse.org> for needinfo: Bug 1202950: radeon [Radeon 6450] Blank screen (Kernel driver regression on Leap 15.4) http://bugzilla.opensuse.org/show_bug.cgi?id=1202950 --- Comment #23 from Jacobs <opensuse(a)jackbonet.eu> --- Hi there, is there any progress with this issue? Any ideas how to solve the problem or how to be able to perform the upgrade? Thanks.

1 0

[Bug 1205891] System freeze
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205891 https://bugzilla.suse.com/show_bug.cgi?id=1205891#c9 --- Comment #9 from Frank Kr�ger <fkrueger(a)mailbox.org> --- (In reply to Branislav Klocok from comment #7) > Today there was an upgrade to 252.2-2.1. To me it seems the problem > disappeared. Can anyone confirm? For me today's update made it worse, black screen after suspend and hibernate, switching TTY doesn't have any effect. Downgrading to systemd-252.2-1.1.x86_64 and performing a cold boot solved the issue, as described in comment 5. This bug is really weird, I cannot find any hints in the logs. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205891] System freeze
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205891 https://bugzilla.suse.com/show_bug.cgi?id=1205891#c8 --- Comment #8 from Ailin Nemui <ailin.nemui(a)gmail.com> --- did you wait 2 hours after suspend to check if the issue appears? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205891] System freeze
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205891 https://bugzilla.suse.com/show_bug.cgi?id=1205891#c7 --- Comment #7 from Branislav Klocok <branislav.klocok(a)orava.sk> --- Today there was an upgrade to 252.2-2.1. To me it seems the problem disappeared. Can anyone confirm? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193599] New: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193599 Bug ID: 1193599 Summary: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following errors appear at boot broken atomic modeset userspace detected, disabling atomic [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D Full log https://paste.opensuse.org/83436185 Hardware Dell Precision 7530 CPU: Intel Xeon E-2186M GPU: Intel P630 / Nvidia Quadro P3200 -- You are receiving this mail because: You are the assignee for the bug.

1 33

[Bug 1206172] New: mhvtl fails to build on Leap 15.5 error: too few arguments to function 'mhvtl_queuecommand_lck'
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206172 Bug ID: 1206172 Summary: mhvtl fails to build on Leap 15.5 error: too few arguments to function 'mhvtl_queuecommand_lck' Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.5/mhvtl/… mhvtl fails to build on Leap 15.5, based on the SCSI nature it seem to be related to Bug 1206169 Could you please look a it? 66s] make: Entering directory '/usr/src/linux-5.14.21-150500.34-obj/x86_64/default' [ 67s] CC [M] /home/abuild/rpmbuild/BUILD/mhvtl-1.64_release+835.6beb0aa01437/obj/default/mhvtl.o [ 68s] In file included from /home/abuild/rpmbuild/BUILD/mhvtl-1.64_release+835.6beb0aa01437/obj/default/mhvtl.c:63:0: [ 68s] /home/abuild/rpmbuild/BUILD/mhvtl-1.64_release+835.6beb0aa01437/obj/default/mhvtl.c: In function 'mhvtl_queuecommand': [ 68s] /home/abuild/rpmbuild/BUILD/mhvtl-1.64_release+835.6beb0aa01437/obj/default/mhvtl.c:300:22: error: too few arguments to function 'mhvtl_queuecommand_lck' [ 68s] static DEF_SCSI_QCMD(mhvtl_queuecommand) [ 68s] ^ [ 68s] /usr/src/linux-5.14.21-150500.34/include/scsi/scsi_host.h:516:8: note: in definition of macro 'DEF_SCSI_QCMD' [ 68s] rc = func_name##_lck(cmd); \ [ 68s] ^~~~~~~~~ [ 68s] /home/abuild/rpmbuild/BUILD/mhvtl-1.64_release+835.6beb0aa01437/obj/default/mhvtl.c:278:12: note: declared here [ 68s] static int mhvtl_queuecommand_lck(struct scsi_cmnd * [ 68s] ^~~~~~~~~~~~~~~~~~~~~~ [ 68s] make[2]: *** [/usr/src/linux-5.14.21-150500.34/scripts/Makefile.build:272: /home/abuild/rpmbuild/BUILD/mhvtl-1.64_release+835.6beb0aa01437/obj/default/mhvtl.o] Error 1 [ 68s] make[1]: *** [/usr/src/linux-5.14.21-150500.34/Makefile:1891: /home/abuild/rpmbuild/BUILD/mhvtl-1.64_release+835.6beb0aa01437/obj/default] Error 2 [ 68s] make: *** [../../../linux-5.14.21-150500.34/Makefile:220: __sub-make] Error 2 [ 68s] make: Leaving directory '/usr/src/linux-5.14.21-150500.34-obj/x86_64/default' [ 68s] error: Bad exit status from /var/tmp/rpm-tmp.xY7F0m (%build) [ 68s] -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1206169] New: mhvtl fails to build on Leap 15.5 error: 'struct scsi_cmnd' has no member named 'scsi_done'
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206169 Bug ID: 1206169 Summary: mhvtl fails to build on Leap 15.5 error: 'struct scsi_cmnd' has no member named 'scsi_done' Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello this particular kmp fails to buidl on Leap 15.5 Could you please look into it? https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.5/vhba-k… 48s] make[1]: Entering directory '/usr/src/linux-5.14.21-150500.34-obj/x86_64/default' [ 50s] CC [M] /home/abuild/rpmbuild/BUILD/obj-default/vhba.o [ 51s] /home/abuild/rpmbuild/BUILD/obj-default/vhba.c: In function 'vhba_queuecommand': [ 51s] /home/abuild/rpmbuild/BUILD/obj-default/vhba.c:492:12: error: 'struct scsi_cmnd' has no member named 'scsi_done' [ 51s] cmd->scsi_done(cmd); [ 51s] ^~ [ 51s] /home/abuild/rpmbuild/BUILD/obj-default/vhba.c: In function 'vhba_ctl_write': [ 51s] /home/abuild/rpmbuild/BUILD/obj-default/vhba.c:827:18: error: 'struct scsi_cmnd' has no member named 'scsi_done' [ 51s] vcmd->cmd->scsi_done(vcmd->cmd); [ 51s] ^~ [ 51s] /home/abuild/rpmbuild/BUILD/obj-default/vhba.c: In function 'vhba_ctl_release': [ 51s] /home/abuild/rpmbuild/BUILD/obj-default/vhba.c:953:18: error: 'struct scsi_cmnd' has no member named 'scsi_done' [ 51s] vcmd->cmd->scsi_done(vcmd->cmd); [ 51s] ^~ [ 51s] make[3]: *** [/usr/src/linux-5.14.21-150500.34/scripts/Makefile.build:272: /home/abuild/rpmbuild/BUILD/obj-default/vhba.o] Error 1 [ 51s] make[2]: *** [/usr/src/linux-5.14.21-150500.34/Makefile:1891: /home/abuild/rpmbuild/BUILD/obj-default] Error 2 [ 51s] make[1]: *** [../../../linux-5.14.21-150500.34/Makefile:220: __sub-make] Error 2 [ 51s] make[1]: Leaving directory '/usr/src/linux-5.14.21-150500.34-obj/x86_64/default' [ 51s] make: *** [Makefile:14: modules] Error 2 [ 51s] error: Bad exit status from /var/tmp/rpm-tmp.s00T1A (%build) -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1205774] New: Kernel 6.0.8 + nvidia 525.53 crash on BUG: kernel NULL pointer dereference, #PF: supervisor instruction fetch in kernel mode
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205774 Bug ID: 1205774 Summary: Kernel 6.0.8 + nvidia 525.53 crash on BUG: kernel NULL pointer dereference, #PF: supervisor instruction fetch in kernel mode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bruno(a)ioda-net.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863125 --> http://bugzilla.opensuse.org/attachment.cgi?id=863125&action=edit Last kernel 6.0.8 boot and crash Hello I need help to find the root cause of crashes (complete freeze of the workstation). Since the introduction of kernel 6.0.8 and latest nvidia 525.53 I constantly face complete machine freeze, when I'm using my external monitors. nov 25 16:05:34 qt-kt kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 nov 25 16:05:34 qt-kt kernel: #PF: supervisor instruction fetch in kernel mode nov 25 16:05:34 qt-kt kernel: #PF: error_code(0x0010) - not-present page nov 25 16:05:34 qt-kt kernel: PGD 0 P4D 0 nov 25 16:05:34 qt-kt kernel: Oops: 0010 [#1] PREEMPT SMP PTI nov 25 16:05:34 qt-kt kernel: CPU: 3 PID: 1004 Comm: nvidia-modeset/ Tainted: P OE 6.0.8-1-default #1 openSUSE Tumbleweed 9d20364b934f5aab0a9bdf84e8f45cfdfae39dab nov 25 16:05:34 qt-kt kernel: Hardware name: Dell Inc. Precision 7510/0YH43H, BIOS 1.29.3 09/18/2022 nov 25 16:05:34 qt-kt kernel: RIP: 0010:0x0 nov 25 16:05:34 qt-kt kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6. nov 25 16:05:34 qt-kt kernel: RSP: 0018:ffffadc300703c90 EFLAGS: 00010207 nov 25 16:05:34 qt-kt kernel: RAX: 0000000000000000 RBX: ffff9b2996c75378 RCX: 0000000000000004 nov 25 16:05:34 qt-kt kernel: RDX: 0000000000000010 RSI: ffff9b2996c75378 RDI: ffffadc300703a10 nov 25 16:05:34 qt-kt kernel: RBP: ffff9b292ef8b560 R08: 0000000000000000 R09: 0000000000000040 nov 25 16:05:34 qt-kt kernel: R10: ffff9b2886b28008 R11: ffffadc300703c00 R12: 0000000000000000 nov 25 16:05:34 qt-kt kernel: R13: 0000000000000000 R14: ffffffffc4fbee70 R15: ffffffffc4eb7580 nov 25 16:05:34 qt-kt kernel: FS: 0000000000000000(0000) GS:ffff9b37c44c0000(0000) knlGS:0000000000000000 nov 25 16:05:34 qt-kt kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 nov 25 16:05:34 qt-kt kernel: CR2: ffffffffffffffd6 CR3: 000000075be10001 CR4: 00000000003706e0 nov 25 16:05:34 qt-kt kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 nov 25 16:05:34 qt-kt kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 nov 25 16:05:34 qt-kt kernel: Call Trace: nov 25 16:05:34 qt-kt kernel: <TASK> nov 25 16:05:34 qt-kt kernel: _nv001281kms+0x194/0x1a0 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv001274kms+0x9a/0xd0 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv001466kms+0x172/0x180 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv001149kms+0xf3/0xa50 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? schedule+0x5a/0xd0 nov 25 16:05:34 qt-kt kernel: ? schedule_timeout+0x10e/0x150 nov 25 16:05:34 qt-kt kernel: ? nvkms_sema_up+0x10/0x10 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? __down_common+0x10b/0x1e0 nov 25 16:05:34 qt-kt kernel: ? nvkms_sema_up+0x10/0x10 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _nv002457kms+0x2d/0x70 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? nvkms_kthread_q_callback+0x88/0xf0 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? _main_loop+0x77/0x130 [nvidia_modeset 4cdb9c16932eaf3d76d37eaaf2544a31bf3316d8] nov 25 16:05:34 qt-kt kernel: ? kthread+0xd7/0x100 nov 25 16:05:34 qt-kt kernel: ? kthread_complete_and_exit+0x20/0x20 nov 25 16:05:34 qt-kt kernel: ? ret_from_fork+0x1f/0x30 nov 25 16:05:34 qt-kt kernel: </TASK> nov 25 16:05:34 qt-kt kernel: Modules linked in: rfcomm snd_seq_dummy snd_hrtimer snd_seq nf_nat_sip nft_objref af_packet nf_conntrack_sip nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct n> nov 25 16:05:34 qt-kt kernel: processor_thermal_device_pci_legacy irqbypass iwlwifi processor_thermal_device pcspkr ledtrig_audio processor_thermal_rfim snd_usbmidi_lib efi_pstore snd_intel_sdw_acpi sparse_keymap processor_thermal_mbox cdc_wdm videob> nov 25 16:05:34 qt-kt kernel: fuse configfs dmi_sysfs ip_tables x_tables cmac algif_hash algif_skcipher af_alg hid_logitech_hidpp hid_logitech_dj hid_generic dm_crypt usbhid essiv authenc trusted asn1_encoder tee bnep btusb btrtl btbcm btintel btmtk > nov 25 16:05:34 qt-kt kernel: CR2: 0000000000000000 nov 25 16:05:34 qt-kt kernel: ---[ end trace 0000000000000000 ]--- Most of the time this happen after resuming the screens, the primary one get on, but the second is always in suspend mode, I have to open neither display settings in plasma or nvidia-settings to set on the second monitor (displayport slave link) after switching off and on the monitor. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1206058] New: Leap 15.4 kernel do not work on a RX 5700 XT
by bugzilla_noreply＠suse.com 06 Dec '22

06 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206058 Bug ID: 1206058 Summary: Leap 15.4 kernel do not work on a RX 5700 XT Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: giuliano.belinassi(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The current kernel in openSUSE leap 15.4 do not work on AMD RX 5700 XT, and I assume it doesn't work on all generations of AMD RDNA1 and RDNA2 cards as well. The kernel loops printing the following message: PCIe bus error: severity=Uncorrected (Non-fatal), type=Transactional Layer device [1002:1479] error status/mask=00100000/00000000 Unsup Req (First) Loading Leap 15.4 installer with AMDGPU driver loaded results in a crash after the graphics screen is loaded. Switching to CTRL-ALT-F1 it reports: gzip: stdout: No space left on device Switching to CTRL-ALT-F4 it reports the PCIe bus error mentioned above. Blacklisting the AMDGPU driver results in the installer loading correctly. -- You are receiving this mail because: You are the assignee for the bug.

1 4