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: iwl3945: if I leave my machine running overnight, wifi will not work in the morning
Date: Sun, 19 Oct 2008 23:40:37 +0200 [thread overview]
Message-ID: <20081019214035.GA30485@elf.ucw.cz> (raw)
Hi!
Kernel 2.6.27-rc8; happened few times already.
root@amd:~# ifconfig wlan0 down
root@amd:~# SysRq : Changing Loglevel
Loglevel set to 9
root@amd:~# ifconfig wlan0 up
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
root@amd:~# 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
root@amd:~# ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2): 56 data bytes
wlan0: deauthenticated
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
^C ##### ping will not reply.
--- 10.0.0.2 ping statistics ---
23 packets transmitted, 0 packets received, 100% packet loss
root@amd:~#
#### iwlist works:
root@amd:~# 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=43/100 Signal level:-83 dBm Noise
level=-99 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
...
root@amd:~# iwconfig wlan0 essid pavel
root@amd:~# 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:~# ping hobit
PING hobit.ucw.cz (10.0.0.2): 56 data bytes
^C
--- hobit.ucw.cz ping statistics ---
34 packets transmitted, 0 packets received, 100% packet loss
root@amd:~#
Is there documentation of
/sys/module/iwl3945/drivers/pci:iwl3945/{un,}bind somewhere? I believe
that's the next step, but could not figure it out.
After reboot, network will work (I believe ;-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next reply other threads:[~2008-10-19 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 21:40 Pavel Machek [this message]
2008-10-19 22:06 ` iwl3945: if I leave my machine running overnight, wifi will not work in the morning Pavel Machek
2008-10-21 19:40 ` Pavel Machek
2008-10-21 19:43 ` Pavel Machek
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=20081019214035.GA30485@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