On 1/20/06, Lee Revell <[EMAIL PROTECTED]> wrote: > > Why don't these cause excessive scheduling delays in eepro100 then? > Can't we just copy the eepro100 behavior? Reports still float around from time to time about hangs with the eepro100 which go away when the e100 driver is used. We don't maintain the eepro100 driver so I can't tell you much about it other than the reports we get sometimes.
There is a timer routine in the eepro100 driver which does the check for link as well as a check for on of the hang conditions (with work-around). It does the check for link in a different way than e100. e100 uses mii call where eepro100 does it manually. Another difference is that eepro100 doesn't get stats unless called by the system. It's not in the timer routine at all. Can we try a couple of things? 1) just comment out all the check for link code in the e100 driver and give that a try and 2) just comment out the update stats call and see if that works. These seem to be the differences and we need to know which one is causing the problem. -- Cheers, John - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
