Subject: pkg/17843: net/wistumbler consumes LOTS of cpu if its interface vanishes
To: None <gnats-bugs@gnats.netbsd.org>
From: None <kre@munnari.OZ.AU>
List: netbsd-bugs
Date: 08/05/2002 15:23:11
>Number:         17843
>Category:       pkg
>Synopsis:       net/wistumbler consumes LOTS of cpu if its interface vanishes
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 05 01:30:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Robert Elz
>Release:        NetBSD 1.5ZC
>Organization:
	Prince of Songkla University
>Environment:
	
	
System: NetBSD delta.cs.mu.OZ.AU 1.5ZC NetBSD 1.5ZC (DELTA) #4: Mon May 27 23:17:55 ICT 2002 kre@delta.cs.mu.OZ.AU:/usr/src/sys.X/arch/i386/compile/DELTA i386
Architecture: i386
Machine: i386
>Description:
	If you have net/wistumbler running, and detach the interface
	it is using, then it goes into a CPU loop (looks to be a heavy
	syscall CPU loop).   That is, simply pop the PCMCIA card that
	is wi0...

>How-To-Repeat:
	First fix (or work around) pkg/17842 so net/wistumbler can be
	compiled.   Compile and install it.   Run it on a wireless card
	that can be removed.   Remove the card.   Observe wistumbler
	using large amounts of CPU time, and the rest of the system being
	very sluggish.
>Fix:
	Sorry, this one isn't important enough to go hunting for
	(easy workaround is to kill wistumbler before popping the card,
	killing it after it loops is also pretty easy).
>Release-Note:
>Audit-Trail:
>Unformatted: