[Bug 1195405] New: Kernel backtrace on wifi after latest upgrade
http://bugzilla.opensuse.org/show_bug.cgi?id=1195405 Bug ID: 1195405 Summary: Kernel backtrace on wifi after latest upgrade Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: cy6erGn0m@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 855776 --> http://bugzilla.opensuse.org/attachment.cgi?id=855776&action=edit Complete dmesg After the latest major Tumbleweed upgrade, wifi stopped working and I see the following backtrace in the kernel log (fortunately, it boots up successfully). [ 6.384503] NET: Registered PF_ALG protocol family [ 6.797490] irq 16: nobody cared (try booting with the "irqpoll" option) [ 6.797495] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 5.16.2-1-default #1 openSUSE Tumbleweed b40a195b7ff0f3399a616c3290f963c4ad189e84 [ 6.797498] Hardware name: Dell Inc. XPS 15 9550/0N7TVV, BIOS 1.14.0 02/13/2020 [ 6.797499] Call Trace: [ 6.797501] <IRQ> [ 6.797503] dump_stack_lvl+0x48/0x5e [ 6.797508] __report_bad_irq+0x35/0xa7 [ 6.797510] note_interrupt.cold+0xb/0x61 [ 6.797512] handle_irq_event+0xa3/0xb0 [ 6.797515] handle_fasteoi_irq+0x78/0x1d0 [ 6.797518] __common_interrupt+0x3e/0xa0 [ 6.797521] common_interrupt+0x7b/0xa0 [ 6.797524] </IRQ> [ 6.797524] <TASK> [ 6.797525] asm_common_interrupt+0x1e/0x40 [ 6.797528] RIP: 0010:poll_idle+0x30/0xb3 [ 6.797530] Code: 56 49 89 f6 41 55 41 89 d5 41 54 55 48 89 fd 53 65 8b 3d 9b 46 da 79 e8 ae 24 66 ff 80 65 00 fb 49 89 c4 fb 66 0f 1f 44 00 00 <65> 48 8b 1c 25 c0 1b 02 00 f0 80 4b 02 20 48 8b 03 a8 08 74 32 65 [ 6.797531] RSP: 0018:ffffa990c00f7e78 EFLAGS: 00000206 [ 6.797533] RAX: 000000019529603d RBX: 0000000000000000 RCX: 000000000000001f [ 6.797535] RDX: 0000000000000000 RSI: 000000003161efb0 RDI: fffffffd43b9ef94 [ 6.797536] RBP: ffffc990bfd00200 R08: 000000019529603d R09: 0000000000000007 [ 6.797537] R10: 0000000000000003 R11: 0000000000000001 R12: 000000019529603d [ 6.797538] R13: 0000000000000000 R14: ffffffff8765b5a0 R15: 0000000000000000 [ 6.797540] ? poll_idle+0x22/0xb3 [ 6.797542] cpuidle_enter_state+0x89/0x370 [ 6.797545] cpuidle_enter+0x29/0x40 [ 6.797547] do_idle+0x1f2/0x2a0 [ 6.797549] cpu_startup_entry+0x19/0x20 [ 6.797551] secondary_startup_64_no_verify+0xc2/0xcb [ 6.797554] </TASK> [ 6.797555] handlers: [ 6.797556] [<000000003b57416c>] i801_isr [i2c_i801] [ 6.797561] [<0000000089f1b8b1>] idma64_irq [idma64] [ 6.797564] [<0000000037a52855>] i2c_dw_isr [ 6.797567] Disabling IRQ #16 [ 11.500271] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ PRIVRING ] -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195405 http://bugzilla.opensuse.org/show_bug.cgi?id=1195405#c1 --- Comment #1 from Sergey Mashkov <cy6erGn0m@gmail.com> --- More system info Linux dhcppc0 5.16.2-1-default #1 SMP PREEMPT Mon Jan 24 18:27:48 UTC 2022 (0d710a8) x86_64 x86_64 x86_64 GNU/Linux The device is not recognized by lspci/lsusb but surprisingly bluetooth is: lsusb Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. BCM20703A1 Bluetooth 4.1 + LE -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195405 http://bugzilla.opensuse.org/show_bug.cgi?id=1195405#c2 Sergey Mashkov <cy6erGn0m@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Sergey Mashkov <cy6erGn0m@gmail.com> --- It seems that the system magically self-repaired itself. I personally believe it is something with power management so the defice was OFF for some reason and the system was unable to detect it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1195405 http://bugzilla.opensuse.org/show_bug.cgi?id=1195405#c3 --- Comment #3 from Sergey Mashkov <cy6erGn0m@gmail.com> --- Device was 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.192 latency=0 multicast=yes wireless=IEEE 802.11 resources: irq:137 memory:dd800000-dd807fff memory:dd400000-dd7fffff -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com