Date: Fri, 17 Nov 2000 14:06:43 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Sheldon Hearn <sheldonh@uunet.co.za> Cc: Alfred Perlstein <bright@wintelcom.net>, "Steven E. Ames" <steve@virtual-voodoo.com>, Soren Schmidt <sos@freebsd.dk>, Boris Popov <bp@butya.kz>, Valentin Chopov <valentin@valcho.net>, current@FreeBSD.org Subject: Re: CURRENT is freezing again ... Message-ID: <XFMail.001117140643.jhb@FreeBSD.org> In-Reply-To: <66304.974496332@axl.fw.uunet.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17-Nov-00 Sheldon Hearn wrote: > > > On Fri, 17 Nov 2000 10:30:02 PST, John Baldwin wrote: > >> # sysctl -w debug.ktr_verbose=1 ; command_that_makes_my_machine_go_boom > > All very well and good once you've figured out which command makes your > machine go boom. Yes, I know. I didn't say the method was perfect. I find it frustrating as well. :-/ > But as I said, the locks I'm getting appear completely arbitrary. I'm > no hard-core hacker, but I'm not completely clueless when it comes to > isolating problems by way of deductive reasoning, and I'm stumped as to > what's causing these. I have no idea either. :( I can't magically fix them, and if I don't commit any of this stuff which works on my boxes as far as I can tell, then others won't test it and we won't make progress. If a buildworld usually triggers, then try writing a small C program that beats on a file in /tmp or /var, then start up 10 copies of it in a script that you run as your 'command_that_makes_my_machine_go_boom' to see if it works. :-P > Ciao, > Sheldon. -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.001117140643.jhb>