Date: Tue, 30 Jan 2001 13:56:26 +0200 (SAT) From: John Hay <jhay@icomtek.csir.co.za> To: current@FreeBSD.org Subject: lock order reversal message Message-ID: <200101301156.f0UBuQw75143@zibbi.icomtek.csir.co.za>
next in thread | raw e-mail | index | archive | help
Hi, 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. The disks are scsi on an adaptec ahc controller, with most partitions on da0 and /usr/obj a link to a partition on da2. John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101301156.f0UBuQw75143>