Re: [Iometer-devel] IOMETER for Linux network measurement ... "Grunt thread exiting with 1 still active" errors

[<min...@gm...>]

no. i do not have time to work on this any more...

you can change the code to disable that dead loop as a work around.



On Dec 8, 2008 9:12pm, "David, Howard" <how...@in...> wrote:
>
>
>
>
> Was any progress made on #1244848? Cheung
> Ming said he would follow up. I think we are seeing the same problem.
>
> Thank you,
>
> Howard David
>
> Intel Corp.
>
>
>
> [
> 1244848 ] *** Grunt thread exiting with 1 still active
>
>
>
>
>
> You may monitor this Tracker item after you log in
> (register an account,
> if you do not already have one)
>
>
>
>
>
> Submitted By:
>
> Marc Johnson - marcjohnson
>
>
>
>
> Date Submitted:
>
> 2005-07-25 23:25
>
>
>
>
>
> Last Updated By:
>
> cheungming - Comment added
>
>
>
> Date Last Updated:
>
>
> 2005-08-16 02:19
>
>
>
>
>
> Number of Comments:
>
>
> 2
>
>
>
> Number of Attachments:
>
>
> 0
>
>
>
>
>
> Category: (?)
>
>
> None
>
>
>
> Group: (?)
>
>
> None
>
>
>
>
>
> Assigned To: (?)
>
>
> Nobody/Anonymous
>
>
>
> Priority: (?)
>
>
> 5
>
>
>
>
>
> Status: (?)
>
>
> Open
>
>
>
> Resolution: (?)
>
>
> None
>
>
>
>
>
> Summary: (?)
>
>
> *** Grunt thread exiting with 1 still active
>
>
>
>
> Private: (?)
>
>
> No
>
>
>
>
>
> After running a network test, dynamo continuosly
>
> outputs to console:
>
>
>
> *** Grunt thread exiting with 1 still active
>
> *** Grunt thread exiting with 1 still active
>
> *** Grunt thread exiting with 1 still active
>
>
>
> ...and locks up the GUI (iometer).
>
>
>
> Ctrl-C'ing dynamo is the only way to unlock it.
>
>
>
> Built with iometer-2004.07.30-post.DS2, Makefile-
>
> Linux.x86_64.
>
>
>
> Linux lablx000 2.4.21-27.EL #1 SMP Wed Dec 1
>
> 21:53:39 EST 2004 x86_64 x86_64 x86_64 GNU/Linux
>
>
>
> Any fixes for this?
>
>
>
> Thanks and please advise,
>
> Marc
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Followups:
>
>
>
> Comments
>
>
>
>
>
>
>
>
> Date: 2005-08-16 02:19Sender: cheungmingLogged In: YES user_id=896657  
this is caused by the bug fix on #1088486. the reason isthat a network io  
is differ from disk io. for diskio, theworker stops and then wait current  
io ends and quits, whichis pretty reasonable. but for network worker, it is  
possiblethat there is always 1 io unfinished for certain unknownreason,  
then it dead loop there.
>
>
>
>
>
>
>
> Date: 2005-07-27 13:36Sender: cheungmingLogged In: YES user_id=896657  
Thanks for reporting. I will check this once get time.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: David, Howard
>
> Sent: Monday, December 08, 2008
> 6:03 PM
>
> To:
> 'iom...@li...'
>
> Subject: IOMETER for Linux network
> measurement ... "Grunt thread exiting with 1 still active" errors
>
>
>
>
>
>
>
>
> We have been experimenting with IOMETER for Linux, for evaluating the
> interaction of power management with network traffic performance, and it  
works
> until we get into an endless loop of "*** Grunt thread exiting with 1
> still active". It's not a big deal if we get one of those messages
> when the IOMETER control function stops the test, but if we get hundreds  
of
> messages ... the resulting statistics are no good.
>
>
>
>
>
> Is anyone using IOMETER with Linux for network performance
> testing? Do any of you know who did this work most recently, at
> Intel? There was an Intel contractor hen...@in... back in
> 2004, but he's not here any more.
>
>
>
>
>
> I have not found another micro-benchmark that lets you shape the
> traffic, and observe the BW / average response / maximum response. If
> IOMETER has been replaced by something more recent, we would like to know  
that.
>
>
>
>
>
> Thank you,
>
>
> Howard David and Paul Drews
>
>
> Intel Corp. / Corporate Technology Group / Systems Technology Lab
>
>
>
>
>
>
>
>
>