netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Cc: "Allan, Bruce W" <bruce.w.allan@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"e1000-devel@lists.sourceforge.net"
	<e1000-devel@lists.sourceforge.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: e1000e regression (interface hang) with latest -git
Date: Wed, 21 Jan 2009 19:25:04 +0100	[thread overview]
Message-ID: <20090121182504.GA14259@elte.hu> (raw)
In-Reply-To: <Pine.WNT.4.64.0901211010250.6372@ppwaskie-MOBL2.amr.corp.intel.com>


* Waskiewicz Jr, Peter P <peter.p.waskiewicz.jr@intel.com> wrote:

> > * Ingo Molnar <mingo@elte.hu> wrote:
> > 
> > > The same point remains though: it worked before (and works fine with a 
> > > distro kernel, 2.6.28-0.140.rc9.git1.fc11.x86_64) and doesnt work with 
> > > latest -git.
> > > 
> > > I'll capture some debug data and send it to you.
> > 
> > find attached the debug data:
> > 
> >   ethtool.dump.eth0.before
> >   ethtool.dump.eth0.after
> >   ethtool.dump.eth0.after2
> >   boot.log
> >   config
> > 
> > the 'before' dump is before the hang, shortly after bootup. It also 
> > includes 'ifconfig eth0' output.
> > 
> > the 'after' dump is after the hang - while the interface is hung.
> > 
> > 'after2' dump is after a 'service network restart' - which brought the 
> > interface back.
> > 
> > Note if i wait long enough (half an hour or so), then not even 'service 
> > network restart' will bring back the device.
> > 
> > The kernel i tested is: v2.6.29-rc2-13-gf3b8436
> 
> As Bruce stated, this is an igb issue, not e1000e.  From your boot.log:

(yes, as i said it too two mails ago - it is an igb.)

> igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
> igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
> 
> 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:         35          0       9836       7451       1197       1360        766          0       2196        995        770          0       2051        863       4714       1879   PCI-MSI-edge      eth0-tx-0
 80:       2335          0       2718       3651       5024       9850        533          0       1405       1095          0          0       4421       1229          0       2002   PCI-MSI-edge      eth0-tx-1
 81:         33          0          0       5478       1125       6585       4865       6306          0          0          0        714       3757          0       2662       1020   PCI-MSI-edge      eth0-tx-2
 82:         21       1428       3136       3783       4249       6833          0          0       4175          0          0       1465       1940       1780       6286          0   PCI-MSI-edge      eth0-tx-3
 83:         40          0          0       4788          0       1486          0       7185       3998       8637       1409       6785          0          0          0      10060   PCI-MSI-edge      eth0-rx-0
 84:         70       1441       2606       1342          0       1678       4301       1839          0       6507       6910      16470          0       1484       1004          0   PCI-MSI-edge      eth0-rx-1
 85:         40       1368          0       3560       5022       2040          5       1719          0       2037        956         40          0      17264       6456       2833   PCI-MSI-edge      eth0-rx-2
 86:         44        414          5       1164         30       4513       4595       1542          0      10033       1151          0       4961       4203          0      10703   PCI-MSI-edge      eth0-rx-3
 87:          1          0          0          0          0          0          0          0          0          0          0          0          0          0          0          0   PCI-MSI-edge      eth0

	Ingo

  reply	other threads:[~2009-01-21 18:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090121102840.GA24967@elte.hu>
2009-01-21 17:35 ` e1000e regression (interface hang) with latest -git Allan, Bruce W
     [not found] ` <8DD2590731AB5D4C9DBF71A877482A900DABEA6F@orsmsx509.amr.corp.intel.com>
2009-01-21 17:51   ` Ingo Molnar
2009-01-21 18:03     ` Ingo Molnar
2009-01-21 18:12       ` Waskiewicz Jr, Peter P
2009-01-21 18:25         ` Ingo Molnar [this message]
2009-01-21 21:20           ` igb " Ingo Molnar
2009-01-21 21:34             ` Rafael J. Wysocki
2009-01-21 21:48               ` Ingo Molnar
2009-01-21 22:22                 ` Rafael J. Wysocki
2009-01-21 22:51                   ` Duyck, Alexander H
2009-01-22  0:03                     ` Stephen Hemminger
2009-01-21 10:28 e1000e " Ingo Molnar

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=20090121182504.GA14259@elte.hu \
    --to=mingo@elte.hu \
    --cc=bruce.w.allan@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.com \
    --cc=rjw@sisk.pl \
    /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).