From: "Alan J. Wylie" <alan@wylie.me.uk>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: e1000-devel@lists.sourceforge.net,
Linux Network Development list <netdev@vger.kernel.org>
Subject: Re: skb_pull_rcsum - Fatal exception in interrupt
Date: Mon, 20 Aug 2007 18:04:06 +0100 [thread overview]
Message-ID: <18121.51590.425883.366892@wylie.me.uk> (raw)
In-Reply-To: <36D9DB17C6DE9E40B059440DB8D95F52032A44D8@orsmsx418.amr.corp.intel.com>
On Mon, 20 Aug 2007 09:21:54 -0700, "Brandeburg, Jesse" <jesse.brandeburg@intel.com> said:
> Hi Alan, I work on the team that supports e1000, I'd be interested
> in seeing the dmesg output from the machine before it crashes, maybe
> you can add that to your web collection of data below?
Don't worry - it's definitely not an e1000 problem. I'm in contact
with the netdev guys, who have produced a patch.
Thanks anyway
Alan.
--
Alan J. Wylie http://www.wylie.me.uk/
"Perfection [in design] is achieved not when there is nothing left to add,
but rather when there is nothing left to take away."
-- Antoine de Saint-Exupery
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-08-20 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 15:07 skb_pull_rcsum - Fatal exception in interrupt Alan J. Wylie
2007-08-15 15:54 ` Evgeniy Polyakov
2007-08-20 14:24 ` Herbert Xu
2007-08-16 2:31 ` Herbert Xu
2007-08-20 16:21 ` Brandeburg, Jesse
2007-08-20 17:04 ` Alan J. Wylie [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=18121.51590.425883.366892@wylie.me.uk \
--to=alan@wylie.me.uk \
--cc=e1000-devel@lists.sourceforge.net \
--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