[Bug 1208444] New: 20230216-0 release hardlock
http://bugzilla.opensuse.org/show_bug.cgi?id=1208444 Bug ID: 1208444 Summary: 20230216-0 release hardlock Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs@suse.de Reporter: scott.bradnick@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 864981 --> http://bugzilla.opensuse.org/attachment.cgi?id=864981&action=edit output from 'zypper dup --details' zypper dup from 20230215 -> 20230216 causes hardlock on next boot with 6.1.12. Holding the power button then booting into 6.1.10 and/or 6.1.8 causes the same scenario. I can boot fine into the last pre snapshot and am considering a 'snapper rollback' but wanted to open this issue first (though I can't do any troubleshooting in 20230216-0). Attaching a listing of what would update (from the snapshot). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1208444 http://bugzilla.opensuse.org/show_bug.cgi?id=1208444#c1 --- Comment #1 from Scott Bradnick <scott.bradnick@suse.com> --- I have a 2nd TW system: $ inxi --cpu --graphics CPU: Info: quad core model: Intel Celeron J4115 bits: 64 type: MCP cache: L2: 4 MiB Speed (MHz): avg: 1050 min/max: 800/2500 cores: 1: 800 2: 800 3: 1800 4: 800 Graphics: Device-1: Intel GeminiLake [UHD Graphics 600] driver: i915 v: kernel Display: x11 server: X.Org v: 21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 2560x1440~144Hz API: OpenGL v: 4.6 Mesa 22.3.5 renderer: Mesa Intel UHD Graphics 600 (GLK 2) which doesn't appear to have any issue w/ 20230216, so maybe it's something unique to the 5540 (simple inxi output for it below [from an ssh session])? $ inxi --cpu --graphics CPU: Info: 6-core model: Intel Core i7-9850H bits: 64 type: MT MCP cache: L2: 1.5 MiB Speed (MHz): avg: 2458 min/max: 800/4600 cores: 1: 2600 2: 2600 3: 2600 4: 2600 5: 2600 6: 2600 7: 2600 8: 2600 9: 2600 10: 2600 11: 2600 12: 900 Graphics: Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] driver: i915 v: kernel Device-2: NVIDIA TU117GLM [Quadro T1000 Mobile] driver: nvidia v: 525.89.02 Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo Display: server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8 driver: X: loaded: modesetting,nvidia dri: swrast gpu: i915 resolution: 2560x1440~144Hz API: OpenGL v: 4.5 Mesa 22.3.5 renderer: llvmpipe (LLVM 15.0.7 256 bits) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1208444 Darren Davis <ddavis@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ddavis@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1208444 http://bugzilla.opensuse.org/show_bug.cgi?id=1208444#c8 --- Comment #8 from Scott Bradnick <scott.bradnick@suse.com> --- I'm now running on 6.2.0-5.1.g09a9a65 w/ no issues. I'm wondering if the fix(es) from bsc1206683 were pulled out on SUSE's side but not yet in the mainline kernel before 6.2 series so I was back in hardlock city? Either way, once >=6.2 makes its way into Tumbleweed I'll close this ticket out ~ since I'm mainly just talking to myself -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1208444 http://bugzilla.opensuse.org/show_bug.cgi?id=1208444#c11 Scott Bradnick <scott.bradnick@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #11 from Scott Bradnick <scott.bradnick@suse.com> --- (In reply to Takashi Iwai from comment #10)
The lockdown is (will be) reverted on 6.2.2 kernel. Once after that, with 6.2.x kernel, the original issue is gone, right?
Giving kernel-default-6.2.2-4.1.g3a7e162 a try and everything seems back to normal; I can build nvidia_drm from the .run file as well as the 8852au network module and both load fine. Since my end goal is to use the NVIDIA T1000 card, I'm not going to mess around any more with `prime-select intel` or anything like that to test for those same lockups but it does feel like bbswitch causes this Dell Precision 5540 issue(s) regardless of iGPU or dGPU, but that's for another day. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com