netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ismail Dönmez" <ismail@pardus.org.tr>
To: Thomas Graf <tgraf@suug.ch>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: Problem with commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e
Date: Wed, 25 Apr 2007 11:52:52 +0300	[thread overview]
Message-ID: <200704251152.52906.ismail@pardus.org.tr> (raw)
In-Reply-To: <200704240023.13565.ismail@pardus.org.tr>

[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]

Hi,
On Tuesday 24 April 2007 00:23:13 Ismail Dönmez wrote:
> On Tuesday 24 April 2007 00:17:40 Thomas Graf wrote:
> > * Ismail D?nmez <ismail@pardus.org.tr> 2007-04-23 22:09
> >
> > > Yes I know the fix is in but I wondered why its creating such problems
> > > with 2.6.18 kernel, guess it depends on some other commits.
> >
> > As long as you apply the complete patch including the additional
> > sanity check for RTN_MAX it should work perfectly fine on 2.6.18.
>
> The sanity check part doesn't seem to apply to 2.6.18.
>
> > I can't think of any connection between the patch and the errors
> > you are seeing.
> >
> > Are you absolutely sure the errors you see are directly connected
> > to applying the patch?
>
> Yes actually I am but I'll re-test and see. Thanks.

I was able to reproduce the same problem with Linus' GIT tree too. Since I 
started to see these after I applied the commit 
a0ee18b9b7d3847976c6fb315c06a34fb296de0e to 2.6.18 tree, there is a big 
possiblity that the commit is the culprit.

I attach the relevant dmesg messages. Problem happened after 12 hours of 
uptime and and net connection gets stable again after 1-2 minutes.

Regards,
ismail

-- 
Life is a game, and if you aren't in it to win,
what the heck are you still doing here?

-- Linus Torvalds (talking about open source development)

[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 1348 bytes --]

Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
printk: 1 messages suppressed.
Neighbour table overflow.
printk: 4 messages suppressed.
Neighbour table overflow.
printk: 3 messages suppressed.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
printk: 3 messages suppressed.
Neighbour table overflow.
printk: 15 messages suppressed.
Neighbour table overflow.
printk: 6 messages suppressed.
Neighbour table overflow.
printk: 13 messages suppressed.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
printk: 2 messages suppressed.
Neighbour table overflow.
printk: 1 messages suppressed.
Neighbour table overflow.
Neighbour table overflow.


  reply	other threads:[~2007-04-25  8:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200704231506.34410.ismail@pardus.org.tr>
2007-04-23 18:51 ` Problem with commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e David Miller
2007-04-23 19:09   ` Ismail Dönmez
2007-04-23 21:17     ` Thomas Graf
2007-04-23 21:23       ` Ismail Dönmez
2007-04-25  8:52         ` Ismail Dönmez [this message]
2007-04-25 13:50           ` Ismail Dönmez

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=200704251152.52906.ismail@pardus.org.tr \
    --to=ismail@pardus.org.tr \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@suug.ch \
    /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).