From owner-freebsd-current@FreeBSD.ORG Fri Nov 3 13:33:39 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2976C16A5EB for ; Fri, 3 Nov 2006 13:33:39 +0000 (UTC) (envelope-from pj@smo.de) Received: from ilk.de (mx-out14.ilk.de [194.121.104.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 253E243D55 for ; Fri, 3 Nov 2006 13:33:37 +0000 (GMT) (envelope-from pj@smo.de) Received: from bologna.intern.smo.de (pool15.ka.ilk.net [212.86.194.15]) by ilk.de (8.13.4/8.13.4/ilk-relay) with ESMTP id kA3DXW91021419; Fri, 3 Nov 2006 14:33:33 +0100 Received: from [192.168.153.208] (herdubreid.intern.smo.de [192.168.153.208]) by bologna.intern.smo.de (8.13.4+Sun/8.13.4) with ESMTP id kA3DX0LO007835; Fri, 3 Nov 2006 14:33:05 +0100 (CET) Message-ID: <454B461D.7020907@smo.de> Date: Fri, 03 Nov 2006 14:37:33 +0100 From: Philipp Ost User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20061022 X-Accept-Language: de, en-us, en MIME-Version: 1.0 To: Steve Franks References: <539c60b90611021332p78bd83afvb35accec13a3b7d8@mail.gmail.com> <454A6C26.7030105@smo.de> <539c60b90611021447v3628b7f3p69a57a88e90e30f4@mail.gmail.com> In-Reply-To: <539c60b90611021447v3628b7f3p69a57a88e90e30f4@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: usb mouse freezes kde on boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Nov 2006 13:33:39 -0000 Steve Franks wrote: > I must've come across sounding like I know something ;) Where would > one start to "look up what happened"? Logs? ps? How does one > determine the 'state' of the system? I would check the logfiles (I don't know if KDE has its own one), ps(1) and top(1). I suspect some processes is eating up resources. Based on the output one can draw conclusions which processes interfere and cause the freeze. I must admit though that I don't have much experience when it comes to this type of bugchasing. HTH, Philipp -- www.familie-ost.info/~pj