Bugzilla – Bug 1119
the ipw3945d daemon and left-behind pid files
Last modified: 2008-12-08 22:11:04
You need to log in before you can comment on or make changes to this bug.
As Mike Frysinger reported in http://bugs.gentoo.org/show_bug.cgi?id=140067, the ipw3945d regulatory daemon doesn't check if there is a pid-file left from a hardlock. As also stated by Mike, this is pretty simple to reproduce: # rm -f /var/run/ipw3945d.pid (from a previous run) # modprobe ipw3945 # killall ipw3945d # rmmod ipw3945 # modprobe ipw3945 2006-07-19 14:28:21: ERROR: ipw3945d already running. If ipw3945d is not running then you need to remove '/var/run/ipw3945d.pid' and try again. FATAL: Error running install command for ipw3945 I would suggest something like this to solve this issue (within the daemon): - open the pid-file - determine the pid - check if /proc/<pid> is a) existing and b) a directory - check if the cmdline matches the path/name of the executeable
ipw3945 as a driver has been replaced by iwl3945 in official kernel for a long time. We suggest to use iwl3945 driver instead of the obsolete ipw3945 driver. If you have bug, please report it with product=iwlwifi and platform="Intel(R) Wifi Link 3945". Thanks so much!