John W. Linville wrote: > Obviously it is between you and Dave to decide what is best. We are > carrying this patch in RHEL4 at the moment, so I didn't want to hold > it back from upstream. If you think you have a better solution then > "it's on you"... :-) >
Since 2.6.18 already has the recovery logic in place, we can probably holdoff merging this patch upstream. If e1000 is having similar problems with a similar AMD chipset, it must be a fairly widespread problem. It might be a good idea to push this patch to -stable. - 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
