On Thu, 2019-01-10 at 01:38 +0100, Ian Kumlien wrote: > Confirmed, sending a new mail with summary etc > > On Thu, Jan 10, 2019 at 1:16 AM Ian Kumlien <ian.kuml...@gmail.com> wrote: > > On Wed, Jan 9, 2019 at 12:17 AM Ian Kumlien <ian.kuml...@gmail.com> wrote: > > > On Wed, Jan 9, 2019, 00:09 Florian Fainelli <f.faine...@gmail.com wrote: > > > > [--8<---] > > > > > > > when looking at "git log v4.19...v4.20 > > > > > drivers/net/ethernet/intel/ixgbe/" nothing else really stands out... > > > > > The machine is also running NAT for my home network and all of that > > > > > works just fine... > > > > > > > > > > I started with tcpdump, prooving that packets reached all the way > > > > > outside but replies never made it, reboorting > > > > > with 4.19.13 resulted in replies appearing in the tcpdump. > > > > > > > > > > I don't quite know where to look - and what can i do to test - i tried > > > > > disabling all offloading (due to the UDP > > > > > offloading changes) but nothing helped... > > > > > > > > > > Ideas? Patches? ;) > > > > > > > > Running a bisection would certainly help find the offending commit if > > > > that is something that you can do? > > > > > > I was hoping for a likely suspect but this was on my "Todo" for Friday > > > night anyway... (And I already started testing with some patches reversed) > > > > So after lengthy git bisect sections, both from the latest stable i > > was using (not the best of ideas) > > and from 4.19. > > > > The latest stable yielded 72b0094f918294e6cb8cf5c3b4520d928fbb1a57 - > > which is incorrect... > > > > However, the proper bisect gave me this: > > fb420d5d91c1274d5966917725e71f27ed092a85 is the first bad commit > > commit fb420d5d91c1274d5966917725e71f27ed092a85 > > Author: Eric Dumazet <eduma...@google.com> > > Date: Fri Sep 28 10:28:44 2018 -0700 > > > > tcp/fq: move back to CLOCK_MONOTONIC
Thank you for bisecting. Should be solve by: https://marc.info/?l=linux-netdev&m=154696956604748&w=2 Can you test with the above applied? Thanks, Paolo
