Bug 149968
Summary: | ipw2100 wifi driver dies at random | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | uche.ogbuji |
Component: | kernel | Assignee: | John W. Linville <linville> |
Status: | CLOSED CANTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | davej, dlr, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
URL: | http://www.bughost.org/bugzilla/show_bug.cgi?id=245 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-01-09 19:30:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
uche.ogbuji
2005-03-01 01:57:36 UTC
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. Yes, I upgraded to FC4 (of course :-) ), and the problem persists, although with much lower frequency (every few days now, which is tolerable). The big improvement came when I replaced my access point, however, rather than the upgrade to FC4. I do believe that the former frequency of the problem was the result ogf a bug in the AP triggering a bug in the kernel. Anyway, my updated kernel version is 2.6.11-1.1369_FC4. I see that 2.6.12-1.1398_FC4 is now out. I shall try that and report back, though it may take a few days because I have to see that it stays alive long enough. Thanks. 2.6.14-1.1637_FC4 has been released as an update for FC4. Please retest with this update, as a large amount of code has been changed in this release, which may have fixed your problem. Thank you. I have just tested with both kernels 2.6.13-1.1526_FC4 and 2.6.14-1.1644_FC4, and the problem still exists. I just upgraded the kernel now to check if it helped, but no such luck. My environment: I'm sitting in an office building where the laptop can "see" 3 different AP's on the same network/SSID - one is quite strong (signal 70/100), and the other two are quite weak (signal 10-25/100). The connection dies very quickly if I utilise it, say by rsyncing a lot of data across the wireless net, and then the error message "ipw2100: fatal interrupt, scheduling firmware restart" starts cluttering my dmesg-buffer. Cheers, Kenneth The Fedora-netdev kernels are available here: http://people.redhat.com/linville/kernels/fedora-netdev/ Please give those a try to see if any later patches help this issue, and post the results here...thanks! BTW, please also make sure you are using the latest firmware from the sourceforge project's page: http://ipw2100.sourceforge.net/firmware.php Closed due to lack of response. Please reopen when the requested information becomes available...thanks! I'm seeing similar symptoms with a "Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)" Thinkpad T-41 on Fedora Core 4. Around the time of the crash ("fixable" per the original comment in this issue with ifup/ifdown iff I'm right next to my access point), I get the following in /var/log/messages: Apr 12 08:59:55 localhost kernel: ipw2100: ipw2100: Fatal interrupt. Scheduling firmware restart. I've tried the following kernels, all of which exhibit this problem: 2.6.16-1.2069_FC4 2.6.12-1.1390_FC4 2.6.11-1.1369_FC4 I've got the ipw2100 1.3 firmware installed. FWIW, most of the packages on my Fedora Core 4 installed have been updated to the latest stable release available (via yum). I believe I've provided a response to the last question by Dave Jones. I request that this bug be REOPENED. Note that the corresponding upstream ipw2100 bug remains ASSIGNED (open) as well: http://www.bughost.org/bugzilla/show_bug.cgi?id=245 I don't particularly relish the idea of installed a netdev kernel on this machine (suggested by John Linville), as I use it for the day job. Is there anything else I can do to help? Thanks, Dan At a superficial level, upstream bug <http://www.bughost.org/bugzilla/show_bug.cgi?id=329> appears related, too. (It's also documented as a known issue by Intel in their ipw2100 driver release tarball.) |