Date: Mon, 26 Sep 2011 21:24:35 -0400 From: Arnaud Lacombe <lacombar@gmail.com> To: dave jones <s.dave.jones@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: Kernel panic on FreeBSD 9.0-beta2 Message-ID: <CACqU3MVKunQAZj2q1ng2po451vnLMzbp2aTYcZdFpm8h2Hop_A@mail.gmail.com> In-Reply-To: <CANf5e8bbaRU5_GFX4d4E_wouzdx8Bmf7NjvR1_1EeeW=K0irvA@mail.gmail.com> References: <CANf5e8aG4go4M_vsRExUsJB_sjaN5x-QK-TCDAhSH64JSo0mdQ@mail.gmail.com> <CACqU3MXStMMEoppvDtZS6hV4WGttbdJiF8E-ORwJ%2BQSmnTy-Yg@mail.gmail.com> <CACqU3MV-t4Va6VWUoXy1Y9FYnNJTUw1X%2BE7ik-2%2BtMVuVOV3RA@mail.gmail.com> <CANf5e8bbaRU5_GFX4d4E_wouzdx8Bmf7NjvR1_1EeeW=K0irvA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Mon, Sep 26, 2011 at 8:51 PM, dave jones <s.dave.jones@gmail.com> wrote: > On Mon, Sep 26, 2011 at 1:41 PM, Arnaud Lacombe wrote: >> Hi, >> >> On Mon, Sep 26, 2011 at 1:12 AM, Arnaud Lacombe wrote: >>> Hi, >>> >>> On Mon, Sep 26, 2011 at 12:43 AM, dave jones wrote: >>>> Hi, >>>> I have two production machines running on freebsd 9.0-beta2 and both got >>>> kernel panic related to networking. Any idea how to solve it? thanks. >>>> >>>> http://http://60.248.161.9/p1.jpg >>>> http://http://60.248.161.9/p2.jpg >>>> >>> this host is really slow :-) >>> >>> To avoid the waiting time, the backtrace is: >>> >>> in_pcbbind_setup()+0x28f >>> in_pcbbind()+0xa9 >>> udp_bind() >>> bind() >>> kern_bind() >>> syscall_enter() >>> syscall() >>> >>> faulted at VA 0x07. Origin process in named. >>> >> AFAICT, the crash happens in the following block: >> >> /* >> * XXX >> * This entire block sorely needs a rewrite. >> */ >> if (t && >> ((t->inp_flags & INP_TIMEWAIT) == 0) && >> (so->so_type != SOCK_STREAM || >> ntohl(t->inp_faddr.s_addr) == INADDR_ANY) && >> (ntohl(sin->sin_addr.s_addr) != INADDR_ANY || >> ntohl(t->inp_laddr.s_addr) != INADDR_ANY || >> (t->inp_socket->so_options & >> SO_REUSEPORT) == 0) && >> (inp->inp_cred->cr_uid != >> t->inp_cred->cr_uid)) >> return (EADDRINUSE); >> } >> >> more specifically, `t->inp_socket' is NULL. The top comment may not be >> relevant, as it's been here for the past 8 years. > > Hi Arnaud, > > Ah, thanks for the info. I'm wondering if you have a patch to fix that issue? > Guess what? another production machine got the same panic, oh my~ Can you give us more precision on the condition of the crash ? is it immediately at boot-time ? If not, is it when a special network condition occurs ? What kind of load is named(9) having on average before the panic ? Are you using any fancy configuration or thing out of the ordinary ? Are you using named from the base system, or from port ? Thanks, - Arnaud
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACqU3MVKunQAZj2q1ng2po451vnLMzbp2aTYcZdFpm8h2Hop_A>