I've got a Nehalem testbox that developed a new e1000e problem in this
merge window: after a few minutes of uptime the network interface goes
dead - no rx and no tx. If i ifdown/ifup the interface it comes back. If i
wait too long then even ifdown/ifup does not help anymore - only a reboot.
-Original Message-
From: Ingo Molnar [mailto:mi...@elte.hu]
Sent: Wednesday, January 21, 2009 2:29 AM
To: linux-ker...@vger.kernel.org; Kirsher, Jeffrey T; Brandeburg, Jesse;
Allan, Bruce W; Waskiewicz Jr, Peter P; e1000-devel@lists.sourceforge.net;
net...@vger.kernel.org
Cc: Rafael J.
* Allan, Bruce W bruce.w.al...@intel.com wrote:
-Original Message-
From: Ingo Molnar [mailto:mi...@elte.hu]
Sent: Wednesday, January 21, 2009 2:29 AM
To: linux-ker...@vger.kernel.org; Kirsher, Jeffrey T; Brandeburg, Jesse;
Allan, Bruce W; Waskiewicz Jr, Peter P;
* Ingo Molnar mi...@elte.hu wrote:
One other piece of info (in addition to what Bruce requested) that
would be useful is after you've done ifconfig eht0 up, cat
/proc/interrupts | grep eth0 and send that output (I want to see your
MSI-X configuration).
here it is:
79:
Forgot to reply all...
-- Forwarded message --
From: Jonathan Fournier jonathan.fourn...@gmail.com
Date: Wed, Jan 21, 2009 at 5:14 PM
Subject: Re: [E1000-devel] Question regarding e1000 link status
To: Brandeburg, Jesse jesse.brandeb...@intel.com
Hi Jesse,
On Wed, Jan 21, 2009
On Wednesday 21 January 2009, Ingo Molnar wrote:
* Rafael J. Wysocki r...@sisk.pl wrote:
On Wednesday 21 January 2009, Ingo Molnar wrote:
* Ingo Molnar mi...@elte.hu wrote:
One other piece of info (in addition to what Bruce requested) that
would be useful is after
The code was refactored, e1000_hw.c became all the split out files you list
below.
I saw your message on netdev too, we're the only ones that ever reply to intel
related issues, it seems :-)
so what is the actual connection type on your ethernet, is it a directly
connected fiber port? Is it
Rafael J. Wysocki wrote:
On Wednesday 21 January 2009, Ingo Molnar wrote:
* Rafael J. Wysocki r...@sisk.pl wrote:
On Wednesday 21 January 2009, Ingo Molnar wrote:
* Ingo Molnar mi...@elte.hu wrote:
One other piece of info (in addition to what Bruce requested)
that would be useful is
* Rafael J. Wysocki r...@sisk.pl wrote:
On Wednesday 21 January 2009, Ingo Molnar wrote:
* Ingo Molnar mi...@elte.hu wrote:
One other piece of info (in addition to what Bruce requested) that
would be useful is after you've done ifconfig eht0 up, cat
/proc/interrupts | grep
Jonathan Fournier wrote:
so what is the actual connection type on your ethernet, is it a
directly connected fiber port? Is it a serdes blade? forgive me
I've never tested one of the ATCA platforms.
I just found out more documentation for that platform, since most ATCA
switch are
On Wed, Jan 21, 2009 at 6:10 PM, Brandeburg, Jesse
jesse.brandeb...@intel.com wrote:
Jonathan Fournier wrote:
so what is the actual connection type on your ethernet, is it a
directly connected fiber port? Is it a serdes blade? forgive me
I've never tested one of the ATCA platforms.
I just
On Wed, 21 Jan 2009 14:51:07 -0800
Duyck, Alexander H alexander.h.du...@intel.com wrote:
Rafael J. Wysocki wrote:
On Wednesday 21 January 2009, Ingo Molnar wrote:
* Rafael J. Wysocki r...@sisk.pl wrote:
On Wednesday 21 January 2009, Ingo Molnar wrote:
* Ingo Molnar mi...@elte.hu
12 matches
Mail list logo
