On Fri, 24 Apr 2015, Thomas Klausner wrote:
On Thu, Apr 23, 2015 at 11:23:20PM +0000, Paul Goyette wrote:
Log Message:
Welcome to 7.99.x and the modularization of sysmon!
I've built a 7.99.11 kernel today and booted it, and it twice failed
in the same place during boot.
acpicpu1 at cpu1: ACPI CPU
coretemp1 at cpu1: thermal sensor, 1 C resolution
Mutex error: mutex_vector_enter: locking against myself
lock address : 0xffffffff811c0040
current cpu : 0
current lwp : 0xffffffff810d2b80
owner field : 0xffffffff810d2b80 wait spin: 0/0
panic: lock error: Mutex: mutex_vector_enter: locking against myself: lock
0xffffffff811c0040 cpu 0 lwp 0xffffffff810d2b80
fata breakpoint trap in supervisor mode
trap type 1 code 0 rip ffffffff80289eed cs 8 rflags 246 cr2 0 ilevel 8 rsp
ffffffff81373c00
curlwp 0xffffffff810d2b80 pid 0.1 lowest kstrack 0xffffffff813702c0
7.99.10 from yesterday boots fine.
Hmmm. The dmesg would at least suggest that this would be a result of
my changes. Is there any chance you can get a backtrace? Or use the
kernel map to identify which lock is being referenced? (Both data would
be useful.)
-------------------------------------------------------------------------
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired) | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com |
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
-------------------------------------------------------------------------
