From: Richard Laager <rlaager@wiktel.com>
To: netdev@vger.kernel.org
Subject: Re: Fw: [Bug 82471] New: net/core/dev.c skb_war_bad_offload
Date: Wed, 31 Dec 2014 00:51:55 -0600 [thread overview]
Message-ID: <1420008715.4687.79.camel@watermelon.coderich.net> (raw)
In-Reply-To: <1418805852.5277.25.camel@watermelon.coderich.net>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
I was able to do some bisection using Ubuntu-packaged kernels.
The kernel from Precise (3.2.0-74.109) works (on a Trusty system).
On 3.5.0-51-generic (3.5.0-51.76) from Quantal, I get a different kind
of brokenness. I don't get a stack dump, but I get this kernel message
printed:
skbuff: bond0.7: received packets cannot be forwarded while LRO is enabled
The kernels from Raring (3.8.0-35.50) and Saucy (3.11.0-26.45) are
broken in the same way as Trusty.
Does that skbuff error message provide any clue? If not, it seems that
I'll have to bisect from working-on-3.2 to broken-on-3.5, then revert
that offending commit in each test as I bisect again from 3.5 to 3.8?
--
Richard
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-12-31 6:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 8:44 Fw: [Bug 82471] New: net/core/dev.c skb_war_bad_offload Richard Laager
2014-12-17 9:55 ` Michal Kubecek
2014-12-17 14:52 ` Richard Laager
2014-12-31 6:51 ` Richard Laager [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-15 21:26 Stephen Hemminger
2014-11-04 21:59 ` Jesse Brandeburg
2014-11-04 22:57 ` Tom Herbert
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=1420008715.4687.79.camel@watermelon.coderich.net \
--to=rlaager@wiktel.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).