linux-kernel - Re: iwl3945: if I leave my machine running overnight, wifi will not work in the morning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 21 Oct 2008 21:43:24 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	jbenc@...e.cz, kernel list <linux-kernel@...r.kernel.org>,
	i.zhu@...el.com, reinette.chatre@...el.com,
	linux-wireless@...r.kernel.org, ipw3945-devel@...ts.sourceforge.net
Subject: Re: iwl3945: if I leave my machine running overnight, wifi will
	not work in the morning

On Tue 2008-10-21 21:40:31, Pavel Machek wrote:
> On Mon 2008-10-20 00:06:55, Pavel Machek wrote:
> > On Sun 2008-10-19 23:40:35, Pavel Machek wrote:
> > > Hi!
> > > 
> > > Kernel 2.6.27-rc8; happened few times already.
> > 
> > ...
> > > After reboot, network will work (I believe ;-).
> > 
> > Hmm, it did not this time.
> 
> Happened again...
> 
> root@amd:/mnt# ifconfig wlan0 down
> root@amd:/mnt# iwlist wlan0 scan
> Warning: Driver for device wlan0 has been compiled with version 22
> of Wireless Extension, while this program supports up to version 17.
> Some things may be broken...
> 
> wlan0     Interface doesn't support scanning : Network is down
> 
> root@amd:/mnt# ifconfig wlan0 10.0.0.6 up
> root@amd:/mnt# iwlist wlan0 scan
> Warning: Driver for device wlan0 has been compiled with version 22
> of Wireless Extension, while this program supports up to version 17.
> Some things may be broken...
> 
> wlan0     Scan completed :
>           Cell 01 - Address: 00:11:2F:0E:95:A0
>                     ESSID:"pavel"
>                     Mode:Master
>                     Channel:1
>                     Frequency:2.412 GHz (Channel 1)
>                     Quality=95/100  Signal level:-34 dBm  Noise
> level=-68 dBm
>                     Encryption key:off
>                     Bit Rate:1 Mb/s
>                     Bit Rate:2 Mb/s
>                     Bit Rate:5.5 Mb/s
>                     Bit Rate:11 Mb/s
>                     Bit Rate:6 Mb/s
>                     Bit Rate:9 Mb/s
>                     Bit Rate:12 Mb/s
>                     Bit Rate:18 Mb/s
>                     Bit Rate:24 Mb/s
>                     Bit Rate:36 Mb/s
>                     Bit Rate:48 Mb/s
>                     Bit Rate:54 Mb/s
>                     Extra:tsf=000000262894417f
>                     Extra: Last beacon: 76ms ago
> 
> root@amd:/mnt# iwconfig wlan0 essid pavel
> root@amd:/mnt# ping hobit
> PING hobit.ucw.cz (10.0.0.2): 56 data bytes
> ^C
> --- hobit.ucw.cz ping statistics ---
> 4 packets transmitted, 0 packets received, 100% packet loss
> root@amd:/mnt# 
> 
> 
> This time I tried rebooting the AP, but it did not help. dmesg says:
> 
> wlan0: No ProbeResp from current AP 00:11:2f:0e:95:a0 - assume out of
> range
> wlan0: deauthenticated
> iwl3945 0000:03:00.0: PCI INT A disabled
> iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> iwl3945 0000:03:00.0: restoring config space at offset 0x1 (was
> 0x100102, writing 0x100106)
> Registered led device: iwl-phy0:radio
> Registered led device: iwl-phy0:assoc
> Registered led device: iwl-phy0:RX
> Registered led device: iwl-phy0:TX
> wlan0: authenticate with AP 00:11:2f:0e:95:a0
> wlan0: authenticate with AP 00:11:2f:0e:95:a0
> wlan0: authenticated
> wlan0: associate with AP 00:11:2f:0e:95:a0
> wlan0: RX AssocResp from 00:11:2f:0e:95:a0 (capab=0x401 status=0
> aid=1)
> wlan0: associated
> wlan0: authenticate with AP 00:11:2f:0e:95:a0
> wlan0: authenticated
> wlan0: associate with AP 00:11:2f:0e:95:a0
> wlan0: RX ReassocResp from 00:11:2f:0e:95:a0 (capab=0x401 status=0
> aid=1)
> wlan0: associated
> wlan0: No ProbeResp from current AP 00:11:2f:0e:95:a0 - assume out of
> range
> wlan0: authenticate with AP 00:11:2f:0e:95:a0
> wlan0: authenticated
> wlan0: associate with AP 00:11:2f:0e:95:a0
> wlan0: RX ReassocResp from 00:11:2f:0e:95:a0 (capab=0x401 status=0
> aid=1)
> wlan0: associated
> root@amd:/mnt# 

reboot, and network is back.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/