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 12:59:24 -0800 (PST) [thread overview]
Message-ID: <314995.84049.qm@web121708.mail.ne1.yahoo.com> (raw)
In-Reply-To: <F675EE07F28A0A4E933E5F9DD28672FB01197E098F@orsmsx508.amr.corp.intel.com>
Tushar,
As promised:
$ /sbin/ifconfig -a
br0 Link encap:Ethernet HWaddr 00:03:47:3b:29:5c
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::203:47ff:fe3b:295c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:372485 errors:0 dropped:0 overruns:0 frame:0
TX packets:383917 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:37566127 (35.8 MiB) TX bytes:225458273 (215.0 MiB)
eth0 Link encap:Ethernet HWaddr 00:90:27:76:d0:ec
inet addr:10.0.43.2 Bcast:10.0.43.255 Mask:255.255.255.0
inet6 addr: fe80::290:27ff:fe76:d0ec/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:432016 errors:0 dropped:0 overruns:0 frame:0
TX packets:377602 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:229629017 (218.9 MiB) TX bytes:41958103 (40.0 MiB)
eth1 Link encap:Ethernet HWaddr 00:03:47:3b:29:5c
inet6 addr: fe80::203:47ff:fe3b:295c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:364683 errors:0 dropped:0 overruns:0 frame:0
TX packets:369235 errors:1 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:42445811 (40.4 MiB) TX bytes:203414933 (193.9 MiB)
eth2 Link encap:Ethernet HWaddr 00:03:47:3b:29:5d
inet6 addr: fe80::203:47ff:fe3b:295d/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:9059 errors:1 dropped:0 overruns:0 frame:1
TX packets:15437 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:691449 (675.2 KiB) TX bytes:22232699 (21.2 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:797 errors:0 dropped:0 overruns:0 frame:0
TX packets:797 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:81543 (79.6 KiB) TX bytes:81543 (79.6 KiB)
$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 10.0.43.2
netmask 255.255.255.0
network 10.0.43.0
broadcast 10.0.43.255
gateway 10.0.43.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 192.168.0.1
dns-search underworld
auto br0
iface br0 inet static
address 192.168.0.1
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
bridge-ports eth1 eth2
bridge_hello 1
bridge_fd 4
bridge_maxage 4
post-up /sbin/route add -net 224.0.0.0 netmask 240.0.0.0 dev br0
Cheers,
Chris
next prev parent reply other threads:[~2011-01-11 20:59 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 ` [E1000-devel] " Chris Rankin
2011-01-11 20:59 ` Chris Rankin [this message]
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=314995.84049.qm@web121708.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