Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Oops\s+in\s+arp_rcv\,\s+patch\s*$/: 10 ]

Total 10 documents matching your query.

1. Oops in arp_rcv, patch (score: 1)
Author: Jacek Konieczny <jajcus@xxxxxxx>
Date: Wed, 4 Jul 2001 16:46:54 +0200
One of my router has rebooted a lot last days. I couldn't find the reason as the oops were not logged, and during most of crashes there was noone at the console. But finnaly I got the oops on a seri
/archives/netdev/2001-07/msg00006.html (11,988 bytes)

2. Re: Oops in arp_rcv, patch (score: 1)
Author: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxx>
Date: Thu, 05 Jul 2001 23:02:55 +0900
linux-2.4.x (0-test1 to 6) kernels are ok. -- yoshfuji
/archives/netdev/2001-07/msg00007.html (8,694 bytes)

3. Re: Oops in arp_rcv, patch (score: 1)
Author: xxxxxx>
Date: Thu, 5 Jul 2001 17:05:58 -0700 (PDT)
... It looks perfectly fine to me, all neigh_event_ns() return arguments are checked in the current 2.4.x sources, I don't know what you are talking about wrt. 2.4.5 since it is fine there too: n = n
/archives/netdev/2001-07/msg00011.html (8,379 bytes)

4. Re: Oops in arp_rcv, patch (score: 1)
Author: xxxxxx>
Date: Fri, 6 Jul 2001 10:35:08 +0200
Or maybe I was looking not good enough. Sorry, for false alarm. But the bug is really present in 2.2.19 and the patch was made for that version. At least, after applying that my router started buildi
/archives/netdev/2001-07/msg00012.html (8,948 bytes)

5. Re: Oops in arp_rcv, patch (score: 1)
Author: xxxxxx>
Date: Fri, 6 Jul 2001 04:37:53 -0700 (PDT)
Thanks, fixed in my 2.2.x tree and sent off to Alan. Later, David S. Miller davem@xxxxxxxxxx
/archives/netdev/2001-07/msg00013.html (7,854 bytes)

6. Oops in arp_rcv, patch (score: 1)
Author: Jacek Konieczny <jajcus@xxxxxxx>
Date: Wed, 4 Jul 2001 16:46:54 +0200
Hi, One of my router has rebooted a lot last days. I couldn't find the reason as the oops were not logged, and during most of crashes there was noone at the console. But finnaly I got the oops on a s
/archives/netdev/2001-07/msg00183.html (11,988 bytes)

7. Re: Oops in arp_rcv, patch (score: 1)
Author: YOSHIFUJI Hideaki / <yoshfuji@xxxxxxxxxx>
Date: Thu, 05 Jul 2001 23:02:55 +0900
linux-2.4.x (0-test1 to 6) kernels are ok. -- yoshfuji
/archives/netdev/2001-07/msg00184.html (8,750 bytes)

8. Re: Oops in arp_rcv, patch (score: 1)
Author: "David S. Miller" <davem@xxxxxxxxxx>
Date: Thu, 5 Jul 2001 17:05:58 -0700 (PDT)
... It looks perfectly fine to me, all neigh_event_ns() return arguments are checked in the current 2.4.x sources, I don't know what you are talking about wrt. 2.4.5 since it is fine there too: n = n
/archives/netdev/2001-07/msg00188.html (8,435 bytes)

9. Re: Oops in arp_rcv, patch (score: 1)
Author: Jacek Konieczny <jajcus@xxxxxxx>
Date: Fri, 6 Jul 2001 10:35:08 +0200
Or maybe I was looking not good enough. Sorry, for false alarm. But the bug is really present in 2.2.19 and the patch was made for that version. At least, after applying that my router started buildi
/archives/netdev/2001-07/msg00189.html (8,979 bytes)

10. Re: Oops in arp_rcv, patch (score: 1)
Author: "David S. Miller" <davem@xxxxxxxxxx>
Date: Fri, 6 Jul 2001 04:37:53 -0700 (PDT)
Thanks, fixed in my 2.2.x tree and sent off to Alan. Later, David S. Miller davem@xxxxxxxxxx
/archives/netdev/2001-07/msg00190.html (7,941 bytes)


This search system is powered by Namazu