Hi Jeff and Yanir, On Saturday, 30. May 2015 01:18:44 Brown, Aaron F wrote: > > any news on this from the Intel labs? > > Nothing significant. Another one of our testers (whom works more closely > with the current e1000e driver owner than I) has managed to replicate it > on several systems and I know the developer spent some time poking around > the setup, but I don't think he's found the root cause yet and has been > busy chasing a number of other issues.
so, any news from the Intel labs? I've seen some "hang fixes" on 03.06.2015, but I'm not sure if they are related to this issue. This problem is pretty annoying: We have a performance penalty for all network cards right now as the buffer size of the core network stack had to be decreased to 4096 bytes again on our side. (https://www.marc.info/?l=linux-netdev&m=142131668206333) Better than no e1000e network connectivity though. The initial report on this issue was on 14.01.2015: https://www.marc.info/?l=linux-netdev&m=142124954120315 Best regards, Thomas -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
