From owner-freebsd-current Fri Nov 17 13:29:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id AF9EA37B479; Fri, 17 Nov 2000 13:29:42 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13wt23-0004EK-00; Fri, 17 Nov 2000 23:26:51 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id XAA23375; Fri, 17 Nov 2000 23:26:51 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 23180; Fri Nov 17 23:25:33 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13wt0m-000HFR-00; Fri, 17 Nov 2000 23:25:32 +0200 From: Sheldon Hearn To: John Baldwin Cc: current@freebsd.org, Valentin Chopov , Boris Popov , Soren Schmidt , "Steven E. Ames" , Alfred Perlstein Subject: Re: CURRENT is freezing again ... In-reply-to: Your message of "Fri, 17 Nov 2000 10:30:02 PST." Date: Fri, 17 Nov 2000 23:25:32 +0200 Message-ID: <66304.974496332@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. 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. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message