4 ms·
I wonder if this is an issue with the BSDs too. Sometimes they peek at Linux for these things.
by jmclnx 4y ago
I wonder if this is an issue with the BSDs too. Sometimes they peek at Linux for these things.
- wmf 4y agoThis is a hardware bug so I would expect it to affect all OSes. Turning off TSO is counterintuitive so drivers tend to turn it on by default.
- AdrianB1 4y agoProbably not, BSD network drivers were a bit more advanced than Linux ones as some companies (like Netflix) invested time and effort in optimizations and monitoring. I am not saying BDS is better, just a few things are quite different vs Linux.
- betaby 4y ago> a bit more advanced than Linux ones and then we look at the wifi stack in BSD(s)...
- AdrianB1 4y agoI don't think that companies like Netflix are interested in WiFi to serve massive amounts of video :)
- ilyt 4y ago> Probably not, BSD network drivers were a bit more advanced than Linux ones as some companies (like Netflix) invested time and effort in optimizations and monitoring. for those 3 nics they use. I doubt some random 2.5Gbit nic is on their list of stuff to fix
- KyleSanderson 4y agoIt isn't. It's a pure driver bug with all of these. There's a pending patch to clear the MSI registers on disconnect that I'm planning on driving to testing tomorrow. I hounded them for 4 months by sending full stacks with symbols and they don't have any hardware in the lab (which is very common now, unfortunately)... If you want to recover, set a ifdown script to `rmmod igc && modprobe igc` and you will never panic or hang, just have a longer interface bounce time. I'm running this on a 6 nic system which is completely egregious, but it hasn't crashed / hung / panic'd in the field since doing that.