Date: Thu, 25 Aug 2005 01:40:17 GMT From: "Evgueni V. Gavrilov" <aquatique@rusunix.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/85239: assigning an address to ng_fec(4) iface causes panic Message-ID: <200508250140.j7P1eHCI005066@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR kern/85239; it has been noted by GNATS. From: "Evgueni V. Gavrilov" <aquatique@rusunix.org> To: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> Cc: bug-followup@freebsd.org, Brooks Davis <brooks@one-eyed-alien.net> Subject: Re: kern/85239: assigning an address to ng_fec(4) iface causes panic Date: Thu, 25 Aug 2005 08:34:53 +0700 Maksim Yevmenkin wrote: >>I've applied Maksim's patch (with some modifications since 6.0-BETA3 >>holds ng_fec.c 1.18, not 1.20) > > ok. just to verify, you have applied the second patch? right? as > Brooks pointed out the first patch did not make required change in > ng_fec_ioctl() (call to ng_fec_init() was still using ifp pointer > instead of priv pointer). yes, of course slight modifications used because I've got the trouble with 6.0-BETA3, not -CURRENT http://aquatique.rusunix.org/20050824.ng_fec.c.patch this is the patch I've applied >>The short response: it works finally :) >> >>But assigning an address to fec iface being down causes frezze, so I >>made following startup: > > i can not reproduce the freeze here :( i did simple test (below). > unfortunately i do not have hardware to recreate your setup here :( I suppose that in order to reproduce this issue you need to configure Fast (Ether|Giga)Channel on switch ports too. I agree that it's not always possible. > can you drop into the debugger (ctrl+alt+esc) and try to get a stack > trace? if you can not - could you please try to put some printf's into > /sys/netgraph/ng_fec.c to see where it locks up? I'll try to inviestigate this upon next scheduled downtime for this machine. Unfortunately I can't put it down for a long time (that's the reason of using ng_fec(4) on that machine: high availability). > beetle# ifconfig fec0 inet 192.168.1.1 netmask 255.255.255.0 > beetle# ifconfig fec0 > fec0: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500 > inet6 fe80::211:43ff:fe54:22c9%fec0 prefixlen 64 scopeid 0x4 > inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 > ether 00:00:00:00:00:00 > media: Ethernet none > status: no carrier I suppose the issue is apparent only using several interfaces in the ng_fec(4) bundle with Fast (Ether|Giga)Channel configured on switch ports.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200508250140.j7P1eHCI005066>