From: Paolo Abeni <pabeni@redhat.com>
To: Ian Kumlien <ian.kumlien@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
jeffrey.t.kirsher@intel.com,
Roopa Prabhu <roopa@cumulusnetworks.com>,
nikolay@cumulusnetworks.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [BUG] v4.20 - bridge not getting DHCP responses? (works in 4.19.13)
Date: Thu, 10 Jan 2019 09:08:07 +0100 [thread overview]
Message-ID: <6d6297de1fc895f8e589f9ab9140709a0874cbfd.camel@redhat.com> (raw)
In-Reply-To: <CAA85sZtG4cQd5-SrhZWJ-4wXx5f=0b=C0=_Yc0p1Tvxwpg6Oxw@mail.gmail.com>
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.kumlien@gmail.com> wrote:
> > On Wed, Jan 9, 2019 at 12:17 AM Ian Kumlien <ian.kumlien@gmail.com> wrote:
> > > On Wed, Jan 9, 2019, 00:09 Florian Fainelli <f.fainelli@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 <edumazet@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
prev parent reply other threads:[~2019-01-10 8:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 21:26 Ian Kumlien
2019-01-06 22:21 ` Fwd: " Ian Kumlien
2019-01-08 22:10 ` Ian Kumlien
2019-01-08 22:51 ` Stephen Hemminger
2019-01-08 23:00 ` Ian Kumlien
2019-01-08 23:09 ` Florian Fainelli
[not found] ` <CAA85sZvVHCYFRXp5cYzSDNpesNMtCZOB+Gnb+N+SmraD6eke1A@mail.gmail.com>
2019-01-10 0:16 ` Ian Kumlien
2019-01-10 0:38 ` Ian Kumlien
2019-01-10 8:08 ` Paolo Abeni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6d6297de1fc895f8e589f9ab9140709a0874cbfd.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=f.fainelli@gmail.com \
--cc=ian.kumlien@gmail.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®