From owner-freebsd-threads@FreeBSD.ORG Thu May 22 17:03:58 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D41637B401; Thu, 22 May 2003 17:03:58 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFA5343FA3; Thu, 22 May 2003 17:03:57 -0700 (PDT) (envelope-from davidxu@freebsd.org) Received: from tiger (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with SMTP id h4N03tUp023997; Thu, 22 May 2003 17:03:56 -0700 (PDT) (envelope-from davidxu@freebsd.org) Message-ID: <006901c320bf$401583a0$0701a8c0@tiger> From: "David Xu" To: "Julian Elischer" , "Dan Nelson" References: Date: Fri, 23 May 2003 08:07:06 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 cc: threads@freebsd.org cc: Daniel Eischen Subject: Re: libkse and SMP (was Re: USB bulk read & pthreads) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Xu List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2003 00:03:58 -0000 ----- Original Message -----=20 From: "Julian Elischer" To: "Dan Nelson" Cc: ; "Daniel Eischen" ; = Sent: Friday, May 23, 2003 5:13 AM Subject: Re: libkse and SMP (was Re: USB bulk read & pthreads) >=20 >=20 > On Thu, 22 May 2003, Dan Nelson wrote: >=20 > > In the last episode (May 22), Dan Nelson said: > > > In the last episode (May 22), Julian Elischer said: > > > > AHA! > > > > I've seen this panic from ksetest.. > > > > can you go to /usr/src/tools/KSE/ksetest > > > > and=20 > > > > make > > > > ./ksetest > > > >=20 > > > > it may not do it the first time so let it run 10 seconds then = kill > > > > it with ^C and retry about 10 times.. > > >=20 > > > It's not cooperating.. It hasn't crashed for me yet. Sometimes = it > > > exits cleanly on its own immediately after starting (see below), = but > > > it's never caused a panic. I'll try automating it by running it = in a > > > loop with a 2nd script running killall -9 ksetest every 10 = seconds. > >=20 > > Ok, after an hour still no panics. Should it really be exiting on = its > > own this often, though? > >=20 > > $ lastcomm ksetest | cut -c1-20 | sort | uniq -c > >=20 > > 75 ksetest - > > 366 ksetest -X > >=20 > > The above proceses were generated by the following loops in two > > different vtys: >=20 > no it's not supposed to stop.. I wonder why it does it.. > I have seen it a few ties on my system.. I'll try track it down.. >=20 >=20 > >=20 > > while sleep 10 ; do killall -9 ksetest ; done > > while : ; do ./ksetest; done > > =20 > Thanks.. >=20 > it's almost as if after a system has seen this crash few times > it gets immune from it in some way.. >=20 > my system has stopped doing it.. :-( >=20 > thanks for trying however.. >=20 >=20 It must be caused by an invalid thread pointer or some memory blocks = belong zoombie threads are corrupted, but I don't know where it came from. cpu_thread_clean only frees pcb_ext, and it is just an i386 hardware = I/O port map page, in normal case pcb_ext is zero, because we never access hardware I/O port in ksetest. > > --=20 > > Dan Nelson > > dnelson@allantgroup.com > >=20 >=20 Dvaid Xu