Date: Sun, 19 Jul 2009 15:02:01 +0200 (CEST) From: Alexander Best <alexbestms@math.uni-muenster.de> To: John Baldwin <jhb@freebsd.org>, <freebsd-current@freebsd.org> Cc: Thomas Backman <serenity@exscape.org> Subject: Re: core dumps being overwritten Message-ID: <permail-20090719130201f7e55a9d0000677a-a_best01@message-id.uni-muenster.de> In-Reply-To: <200907170901.31617.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?permail-20090719130201f7e55a9d0000677a-a_best01>