Reinhard Tartler ha scritto:
This does only say that Linux couldn't schedule the wpasupplicant
process for more than 61s. This is not an sufficiant indication that the
wpa_supplicant process is at fault here.
TBH, I think this is more an user configuration or hardware
problem. Most probably your wifi driver got stuck for some reason. If
you agree, please close this bug or reassign to package containing the
wifi driver you are using.
I am reluctant to agree because it happens also when wpa_supplicant is
not running and the wifi device is turned off. A very common effect of
this type of crash is that the JFS filesystem creates a 'stale NFS file'
at /etc/mtab (I suppose failing to delete it), but the filesystem is
marked as clean so I have to force a fsck to fix it (root filesystem
won't mount without being able to write to /etc/mtab).
Does the backtrace tell anything relevant?
Perhaps we need serial console output?
I agree that the wpasupplicant is not responsible anyway.
Package: linux-image-2.6.28-1-686
Version: 2.6.28-1
Best regards,
--
Daniele C.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
