Date: Wed, 21 Sep 2011 17:13:39 +0400 From: Sergey Kandaurov <pluknet@gmail.com> To: Garrett Cooper <yanegomi@gmail.com> Cc: freebsd-net@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: LOR in route.c // scope6.c Message-ID: <CAE-mSO%2B3qQ1LSdmt=JdUWT%2BZLZjMrNqobTPESKeZbS_CHpjYZA@mail.gmail.com> In-Reply-To: <CAGH67wSS-Uxobeq3FgDq4VSSJYG8WDsVaDvXtt=uW%2BY8GS4wkA@mail.gmail.com> References: <CAGH67wSS-Uxobeq3FgDq4VSSJYG8WDsVaDvXtt=uW%2BY8GS4wkA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19 August 2011 05:07, Garrett Cooper <yanegomi@gmail.com> wrote: > Hi, > =A0 =A0I've periodically seen the following LOR when trying to repro a > panic after restarting my network configuration: > > :lock order reversal: > =A01st 0xc4142f1c rtentry (rtentry) @ /usr/src/sys/net/routec:362 > =A02nd 0xc3d08604 if_afdata (if_afdata) @ /usr/src/sys/netinet6/scope6.c:= 417 > KDB: stack backtrace: > db_trace_self_wrapper(...) > _witness_debugger(...) > _rw_wlock(...) > in6_setscope(...) > in6_purgeaddr(...) > in6_control(...) > ifioctl(...) > soo_ioctl(...) > kern_ioctl(...) > ioctl(...) > syscallenter(...) > syscall(...) > Xint0x80_syscall() > > I don't have a full backtrace or core for this. This was running > r224948 UP with WITNESS. > I just got exactly the same LOR on a very fresh current with /etc/rc.d/netif restart, and then I lost the system. Thanks for the report. I hope to dig out the solution... --=20 wbr, pluknet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE-mSO%2B3qQ1LSdmt=JdUWT%2BZLZjMrNqobTPESKeZbS_CHpjYZA>