Date: Wed, 30 Mar 2005 16:37:26 -0600 From: Jon Noack <noackjr@alumni.rice.edu> To: Rene Ladan <r.c.ladan@student.tue.nl> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: new LORs on 5.4 pre Message-ID: <424B2A26.8090101@alumni.rice.edu> In-Reply-To: <20050330142312.GB2020@82-168-75-155-bbxl.xdsl.tiscali.nl> References: <20050330091750.GA863@82-168-75-155-bbxl.xdsl.tiscali.nl> <20050330135213.GC66640@xor.obsecurity.org> <20050330142312.GB2020@82-168-75-155-bbxl.xdsl.tiscali.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/30/05 08:23, Rene Ladan wrote: > On Wed, Mar 30, 2005 at 05:52:13AM -0800, Kris Kennaway wrote: >>On Wed, Mar 30, 2005 at 11:17:50AM +0200, Rene Ladan wrote: >>>Hi, >>> >>>I've stumbled over some new LORs (all continuable) on 5.4pre from >>>2005-03-29 09:49 UTC, thus before the bpf/DHCP fix. >>> >>>lock order reversal >>> 1st 0xc0642b60 Giant (Giant) @ /usr/src/sys/kern/kern_timeout.c:256 >>> 2nd 0xc14d7264 fxp0 (network driver) @ /usr/src/sys/modules/fxp/../../dev/fxp/if_fxp.c:1233 >> >>Is your fxp module up-to-date? Stale modules (i.e. compiled for a >>different kernel than the one you're running) will cause problems. > > All modules are up to date. This LOR popped up after installing from a > resume buildworld. After blowing away /usr/obj, make cleandir twice in > /usr/src and rebuilding and reinstalling world+kernel, it and the others > still pop up, especially after any of these commands: > > # dhclient fxp0 > # ntpd -q > % fetchmail (only at startup, not after wakeup) > > Browsing in links does _not_ trigger a LOR. I saw a LOR similar to the rtentry one on -CURRENT a few days ago. See my message "4 LORs and a freeze with wi(4)": http://lists.freebsd.org/pipermail/freebsd-current/2005-March/047862.html Jon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?424B2A26.8090101>