Re: new LORs on 5.4 pre
From: Rene Ladan (r.c.ladan_at_student.tue.nl)
Date: 03/30/05
- Previous message: Rene Ladan: "Re: 5.4pre panic"
- In reply to: Kris Kennaway: "Re: new LORs on 5.4 pre"
- Next in thread: Jon Noack: "Re: new LORs on 5.4 pre"
- Reply: Jon Noack: "Re: new LORs on 5.4 pre"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 30 Mar 2005 16:23:12 +0200 To: Kris Kennaway <kris@obsecurity.org>
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.
> Kris
Regards,
Rene
-- "It won't fit on the line." -- me, 2001
- application/pgp-signature attachment: stored
- Previous message: Rene Ladan: "Re: 5.4pre panic"
- In reply to: Kris Kennaway: "Re: new LORs on 5.4 pre"
- Next in thread: Jon Noack: "Re: new LORs on 5.4 pre"
- Reply: Jon Noack: "Re: new LORs on 5.4 pre"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|