From: Pavel Machek <pavel@suse.cz>
To: jbenc@suse.cz, kernel list <linux-kernel@vger.kernel.org>,
i.zhu@intel.com, reinette.chatre@intel.com,
linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net
Subject: Re: iwl3945: if I leave my machine running overnight, wifi will not work in the morning
Date: Tue, 21 Oct 2008 21:43:24 +0200 [thread overview]
Message-ID: <20081021194324.GA1811@elf.ucw.cz> (raw)
In-Reply-To: <20081021194031.GB17255@elf.ucw.cz>
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
next prev parent reply other threads:[~2008-10-21 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 21:40 iwl3945: if I leave my machine running overnight, wifi will not work in the morning Pavel Machek
2008-10-19 22:06 ` Pavel Machek
2008-10-21 19:40 ` Pavel Machek
2008-10-21 19:43 ` Pavel Machek [this message]
2008-10-21 20:13 ` reinette chatre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081021194324.GA1811@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=i.zhu@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=jbenc@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox