[Bug 1206683] New: kernel-default 6.1.0-1.1 freezes up 2 different machines
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 Bug ID: 1206683 Summary: kernel-default 6.1.0-1.1 freezes up 2 different machines Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: scott.bradnick@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I have 2 systems: 1) Intel Celeron J4115 and Intel GeminiLake [UHD Graphics 600] (driver: i915) 2) Intel Core i7-9850H and Intel CoffeeLake-H GT2 [UHD Graphics 630] along with NVIDIA TU117GLM [Quadro T1000 Mobile] #1 boots to a lightdm login but within 30s-1m of logging in, locks up completely with whatever was last on the screen frozen there and the mouse cursor missing. I'm not sure if it'd just lock up w/o me logging in - I'll try that next time. #2 seems to go through 99% of its boot process, then just as it would kick over to lightdm, it doesn't do anything but freeze up w/ something in the history of the boot process (what looks like dmesg output, the format at least). It boots w/ "splash=silent" and "quiet" REMOVED. #2 generally runs off NVIDIA's latest .run and all was fine prior, I could attempt to possibly use prime-select when booted to the previous kernel and use the iGPU to see if it freezes similarly to #1, but I haven't gotten too adventurous yet. Both work just fine on 6.0.12-1.1 and while I'm kicking around the idea of getting 6.1.1 from https://build.opensuse.org/package/show/Kernel:stable/kernel-default I haven't delved into that either. I'm happy to provide logs and more info, not sure if the freezing/hard lockups will make that impossible. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c1 --- Comment #1 from Scott Bradnick <scott.bradnick@suse.com> --- Gave 6.1.1 ge71748d a try and have the same issue. I tried it with `plymouth.enable=0` as well as 'rescue mode' (not both at the same time) and it made it to a tty1 login screen initially but immediately froze. Can't ssh to it or anything (it did get the assigned IP, but seems to hard-lock, so I can't access it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c2 Dave Plater <davejplater@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |davejplater@gmail.com --- Comment #2 from Dave Plater <davejplater@gmail.com> --- Mine mostly freezes at the point that X display loads. I managed to complete a boot in steps via levels one then three then it continued to level 5 and plasma5 UI. I'm writing this after booting with the previous 6.0.12 kernel I have an hp pavilion with generation 6 intel chipset : Arch: X86-64 Vendor: "GenuineIntel" Model: 6.78.3 "Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz" Features: fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,syscall,nx,pdpe1gb,rdtscp,lm,constant_tsc,art,arch_perfmon,pebs,bts,rep_good,nopl,xtopology,nonstop_tsc,cpuid,aperfmperf,pni,pclmulqdq,dtes64,monitor,ds_cpl,vmx,est,tm2,ssse3,sdbg,fma,cx16,xtpr,pdcm,pcid,sse4_1,sse4_2,x2apic,movbe,popcnt,tsc_deadline_timer,aes,xsave,avx,f16c,rdrand,lahf_lm,abm,3dnowprefetch,cpuid_fault,epb,invpcid_single,pti,ssbd,ibrs,ibpb,stibp,tpr_shadow,vnmi,flexpriority,ept,vpid,ept_ad,fsgsbase,tsc_adjust,bmi1,avx2,smep,bmi2,erms,invpcid,mpx,rdseed,adx,smap,clflushopt,intel_pt,xsaveopt,xsavec,xgetbv1,xsaves,dtherm,arat,pln,pts,hwp,hwp_notify,hwp_act_window,hwp_epp,md_clear,flush_l1d,arch_capabilities Clock: 2000 MHz BogoMips: 3999.93 Cache: 3072 kb Units/Processor: 16 Config Status: cfg=no, avail=yes, need=no, active=unknown -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 Dave Plater <davejplater@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@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=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c3 --- Comment #3 from Dave Plater <davejplater@gmail.com> --- my tumbleweed partition that's quite old appears to function with the 6.1.0 kernel: davepl@ArbuthnotT:~> cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20221220" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20221220" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20221220" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" Hardware Class: cpu Arch: X86-64 Vendor: "GenuineIntel" Model: 6.60.3 "Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz" Features: fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,syscall,nx,pdpe1gb,rdtscp,lm,constant_tsc,arch_perfmon,pebs,bts,rep_good,nopl,xtopology,nonstop_tsc,cpuid,aperfmperf,pni,pclmulqdq,dtes64,monitor,ds_cpl,vmx,smx,est,tm2,ssse3,sdbg,fma,cx16,xtpr,pdcm,pcid,sse4_1,sse4_2,x2apic,movbe,popcnt,tsc_deadline_timer,aes,xsave,avx,f16c,rdrand,lahf_lm,abm,cpuid_fault,invpcid_single,pti,ssbd,ibrs,ibpb,stibp,tpr_shadow,vnmi,flexpriority,ept,vpid,ept_ad,fsgsbase,tsc_adjust,bmi1,avx2,smep,bmi2,erms,invpcid,xsaveopt,dtherm,ida,arat,pln,pts,md_clear,flush_l1d Clock: 1425 MHz BogoMips: 6599.96 Cache: 6144 kb Units/Processor: 16 Config Status: cfg=no, avail=yes, need=no, active=unknown -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c4 --- Comment #4 from Dave Plater <davejplater@gmail.com> --- Created attachment 863711 --> http://bugzilla.opensuse.org/attachment.cgi?id=863711&action=edit kernel logs after starting via runlevel 1 I can boot into plasma5 if I first boot to runlevel 1, then 3 and then to 5 and kde starts and it hasn't frozen yet. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 Dave Plater <davejplater@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|kernel-default 6.1.0-1.1 |kernel-default 6.1.0-1.1 |freezes up 2 different |freezes before the gui |machines |appears -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c5 --- Comment #5 from Dave Plater <davejplater@gmail.com> --- My tumbleweed partition on my i5 generation 4 machine with 8 gigs of ram boots up without problem even after upgrading to the latest release but this generation 6 i3 with 4 gigs of ram freezes on a direct boot. Last time I booted up via runlevels it froze after I closed the lid. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c6 --- Comment #6 from Dave Plater <davejplater@gmail.com> --- Created attachment 863712 --> http://bugzilla.opensuse.org/attachment.cgi?id=863712&action=edit Phone picture of screen when frozen After I closed the laptops lid and opened it again, the mouse pointer was able to move about a centimeter before the system froze. it consistently stops at the screen in the attached image. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 Dave Plater <davejplater@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|kernel-default 6.1.0-1.1 |kernel 6.1.1 freezes before |freezes before the gui |the gui appears |appears | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c7 --- Comment #7 from Dave Plater <davejplater@gmail.com> --- Unfortunately the 6.1.1 kernel from the latest snapshot also freezes. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c8 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scott.bradnick@suse.com, | |tiwai@suse.com Flags| |needinfo?(scott.bradnick@su | |se.com) --- Comment #8 from Takashi Iwai <tiwai@suse.com> --- It's quite difficult to debug without any logs and hardware details. Please try to get the hwinfo outputs from the last working kernels, and check whether you get any relevant kernel errors in the past log at crashing. At next, make sure that the issue is reproduced without Nvidia binary-only stuff. We cannot debug it with Nvidia driver due to the obvious reason. Also, verify whether it's about the graphics driver or not; you can boot with nomodeset for testing. Last but not least, installing kdump and getting the crash dump (at least the last dmesg output) would be really helpful. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 Martin Li��ka <martin.liska@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.liska@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=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c9 --- Comment #9 from Dave Plater <davejplater@gmail.com> --- My pc with a generation 4 i5-4590 cpu doesn't freeze but my laptop with a generation 6 i3-6006U freezes. If I go to runlevel 1 and work my way up to level 5 in steps the laptop boots into kde but if I close the lid and sleep it freezes. This is a total lockout and only a long press on the power switch to switch it off succeeds. I attached the log from the laptop and a picture of the freeze up point. The only other difference between machines is the laptop has 4 gig of ram and the pc has eight. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 Frank Kr�ger <fkrueger@mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger@mailbox.org -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c10 --- Comment #10 from Markus Ko�mann <markus.kossmann@gmx.de> --- I'am suffering from the same problem on a Dell XPS15 (2018) with tumbleweed current (20221227). When booted with 6.0.12 inxi -G reports : Graphics: Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] driver: i915 v: kernel Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: N/A Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo Display: server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5 driver: X: loaded: modesetting dri: iris gpu: i915 resolution: 3840x2160~60Hz API: OpenGL v: 4.6 Mesa 22.2.4 renderer: Mesa Intel UHD Graphics 630 (CFL GT2) The Nvidia graphics is disabled. "prime-select get-status" reports: Driver configured: intel [bbswitch] NVIDIA card is OFF So the problem is probably not the nvidia driver I have installed kdump, but I haven't managed to get a dump yet. There is no automatic dump when the system freezes with 6.1.1. How to generate the crashdump ? @Scott Bradnick: What does "prime-select get-status" report on your second system with 6.0.12 ? Is the Intel graphics still active when using the nvidia card ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c11 --- Comment #11 from Scott Bradnick <scott.bradnick@suse.com> --- (In reply to Markus Ko�mann from comment #10)
@Scott Bradnick: What does "prime-select get-status" report on your second system with 6.0.12 ? Is the Intel graphics still active when using the nvidia card ?
I don't think the NVIDIA card has anything to do w/ it. My 1st experience with this issue was system #1 which doesn't have a dedicated graphics card. For system #2, "prime-select get-current" shows the T1000 active (as I'd normally want it to be), but I do a fun song-and-disable-it-dance with bbswitch when using the .run since I always want the NVIDIA card active and need to use secure boot [I'm not saying they're 100% related, but getting bbswitch out of the way has helped tremendously and worked for at least a dozen kernel updates (i.e. it's not any issue here)] ; but none of that comes into play here because the system isn't up long enough on 6.1.0+ to even begin to setup NVIDIA. Today there was a bbswitch update, so it's back in that default state, still froze. I've been able to boot system #1 into 6.1.1 and switch to tty4 and capture "hwinfo --all --log <some log file>" and "dmesg -T" ~ also for 6.0.12 but considering there's no "crash" in either case, I'm not sure how that will help even if I upload them. Same with crash dumps as these are hard lockups w/ no indication it'd trigger anything. I'm not arguing against providing one, just not sure I want to install/configure it for naught. On system #1 I was using 6.1.1 for 15-20min on tty4 and after about 45s-1m of logging in via lightdm on tty7 it froze. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c12 Markus Ko�mann <markus.kossmann@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markus.kossmann@gmx.de --- Comment #12 from Markus Ko�mann <markus.kossmann@gmx.de> --- My idea was that the common denominator for the problem is intel IGP in some version.From 6th gen up to at least 8th gen. Dave Platers 4th gen Intel IGP doesn't seem to be affected But that theory fails if intel IGP is completely disabled on your second system and you don't use something like PRIME Render Offload -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c13 Scott Bradnick <scott.bradnick@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(scott.bradnick@su | |se.com) | --- Comment #13 from Scott Bradnick <scott.bradnick@suse.com> --- (In reply to Markus Ko�mann from comment #12)
My idea was that the common denominator for the problem is intel IGP in some version.From 6th gen up to at least 8th gen. Dave Platers 4th gen Intel IGP doesn't seem to be affected But that theory fails if intel IGP is completely disabled on your second system and you don't use something like PRIME Render Offload
For #2, I attempt to ALWAYS use the NVIDIA dGPU; I can't say w/ 100% certainty that even though it shows this: $ prime-select get-current Driver configured: nvidia [bbswitch] NVIDIA card is ON that the iGPU is removed from the equation. Especially considering part of .run is to disable nouveau (and I'm sure that's still the case; only i915 is loaded on 6.0.12 right now since it was 'cleaned up' when the new kernel came into play). Since I'm in a funky state w/ a "new" kernel and the .run NOT being [re]run, things feel messy. I've not booted back into some other btrfs snapshot since ALL other updates w/ 6.0.12 work fine. I've added "6.0.12-1.1" to /etc/zypp/zypp.conf: multiversion.kernels = latest,latest-1,6.0.12-1.1,running I don't want to make too many off-the-wall changes when nearly everything points to something odd w/ 6.1.0+ (granted, I don't have specific evidence to back that up). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c14 --- Comment #14 from Scott Bradnick <scott.bradnick@suse.com> --- Cause I'm at the 'nothing left to lose' stage of not knowing what to do next to actually help the kernel maintainers diagnose this, I added https://build.opensuse.org/package/show/Kernel:HEAD/kernel-default as a repo and installed 6.2.0 ... having generally positive results: $ uptime && uname -r 19:24:08 up 1:55, 2 users, load average: 0.00, 0.00, 0.00 6.2.0-rc1-1.g769d7ad-default Tomorrow I'll see how the latest .run from NVIDIA works and if the 6.1.0+ series just has some upstream oddity that isn't playing nice w/ my machines. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c15 --- Comment #15 from Dave Plater <davejplater@gmail.com> --- I've no external graphics on either my laptop or pc. My PC doesn't have wifi and as my laptop seems to freeze when wifi is loaded maybe wifi is a common denominator. # hwinfo --wlan 06: PCI 200.0: 0282 WLAN controller [Created at pci.386] Unique ID: S6TQ.ssFGCi855d4 Parent ID: HnsE.ki2WjITNw07 SysFS ID: /devices/pci0000:00/0000:00:1c.5/0000:02:00.0 SysFS BusID: 0000:02:00.0 Hardware Class: network Device Name: "WLAN" Model: "Realtek RTL8723DE 802.11b/g/n PCIe Adapter" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0xd723 "RTL8723DE 802.11b/g/n PCIe Adapter" SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x8319 Driver: "rtw_8723de" Driver Modules: "rtw88_8723de" Device File: wlo1 Features: WLAN I/O Ports: 0x3000-0x30ff (rw) Memory Range: 0xb1000000-0xb100ffff (rw,non-prefetchable) IRQ: 128 (no events) HW Address: 76:9e:09:f9:ba:3c Permanent HW Address: 5c:ea:1d:43:d9:15 Link detected: no WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v000010ECd0000D723sv0000103Csd00008319bc02sc80i00" Driver Info #0: Driver Status: rtw88_8723de is active Driver Activation Cmd: "modprobe rtw88_8723de" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #8 (PCI bridge) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c16 --- Comment #16 from Dave Plater <davejplater@gmail.com> --- If I boot into the 6.1.1 kernel via runlevel 1, 3 then 5 for the gui and unload the rtw88_8723de module I am able to close the laptop's lid to sleep but with the module present the laptop doesn't recover from sleep. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c17 --- Comment #17 from Dave Plater <davejplater@gmail.com> --- These messages, along with other wlan errors aren't present when booting the 6.0.12 kernel: Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: failed to poll offset=0x6 mask=0x2 value=0x2 Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: mac power on failed Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: failed to power on mac Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: leave idle state failed Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: failed to leave ips state Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: failed to leave idle state Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S1 TX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S1 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S1 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S1 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL update_postmaps[1716]: chmod: cannot access '/etc/postfix/relocated.': No such file or directory Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S1 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL update_postmaps[1717]: postmap: fatal: config variable inet_interfaces: host not found: localhost Dec 27 11:00:51 ArbuthnotL postfix/postmap[1717]: fatal: config variable inet_interfaces: host not found: localhost Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S0 TX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S0 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S0 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S0 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S0 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S1 TX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S1 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S1 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S1 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S1 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S0 TX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S0 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S0 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S0 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: S0 RX IQK isn't done Dec 27 11:00:51 ArbuthnotL kernel: wlo1: send auth to 0c:70:4a:d5:92:a0 (try 1/3) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c18 --- Comment #18 from Markus Ko�mann <markus.kossmann@gmx.de> --- Created attachment 863737 --> http://bugzilla.opensuse.org/attachment.cgi?id=863737&action=edit boot.log -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c19 --- Comment #19 from Markus Ko�mann <markus.kossmann@gmx.de> --- Created attachment 863738 --> http://bugzilla.opensuse.org/attachment.cgi?id=863738&action=edit rotated older boot.log My system logs to /var/log/boot.log and /var/log/messages. When the system crashed logging to /var/log/messages wasn't started yet. So there is only boot.log. Unfortunately there seems to be not much useful information in boot.log. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c20 --- Comment #20 from Markus Ko�mann <markus.kossmann@gmx.de> --- My laptop has different WLAN : Atheros QCA 6174 using the ath10k driver -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c21 --- Comment #21 from Takashi Iwai <tiwai@suse.com> --- I guess there are several different issues, casually showing the similar end effect "desktop frozen". After figuring out the cause, we should open a different bug report. In anyway, can anyone test whether the issue is related with the (i915) graphics driver? Have anyone checked with nomodeset boot option? Or maybe better with i915.modeset=0 option? And, as requested in comment 8, please give the outputs of hwinfo on the affected machines, taken from the working kernel. Also the dmesg outputs from the working kernel would be helpful, too. After getting the information of the working state, let's try to get the logs from the broken state. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c22 --- Comment #22 from Scott Bradnick <scott.bradnick@suse.com> --- (In reply to Takashi Iwai from comment #21)
In anyway, can anyone test whether the issue is related with the (i915) graphics driver? Have anyone checked with nomodeset boot option? Or maybe better with i915.modeset=0 option?
I've tried that, made no difference. This seems to be a network related catalyst vs. graphics. And unless there's an alternative to i915 for the onchip iGPU, I can't really disable it.
And, as requested in comment 8, please give the outputs of hwinfo on the affected machines, taken from the working kernel. Also the dmesg outputs from the working kernel would be helpful, too.
After getting the information of the working state, let's try to get the logs from the broken state.
I agree w/ others that this seems related to or pointing at network interaction and manifests itself in a graphics lockup - no clue why. Just focusing on system #1 - I installed/booted 6.2~rc1-1.1.g769d7ad from Kernel:HEAD and experienced the same lockup where I can boot to a login screen, even login to a tty and sit there for extended time but as soon as I login via lightdm on tty7 I get a hard lock w/in 45-60s (if not quicker). So I decided to blacklist the r8169 module (for the dual 2.5GbE ports) and unplug the USB Wifi adapter: $ inxi --network Network: Device-1: Realtek RTL8125 2.5GbE driver: N/A Device-2: Realtek RTL8125 2.5GbE driver: N/A Device-3: NetGear A6210 type: USB driver: mt76x2u And it was up for 2 hours (and a few screensaver locks and monitor poweroffs) w/o issue, other than what's a computer in 202X w/o internet access good for? But plugging the NetGear device back in and logging in via lightdm caused it to hard lock w/in 30-60s (again, I'm not sure how long it's taking but it's not immediate and it's well under 5m). I ran dmesg before the hard lock and all it showed between the ~40s of initial boot messages and the ~2h later output was the fact that I plugged in the NetGear device. Here's some output from hwinfo [--netcard,--network]: "--netcard": 42: USB 00.0: 0282 WLAN controller [Created at usb.122] Unique ID: <snip> Parent ID: <snip> SysFS ID: /devices/pci0000:00/0000:00:15.0/usb2/2-2/2-2:1.0 SysFS BusID: 2-2:1.0 Hardware Class: network Model: "NetGear A6210" Hotplug: USB Vendor: usb 0x0846 "NetGear, Inc." Device: usb 0x9053 "A6210" Revision: "1.00" Serial ID: "100" Driver: "mt76x2u" Driver Modules: "mt76x2u" Device File: wlp0s21f0u2 Features: WLAN HW Address: <snip> Permanent HW Address: <snip> Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7 5.72 5.745 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "usb:v0846p9053d0100dc00dsc00dp00icFFiscFFipFFin00" Driver Info #0: Driver Status: mt76x2u is active Driver Activation Cmd: "modprobe mt76x2u" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #56 (Hub) "--network": 54: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: _hed.ndpeucax6V1 Parent ID: hSuP.geLYROERbfC SysFS ID: /class/net/wlp0s21f0u2 SysFS Device Link: /devices/pci0000:00/0000:00:15.0/usb2/2-2/2-2:1.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "mt76x2u" Driver Modules: "mt76x2u" Device File: wlp0s21f0u2 HW Address: <snip> Permanent HW Address: <snip> Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #35 (Ethernet controller) As for system #2, it's been happy on 6.2~rc1-1.1.g769d7ad for the last 8hrs, but it runs a "Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi" wireless card and has no onboard Ethernet port(s) - those are on the Dell dock, which I rarely use and cause MANY entries in dmesg (or somewhere similar months ago) to the point where I'd blacklisted the driver for those ports so on the rare occasion I did use the dock, it wasn't flooded with the messages. I'm going to use prime-select to switch to intel and see if the same thing happens on #2 that's happening on #1. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c23 --- Comment #23 from Frank Kr�ger <fkrueger@mailbox.org> --- (In reply to Scott Bradnick from comment #22)
(In reply to Takashi Iwai from comment #21)
In anyway, can anyone test whether the issue is related with the (i915) graphics driver? Have anyone checked with nomodeset boot option? Or maybe better with i915.modeset=0 option?
I've tried that, made no difference. This seems to be a network related catalyst vs. graphics. And unless there's an alternative to i915 for the onchip iGPU, I can't really disable it.
And, as requested in comment 8, please give the outputs of hwinfo on the affected machines, taken from the working kernel. Also the dmesg outputs from the working kernel would be helpful, too.
After getting the information of the working state, let's try to get the logs from the broken state.
I agree w/ others that this seems related to or pointing at network interaction and manifests itself in a graphics lockup - no clue why.
Just focusing on system #1 - I installed/booted 6.2~rc1-1.1.g769d7ad from Kernel:HEAD and experienced the same lockup where I can boot to a login screen, even login to a tty and sit there for extended time but as soon as I login via lightdm on tty7 I get a hard lock w/in 45-60s (if not quicker).
So I decided to blacklist the r8169 module (for the dual 2.5GbE ports) and unplug the USB Wifi adapter:
$ inxi --network Network: Device-1: Realtek RTL8125 2.5GbE driver: N/A Device-2: Realtek RTL8125 2.5GbE driver: N/A Device-3: NetGear A6210 type: USB driver: mt76x2u
And it was up for 2 hours (and a few screensaver locks and monitor poweroffs) w/o issue, other than what's a computer in 202X w/o internet access good for? But plugging the NetGear device back in and logging in via lightdm caused it to hard lock w/in 30-60s (again, I'm not sure how long it's taking but it's not immediate and it's well under 5m). I ran dmesg before the hard lock and all it showed between the ~40s of initial boot messages and the ~2h later output was the fact that I plugged in the NetGear device.
As stated in comment 21, it seems that there are several different issues involved here. As for your system #1 and the USB NetGear Wifi issue, this might be related to https://lore.kernel.org/lkml/35c73172-4e06-3877-56bd-133f9192adc3@leemhuis.i... (see also https://bugzilla.kernel.org/show_bug.cgi?id=216839). Hope this helps. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c24 --- Comment #24 from Scott Bradnick <scott.bradnick@suse.com> --- (In reply to Frank Kr�ger from comment #23)
As stated in comment 21, it seems that there are several different issues involved here. As for your system #1 and the USB NetGear Wifi issue, this might be related to https://lore.kernel.org/lkml/35c73172-4e06-3877-56bd-133f9192adc3@leemhuis. info/ (see also https://bugzilla.kernel.org/show_bug.cgi?id=216839). Hope this helps.
Sure :) It's never a simple "that's it" lone item. There's really little h/w similarities between system #1 and #2 that I just find it odd they both hard lock. Seems #2 works just fine on 6.2 w/ the intel iGPU and iwlwifi driver ; still locks up on 6.1.1 ... If I blacklist iwlwifi and reboot to 6.1.1, it locks as well. Even if I disable the WLAN/Bluetooth devices from the BIOS it still locks up. Boots fine on 6.2 but there's no wifi device, so it's staying on 6.2 w/ WLAN/Bluetooth enabled for the time being; will save the NVIDIA .run file on 6.2 for another day. Those kernel.org links do seem to echo my problem, esp. w/ system #1. I'm not sure how to [easily] track the patching of net/mac80211/rx.c into something like Kernel:HEAD or Kernel:stable, so I'll need to do some more digging. #1 will stay on 6.0.12 until [hopefully] that patch resolves it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c25 --- Comment #25 from Frank Kr�ger <fkrueger@mailbox.org> --- (In reply to Scott Bradnick from comment #24)
(In reply to Frank Kr�ger from comment #23)
As stated in comment 21, it seems that there are several different issues involved here. As for your system #1 and the USB NetGear Wifi issue, this might be related to https://lore.kernel.org/lkml/35c73172-4e06-3877-56bd-133f9192adc3@leemhuis. info/ (see also https://bugzilla.kernel.org/show_bug.cgi?id=216839). Hope this helps.
...
Those kernel.org links do seem to echo my problem, esp. w/ system #1. I'm not sure how to [easily] track the patching of net/mac80211/rx.c into something like Kernel:HEAD or Kernel:stable, so I'll need to do some more digging. #1 will stay on 6.0.12 until [hopefully] that patch resolves it.
Hopefully Takashi Iwai will provide a test kernel with either the patch or the reverted commit as described here: https://lore.kernel.org/lkml/35c73172-4e06-3877-56bd-133f9192adc3@leemhuis.i... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c26 --- Comment #26 from Dave Plater <davejplater@gmail.com> --- Still following the trial and error path, I noticed that network manager appeared to be a common denominator. I changed to wicked via yast and booted kernel 6.1.1 and the laptop boots and runs as if it had a 6.0.12 kernel. Next I'll try changing my pc to network manager to prove if it is definitely network manager / kernel interaction. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c27 --- Comment #27 from Dave Plater <davejplater@gmail.com> --- the 4th gen pc boots with a network manager managed network -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c28 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #28 from Takashi Iwai <tiwai@suse.com> --- (In reply to Frank Kr�ger from comment #25)
Hopefully Takashi Iwai will provide a test kernel with either the patch or the reverted commit as described here: https://lore.kernel.org/lkml/35c73172-4e06-3877-56bd-133f9192adc3@leemhuis. info/
It's being built in OBS home:tiwai:bsc1206683 repo. Give it a try once after it finishes (and succeeds) the build. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c29 --- Comment #29 from Dave Plater <davejplater@gmail.com> --- Created attachment 863746 --> http://bugzilla.opensuse.org/attachment.cgi?id=863746&action=edit journalctl -r > journal-nonm-6.1.1.txt This log is from laptop which booted kernel 6.1.1 without network manager and the point where i switched back to network manager. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c31 --- Comment #31 from Scott Bradnick <scott.bradnick@suse.com> --- Installed 6.1.1-1.g081acb5-default on system #2 (the Dell with a i7-9850H and a wifi card using iwlwifi) and it's behaving as well -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c32 --- Comment #32 from Dave Plater <davejplater@gmail.com> --- Looks like I'm the odd one out. Neither kernel-default-6.1.1-1.1.g081acb5 or kernel-default-6.2~rc1-1.1.g769d7ad are able to boot past the wifi startup stage when using network manager. This includes not booting as far as runlevel 3 without going via runlevel 1 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c33 Hendrik Woltersdorf <hendrikw@arcor.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hendrikw@arcor.de --- Comment #33 from Hendrik Woltersdorf <hendrikw@arcor.de> --- Just for the records: I have the same problem with an AMD system: CPU: 6-core AMD Ryzen 5 5600G with Radeon Graphics (-MT MCP-) speed/min/max: 2025/1400/4464 MHz Kernel: 6.1.1-1.g081acb5-default x86_64 Up: 0h 1m Mem: 2361.0/15281.3 MiB (15.5%) Storage: 2.73 TiB (30.1% used) Procs: 367 Shell: Bash inxi: 3.3.23 Graphics: Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series] driver: amdgpu v: kernel Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: radeonsi gpu: amdgpu resolution: 2560x1440~60Hz API: OpenGL v: 4.6 Mesa 22.2.4 renderer: AMD Radeon Graphics (renoir LLVM 15.0.5 DRM 3.49 6.1.1-1.g081acb5-default) Network: Device-1: Realtek RTL8125 2.5GbE driver: r8169 But the kernel from Takashis repo works for me. If someone wants more info about my hardware, system logs etc., just ping me. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c34 Dave Plater <davejplater@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(tiwai@suse.com) --- Comment #34 from Dave Plater <davejplater@gmail.com> --- Created attachment 863752 --> http://bugzilla.opensuse.org/attachment.cgi?id=863752&action=edit Hardware information from HP 15-bs0xx With Wifi enabled my HP laptop with the latest tumbleweed snapshot locks up on wifi load on the 6.1.0, 6.1.1, Takashi's kernel from his home repo and 6.2.rc2 from Kernal:Head. If I switch to wicked network management or even disable wifi in the kde network management applet I can boot successfully with any of the above kernels Should I open a fresh bug? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c35 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?, | |needinfo?(tiwai@suse.com) | --- Comment #35 from Takashi Iwai <tiwai@suse.com> --- If my test kernel doesn't work for you, it's likely a different bug, and it's worth to open another report. As the fix seems working for the original report, I'm going to send a PR to TW kernel (stable branch). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c36 --- Comment #36 from Dave Plater <davejplater@gmail.com> --- (In reply to Takashi Iwai from comment #35)
If my test kernel doesn't work for you, it's likely a different bug, and it's worth to open another report.
As the fix seems working for the original report, I'm going to send a PR to TW kernel (stable branch).
My problem is the kernel freezes when wifi is started by network manager. I've managed to get a blip from the 6.1.1 debug kernel, I'll attach the screenshot but there's a big hole in messages at the time the boot was taking place. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c37 --- Comment #37 from Dave Plater <davejplater@gmail.com> --- Created attachment 863754 --> http://bugzilla.opensuse.org/attachment.cgi?id=863754&action=edit Screen picture of point of freeze -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c38 --- Comment #38 from Dave Plater <davejplater@gmail.com> --- Extracted from Comment 22 This is identical to my problem but with an internal usb wifi/bluetooth : I agree w/ others that this seems related to or pointing at network interaction and manifests itself in a graphics lockup - no clue why. Just focusing on system #1 - I installed/booted 6.2~rc1-1.1.g769d7ad from Kernel:HEAD and experienced the same lockup where I can boot to a login screen, even login to a tty and sit there for extended time but as soon as I login via lightdm on tty7 I get a hard lock w/in 45-60s (if not quicker). So I decided to blacklist the r8169 module (for the dual 2.5GbE ports) and unplug the USB Wifi adapter: $ inxi --network Network: Device-1: Realtek RTL8125 2.5GbE driver: N/A Device-2: Realtek RTL8125 2.5GbE driver: N/A Device-3: NetGear A6210 type: USB driver: mt76x2u And it was up for 2 hours (and a few screensaver locks and monitor poweroffs) w/o issue, other than what's a computer in 202X w/o internet access good for? But plugging the NetGear device back in and logging in via lightdm caused it to hard lock w/in 30-60s (again, I'm not sure how long it's taking but it's not immediate and it's well under 5m). I ran dmesg before the hard lock and all it showed between the ~40s of initial boot messages and the ~2h later output was the fact that I plugged in the NetGear device. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c39 Larry Finger <Larry.Finger@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Larry.Finger@gmail.com --- Comment #39 from Larry Finger <Larry.Finger@gmail.com> --- (In reply to Dave Plater from comment #15)
I've no external graphics on either my laptop or pc.
My PC doesn't have wifi and as my laptop seems to freeze when wifi is loaded maybe wifi is a common denominator. # hwinfo --wlan 06: PCI 200.0: 0282 WLAN controller [Created at pci.386] Unique ID: S6TQ.ssFGCi855d4 Parent ID: HnsE.ki2WjITNw07 SysFS ID: /devices/pci0000:00/0000:00:1c.5/0000:02:00.0 SysFS BusID: 0000:02:00.0 Hardware Class: network Device Name: "WLAN" Model: "Realtek RTL8723DE 802.11b/g/n PCIe Adapter" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0xd723 "RTL8723DE 802.11b/g/n PCIe Adapter" SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x8319 Driver: "rtw_8723de" Driver Modules: "rtw88_8723de" Device File: wlo1 Features: WLAN I/O Ports: 0x3000-0x30ff (rw) Memory Range: 0xb1000000-0xb100ffff (rw,non-prefetchable) IRQ: 128 (no events) HW Address: 76:9e:09:f9:ba:3c Permanent HW Address: 5c:ea:1d:43:d9:15 Link detected: no WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v000010ECd0000D723sv0000103Csd00008319bc02sc80i00" Driver Info #0: Driver Status: rtw88_8723de is active Driver Activation Cmd: "modprobe rtw88_8723de" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #8 (PCI bridge)
(In reply to Dave Plater from comment #17)
These messages, along with other wlan errors aren't present when booting the 6.0.12 kernel: Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: failed to poll offset=0x6 mask=0x2 value=0x2 Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: mac power on failed Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: failed to power on mac Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: leave idle state failed Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: failed to leave ips state Dec 27 11:00:51 ArbuthnotL kernel: rtw_8723de 0000:02:00.0: failed to leave idle state
With the rtw88 driver, there have been problems with HP and Lenovo BIOS coding. Some users have found improvements with use of these two options for rtw88_core (if using the in-kernel version), or rtw_core (if using the external module package). Use 'lsmod | grep rtw' to determine which you are using: parm: disable_lps_deep:Set Y to disable Deep PS (bool) parm: support_bf:Set Y to enable beamformee support (bool) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c40 --- Comment #40 from Dave Plater <davejplater@gmail.com> --- (In reply to Larry Finger from comment #39)
With the rtw88 driver, there have been problems with HP and Lenovo BIOS coding. Some users have found improvements with use of these two options for rtw88_core (if using the in-kernel version), or rtw_core (if using the external module package). Use 'lsmod | grep rtw' to determine which you are using:
parm: disable_lps_deep:Set Y to disable Deep PS (bool) parm: support_bf:Set Y to enable beamformee support (bool)
I've reinstated home:plater/rtw88 and updated to the latest git revision 51c88888f72248f4cf266ca177cb4195af0338bc. In this state with no rtw_8723de module loaded I can boot and leave sleep mode with no lockup: # lsmod |grep rtw rtw_8723d 61440 0 rtw_pci 36864 0 rtw_core 282624 2 rtw_8723d,rtw_pci mac80211 1302528 2 rtw_core,rtw_pci cfg80211 1118208 2 rtw_core,mac80211 but with rtw_8723de active I get the freeze either on boot or after waking from sleep. This is with rtw88 built against Tiwai's kernel and Tiwai's kernel running. If I activate rtw_8723de, I get wifi and the laptop works fine as long as it's not shut down or doesn't enter sleep. I have: # cat /etc/modprobe.d/50-rtw_core.conf options disable_lps_deep:Set Y to disable Deep PS (bool) options support_bf:Set Y to enable beamformee support (bool) which results in : # modinfo rtw_core filename: /lib/modules/6.1.1-2-default/updates/rtw_core.ko license: Dual BSD/GPL description: Realtek 802.11ac wireless core module author: Realtek Corporation suserelease: openSUSE Tumbleweed srcversion: C8DCD276721114ED47337E6 depends: mac80211,cfg80211 retpoline: Y name: rtw_core vermagic: 6.1.1-2-default SMP preempt mod_unload modversions sig_id: PKCS#7 signer: home:plater OBS Project sig_key: A6:AE:BD:2E:50:3E:C7:76 sig_hashalgo: sha256 signature: 03:84:82:6E:67:08:9D:1B:F7:2C:53:75:23:AC:02:2B:AA:D7:EA:FD: 40:44:33:BA:40:CD:21:33:4E:F3:6F:75:F4:1E:0D:75:CD:61:01:D1: AC:2C:99:BD:F2:14:42:3D:A0:4D:20:BA:94:CE:97:82:9E:7D:E4:7B: 17:EF:04:65:AB:7E:87:51:F8:48:1C:15:13:AB:63:7B:8F:95:E1:FC: 1F:C6:12:D5:55:07:57:6D:F7:A1:64:FE:F6:43:51:FC:C9:09:28:4C: EC:D2:0E:34:E0:64:E4:B9:85:8F:49:74:B2:BB:B5:2F:00:97:1F:83: D5:FD:C0:61:15:86:D1:50:CB:BE:D7:25:1E:91:07:06:C3:69:9C:74: B4:24:EE:67:F6:85:85:11:5B:EB:DD:B0:7B:89:92:59:9D:A1:F9:0E: D7:AB:36:85:AC:D2:36:36:5B:F7:C4:DB:D0:74:EA:BF:DB:A6:08:D6: 13:48:08:37:8E:99:FF:81:65:7B:80:3A:1D:F1:98:1F:77:26:D4:D8: 64:DE:AF:F0:AF:1F:75:19:AD:F8:B2:5A:E1:EA:95:D9:5B:BD:BE:15: E1:B0:F6:4B:ED:B0:7D:BC:03:DF:89:BA:67:7F:65:DE:B8:F5:AB:7A: F5:22:2F:A7:E7:FD:9C:1F:BF:47:91:AD:DD:FE:15:93 parm: disable_lps_deep:Set Y to disable Deep PS (bool) parm: support_bf:Set Y to enable beamformee support (bool) parm: debug_mask:Debugging mask (uint) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c41 --- Comment #41 from Dave Plater <davejplater@gmail.com> --- I've opened Bug 1206767 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com