Date: Sun, 24 Jun 2012 20:50:41 +0200 (CEST) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Mateusz Guzik <mjguzik@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: reason for "magic" crashes. Message-ID: <alpine.BSF.2.00.1206242049230.73675@wojtek.tensor.gdynia.pl> In-Reply-To: <20120624180526.GA15899@dft-labs.eu> References: <20120623162415.303430@gmx.com> <alpine.BSF.2.00.1206231947160.40095@wojtek.tensor.gdynia.pl> <alpine.BSF.2.00.1206241856090.73001@wojtek.tensor.gdynia.pl> <20120624180526.GA15899@dft-labs.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
>> >> >> There is nothing in cron that is done at sunday. >> >> i don't run "periodic" stuff in /etc/crontab >> > > Compile the kernel with the following: > > makeoptions DEBUG="-O0 -g" > > options KDB # Enable kernel debugger support. > options DDB # Support DDB. > options GDB # Support remote GDB. > options DEADLKRES # Enable the deadlock resolver > options INVARIANTS # Enable calls of extra sanity checking > options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS > options WITNESS # Enable checks to detect deadlocks and cycles > options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed > options DIAGNOSTIC > > After kernel panic ddb prompt will be waiting for you. Type in: > dump <enter> > reset <enter> > > Make sure you have swap that can handle crashdumps. already did this part and debug part, but not DDB. As you see - hang not crashdump how much would it slow down whole thing? If less than 2 times it can be - CPU are rerely half loaded
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1206242049230.73675>