6.1.0-rpi6-rpi-v8: oops when starting netconsole: netpoll_send_skb_on_dev(): wlan0 enabled interrupts in poll (brcmf_netdev_start_xmit+0x0/0x39c [brcmfmac])

Open
#5,767 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, linux

Research direction

Start with the warning in net/core/netpoll.c and the brcmf_netdev_start_xmit entry point named in the log. Reproduce the issue using the provided modprobe netconsole command on a Raspberry Pi 4 connected through wlan0, then inspect the attached dmesg output. Done means netconsole starts without the enabled-interrupts warning or resulting oops.

Written by the indexing model from the issue text.

Description

Describe the bug

Oops when loading netconsole module

Steps to reproduce the behaviour

raspberry pi 4 connected to lan via wifi, then on console:

modprobe netconsole netconsole=@/wlan0,514@192.168.68.249/

[   19.537100] netpoll_send_skb_on_dev(): wlan0 enabled interrupts in poll (brcmf_netdev_start_xmit+0x0/0x39c [brcmfmac])
[   19.537195] WARNING: CPU: 2 PID: 1019 at net/core/netpoll.c:370 netpoll_send_skb+0x284/0x2a0
Device (s)

Raspberry Pi 4 Mod. B

System
root@voron24:~# cat /etc/rpi-issue
Raspberry Pi reference 2023-10-10
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 962bf483c8f326405794827cce8c0313fd5880a8, stage4
root@voron24:~# vcgencmd version
Oct 17 2023 15:39:16
Copyright (c) 2012 Broadcom
version 30f0c5e4d076da3ab4f341d88e7d505760b93ad7 (clean) (release) (start)
root@voron24:~# uname -a
Linux voron24 6.1.0-rpi6-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.58-1+rpt2 (2023-10-27) aarch64 GNU/Linux
Logs

dmesg.txt

Additional context

No response

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.