Your message dated Sat, 27 Dec 2008 10:15:12 GMT
with message-id <[email protected]>
and subject line waproamd has been removed from Debian, closing #281275
has caused the Debian Bug report #281275,
regarding Deadlocks on PCMCIA insert
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
281275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=281275
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: waproamd
Version: 0.6-4
Severity: normal
If I insert a Cisco Aironet 352 card, cardmgr detects it and loads the
airo and airo_cs modules. This generates a hotplug event which causes
/etc/hotplug.d/net/waproamd.hotplug to start a waproamd process for the
new interface. Waproamd starts and hangs after printing "Scanning...".
I am not able to kill the waproamd process, even with "kill -9". Only
if I kill -9 both waproamd and cardmgr am I able to clean things up.
This doesn't happen every time. It happens most frequently after APM
suspend and resume, but even then, not every time. Adding "sleep"
commands in various places did not help.
My guess is that waproamd is blocking on some lock that is held by
something upstream in the cardmgr->hotplug chain.
I have found that running waproamd via "at" solves the problem:
--- waproamd.hotplug_ORIG 2004-05-13 18:52:15.000000000 +0200
+++ waproamd.hotplug 2004-11-03 13:29:14.000000000 +0100
@@ -31,7 +31,7 @@
for IF in $HOTPLUG_INTERFACES ; do
if [ "$INTERFACE" = "$IF" -o "$IF" = "all" ] ; then
debug_mesg Invoking $DAEMON_NAME for $INTERFACE
- /etc/init.d/$DAEMON_NAME start $INTERFACE
+ echo "/etc/init.d/$DAEMON_NAME start $INTERFACE" | at
now
break
fi
done
Using "start-stop-daemon --start --background" to run the initscript
did not fix the problem.
If you choose not to apply this patch then I suggest tagging this
report "wontfix" and leaving it open so that others are made aware
of this solution.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1
Locale: lang=en...@euro, lc_ctype=en...@euro
Versions of packages waproamd depends on:
ii debconf 1.4.32 Debian configuration management sy
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libdaemon0 0.6-1 lightweight C library for daemons
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Version: 0.6-9+rm
The waproamd package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/509389 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
http://Marco.Tondela.org
--- End Message ---
