From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 31 17:34:48 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91D1516A41F for ; Sat, 31 Dec 2005 17:34:48 +0000 (GMT) (envelope-from a.pirko@inode.at) Received: from smartmx-07.inode.at (smartmx-07.inode.at [213.229.60.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0242743D64 for ; Sat, 31 Dec 2005 17:34:47 +0000 (GMT) (envelope-from a.pirko@inode.at) Received: from [85.124.24.193] (port=50359 helo=[192.168.1.11]) by smartmx-07.inode.at with esmtp (Exim 4.50) id 1Eskcw-0005Vs-IL for freebsd-hackers@freebsd.org; Sat, 31 Dec 2005 18:34:46 +0100 Message-ID: <43B6C134.6060802@inode.at> Date: Sat, 31 Dec 2005 18:34:44 +0100 From: Armin Pirkovitsch User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 31 Dec 2005 17:40:00 +0000 Subject: Deadlock FreeBSD 6 / 7 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2005 17:34:48 -0000 Hi! I have some troubles with my notebook and any version of FreeBSD (starting with 6 since my sata controller wasn't supported earlier). It looks like as it would end up in a deadlock which means i have no access to the debugger nor to any other kind of tracing methods. Even with KTR, WITTNESS and DIAGNOSTIC enabled in the kerenl I get no message what went wrong or what might have caused the trouble. These fullstops always turn up when i compile and install programs (or sometimes during the installation of FreeBSD itself) Hardware: Intel Pentium-M 760 (Centrino, 2GHz) VIA VT 6421 SATA Controller 80GB Samsung SATA HD I guess one of those parts creates the trouble, but I have no idea how to trace it... Is there a way to run the whole thing in some kind of debugger? Or is there a diffrent way to locate the problem? Thank's in advance and a Happy New Year, -- Armin Pirkovitsch a.pirko@inode.at