* Re: Problem with commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e
[not found] <200704231506.34410.ismail@pardus.org.tr>
@ 2007-04-23 18:51 ` David Miller
2007-04-23 19:09 ` Ismail Dönmez
0 siblings, 1 reply; 6+ messages in thread
From: David Miller @ 2007-04-23 18:51 UTC (permalink / raw)
To: ismail; +Cc: tgraf, netdev
From: Ismail Dönmez <ismail@pardus.org.tr>
Date: Mon, 23 Apr 2007 15:06:34 +0300
> --- a/net/ipv4/fib_semantics.c
> +++ b/net/ipv4/fib_semantics.c
> @@ -89,7 +89,7 @@ static const struct
> {
> int error;
> u8 scope;
> -} fib_props[RTA_MAX + 1] = {
> +} fib_props[RTN_MAX + 1] = {
This fix is already in the net-2.6.22 tree.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e
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
0 siblings, 1 reply; 6+ messages in thread
From: Ismail Dönmez @ 2007-04-23 19:09 UTC (permalink / raw)
To: David Miller; +Cc: tgraf, netdev
Hi,
On Monday 23 April 2007 21:51:25 David Miller wrote:
> From: Ismail Dönmez <ismail@pardus.org.tr>
> Date: Mon, 23 Apr 2007 15:06:34 +0300
>
> > --- a/net/ipv4/fib_semantics.c
> > +++ b/net/ipv4/fib_semantics.c
> > @@ -89,7 +89,7 @@ static const struct
> > {
> > int error;
> > u8 scope;
> > -} fib_props[RTA_MAX + 1] = {
> > +} fib_props[RTN_MAX + 1] = {
>
> This fix is already in the net-2.6.22 tree.
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.
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)
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e
2007-04-23 19:09 ` Ismail Dönmez
@ 2007-04-23 21:17 ` Thomas Graf
2007-04-23 21:23 ` Ismail Dönmez
0 siblings, 1 reply; 6+ messages in thread
From: Thomas Graf @ 2007-04-23 21:17 UTC (permalink / raw)
To: Ismail Dönmez; +Cc: David Miller, netdev
* 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.
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?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e
2007-04-23 21:17 ` Thomas Graf
@ 2007-04-23 21:23 ` Ismail Dönmez
2007-04-25 8:52 ` Ismail Dönmez
0 siblings, 1 reply; 6+ messages in thread
From: Ismail Dönmez @ 2007-04-23 21:23 UTC (permalink / raw)
To: Thomas Graf; +Cc: David Miller, netdev
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
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.
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: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e
2007-04-23 21:23 ` Ismail Dönmez
@ 2007-04-25 8:52 ` Ismail Dönmez
2007-04-25 13:50 ` Ismail Dönmez
0 siblings, 1 reply; 6+ messages in thread
From: Ismail Dönmez @ 2007-04-25 8:52 UTC (permalink / raw)
To: Thomas Graf; +Cc: David Miller, netdev
[-- 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem with commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e
2007-04-25 8:52 ` Ismail Dönmez
@ 2007-04-25 13:50 ` Ismail Dönmez
0 siblings, 0 replies; 6+ messages in thread
From: Ismail Dönmez @ 2007-04-25 13:50 UTC (permalink / raw)
To: Thomas Graf; +Cc: David Miller, netdev
[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]
On Wednesday 25 April 2007 11:52:52 Ismail Dönmez wrote:
> 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.
Ignore this my laptop seems to be totally dying now including wireless card
too. Sorry for the noise.
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: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2007-04-25 13:49 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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
2007-04-25 13:50 ` Ismail Dönmez
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).