[Bug 1195857] New: System suspend stopped working because of wifi
http://bugzilla.opensuse.org/show_bug.cgi?id=1195857 Bug ID: 1195857 Summary: System suspend stopped working because of wifi Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: cy6erGn0m@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After upgrading tumbleweed, system suspend stopped working because of failing to enter PM state. dmesg excerpt: [44812.779354] brcmfmac 0000:02:00.0: brcmf_pcie_pm_enter_D3: Timeout on response for entering D3 substate [44812.779365] PM: pci_pm_suspend(): brcmf_pcie_pm_enter_D3+0x0/0x140 [brcmfmac] returns -5 [44812.779468] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -5 [44812.779486] brcmfmac 0000:02:00.0: PM: failed to suspend async: error -5 [44812.779642] PM: Some devices failed to suspend, or early wake event detected sudo lshw -C Network *-network description: Wireless interface product: BCM43602 802.11ac Wireless LAN SoC vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@0000:02:00.0 logical name: wlp2s0 version: 01 serial: 40:49:0f:fe:d3:4b width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=brcmfmac driverversion=7.35.177.61 firmware=01-ea662a8c ip=192.168.0.2 latency=0 multicast=yes wireless=IEEE 802.11 resources: irq:136 memory:dd800000-dd807fff memory:dd400000-dd7fffff More related kernel logs at the beginning: dmesg | grep brcmfmac [ 4.290886] usbcore: registered new interface driver brcmfmac [ 4.290936] brcmfmac 0000:02:00.0: enabling device (0000 -> 0002) [ 4.399941] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43602-pcie for chip BCM43602/1 [ 4.400915] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.Dell Inc.-XPS 15 9550.bin failed with error -2 [ 4.443495] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.Dell Inc.-XPS 15 9550.txt failed with error -2 [ 4.443518] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 [ 4.965032] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43602-pcie for chip BCM43602/1 [ 4.965053] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 4.965653] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43602/1 wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c locate 'brcm/brcmfmac43602' /usr/lib/firmware/brcm/brcmfmac43602-pcie.ap.bin.xz /usr/lib/firmware/brcm/brcmfmac43602-pcie.bin.xz What I don't get is why does it try to load "brcm/brcmfmac43602-pcie.Dell Inc.-XPS 15 9550.bin" that is of course missing? -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195857 http://bugzilla.opensuse.org/show_bug.cgi?id=1195857#c1 --- Comment #1 from Sergey Mashkov <cy6erGn0m@gmail.com> --- Created attachment 856100 --> http://bugzilla.opensuse.org/attachment.cgi?id=856100&action=edit Full kernel log (compressed) -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195857 http://bugzilla.opensuse.org/show_bug.cgi?id=1195857#c2 --- Comment #2 from Sergey Mashkov <cy6erGn0m@gmail.com> --- A little bit more system info System: Host: cy-machine-dell Kernel: 5.16.5-1-default x86_64 bits: 64 Console: pty pts/1 Distro: openSUSE Tumbleweed 20220207 Machine: Type: Laptop System: Dell product: XPS 15 9550 v: N/A serial: JP9LNC2 Mobo: Dell model: 0N7TVV v: A01 serial: /JP9LNC2/CN1296369H0129/ UEFI: Dell v: 1.14.0 date: 02/13/2020 Network: Device-1: Broadcom BCM43602 802.11ac Wireless LAN SoC driver: brcmfmac IF: wlp2s0 state: up mac: 40:49:0f:fe:d3:4b Bluetooth: Device-1: Broadcom BCM20703A1 Bluetooth 4.1 + LE type: USB driver: btusb Report: rfkill ID: hci0 state: up address: see --recommends Sensors: System Temperatures: cpu: 44.0 C mobo: N/A Fan Speeds (RPM): cpu: 2493 fan-2: 2506 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195857 http://bugzilla.opensuse.org/show_bug.cgi?id=1195857#c3 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cy6erGn0m@gmail.com, | |tiwai@suse.com Flags| |needinfo?(cy6erGn0m@gmail.c | |om) --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- Could you identify which previous kernel still worked and which new one doesn't? You can find the older kernels in TW history repo, too, https://download.opensuse.org/history/ About the firmware: the firmware file with the machine name is for a vendor-specific firmware. The driver tries to load it at first, then falls back to more generic firmware files. Typically used for Raspberry Pi. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195857 http://bugzilla.opensuse.org/show_bug.cgi?id=1195857#c4 --- Comment #4 from Sergey Mashkov <cy6erGn0m@gmail.com> --- Thanks for quick reply. Just tried different kernel versions and what I see: 5.16.2-1 WORKS (from here https://download.opensuse.org/history/20220201/tumbleweed/repo/oss/) 5.16.4-1 DOESN'T work 5.16.5-1 DOESN'T work I don't get where do I find 5.16.3. It seems to be missing. I see here https://download.opensuse.org/history/20220202/tumbleweed/repo/oss/x86_64/ both 2-1 and 4-1 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195857 http://bugzilla.opensuse.org/show_bug.cgi?id=1195857#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- Thanks. Unfortunately, I couldn't spot the possible fix through a quick glance between 5.16.2 and 5.16.4. There haven't been any changes in brcmfmac driver itself, for example, and PCI change doesn't seem related. The best we can do for now is to identify the breakage via git bisection. You'd need to build the kernel, install and test it by yourself. As the range is relatively narrow (between 5.16.2 and 5.16.4), it would be relatively straightforward. Also, you can reduce the kernel config at first via "make localmodconfig", which helps a lot for kernel build time reduction. In nutshell, the step is something like below: - Install git, kernel-tools, gcc, bc, libelf-devel, bison, flex, libopenssl-devel packages. - Clone linux-stable git tree % git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git - Check out v5.16.2 % cd linux-stable % git checkout v5.16.2 - Create a reduced kernel config via "make localmodconfig" % make localmodconfig Then edit .config file, modify CONFIG_LOCALVERSION to "-test", for example. - Build it % make -j8 - Install it % sudo make install Then you can boot and test with it. The v5.16.2 should be the working kernel. After confirming it's working, check out v5.16.4. % cd linux-stable % git checkout v5.16.4 Modify CONFIG_LOCALVERSION again to another suffix for avoiding conflicts. Then make, install and test with it. If v5.16.4 is confirmed to show the expected problem, then start bisection. % git bisect start % git bisect good v5.16.2 % git bisect bad v5.16.4 This will lead you to the point to test. Again, modify CONFIG_LOCALVERSION to a new suffix "e.g. bisect-1", build, install and test. If the tested kernel is OK, run "git bisect good", otherwise "git bisect bad". Repeat the step until it reaches to the culprit commit. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195857 http://bugzilla.opensuse.org/show_bug.cgi?id=1195857#c6 --- Comment #6 from Sergey Mashkov <cy6erGn0m@gmail.com> --- Sorry for delay, had to work more at my main job. The picgture actually has changed. Unfortunately, the older kernel (5.16.2-1) may also fail to suspend with the same error but it only hapens after few days and usually works perfect. With never kernels it never works even after reboot/first boot. The other issue I've faced is that I use secure boot and I don't get how to I make a key and piblish it to the keystore so my custom kernel may boot. I haven't compiled kernels almost about 10 years so could you please point me to some guide how do I set it up properly? -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195857 http://bugzilla.opensuse.org/show_bug.cgi?id=1195857#c7 --- Comment #7 from Sergey Mashkov <cy6erGn0m@gmail.com> --- This seems to be fixed in 5.17.3-1 but not before (I've tested every kernel update). -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com