ipw2100: Fatal interrupt. Scheduling firmware restart. on linux-image-2.6.27-7-generic

[ozstriker78]

Binary package hint: linux-image-2.6.27-7-generic

This bug is existence in all prior kernels. I'm creating it for this kernel via special request....

  283.784411] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
[ 283.784437] ipw2100: Copyright(c) 2003-2006 Intel Corporation
[ 283.787724] ipw2100 0000:02:02.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
[ 283.789176] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
[ 283.791363] firmware: requesting ipw2100-1.3.fw
[ 284.121270] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 296.431991] NET: Registered protocol family 17
[ 297.529326] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 298.500750] ieee80211_crypt: registered algorithm 'TKIP'
[ 316.240026] eth1: no IPv6 routers present
[ 976.205583] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 3696.786552] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 4106.379929] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 4181.439050] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 4592.088222] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 4800.951337] ipw2100: Fatal interrupt. Scheduling firmware restart.

[Leann Ogasawara (leannogasawara)]

Hi ozstriker78,

I assume you have the linux-firmware package installed? Recently the firmware files were moved to that package. I know there were some issue with peoples wireless drivers not working due to missing firmware but it was because they hadn't had the linux-firmware package installed.

Also, does your wireless not work due to these errors? How often do the errors appear? Are you doing anything specifically when they appear? Do they reappear if you unload/reload the driver? Thanks.

[ozstriker78 (ozstriker78)]

The wireless does work. The resets tend to happen more often when I am
transfering data. I'm wondering if it is a bug in the firmware
because an IRQ call shouldn't trigger a device reset, in my mind
anyway.

Thoughts?

On 10/23/08, Leann Ogasawara <email address hidden> wrote:
> Hi ozstriker78,
>
> I assume you have the linux-firmware package installed? Recently the
> firmware files were moved to that package. I know there were some issue
> with peoples wireless drivers not working due to missing firmware but it
> was because they hadn't had the linux-firmware package installed.
>
> Also, does your wireless not work due to these errors? How often do the
> errors appear? Are you doing anything specifically when they appear?
> Do they reappear if you unload/reload the driver? Thanks.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> ipw2100: Fatal interrupt. Scheduling firmware restart. on
> linux-image-2.6.27-7-generic
> https://bugs.launchpad.net/bugs/285943
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Sent from Google Mail for mobile | mobile.google.com

[iponeverything (cookema)]

I am seeing this also. Can connect, but have resets during transfers.

Is this bug related to: Bug #24776

[kernel-janitor (kernel-janitor)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Martin (martin22)]

Still occurs on Ubuntu 12.04. In my case, a workaround is to disable mode 802.11n on the access point.

[penalvch (penalvch)]

ozstricker78, thank you for reporting this bug to Ubuntu. Intrepid reached EOL on April 30, 2010.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this an issue in a supported release? If so, could you please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 285943

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]