[Bug 464805] New: WLAN Firmware errors with 11.1
https://bugzilla.novell.com/show_bug.cgi?id=464805 Summary: WLAN Firmware errors with 11.1 Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: axel.braun@gmx.de QAContact: qa@suse.de Found By: --- Hi, I'm running since about 3 years Linux on the ThinkPad Z60m, an I upgraded from 10.3 to 11.1 beginning of the year. Since then I get frequent firmware errors: Jan 7 12:23:48 z60m dhclient: DHCPACK from 192.168.1.1 Jan 7 12:23:48 z60m dhclient: bound to 192.168.1.35 -- renewal in 1541 seconds. Jan 7 12:40:25 z60m kernel: ipw2200: device failed to start within 500ms Jan 7 12:40:25 z60m kernel: ipw2200: Unable to load firmware: -62 Jan 7 12:40:25 z60m kernel: ipw2200: Failed to up device Or Jan 9 12:15:15 z60m dhclient: DHCPACK from 192.168.1.1 Jan 9 12:15:15 z60m dhclient: bound to 192.168.1.33 -- renewal in 1557 seconds. Jan 9 12:21:28 z60m kernel: ipw2200: Firmware error detected. Restarting. Jan 9 12:21:29 z60m kernel: ipw2200: Firmware error detected. Restarting. Jan 9 12:41:12 z60m dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 Jan 9 12:41:12 z60m dhclient: DHCPACK from 192.168.1.1 The later message is uncritical, the first one requires a reboot to get the WLAN up and running again. Just switching it off is not sufficient -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c1
--- Comment #1 from Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c2
--- Comment #2 from Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c3
--- Comment #3 from Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c4
--- Comment #4 from Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
Robert Vojcik
https://bugzilla.novell.com/show_bug.cgi?id=464805
Greg Kroah-Hartman
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c5
--- Comment #5 from Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User kkeil@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c6
Karsten Keil
https://bugzilla.novell.com/show_bug.cgi?id=464805
User jslaby@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c7
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=464805
User jslaby@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c8
--- Comment #8 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c9
Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User jslaby@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c10
--- Comment #10 from Jiri Slaby
I get these errors with the new kernel as well:
I suppose the device gets stuck too? In that case I don't understand, since old kernel contains a driver from 10.3. Could you recheck with 10.3 kernel: ftp://ftp.suse.com/pub/projects/kernel/kotd/SL103_BRANCH/i386/ that the problem isn't there with 11.1 system? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=464805
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c11
--- Comment #11 from Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c12
Axel Braun
(In reply to comment #9)
I get these errors with the new kernel as well:
I suppose the device gets stuck too?
yes... unfortunately the same problem: Feb 20 21:21:55 z60m kernel: ipw2200: Firmware error detected. Restarting. Feb 20 21:21:56 z60m kernel: ipw2200: Firmware error detected. Restarting. Feb 20 21:25:53 z60m dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 Feb 20 21:25:58 z60m dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 Feb 20 21:26:12 z60m dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 Feb 20 21:26:12 z60m dhclient: DHCPACK from 192.168.1.1 Feb 20 21:26:12 z60m dhclient: bound to 192.168.1.33 -- renewal in 1435 seconds. [...] Feb 20 22:14:22 z60m dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 Feb 20 22:14:22 z60m dhclient: DHCPACK from 192.168.1.1 Feb 20 22:14:22 z60m dhclient: bound to 192.168.1.33 -- renewal in 1603 seconds Feb 20 22:27:28 z60m avahi-daemon[3296]: Withdrawing address record for 192.168.1.33 on eth1. Feb 20 22:27:28 z60m avahi-daemon[3296]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.1.33. (k)networkmanager still shows full connection, but that is a different story. Is the firmware shipped with the 11.1 kernel the same as the one with 10.3? Could this be a hardware-problem then? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
User jslaby@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c13
Jiri Slaby
Is the firmware shipped with the 11.1 kernel the same as the one with 10.3?
Helmut, any ideas here, please? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c14
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c15
--- Comment #15 from Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c16
Axel Braun
Just exchange "options ipw2200 hwcrypto=0 led=1 associate=0" with "options ipw2200 hwcrypto=0 led=0 associate=0".
No change in results...still FW errors. And the LED is still blinking...
Another question: what type of AP are you using? Is it already 11n capable?
I doubt that. It is sold as Arcor 200 DSL Modem, in fact it is s Zyxel Modem: ZyNOS Firmware-Version: V3.40(AHS.0) | 4/7/2006 DSL Firmware-Version:DMT FwVer: 3.5.10.0_B_TC, HwVer: T14F7_1.0 Standard:ADSL_G.dmt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c17
Helmut Schaa
(In reply to comment #14)
Just exchange "options ipw2200 hwcrypto=0 led=1 associate=0" with "options ipw2200 hwcrypto=0 led=0 associate=0".
No change in results...still FW errors. And the LED is still blinking...
Did you reload the module after editing modprobe file? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c18
Axel Braun
Did you reload the module after editing modprobe file? I rebooted, as I changed the kernel back to 2.6.27.7-9-default
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
User jslaby@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c19
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c20
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
User jslaby@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c21
Jiri Slaby
Jiri, are you going to build a kernel with ipw2200 debugging enabled for Axel?
Yes, ready at: http://labs.suse.cz/jslaby/bug-464805/ Axel, could you try it with the debug enabled as written in comment #20? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c22
Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c23
--- Comment #23 from Helmut Schaa
Mar 7 23:03:07 z60m kernel: ipw2200: I ipw_handle_missed_beacon Missed beacon: 9 - initiate roaming
Ok, here the driver recognizes 9 missed beacons and tries to initiate roaming, which triggers a scan.
Mar 7 23:03:12 z60m kernel: ipw2200: U ipw_scan_check Scan completion watchdog resetting adapter after (5000ms).
The scan did not finish after 5 seconds. Hence, the driver thinks the card is stuck and triggers a restart. I'm not sure why the scan did not finish within 5 seconds. I counted 18 scan notifications (=#scanned channel) on 11a channels which should not be more than 18 * 120 <= 3 sec. However, the ipw2200 firmware does some scan magic and switches back to the operating channel once in a while. That could explain the timeout.
Mar 7 23:03:12 z60m kernel: ipw2200: Firmware error detected. Restarting.
I guess this one can safely be ignored as it happens during adapter shutdown. Jiri, my suggestion is to simply increase the IPW_SCAN_CHECK_WATCHDOG to something around 10 seconds. I already made such a patch a while ago (see [1]) but it turned out to be a different issue (see [2]) and thus I dropped that patch again. [1] http://sourceforge.net/mailarchive/forum.php?thread_name=200811251809.55461.helmut.schaa%40gmail.com&forum_name=ipw2100-devel [2] http://sourceforge.net/mailarchive/forum.php?thread_name=200811261805.39953.helmut.schaa%40gmail.com&forum_name=ipw2100-devel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c24
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c25
Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c26
Helmut Schaa
There are tons of other WLAN/different SSID around, but only one AP to which I have access.
So, I guess you are not moving around that much ;) Hmm, ok, that means when the scenario described in comment #23 happens 1) the signal strength is horrible (9 consecutive missed beacons is really bad) 2) or something jams your signal once in a while 3) or there are too much APs interfering with yours Apart from the firmware restarts, is your signal strong and do you get good throughput? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c27
Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c28
--- Comment #28 from Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
User jslaby@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c29
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c30
Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c31
--- Comment #31 from Helmut Schaa
Mar 10 19:35:22 z60m kernel: ipw2200: I ipw_handle_missed_beacon Missed beacon: 1
[...]
Mar 10 19:35:23 z60m kernel: ipw2200: I ipw_handle_missed_beacon Missed beacon: 9 - initiate roaming
[...]
Mar 10 19:35:24 z60m kernel: ipw2200: I ipw_handle_missed_beacon Missed beacon: 25 - disassociate
[...]
Mar 10 19:35:24 z60m kernel: ipw2200: U ipw_send_disassociate Disassocation attempt from 00:13:49:9a:e6:93 on channel 6.
Unfortunately, there's no valuable debug output before this beacon-miss storm happens. I'm not sure if it is the firmware/driver here that misbehaves or if there something jams your wireless signal or your AP behaves incorrect. The only way to be sure that beacons still arrive but are dropped by the firmware would be to sniff the traffic with a seconds wireless card while ipw2200 prints the messages about beacon misses. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c32
--- Comment #32 from Axel Braun
The only way to be sure that beacons still arrive but are dropped by the firmware would be to sniff the traffic with a seconds wireless card while ipw2200 prints the messages about beacon misses.
You mean with kismet or something? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c33
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c34
Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c35
--- Comment #35 from Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c36
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c37
--- Comment #37 from Axel Braun
Hmm, unfortunately the wireshark dump does not contain any frames sent by your AP. Seems like you've sniffed the ethernet port :)
Hm...I used a second machine, and saw at least some packets from the 192.168.1.* network...anyway, will try again, probably on the weekend. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c38
--- Comment #38 from Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c39
--- Comment #39 from Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c40
--- Comment #40 from Axel Braun
Of course the channel has to be set to the same as your AP is using: - iwconfig wlan1 channel X
How can I find out which channel is used by the AP? Thx! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c41
--- Comment #41 from Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c42
Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c43
Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c45
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c46
Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c47
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c48
--- Comment #48 from Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=464805
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c49
--- Comment #49 from Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=464805
User axel.braun@gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=464805#c50
--- Comment #50 from Axel Braun
participants (1)
-
bugzilla_noreply@novell.com