So should we be reporting this upstream? It's safe to assume that Canonical is not going to be doing a lot of kernel hacking in this case, right? The issue persists upstream, and 2.6.27 is nearing completion: http://kerneltrap.org/Linux/2.6.27-rc8_This_One_Should_Be_The_Last_One Where do we need to volunteer to get the ball rolling? The e1000e eeprom bug is still rearing its ugly head, but I'm guessing our warranties will cover that so we don't have a whole lot to be afraid of.
So should we be reporting this upstream? It's safe to assume that Canonical is not going to be doing a lot of kernel hacking in this case, right? The issue persists upstream, and 2.6.27 is nearing completion: http:// kerneltrap. org/Linux/ 2.6.27- rc8_This_ One_Should_ Be_The_ Last_One Where do we need to volunteer to get the ball rolling? The e1000e eeprom bug is still rearing its ugly head, but I'm guessing our warranties will cover that so we don't have a whole lot to be afraid of.