On Mon, 2 Jul 2007 14:37:06 +0100 "Daniel J Blueman" <[EMAIL PROTECTED]> wrote:
> Hi Stephen, > > When the sky2 driver initialises, it sets the the ISR timer register > (STAT_ISR_TIMER_INI) to 125 * 20 = 2500, whereas the vendor sk98lin > driver sets it to 400, irrespective of the clockspeed of the NIC > processor. > > I guess you found more performance/stability from this value...? Not really, it was just a rough guess to try and get more frames per irq under DoS load. Haven't fine tuned those values. > > I've checked through the errata workarounds common to my rev-1 and 2 > Yukon-EC chips...the HWF_WA_DEV_4167 "oversize receive hang" > workaround checks and can reset the (as I understand) bus master unit > of the NIC (in CheckRxPath) in a periodic timer that is fired, where > is finds no progress is made. Where did you get those errata's. I keep having to do reverse engineering guessing with vendor driver. > With the issues we see, can they be detected earlier by the stats > counters not being incremented, then resetting the bus-master unit, > rather than the whole chip getting kicked after a far longer period. > > It looks like if it is a silicon bug, we can just acknowledge it and > have a better framework to detect the chip's PCI interface locking up > and kick it in a smarter way perhaps... > > Daniel > -- > Daniel J Blueman -- Stephen Hemminger <[EMAIL PROTECTED]> - 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
