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@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 on the CC list for the bug.