From owner-freebsd-current@FreeBSD.ORG Tue Jun 24 12:21:02 2003 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 679A737B401 for ; Tue, 24 Jun 2003 12:21:02 -0700 (PDT) Received: from sccrmhc13.attbi.com (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BDFE43FBD for ; Tue, 24 Jun 2003 12:21:01 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([12.233.125.100]) by attbi.com (sccrmhc13) with ESMTP id <2003062419205901600gd08pe>; Tue, 24 Jun 2003 19:21:00 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA93993; Tue, 24 Jun 2003 12:20:59 -0700 (PDT) Date: Tue, 24 Jun 2003 12:20:58 -0700 (PDT) From: Julian Elischer To: Michael Edenfield In-Reply-To: <20030624191656.GA30891@basement.kutulu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Unkillable processes with libKSE 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: Tue, 24 Jun 2003 19:21:02 -0000 If it's duplicatable on recent systems I'll see it on my test system... thanks.. On Tue, 24 Jun 2003, Michael Edenfield wrote: > * Julian Elischer [030624 14:47]: > > > > I had the same experience just running the KSE test application from > > > /usr/src/tools last night. I ended up with three unkillable ksetest > > > applications and ultimately rebooted to get rid of them. I was > > > planning to report it as soon as I finished reading my email :) > > > > "Interesting".. > > > > I'll check on my testd machine.. > > the test program responded to ^C as of a few days ago.. > > I just rebuilt my system to see if the problem had perhaps been > solved, but it's still doing it. It doesn't cause any problems (the > process doesn't look like it's doing anything, just not going away) so > I am gonna just let the processes sit there. > > root@basement:/usr/src/tools/KSE/ksetest# ./ksetest > main() : 0x804c000 > eip -> 0x280c06b3 > uts() at : 0x8048e20 > uts stack at : 0x814d000 - 0x8155000 > main() : 0x804c400 > eip -> 0x280c06b3 > uts() at : 0x8048e20 > uts stack at : 0x8255000 - 0x825d000 > thread_start() : 0x804c800 804c800 > thread_start() : 0x826d000 826d000 > kse_create() -> 0 > +-kse_create() -> -1 > main() : 0x826d800 > eip -> 0x280c06b3 > uts() at : 0x8048e20 > uts stack at : 0x837e000 - 0x8386000 > main() : 0x826dc00 > eip -> 0x280c06b3 > uts() at : 0x8048e20 > uts stack at : 0x8486000 - 0x848e000 > thread_start() : 0x848e000 848e000 > thread_start() : 0x848e800 848e800 > thread_start() : 0x84af000 84af000 > kse_create() -> 0 > A*.kse_create() -> -1 > [...] > *R*.S.*T*.^C^D^Z > > (no response on this tty, so I close it). > > On another tty I get this: > > root@basement:/home/kutulu# ps x | grep ksetest > 30947 p2 RL- 0:00.12 ./ksetest > 30947 p2 RL- 0:00.12 ./ksetest > 30947 p2 TL- 0:00.12 ./ksetest > root@basement:/home/kutulu# kill -KILL 30947 > root@basement:/home/kutulu# ps x | grep ksetest > 30947 p2 RL- 0:00.12 ./ksetest > 30947 p2 RL- 0:00.12 ./ksetest > 30947 p2 TL- 0:00.12 ./ksetest > root@basement:/home/kutulu# top > > [...] > 30947 root 76 0 5760K 628K WAIT 0:00 0.00% 0.00% ksetest > 30947 root 8 0 5760K 628K RUN 0:00 0.00% 0.00% ksetest > 30947 root 8 0 5760K 628K RUN 0:00 0.00% 0.00% ksetest > [...] > > I don't have DDB in this kernel at the moment (it's remote and I > prefer the crash dumps) but I can put it in and try again if there's > something you can use from it. > > --Mike >