From: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, jeffrey.t.kirsher@intel.com,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Bruce Allan <bruce.w.allan@intel.com>,
Alex Duyck <alexander.h.duyck@intel.com>
Subject: Re: 2.6.34.1, e1000e, VLAN's and kernel BUG
Date: Wed, 21 Jul 2010 17:38:07 +0300 [thread overview]
Message-ID: <201007211738.07605.nuclearcat@nuclearcat.com> (raw)
In-Reply-To: <1279722611.2452.49.camel@edumazet-laptop>
On Wednesday 21 July 2010 17:30:11 Eric Dumazet wrote:
> >
> > 66 89 41 7a <83> 3b 00 0f 84 a0 00 00 00 8d 7b 5c 89 f8 e8 5c de 05 00
> > f6 43
> >
> > --
>
> You might need patch provided by commit b0f77d0eae0c58a5a
>
> http://git2.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;
> h=b0f77d0eae0c58a5a
Thanks, i will try it.
prev parent reply other threads:[~2010-07-21 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 14:03 2.6.34.1, e1000e, VLAN's and kernel BUG Denys Fedoryshchenko
2010-07-21 14:30 ` Eric Dumazet
2010-07-21 14:38 ` Denys Fedoryshchenko [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=201007211738.07605.nuclearcat@nuclearcat.com \
--to=nuclearcat@nuclearcat.com \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=eric.dumazet@gmail.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.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).