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: Mon, 10 Jan 2011 15:41:48 -0800 (PST) [thread overview]
Message-ID: <688142.89079.qm@web121707.mail.ne1.yahoo.com> (raw)
In-Reply-To: <F675EE07F28A0A4E933E5F9DD28672FB01197E08E2@orsmsx508.amr.corp.intel.com>
--- On Mon, 10/1/11, Dave, Tushar N <tushar.n.dave@intel.com> wrote:
> Does the issue appears only when you add a bridge?
Tushar,
I'm not sure what you mean by "add a bridge". I've been using this box ever since the late 1990s, and have had the 3 e100 port since the early 2000s, so I can't say that I "do" anything with it apart from use it.
The PCI configuration remains as it always has, and the box get rebooted only to receive stable kernel updates. Looking back through old dmesg logs, it looks like this issue also happened in 2.6.33.6 too without me ever realising. Hence I am suspecting that this problem has been happening intermittently for ages...
Is there anything else I can tell you about this ropey old P200 MMX PC before Indiana Jones finds it and tries putting it in his museum ;-)?
Cheers,
Chris
next prev parent reply other threads:[~2011-01-10 23:41 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 [this message]
2011-01-11 0:37 ` Dave, Tushar N
2011-01-11 8:52 ` [E1000-devel] " Chris Rankin
2011-01-11 20:59 ` 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=688142.89079.qm@web121707.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