you're right. i found this in one of my logs: savecore: unable to read from bounds, using 0 Expensive timeout(9) function: 0xc051b930(0xc0a22340) 0.013787226 s savecore: unable to read from bounds, using 0 savecore: reboot after panic: mutex ACPI global lock owned at /usr/src/sys/kern/kern_event.c:1758 Jul 16 00:22:20 otaku savecore: reboot after panic: mutex ACPI global lock owned at /usr/src/sys/kern/kern_event.c:1758 savecore: writing core to vmcore.0 Writing crash summary to /var/crash/core.txt.0. alex John Baldwin schrieb am 2009-07-17: > On Thursday 16 July 2009 4:04:17 am Alexander Best wrote: > > exactly. `cat /var/crash/bounds` => 2. > This can happen if you lose the 'bounds' file during a crash or if > that file > is corrupted in some other fashion.Received on Sun Jul 19 2009 - 11:02:04 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:52 UTC