On Thu, 2008-02-14 at 18:21 -0500, Andy Gospodarek wrote: > On Thu, Feb 14, 2008 at 02:48:09PM -0800, Michael Chan wrote: > > Andy, I think you still missed my point. I don't believe this problem > > was caused by the bridge or the chipset at all. Some corruption caused > > us to not find the SKB in the TX ring where it was expected. So the > > driver assumed it was the bridge re-ordering I/O and printed that > > warning message and took recovery action. The recovery action had no > > effect in this case since apparently it was caused by something else and > > the corruption happened again later. This 2nd time, we hit the BUG_ON() > > seeing that the recovery action did not work. > > > > > > Ah, I see. Due to at leat a 2 second delay between the message and the > panic, I figured it would be good data to gather.... > > > Yeah, 2 seconds for the link to come up after chip reset to recover. It then panicked sometime later and rebooted about 90 seconds after the initial warning message.
It was also running at the slower 100Mbps link speed. Tx packets stay longer in the TX ring at this slower speed, increasing the window of time that the nr_frags in the SKB can be corrupted. Ralf, please try the debug patch that I sent out earlier. Thanks. -- 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
