From: Andrew Morton <akpm@linux-foundation.org>
To: linux@horizon.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.23-rc8 network problem. Mem leak? ip1000a?
Date: Fri, 28 Sep 2007 02:20:51 -0700 [thread overview]
Message-ID: <20070928022051.a6f27b1e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070928020617.7389.qmail@science.horizon.com>
On 27 Sep 2007 22:06:17 -0400 linux@horizon.com wrote:
> Uniprocessor Althlon 64, 64-bit kernel, 2G ECC RAM,
> 2.6.23-rc8 + linuxpps (5.0.0) + ip1000a driver.
> (patch from http://marc.info/?l=linux-netdev&m=118980588419882)
>
> After a few hours of operation, ntp loses the ability to send packets.
> sendto() returns -EAGAIN to everything, including the 24-byte UDP packet
> that is a response to ntpq.
>
> ...
>
> Killing and restarting ntpd gets it running again for a few hours.
> Here's after about two hours of successful operation. (I'll try to
> remember to run slabinfo before killing ntpd next time.)
ntpd. Sounds like pps leaking to me.
>
> Can anyone offer some diagnosis advice?
>
CONFIG_DEBUG_SLAB_LEAK?
next prev parent reply other threads:[~2007-09-28 9:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 2:06 2.6.23-rc8 network problem. Mem leak? ip1000a? linux
2007-09-28 9:20 ` Andrew Morton [this message]
2007-09-30 7:59 ` linux
2007-09-30 9:23 ` Andrew Morton
2007-09-30 11:40 ` linux
2008-01-08 6:52 ` linux
2008-01-08 7:07 ` David Miller
2008-01-08 7:14 ` David Miller
2008-01-08 7:51 ` Francois Romieu
2008-01-08 12:28 ` [PATCH 1/3] drivers/net/ipg.c: Fix skbuff leak linux
2008-01-08 13:19 ` linux
2008-01-08 21:36 ` Francois Romieu
2008-01-08 23:00 ` David Miller
2008-01-08 23:28 ` Francois Romieu
2008-01-09 0:38 ` linux
2008-01-09 8:39 ` David Miller
2008-01-09 23:34 ` Francois Romieu
2008-01-09 23:56 ` David Miller
2008-01-09 23:30 ` Francois Romieu
2008-01-10 7:28 ` ipg.c bugs linux
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=20070928022051.a6f27b1e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=netdev@vger.kernel.org \
/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).