From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: e1000 driver problems
Date: Mon, 03 Dec 2007 07:20:48 -0800 [thread overview]
Message-ID: <47541ED0.9090808@intel.com> (raw)
In-Reply-To: <20071203095023.GG26573@ics.muni.cz>
Lukas Hejtmanek wrote:
> On Tue, Nov 27, 2007 at 10:23:00AM -0800, Kok, Auke wrote:
>> can you see if your problem goes away with this patch?
>
> I cannot test it right now but friend of mine has the same card with 2.6.23.1
> kernel. it does not. he also tried module 7.6.12 from source fourge, your patch
> did not help. Moreover, it just hangs network connections after while. No
> message in dmesg about hangup.
can you open up a ticket on e1000.sf.net and fill in a full bugreport including
output of all of these? :
- ethttool -i eth0
- ethtool -e eth0
- lspci -vv
- full dmesg (not just the driver parts)
- dmidecode
- cat /proc/interrupts
I'd like to see if maybe we can reproduce this in our lab.
Thanks,
Auke
next prev parent reply other threads:[~2007-12-03 15:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061017205316.25914.qmail@web83109.mail.mud.yahoo.com>
[not found] ` <45354850.6050900@intel.com>
[not found] ` <20071120143803.GA5638@ics.muni.cz>
[not found] ` <474B5610.4030800@intel.com>
[not found] ` <20071127150700.GB4365@ics.muni.cz>
[not found] ` <474C4A74.90705@intel.com>
[not found] ` <20071127173146.GG4365@ics.muni.cz>
2007-11-27 17:40 ` e1000 driver problems Kok, Auke
2007-11-27 17:44 ` Lukas Hejtmanek
2007-11-27 18:23 ` Kok, Auke
2007-12-03 9:50 ` Lukas Hejtmanek
2007-12-03 15:20 ` Kok, Auke [this message]
2007-12-04 15:03 ` Lukas Hejtmanek
2007-12-04 15:34 ` Lukas Hejtmanek
2007-12-04 16:02 ` Matt Mathis
2007-12-04 17:08 ` Lukas Hejtmanek
2007-12-04 17:19 ` Kok, Auke
2007-12-04 18:05 ` Rick Jones
2007-12-04 19:59 ` Lukas Hejtmanek
2007-12-04 20:38 ` Kok, Auke
2007-12-18 11:08 ` Lukas Hejtmanek
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=47541ED0.9090808@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=netdev@vger.kernel.org \
--cc=xhejtman@ics.muni.cz \
/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).