Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#1467 - ieee80211_tx_status: headroom too small #6432

Open
openwrt-bot opened this issue Apr 2, 2018 · 1 comment
Open

FS#1467 - ieee80211_tx_status: headroom too small #6432

openwrt-bot opened this issue Apr 2, 2018 · 1 comment
Labels
flyspray kernel

Comments

@openwrt-bot
Copy link

@openwrt-bot openwrt-bot commented Apr 2, 2018

enrique.rodriguez:

Latest LEDE on Gateworks Newport GW6300 (octeontx) with Compex WLE900VX ath10k radio. Using 4.14.13 mainline OpenWrt kernel

The syslog is getting spammed with "headroom too small" errors when a monitor wireless interface exists and a station gets connected:

Thu Jan 1 00:52:00 1970 kern.err kernel: [ 157.740108] ieee80211_tx_status: headroom too small Thu Jan 1 00:52:01 1970 kern.err kernel: [ 158.764099] ieee80211_tx_status: headroom too small Thu Jan 1 00:52:02 1970 kern.err kernel: [ 159.788129] ieee80211_tx_status: headroom too small

These errors are shown using ath10k and ath10k-ct driver versions (currently using ath10k-ct)

Steps to reproduce:

  • Create a new monitor wireless interfaceiw phy phy0 interface add mon0 type monitor
    ip l set dev mon0 up
  • Connect a client to the access point configured radio

Full logread info attached separately

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented May 3, 2018

enrique.rodriguez:

I've detected that the error only happens when using 4.14 kernel and an ath10k radio that is part of a bridge. This is an example brctl output where wlan0 and wlan1 are inside br-lan bridge:

root@LEDE:~# brctl show
bridge name bridge id STP enabled interfaces
br-lan 9000.04f021132a4a no eth0.1
eth0.2
wlan0

If the wireless interface is not part of a bridge, it works correctly and no errors are shown.

Maybe this is a kernel related issue?

@aparcar aparcar added the kernel label Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray kernel
Projects
None yet
Development

No branches or pull requests

2 participants