Date: Thu, 19 Mar 2009 09:12:24 -0700 From: Sam Leffler <sam@freebsd.org> To: Vany Serezhkin <ivan@serezhkin.com> Cc: freebsd-net@freebsd.org Subject: Re: 802.1x broken after SVN rev 189592 Message-ID: <49C26EE8.3040100@freebsd.org> In-Reply-To: <49C2504F.2030003@serezhkin.com> References: <49C2504F.2030003@serezhkin.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Vany Serezhkin wrote:
> Hello.
>
> I do not really sure in this, but :
>
> after the current updated to
> 20090309 Merge IGMPv3 and Source-Specific Multicast (SSM) to the FreeBSD
> IPv4 stack.
>
> I can't use any wpa_supplicant related networks.
>
> It faulted in any WPA authentications , that i tried.
> Also it faulted when i try to login via 802.1x in my job network.
>
> All happens after i starts wpa_supplicant and looks like these:
>
> #11 0xc05cabec in panic (fmt=0xc08b16e9 "sbappendaddr_locked") at
> /opt/src/sys/kern/kern_shutdown.c:559
> #12 0xc061fd40 in sbappendaddr_locked (sb=0xc66dd670, asa=0xc09021b4,
> m0=0xce435b00, control=0x0)
> at /opt/src/sys/kern/uipc_sockbuf.c:632
> #13 0xc0620418 in sbappendaddr (sb=0xc66dd670, asa=0xc09021b4,
> m0=0xce435b00, control=0x0)
> at /opt/src/sys/kern/uipc_sockbuf.c:679
> #14 0xc0671be4 in raw_input (m0=0xc64b0100, proto=0xe664ec60,
> src=0xc09021b4) at /opt/src/sys/net/raw_usrreq.c:96
> #15 0xc06749e7 in rts_input (m=0xc64b0100) at
> /opt/src/sys/net/rtsock.c:151
> #16 0xc066f752 in swi_net (dummy=0x0) at /opt/src/sys/net/netisr.c:145
> #17 0xc05aa148 in intr_event_execute_handlers (p=0xc61617ec,
> ie=0xc61a2d00) at /opt/src/sys/kern/kern_intr.c:1134
> #18 0xc05ab4d4 in ithread_loop (arg=0xc60ec660) at
> /opt/src/sys/kern/kern_intr.c:1147
> #19 0xc05a7ac9 in fork_exit (callout=0xc05ab469 <ithread_loop>,
> arg=0xc60ec660, frame=0xe664ed38)
> at /opt/src/sys/kern/kern_fork.c:821
> #20 0xc0833170 in fork_trampoline () at
> /opt/src/sys/i386/i386/exception.s:270
>
Are you certain it's that revision? Have you tried r189931 which worked
around certain problems in the initial commit?
Can you provide sufficient info to reproduce your problem? Filing a PR
for reference is likely the best thing to do.
Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49C26EE8.3040100>