From owner-freebsd-current@FreeBSD.ORG Thu Nov 4 18:25:02 2004 Return-Path: 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 3AAF016A4E7; Thu, 4 Nov 2004 18:25:02 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14AB943D39; Thu, 4 Nov 2004 18:25:02 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id C2C747A403; Thu, 4 Nov 2004 10:25:01 -0800 (PST) Message-ID: <418A73FD.2070201@elischer.org> Date: Thu, 04 Nov 2004 10:25:01 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Ken Smith References: <200411020143.34251.gte990t@mail.gatech.edu> <200411040329.21834.michaelnottebrock@gmx.net> <4189CCB8.2050104@alexdupre.com> <200411041534.30965.michaelnottebrock@gmx.net> <20041104144605.GF24440@electra.cse.Buffalo.EDU> In-Reply-To: <20041104144605.GF24440@electra.cse.Buffalo.EDU> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: re@freebsd.org Subject: Re: [FreeBSD 5.3-RC2] Processes STILL hanging in unkillable state X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 04 Nov 2004 18:25:02 -0000 Ken Smith wrote: >On Thu, Nov 04, 2004 at 03:34:26PM +0100, Michael Nottebrock wrote: > > >>On Thursday, 4. November 2004 07:31, Alex Dupre wrote: >> >> >>>Michael Nottebrock wrote: >>> >>> >>>>Could all people who are seeing this please post their kernel >>>>configurations, sysctl.conf and perhaps some system details (platform, >>>>UP/MP), too. >>>> >>>> >>Looking at all of these, I fail to see anything "special" that all these >>machines have in common - looks like there's a full range from tuned >>configurations with eyebrowraisers like PREEMPTION to almost-unmodified >>GENERIC and pretty different hardware, too. :( >> >>So if anybody spots something interesting here after all, or thinks Marc >>Ramirez backtraces / debug sessions reveal anything about the bug, please >>take over... >> >> if you can get to teh kernel debugger on a serial link, (there is a sysctl to drop yuo into it) then the appropriate lines of 'ps' would be interesting. also x/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx {address} where address is the address of the ksegrp in question (in threaded processes) myght be interesting. (you can get that from the ps in ddb) >> >> > >In particular if you manage to wedge processes in an unkillable state >the output of "ps -o f -l" might be useful. I'd like to see all of the >flags set for a process that gets wedged. > > please also add the -H option to show the threads in question.