Re: sys/modules/geom/geom_part/geom_part_apm compilation error

2010-05-23 Thread Ronald van der Pol
On Sun, May 23, 2010 at 17:58:51 +0400, Dmitry Morozovsky wrote: > Wait for a few hours, or try to integrate SVN change 200534 (to > /sys/geom/part/*). I waited for the new commit. The kernel is now building fine. Thanks! I ran into a problem when installing the kernel. The root filesystem ran

sys/modules/geom/geom_part/geom_part_apm compilation error

2010-05-23 Thread Ronald van der Pol
I want to try the ix(4) 10GE driver on -STABLE. I am compiling -STABLE on a test server. I cvsup'd -STABLE in a clean /usr/src. Compiling world went fine. Kernel stops with this error: /usr/src/sys/modules/geom/geom_part/geom_part_apm/../../../../geom/part/g_part_apm.c:131: error: 'G_PART_ALIAS_A

Re: 4.10 STABLE: IPv6 PMTU Discovery broken

2004-08-12 Thread Ronald van der Pol
On Thu, Aug 12, 2004 at 14:57:31 +0200, Ronald van der Pol wrote: > Yep, I have the same problem with the latest 4.10: no ICMP6 > packet too big packets are sent. Sorry, I made a mistake. I did not set net.inet6.ip6.forwarding=1 on the test machine. Now I have and now I get "pac

Re: 4.10 STABLE: IPv6 PMTU Discovery broken

2004-08-12 Thread Ronald van der Pol
On Thu, Aug 12, 2004 at 14:01:56 +0200, Ronald van der Pol wrote: > So, maybe something changed getween July 17th and now. I will > see what happens after an upgrade to the latest 4.10. Yep, I have the same problem with the latest 4.10: no ICMP6 packet too big packets are sent.

Re: 4.10 STABLE: IPv6 PMTU Discovery broken

2004-08-12 Thread Ronald van der Pol
On Thu, Aug 12, 2004 at 12:02:17 +1000, Mark Andrews wrote: > Is this a known issue? > Do you need more information? I have tried it on 4.10-STABLE FreeBSD 4.10-STABLE #8: Sat Jul 17 10:08:52 CEST 2004 It sends "Packet too big" icmp6s on the wire. I also see the netstat -s -p icmp6 "

Re: 4.10 STABLE: IPv6 PMTU Discovery broken

2004-08-12 Thread Ronald van der Pol
On Thu, Aug 12, 2004 at 12:02:17 +1000, Mark Andrews wrote: > The box does not appear to be generating a ICMP6 too big error > message which I would expect to see once the 1428 octet TCP > segments start arriving. You could also check the output of: netstat -s -p icmp6 There ha