ei_rx_overrun(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ei_rx_overrun(9) πŸ’–

okay so bestie, welcome to the ei_rx_overrun(9) page from the Kernel API Manual β€” yes that's the whole manual name, we're not copying the line, we're just mentioning it, slay ✨


🌸 NAME 🌸

ei_rx_overrun β€” handle receiver overrun 🫢


✨ SYNOPSIS ✨

void ei_rx_overrun (struct net_device *dev );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the network device that threw the exception 😭 like, it's the one going through it, be nice to it

πŸ’… DESCRIPTION πŸ’…

So picture this: we have a receiver overrun πŸ’€ and we've gotta kick the 8390 to get it started again. Sounds easy? It is not. The problem β€” and I cannot stress this enough β€” is that you have to kick it exactly as NS prescribes in the updated datasheets, or, and I quote, "the NIC may act in an unpredictable manner." πŸ™ˆ

And it gets worse, because that includes causing "the NIC to defer indefinitely when it is stopped on a busy network." Ugh. Literally ugh. 😭

⚠️ Called with the lock held. Do not call this with interrupts off or your computer will hate you β€” it takes 10ms or so. Not kidding, 10ms is an eternity in kernel time, bestie. πŸ”₯

🌈 SEE ALSO 🌈

Kernel file ./drivers/net/ethernet/8390/lib8390.c β€” plus these icons, go read them too πŸ‘‘


and that's the whole vibe, bestie β€” this page lives in ./drivers/net/ethernet/8390 and it's stamped October 2026, so go forth and kick that 8390 exactly how NS says to πŸ’œπŸ¦‹ periodt

πŸ“¦ where this page comes from