[Bug 24776] Re: ipw2100 - "Fatal interrupt. Scheduling firmware restart."
mike at himikeb.com
Tue Mar 10 14:47:52 UTC 2009
I am now using Intrepid 2.6.27-11-generic and the ipw2100 driver IS
In a recent, previous 2.6.27 version of the kernel, it was NOT working.
But prior to that, it WAS working. So... something about this drive is
Hopefully, this is some sort of clue to the problem.
From: ekul <ekul.taylor at gmail.com>
Reply-to: Bug 24776 <24776 at bugs.launchpad.net>
To: mike at himikeb.com
Subject: [Bug 24776] Re: ipw2100 - "Fatal interrupt. Scheduling firmware
Date: Mon, 09 Mar 2009 20:27:08 -0000
In Jaunty Alpha 5 I have begun experiencing this issue.
Kernel Version: 2.6.28-8-generic
Driver Version: git-1.2.2
Firmware Version: 1.3
Relevant lines from dmesg:
[ 15.544529] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
[ 15.544539] ipw2100: Copyright(c) 2003-2006 Intel Corporation
[ 15.636680] ipw2100 0000:02:03.0: PCI INT A -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5
[ 15.637801] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
[ 15.637832] ipw2100 0000:02:03.0: firmware: requesting ipw2100-1.3.fw
[ 34.905219] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 34.905557] ipw2100: eth1: firmware fatal error
[ 69.105320] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 69.105751] ipw2100: eth1: firmware fatal error
[ 598.267625] ipw2100: Fatal interrupt. Scheduling firmware restart.
There doesn't seem to be a particular set of circumstances that cause
the issue (unlike the attached bugzilla report which seems to be
triggered by traffic). This issue has been happening while the only
network application active is pidgin. Sometimes it happens once every 2
or 3 minutes, other times it seems t go for several hours without
I have been running the alpha for quite some time and this seems to be a
recent issue. I will try downgrading to and earlier jaunty kernel
release to see if this still happens
ipw2100 - "Fatal interrupt. Scheduling firmware restart."
You received this bug notification because you are a member of Kernel
Bugs, which is a direct subscriber.
More information about the kernel-bugs