On Tue, Jan 30, 2001 at 01:56:26PM +0200, John Hay wrote:
> Booting with a kernel built from today's source (with devfs also in),
> I see this lock order reversal message:
>
> ###################################
> Routing daemons:.
> Doing IPv6 network setup:add net ::ffff:0.0.0.0: gateway ::1
> add net ::0.0.0.0: gateway ::1
> net.inet6.ip6.forwarding: 0 -> 0
> net.inet6.ip6.accept_rtadv: 0 -> 0
> net.inet6.ip6.accept_rtadv: 0 -> 1
> lock order reversal
> 1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:644
> 2nd 0xc02d5280 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940
> 3rd 0xc85d314c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:949
> add net fe80::: gateway ::1
> add net ff02::: gateway fe80::2a0:c9ff:fe8d:7c5f%fxp0
> ND default interface = fxp0
> IPv4 mapped IPv6 address support=YES.
> Additional daemons: syslogd.
> ###################################
>
> The machine is a SMP box, if that makes a difference. It does not seem
> to cause harm because it continue booting and I can log in.
This shouldn't be a problem. The lock order reversal has been there for a
long time and hasn't caused any problems, but since simplelocks were used
before, we didn't have any diagnostics to tell us it was there.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
