ipw2100 - "Fatal interrupt. Scheduling firmware restart."
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
linux-source-2.6.22 (Baltix) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
/**** ATTENTION ****
I believe this issue is specific to the error that a chipset that is not 802.11G capable will return when it picks up an a beacon from a router that is not mixed-mode, but 802.11G specific. Please verify. Remove mixed-mode from your G routers, and see if you can get this repeated. Then add back mix mode and see if it goes away and if you're connected with 802.11B.
****/
[ Current Status ]
The ipw2100 driver was last updated on 2007-01-31. That tarball release contained an issues file that described this particular bug:
Firmware restart is detected randomly
-------
After running one or two days, Intel PRO/Wireless 2100 Network Connection
driver will only occasionally restart the firmware.
"ipw2100: Fatal interrupt. Scheduling firmware restart"
To resolve this problem, the system must be rebooted.
Defect #329
[ Original Description ]
Since I've upgrade to Breezy, ipw2100 driver no longer works and in dmesg I've
got plenty
"Fatal interrupt. Scheduling firmware restart."
I'm always able to do an iwlist :
% sudo iwlist eth1 scanning
eth1 Scan completed :
...
Cell 02 - Address: 00:07:CB:51:65:E0
But the card no longer register. It stays "unassociated" whatever I've tried :
% sudo iwconfig eth1 essid gaspard key open XXXXXXXXXX mode auto
% sudo iwconfig eth1
eth1 unassociated ESSID:"gaspard" Nickname:"ipw2100"
Bit Rate=0 kb/s Tx-Power:off
Retry min limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Sometimes, it works for a short time and after half an hour or an hour, it crash
again.
I've tried to upgrade ipw2100 and the firmware. No way.
Changed in linux-source-2.6.22: | |
status: | New → Confirmed |
status: | Confirmed → New |
Changed in intellinuxwireless: | |
status: | Unknown → In Progress |
Changed in linux: | |
status: | Unknown → Invalid |
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | New → Triaged |
status: | New → Invalid |
Changed in intellinuxwireless: | |
status: | In Progress → Unknown |
Changed in intellinuxwireless: | |
status: | Unknown → Confirmed |
affects: | linux (Ubuntu) → ipw2100 (Ubuntu) |
description: | updated |
Changed in intellinuxwireless: | |
status: | Confirmed → Unknown |
description: | updated |
Changed in intellinuxwireless: | |
importance: | Unknown → High |
status: | Unknown → In Progress |
no longer affects: | ipw2100 (Ubuntu) |
affects: | intellinuxwireless → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
importance: | High → Undecided |
status: | In Progress → New |
Changed in linux (Ubuntu): | |
status: | Incomplete → Invalid |
Changed in linux (Fedora): | |
importance: | Unknown → Medium |
no longer affects: | linux (Ubuntu) |
affects: | linux (Fedora) → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
importance: | Medium → Undecided |
status: | Invalid → New |
status: | New → Invalid |
If possible, please upgrade to Dapper's 2.6.15-7 kernel. If you do not want to
upgrade to Dapper, then you can also wait for the Dapper Flight 2 CD's, which
are due out within the next few days.
Let me know if this bug still exists with this kernel.