Date: Mon, 04 Jun 2012 13:55:10 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: "Alexander V. Chernikov" <melifaro@FreeBSD.org> Cc: freebsd-net@FreeBSD.org, FreeBSD-Current <freebsd-current@FreeBSD.org> Subject: Re: null pointer panic in bpf_peers_present Message-ID: <4FCC940E.2070008@FreeBSD.org> In-Reply-To: <4FCC5A46.8020007@FreeBSD.org> References: <4FCBCF7E.9020603@FreeBSD.org> <4FCBE3B6.1020003@FreeBSD.org> <4FCC5A46.8020007@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 04/06/2012 09:48 Alexander V. Chernikov said the following: > On 04.06.2012 02:22, Andriy Gapon wrote: >> on 03/06/2012 23:56 Andriy Gapon said the following: >>> >>> I wonder if anybody else is seeing this and if there is a fix... >>> This is very recent (today's) FreeBSD head with pretty dull network >>> configuration. During boot I run into the following panic: >>> >>> <118>Setting hostname: xxxxx >>> <118>Starting dhclient. >>> >> My current guess is that the panic occurs because of the newly added (r235745) >> bpf_ifdetach which is an ifnet_departure_event handler. My rc.conf is >> configured to do interface renaming and SIOCSIFNAME seems to post >> ifnet_departure_event followed by ifnet_arrival_event. >> >> Not sure if it's a window between ifnet_departure_event and ifnet_arrival_event >> when if_bpf is NULL, or if if_bpf is never restored in this case. > if_bpf is never restored. > > Can you please try an attached patch ? I can boot successfully with this patch. Thank you! -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FCC940E.2070008>