Scott Feldman wrote:
Was NAPI turned on for e100 in 2.6.7? If not, turn NAPI on in the 2.6.7 driver and see if you get the same result. If you do, it's very likely the bug is in the e100 driver's NAPI implementation.
looks like you are right, enabling NAPI in 2.6.7 does trigger this.
what exactly is this? i didn't enable NAPI in any of the newer kernel versions i was trying, so i'm somewhat confused. :) also, does this affect the e1000 driver in any way?
cheers richard - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
