public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Rankin <rankincj@yahoo.com>
To: "e1000-devel@lists.sourceforge.net"
	<e1000-devel@lists.sourceforge.net>,
	Tushar NDave <tushar.n.dave@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [E1000-devel] [e100] Page allocation failure warning(?) in 2.6.36.3
Date: Tue, 11 Jan 2011 00:52:37 -0800 (PST)	[thread overview]
Message-ID: <838977.21111.qm@web121703.mail.ne1.yahoo.com> (raw)
In-Reply-To: <F675EE07F28A0A4E933E5F9DD28672FB01197E098F@orsmsx508.amr.corp.intel.com>

--- On Tue, 11/1/11, Dave, Tushar N <tushar.n.dave@intel.com> wrote:
The reason I asked you about bridge is because I have
> noticed "br0: port 1(eth1) entering learning state" in the
> dmesg log you sent.
> I am trying to figure out exactly what sequence of commands
> you run that produce this message " br0: port 1(eth1)
> entering learning state" in log.

Tushar,

Ah, sorry. I thought you were referring to a PCI bridge, or something similar.

The br0 interface contains the eth1 and eth2 interfaces, which each connects to a PC on the private LAN. The eth0 interface connects to the ADSL router, and br0 holds the PC's internal LAN IP address. (eth0, eth1 and eth2 are all e100 interfaces, of course.)

It's impossible to state whether the problem *only* happens when I use the bridge because:
a) I've always used the bridge, and need to for the LAN to work, and
b) the problem is both rare and intermittent, even when it does happen. I certainly didn't notice it with the 2.6.36.2 kernel, nor any of the 2.6.34 or 2.6.35 kernels, although the fact that I did with the 2.6.33.6 kernel suggests it was present in all those kernels anyway.

I'll send you the bridge setup and ifconfig information later; I'm not in front of that PC right now.

Thanks,
Chris



      

  reply	other threads:[~2011-01-11  8:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08 12:53 [e100] Page allocation failure warning(?) in 2.6.36.3 Chris Rankin
2011-01-10 23:11 ` [E1000-devel] " Dave, Tushar N
2011-01-10 23:41   ` Chris Rankin
2011-01-11  0:37     ` Dave, Tushar N
2011-01-11  8:52       ` Chris Rankin [this message]
2011-01-11 20:59       ` [E1000-devel] " Chris Rankin
2011-01-12 17:35         ` Eric Dumazet
2011-01-12 17:42           ` [E1000-devel] " Chris Rankin
2011-01-12 17:48             ` Eric Dumazet
2011-01-12 18:05           ` Brandeburg, Jesse
2011-01-12 18:14             ` Eric Dumazet
2011-01-12 23:27               ` Chris Rankin
2011-01-13  4:55                 ` Eric Dumazet
2011-01-13  9:00                   ` Chris Rankin
2011-01-13  9:05                     ` Eric Dumazet
2011-01-13  9:24                       ` Chris Rankin

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=838977.21111.qm@web121703.mail.ne1.yahoo.com \
    --to=rankincj@yahoo.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=netdev@vger.kernel.org \
    --cc=tushar.n.dave@intel.com \
    /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