From: Olof Johansson <olof@austin.ibm.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: netdev@oss.sgi.com, cramerj <cramerj@intel.com>, milliner@us.ibm.com
Subject: Re: [2.4] e1000 leaking pci mappings on rx errors?
Date: Mon, 12 Jan 2004 14:47:41 -0600 [thread overview]
Message-ID: <400307ED.3060900@austin.ibm.com> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E0102CBDDC5@orsmsx402.jf.intel.com>
Feldman, Scott wrote:
>>We have a machine here (running a RHEL 2.4.21-based kernel),
>>that started showing leakage of PCI mappings when the driver
>>was upgraded from 5.1.11 to 5.2.20.
>
>
> Olof, please try 5.1.13 and 5.2.16 from sf.net/projects/e1000 to help
> narrow the diff. I'm not seeing anything obvious in the diff between
> 5.1.11 and 5.2.20 that would explain this.
Scott,
5.1.13 is OK, 5.2.16 is leaking.
Also, I noticed it's leaking quite fast, and even before any RX errors
are shown. So my previous guess w.r.t. cause and effect might have been
wrong:
[root@primerib linux-2.4.21-6.EL-olof]# netstat -i
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP
TX-OVR Flg
eth1 1500 0 54793 0 0 0 67048 0 0
0 BMRU
~6240 PCI mappings had been allocated with the above statistics (eth1 is
the problematic interface in our case).
-Olof
--
Olof Johansson Office: 4F005/905
pSeries Linux Development IBM Systems Group
Email: olof@austin.ibm.com Phone: 512-838-9858
All opinions are my own and not those of IBM
next prev parent reply other threads:[~2004-01-12 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 17:43 [2.4] e1000 leaking pci mappings on rx errors? Feldman, Scott
2004-01-12 20:47 ` Olof Johansson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-12 23:36 Feldman, Scott
2004-01-13 0:35 ` Olof Johansson
2004-01-13 1:01 ` Olof Johansson
2004-01-12 16:42 olof
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=400307ED.3060900@austin.ibm.com \
--to=olof@austin.ibm.com \
--cc=cramerj@intel.com \
--cc=milliner@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@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;
as well as URLs for NNTP newsgroup(s).