On Wednesday 09 September 2009 01:49 pm, Felix Stolba wrote: > Brandon Gooch schrieb: > > lock order reversal: > > 1st 0xffffffff807cf200 sysctl lock (sysctl lock) _at_ > > /usr/src/sys/kern/kern_sysctl.c:1608 > > 2nd 0xffffffff80bf1de0 ACPI IBM extras (ACPI IBM extras) _at_ > > /usr/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi > >_ibm.c:481 KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > _witness_debugger() at _witness_debugger+0x2e > > witness_checkorder() at witness_checkorder+0x81e > > _sx_xlock() at _sx_xlock+0x54 > > acpi_ibm_sysctl() at acpi_ibm_sysctl+0x4f > > sysctl_root() at sysctl_root+0xe3 > > userland_sysctl() at userland_sysctl+0x158 > > __sysctl() at __sysctl+0xaa > > syscall() at syscall+0x1dd > > Xfast_syscall() at Xfast_syscall+0xd0 > > --- syscall (202, FreeBSD ELF64, __sysctl), rip = 0x80073769c, > > rsp = 0x7fffffffda58, rbp = 0x4 --- > > I'm getting the same LOR at boot in 9.0-current (source from 7th of > september). It is generally harmless but really annoying. Jung-uk KimReceived on Wed Sep 09 2009 - 16:25:22 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:55 UTC