ei_tx_err(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ei_tx_err(9) β€” like, the kernel API manual, but make it make sense

okay so bestie, welcome to the Kernel API Manual entry for ei_tx_err β€” yes that's the manual name, we're not copying the whole header line, we're being cute about it πŸŽ€


✨ NAME ✨

ei_tx_err β€” handle transmitter error 🫢

🌸 SYNOPSIS 🌸

void ei_tx_err (struct net_device *dev );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the network device which threw the exception πŸ’€ like, this is the card that's having a moment

πŸ’– DESCRIPTION πŸ’–

so picture this: a transmitter error has happened. iconic of it, honestly. most likely it's excess collisions, which β€” fun fact β€” is a fairly normal condition, so don't panic, it's giving "this is fine" πŸ”₯

but here's the slay part: if the error is one where the Tx will have been aborted, we try and send another one right away, instead of letting the failed packet sit and collect dust in the Tx buffer 😭 like ma'am, we are not leaving you on read in there

this is a much better solution, no cap, because it avoids:

  • kernel based Tx timeouts ⏰
  • an unnecessary card reset πŸ™ˆ
lowkey important: called with lock held πŸ”’ don't forget or it's gonna be a whole thing

πŸ‘‘ SEE ALSO πŸ‘‘

go read those too, iykyk πŸ’…


and that's the vibe check, bestie β€” this page lives at ./drivers/net/ethernet/8390, dated October 2026, and it's literally called ei_tx_err(9) in case you forgot already πŸŒˆβœ¨πŸ’œ

πŸ“¦ where this page comes from