Date: Fri, 23 May 2003 08:07:06 +0800 From: "David Xu" <davidxu@freebsd.org> To: "Julian Elischer" <julian@elischer.org>, "Dan Nelson" <dnelson@allantgroup.com> Cc: Daniel Eischen <eischen@pcnet1.pcnet.com> Subject: Re: libkse and SMP (was Re: USB bulk read & pthreads) Message-ID: <006901c320bf$401583a0$0701a8c0@tiger> References: <Pine.BSF.4.21.0305221409580.4662-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Julian Elischer" <julian@elischer.org> To: "Dan Nelson" <dnelson@allantgroup.com> Cc: <threads@freebsd.org>; "Daniel Eischen" <eischen@pcnet1.pcnet.com>; <davidxu@freebsd.org> Sent: Friday, May 23, 2003 5:13 AM Subject: Re: libkse and SMP (was Re: USB bulk read & pthreads) > > > On Thu, 22 May 2003, Dan Nelson wrote: > > > 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 > > > > make > > > > ./ksetest > > > > > > > > it may not do it the first time so let it run 10 seconds then kill > > > > it with ^C and retry about 10 times.. > > > > > > 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. > > > > Ok, after an hour still no panics. Should it really be exiting on its > > own this often, though? > > > > $ lastcomm ksetest | cut -c1-20 | sort | uniq -c > > > > 75 ksetest - > > 366 ksetest -X > > > > The above proceses were generated by the following loops in two > > different vtys: > > 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.. > > > > > > while sleep 10 ; do killall -9 ksetest ; done > > while : ; do ./ksetest; done > > > Thanks.. > > it's almost as if after a system has seen this crash few times > it gets immune from it in some way.. > > my system has stopped doing it.. :-( > > thanks for trying however.. > > 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. > > -- > > Dan Nelson > > dnelson@allantgroup.com > > > Dvaid Xu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?006901c320bf$401583a0$0701a8c0>