Ubuntu
linux-source-2.6.20 package

  1. Bug #109887
  2. Comment #15

Comment 15 for bug 109887

Revision history for this message
Søren Boll Overgaard (boll-fork) wrote :

I can confirm this error on a Lenovo Thinkpad X61s. The error occurs at random intervals between 30 minutes and 12 hours after boot. It is necessary to reboot the system to fix the lockup.

~$ lspci | grep -i wireless
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
~$

The log shows this:
[ 3115.204000] ipw3945: Error sending cmd #07 to daemon: time out after 500ms.
[ 3117.120000] ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
[ 3117.620000] ipw3945: Error sending cmd #08 to daemon: time out after 500ms.
[ 3118.120000] ipw3945: Error sending ADD_STA: time out after 500ms.
[ 3118.620000] ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
[ 3177.620000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
[ 3178.120000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
[ 4640.996000] ADDRCONF(NETDEV_UP): eth0: link is not ready

~$ uname -a
Linux diablo 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

I am running Gutsy, and never saw this problem with feisty. If you need additional information, please let me know.