Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*IPSecv6\/Neighbor\s+discovery\s+crash\s*$/: 14 ]

Total 14 documents matching your query.

1. IPSecv6/Neighbor discovery crash (score: 1)
Author: er@xxxxxxxx>
Date: Thu, 21 Aug 2003 20:49:47 -0500
xxxxxxxxxxxxxxx>
/archives/netdev/2003-08/msg00740.html (9,571 bytes)

2. Re: IPSecv6/Neighbor discovery crash (score: 1)
Author: emminger <shemminger@xxxxxxxx>
Date: Thu, 21 Aug 2003 18:46:40 -0700
get the following trace. (see first crash) I have seen this crash wi
/archives/netdev/2003-08/msg00741.html (7,865 bytes)

3. Re: IPSecv6/Neighbor discovery crash (score: 1)
Author: Tindel" <chad@xxxxxxxxxx>
Date: Fri, 22 Aug 2003 14:55:53 +0900
2 so that she can redirect your call. For any off-hours emergency ple
/archives/netdev/2003-08/msg00743.html (9,408 bytes)

4. Re: IPSecv6/Neighbor discovery crash (score: 1)
Author: xxxx>
Date: Fri, 22 Aug 2003 10:50:16 -0700
rack down what I'm looking for. Chris -- Chris Friesen | MailStop: 04
/archives/netdev/2003-08/msg00750.html (8,378 bytes)

5. Re: IPSecv6/Neighbor discovery crash (score: 1)
Author: xxxxxx>
Date: Fri, 22 Aug 2003 18:12:10 -0500
ware the table always comes up empty which is not a good enough test.
/archives/netdev/2003-08/msg00755.html (9,164 bytes)

6. Re: IPSecv6/Neighbor discovery crash (score: 1)
Author: ger <shemminger@xxxxxxxx>
Date: Fri, 22 Aug 2003 15:58:12 -0700
printed out ok except when the crash occurs. I get absolutely nothin
/archives/netdev/2003-08/msg00756.html (8,352 bytes)

7. Re: IPSecv6/Neighbor discovery crash (score: 1)
Author: minger <shemminger@xxxxxxxx>
Date: Fri, 22 Aug 2003 20:10:47 -0500
then match that assembler up with the output of: bash$ make net/ipv6/
/archives/netdev/2003-08/msg00757.html (8,055 bytes)

8. IPSecv6/Neighbor discovery crash (score: 1)
Author: latten@xxxxxxxxxxxxxx
Date: Thu, 21 Aug 2003 20:49:47 -0500
I am using linux-2.6.0-test3 + patch-2.6.0-test3-bk7 on SMP machines. Upon configuring AH, I do a ping6 to test connectivity and I get the following trace. (see first crash) I have seen this crash wi
/archives/netdev/2003-08/msg01712.html (9,571 bytes)

9. Re: IPSecv6/Neighbor discovery crash (score: 1)
Author: "David S. Miller" <davem@xxxxxxxxxx>
Date: Thu, 21 Aug 2003 18:46:40 -0700
So what exactly is NULL in ndisc_build_ll_hdr(), is it 'dev'? That'd be really weird...
/archives/netdev/2003-08/msg01713.html (7,935 bytes)

10. Re: IPSecv6/Neighbor discovery crash (score: 1)
Author: Kazunori Miyazawa <kazunori@xxxxxxxxxxxx>
Date: Fri, 22 Aug 2003 14:55:53 +0900
I had same crach. I guess it is due to xfrm cache. My impression about the problem is likes this. When we configure IPsec and src and dst of neighbour discoery match the configuration occasionally, T
/archives/netdev/2003-08/msg01715.html (9,517 bytes)

11. Re: IPSecv6/Neighbor discovery crash (score: 1)
Author: "David S. Miller" <davem@xxxxxxxxxx>
Date: Fri, 22 Aug 2003 10:50:16 -0700
I don't think so, fl.fl_icmp_type will be different for ICMP echo flow lookup than for the ndisc ones. Therefore flow cache will not return the older ndisc stacked DST for the ICMP echo flow lookup.
/archives/netdev/2003-08/msg01722.html (8,530 bytes)

12. Re: IPSecv6/Neighbor discovery crash (score: 1)
Author: latten@xxxxxxxxxxxxxx
Date: Fri, 22 Aug 2003 18:12:10 -0500
I tried my old standby of putting a few printk's to help debug. I put them in ndisc_output() and ndisc_build_ll_hdr() and they get printed out ok except when the crash occurs. I get absolutely nothin
/archives/netdev/2003-08/msg01727.html (9,164 bytes)

13. Re: IPSecv6/Neighbor discovery crash (score: 1)
Author: "David S. Miller" <davem@xxxxxxxxxx>
Date: Fri, 22 Aug 2003 15:58:12 -0700
... Why not save yourself all that debugging effort and just use gdb on the kernel image and: (gdb) x/10i ndisc_build_ll_hdr+0x17 then match that assembler up with the output of: bash$ make net/ipv6/
/archives/netdev/2003-08/msg01728.html (8,422 bytes)

14. Re: IPSecv6/Neighbor discovery crash (score: 1)
Author: latten@xxxxxxxxxxxxxx
Date: Fri, 22 Aug 2003 20:10:47 -0500
Sighhhhh and red-face.... I won't make that mistake again. I'm learning. OK, yes, it seems to be complaining about dev->hard_header... Joy ... Why not save yourself all that debugging effort and just
/archives/netdev/2003-08/msg01729.html (8,055 bytes)


This search system is powered by Namazu