[Bug 24776] Re: ipw2100 - "Fatal interrupt. Scheduling firmware restart."
axet (axet-l), this report has been closed since 2017. Hence, it is not scoped to you, or your problem. If you would like your problem addressed, it will help immensely if you use Ubuntu with the computer the problem is reproducible with and file a new report via a terminal to provide necessary debugging logs: ubuntu-bug linux Please feel free to subscribe me to it. ** Attachment removed: "dmesg.log" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/5271053/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - "Fatal interrupt. Scheduling firmware restart." To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - "Fatal interrupt. Scheduling firmware restart."
I have same issue here in 2019. 01:04.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04) M3N notebook 4.15.0-51-generic Ubuntu 18.04.2 LTS a lot of: [11414.173675] ipw2100: Fatal interrupt. Scheduling firmware restart. [12674.408121] ipw2100: Fatal interrupt. Scheduling firmware restart. [64189.132057] ipw2100: wlp1s4: Firmware did not initialize. [64189.132061] ipw2100: wlp1s4: Failed to start the firmware. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/5271053/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - "Fatal interrupt. Scheduling firmware restart." To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - "Fatal interrupt. Scheduling firmware restart."
** No longer affects: linux (Ubuntu) ** Package changed: linux (Fedora) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Medium => Undecided ** Changed in: linux (Ubuntu) Remote watch: Red Hat Bugzilla #149968 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - "Fatal interrupt. Scheduling firmware restart." To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - "Fatal interrupt. Scheduling firmware restart."
** Changed in: linux (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - "Fatal interrupt. Scheduling firmware restart." To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - "Fatal interrupt. Scheduling firmware restart."
Update: It's better to leave the wifi card slot uncovered. When the cover is screwed, it pushes the card that heels a little and probably the "Stradivari" loses the tuning. Some additional info: Linux Mint 13 Maya on a Dell Latitude D600. sudo lshw -C Network *-network:0 description: Ethernet interface product: NetXtreme BCM5705M Gigabit Ethernet vendor: Broadcom Corporation physical id: 0 bus info: pci@:02:00.0 logical name: eth0 version: 01 serial: xx:xx:xx:xx:xx:xx capacity: 1Gbit/s width: 64 bits clock: 66MHz capabilities: pm vpd msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.121 firmware=5705-v3.16 latency=32 link=no mingnt=64 multicast=yes port=twisted pair resources: irq:11 memory:faff-faff *-network:1 description: Wireless interface product: PRO/Wireless LAN 2100 3B Mini PCI Adapter vendor: Intel Corporation physical id: 3 bus info: pci@:02:03.0 logical name: eth1 version: 04 serial: xx:xx:xx:xx:xx:xx width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ipw2100 driverversion=git-1.2.2 firmware=712.0.3:3:0001 ip=192.168.1.100 latency=32 link=yes maxlatency=34 mingnt=2 multicast=yes wireless=IEEE 802.11b resources: irq:5 memory:fafef000-fafe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - "Fatal interrupt. Scheduling firmware restart." To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - "Fatal interrupt. Scheduling firmware restart."
Not the most elegant solution but I extracted the WIFI Card Intel 2100 from my Dell D600, inserted it again in the slot and now I'm sending this message with a wireless connnection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - "Fatal interrupt. Scheduling firmware restart." To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - "Fatal interrupt. Scheduling firmware restart."
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - "Fatal interrupt. Scheduling firmware restart." To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - "Fatal interrupt. Scheduling firmware restart."
ApportVersion: 2.14.1-0ubuntu3.16 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas2018 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=9503db82-5fc2-4130-b02e-7a584bf7bd5b InstallationDate: Installed on 2015-10-20 (0 days ago) InstallationMedia: Linux Mint 17.2 "Rafaela" - Release i386 20150723 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Computer Corporation Inspiron 500m Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic root=UUID=27afd31f-e8a5-4c30-a0f6-9294c393b487 ro forcepae quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.16.0-38-generic N/A linux-backports-modules-3.16.0-38-generic N/A linux-firmware 1.127.12 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: rafaela Uname: Linux 3.16.0-38-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare sudo tape video _MarkForUpload: True dmi.bios.date: 10/15/2003 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A06 dmi.board.name: 04Y212 dmi.board.vendor: Dell Computer Corporation dmi.chassis.type: 8 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA06:bd10/15/2003:svnDellComputerCorporation:pnInspiron500m:pvr:rvnDellComputerCorporation:rn04Y212:rvr:cvnDellComputerCorporation:ct8:cvr: dmi.product.name: Inspiron 500m dmi.sys.vendor: Dell Computer Corporation ** Tags added: apport-collected rafaela -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - "Fatal interrupt. Scheduling firmware restart." To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - "Fatal interrupt. Scheduling firmware restart."
Nicolas Fischmeister, if you have bug in Ubuntu (not Mint), it will help immensely if you filed a new report via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. ** Tags removed: apport-collected rafaela ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/4501716/+files/WifiSyslog.txt ** Attachment removed: "UdevLog.txt" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/4501715/+files/UdevLog.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/4501714/+files/UdevDb.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/4501713/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/4501712/+files/ProcInterrupts.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/4501711/+files/ProcCpuinfo.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/4501710/+files/Lspci.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/4501709/+files/IwConfig.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/4501707/+files/CurrentDmesg.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/4501706/+files/CRDA.txt ** Attachment removed: "BootDmesg.txt" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/4501705/+files/BootDmesg.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/4501704/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - "Fatal interrupt. Scheduling firmware restart." To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Nicolas Chuche, thank you for reporting this bug to Ubuntu. Breezy reached EOL on April 13, 2007. 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 24776 ** No longer affects: ipw2100 (Ubuntu) ** Project changed: intellinuxwireless = linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: High = Undecided ** Changed in: linux (Ubuntu) Status: In Progress = New ** Changed in: linux (Ubuntu) Remote watch: Bughost.org tracker #329 = None ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: New = Incomplete ** No longer affects: linux-source-2.6.15 (Ubuntu) ** No longer affects: linux-source-2.6.22 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - Fatal interrupt. Scheduling firmware restart. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
A similar problem still occurs August 2014 on Lubuntu 14.04.1: I can't connect to my dd-wrt router running an (older WEP secured) mixed-NG access point. As with some of the above solutions, switching my router from NG-mixed to BG-mixed solves the problem, allowing me to connect to my router using the problematic wireless interface, but I have some newer devices that can't connect to BG-mixed access points so I'd like to make changes on the device side rather than on the router side. I've also tried the NDISWrapper solution using the inf files here: https://downloadcenter.intel.com/SearchResult.aspx?lang=engProdId=944 (and I made sure ipw2100 isn't loaded and ndiswrapper is). The device works like the native linux driver, but the problem remains. I should note the linux-firmware package in the Ubuntu repository contains the latest firmware, which is good given the official host http://ipw2100.sourceforge.net/firmware.php has a dead link for the download. It's unfortunate that this bug is still unsolved after nearly 10 years. My HP Pavilion zt3000 is an amazing laptop even in 2014 and still has many more years of life ahead of it. So my long-term solution is to use a small, low-cost USB nano wifi adapter and ignore the internal interface. Not ideal, but it gets the job done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - Fatal interrupt. Scheduling firmware restart. To manage notifications about this bug go to: https://bugs.launchpad.net/intellinuxwireless/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Actually Intel PRO/Wireless 2100 runs only 802.11b. I don't know why a 802.11b interface can detect the NG-mixed mode access point and fails authentication BUT gives no clear error message. It was very misleading that it was incompatible hardware. (The options are to change to BG-mixed AP, or replace the interface with either a Intel PRO/Wireless 2200/similar internal 802.11bg card, or more cost effective a USB wifi adapter. I'm going with the USB adapter) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - Fatal interrupt. Scheduling firmware restart. To manage notifications about this bug go to: https://bugs.launchpad.net/intellinuxwireless/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Still occurs on Ubuntu 12.04. In my case, a workaround is to disable mode 802.11n on the access point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - Fatal interrupt. Scheduling firmware restart. To manage notifications about this bug go to: https://bugs.launchpad.net/intellinuxwireless/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Upgraded to Mint 13 and the wireless no longer works at all. In fact Fn F5 which used to turn it on and off with a light lit/unlit displaying the state never lights up no matter how often I reboot or press the Fn F5 keys. The only Internet access I have/had when using that computer is via wireless. Is this problem likely to be solvable? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - Fatal interrupt. Scheduling firmware restart. To manage notifications about this bug go to: https://bugs.launchpad.net/intellinuxwireless/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Same problem here, and sometimes I go for a couple of weeks with no disconnects and then out of the blue they start occurring every 1-2 minutes. I'm running Linux Mint 11 on an IBM ThinkPad R40, using Wicd instead of Network Manager, and have to keep Wicd open to click on the connect button when necessary, which can be quite often. I see this bug report began in 2005, any chance it might ever be resolved? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - Fatal interrupt. Scheduling firmware restart. To manage notifications about this bug go to: https://bugs.launchpad.net/intellinuxwireless/+bug/24776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
** Changed in: intellinuxwireless Status: Unknown = In Progress ** Changed in: intellinuxwireless Importance: Unknown = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/24776 Title: ipw2100 - Fatal interrupt. Scheduling firmware restart. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I have these log entries on my IBM Thinkpad T40. More of them occur during heavy networking. As adviced by Stefan in #65 I checked the IRQ settings in BIOS. (I believe they were under PCI settings). They all were on IRQ11, too. And I changed all of them to Auto. Additionally I turned off peripherials, which I never use (serial, parallel and infrared). The effect was that the following 4 devices switched from IRQ 11 to IRQ 5 (checked using the lspci command) - 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01) - 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01) - 0:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01) - 02:00.1 CardBus bridge: Texas Instruments PCI1520 PC card Cardbus Controller (rev 01) The fatal interrupts for the ipw2100 (which is still on IRQ 11) do still appear. Maybe they appear somewhat less frequently than before. I have not made any really statistics. Kubuntu Lucid 10.04 with all updates. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Unfortunately my BIOS does not have the option to choose the IRQ and so I cannot confirm this. But perhaps this is a good hint for the developers of ipw2100 to check the IRQ auto-configuration? -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Most time I use a wired connection at home, but now, on hollidays, I experimented again with ipw2100 and found out: my bios-settings where IRQ11 for all interrupts. So I changed them in the BIOS from 11 to 'AUTO', and now it works. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
10.04 Lucid and Thinkpad T41 [ 18.540905] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2 [ 18.540911] ipw2100: Copyright(c) 2003-2006 Intel Corporation [ 18.548532] ipw2100 :02:02.0: PCI INT A - Link[LNKC] - GSI 11 (level, low) - IRQ 11 [ 18.549501] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection [ 18.549526] ipw2100 :02:02.0: firmware: requesting ipw2100-1.3.fw [ 20.110934] ipw2100: Fatal interrupt. Scheduling firmware restart. [ 55.331196] ipw2100: Fatal interrupt. Scheduling firmware restart. [ 112.325813] ipw2100: Fatal interrupt. Scheduling firmware restart. [ 1598.111660] ipw2100: Fatal interrupt. Scheduling firmware restart. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
This is a very old bug and I don't think it will ever get fixed. I have been using ndiswrapper with the windows drivers (with ipw2100 blacklisted) with very good results and very few problems: http://downloadcenter.intel.com/SearchResult.aspx?lang=engProductFamily=Wireless+NetworkingProductLine=Intel%C2%AE+WiFi+ProductsProductProduct=Intel%C2%AE+PRO%2fWireless+2100+Network+Connection I hope this helps... Cheers SuperMau -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Also exists on 10.04 Lucid, using an IBM (Lenovo) Thinkpad T40. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
still exists in 9.10, IBM ThinkPad X32 -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
2.6.28-16-generic #57-Ubuntu SMP Dec 21 13:31:56 iot-emailkb kernel: [ 9509.565176] ipw2100: Fatal interrupt. Scheduling firmware restart. Dec 21 13:32:21 iot-emailkb kernel: [ 9534.961296] ipw2100: Fatal interrupt. Scheduling firmware restart. Dec 21 13:34:15 iot-emailkb kernel: [ 9649.241125] ipw2100: Fatal interrupt. Scheduling firmware restart. Dec 21 13:34:15 iot-emailkb kernel: [ 9649.241229] ipw2100: eth1: firmware fatal error Dec 21 13:35:45 iot-emailkb kernel: [ 9738.945032] ipw2100: Fatal interrupt. Scheduling firmware NOT using wireless. I am wired into a corporate network. Please help. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
@Kay: If you don't use wireless, you may get rid of the message by deactivating wlan in the bios, which most laptops support - maybe as part of 'interface security' or 'power saving'. Or you may list ipw2100 in /etc/modprobe.d/blacklist.conf to prevent it from beeing loaded at all. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I'm also seeing problems on my T41 (ibm thinkpad). Linux Mint 7 works ok most of the time (based on 9.04), while both vanilla ubuntu 9.04 and 9.10 will *not* work. Strangely enough, Mint 8 RC1 (based on 9.10) also *doesn't work, so it seems to be bug compatible with 9.10. Let me know if you need more info and I'll be happy to help. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
ubuntu 8.04 lts kernel 2.6.24-24-generic ap (fritzbox 7113 wlan) in b-only mode - fatal interup (error from above) it worked till the device was moved to a new location (different neighbourhood) -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I'm running jaunty with ipw2100 on a samsung P35 and the bug is still present. Wlan is working but only if my router is set to 802.11b and I'm excluding notebooks with faster wlan devices. When I set the router to mixed mode (802.11b/g) the intel wireless card 2100 cannot connect to the wlan. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
** Description changed: + / 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 ESSID:gaspard Protocol:IEEE 802.11b Mode:Master Channel:11 Encryption key:on Bit Rate:11 Mb/s Extra: Rates (Mb/s): 1 2 5.5 11 Quality=92/100 Signal level=-36 dBm Extra: Last beacon: 31ms ago But the card no longer register. It stays unassociated whatever I've tried : % sudo iwconfig eth1 essid gaspard key open XX mode auto % sudo iwconfig eth1 eth1 unassociated ESSID:gaspard Nickname:ipw2100 Mode:Managed Channel=0 Access Point: 00:00:00:00:00:00 Bit Rate=0 kb/s Tx-Power:off Retry min limit:7 RTS thr:off Fragment thr:off Encryption key:4D7E-7ED3-1D Security mode:open 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. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Is the attention-block at top new? Or do I just mention it by now? However, my router was in mixed-mode-state, and I set it to 802.11b, but the problem is still present. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Ubuntu 9.04 2.6.28-11-generic IBM Thinkpad T40 Intel PRO/Wireless 2100 3B rev 04 Driver git-1.2.2, firmware 1.3 Have the same issue: unable to connect to any Access Point with error ipw2100: Fatal interrupt. Scheduling firmware restart. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I updated to xUbuntu 9.04, kernel 2.6.28-11, and the situation is slightly better. Still a lot of disconnections, but not a complete disaster - sometimes nearly, but sometimes quiete stable. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I can't get wifi working using Dell Inspiron 510m (Intel(R) PRO/Wireless 2100 wifi card) on Ubuntu Jaunty (using ipw2100). I got some errors : ipw2100: Fatal interrupt. Scheduling firmware restart. I tried with the followings kernels : 2.6.28-11-generic, _2.6.27-11-generic_, 2.6.22-14-generic -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
** Description changed: + [ 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 ESSID:gaspard Protocol:IEEE 802.11b Mode:Master Channel:11 Encryption key:on Bit Rate:11 Mb/s Extra: Rates (Mb/s): 1 2 5.5 11 Quality=92/100 Signal level=-36 dBm Extra: Last beacon: 31ms ago But the card no longer register. It stays unassociated whatever I've tried : % sudo iwconfig eth1 essid gaspard key open XX mode auto % sudo iwconfig eth1 eth1 unassociated ESSID:gaspard Nickname:ipw2100 Mode:Managed Channel=0 Access Point: 00:00:00:00:00:00 Bit Rate=0 kb/s Tx-Power:off Retry min limit:7 RTS thr:off Fragment thr:off Encryption key:4D7E-7ED3-1D Security mode:open 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. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
** Changed in: intellinuxwireless Status: Confirmed = Unknown ** Changed in: intellinuxwireless Remote watch: Intel Wireless Linux Bugzilla #1840 = Bughost.org tracker #329 -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
As the kernel bugs are now being reported upstream ( earlier post Launchpad Janitor wrote on 2008-12-23: Kernel team bugs ), is anyone who can help even going to be checking this thread? Also, is it some sort of repeated regression? It was fixed late into a 2.6.27 Intrepid release (my earlier post) but then broke again in the first Jaunty 2.6.28. Oh how I wished I would have kept track of the kernel-versions so I could diff the code now to see how they fixed it. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I can confirm this bug for T41 with Ubuntu 8.04 LTS, since about one week. The wlan is open and router is an arcor-easy-box a800. The second laptop with ipw2200 works fine. Since about one week the connection is often dropped, but most times I can reestablish it, but often for a few minutes only - then the connection is dropped again. The distance to the box is a few meters only. The neighborhood is covered with foreign WLANs (all of them wpa2-secured). But this isn't new and the problems didn't exist for the two months before. (before that, I didn't used wlan, but classic eth). sudo iwconfig eth1 IEEE 802.11b ESSID:pinguin3x2r Nickname:ipw2100 Mode:Managed Frequency:2.452 GHz Access Point: 00:1A:2A:C8:0E:3E Bit Rate=11 Mb/s Tx-Power:16 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=99/100 Signal level=-36 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:190 Missed beacon:2 sudo lspci -vvnn 02:02.0 Network controller [0280]: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter [8086:1043] (rev 04) Subsystem: Intel Corporation Unknown device [8086:2551] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (500ns min, 8500ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 11 Region 0: Memory at c021 (32-bit, non-prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=1 PME- uname -a Linux ibmux 2.6.24-23-generic #1 SMP Wed Apr 1 21:47:28 UTC 2009 i686 GNU/Linux dmesg [74842.346860] eth1: no IPv6 routers present [199585.563861] ipw2100: Fatal interrupt. Scheduling firmware restart. [199591.863511] ipw2100: Fatal interrupt. Scheduling firmware restart. [74854.872861] ipw2100: Fatal interrupt. Scheduling firmware restart. [199615.957413] ipw2100: Fatal interrupt. Scheduling firmware restart. [199622.268519] ipw2100: Fatal interrupt. Scheduling firmware restart. [199627.719040] ipw2100: Fatal interrupt. Scheduling firmware restart. [199639.077566] ipw2100: Fatal interrupt. Scheduling firmware restart. [199646.465495] ipw2100: Fatal interrupt. Scheduling firmware restart. [199649.476289] ipw2100: Fatal interrupt. Scheduling firmware restart. [199654.930402] ipw2100: Fatal interrupt. Scheduling firmware restart. [199660.523830] ipw2100: Fatal interrupt. Scheduling firmware restart. [199665.798431] ipw2100: Fatal interrupt. Scheduling firmware restart. [199674.824377] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [199692.761365] eth1: no IPv6 routers present (zillions of these) -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
** Package changed: linux (Ubuntu) = ipw2100 (Ubuntu) -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Hi I have got my ipw2100 working if i disable in my Fritz Box the WPA mode and only use WPA2. - Intrepid 2.6.27-11-generic -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I am now using Intrepid 2.6.27-11-generic and the ipw2100 driver IS working. 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 inconsistent. Hopefully, this is some sort of clue to the problem. - Mike -Original Message- From: ekul ekul.tay...@gmail.com Reply-to: Bug 24776 24...@bugs.launchpad.net To: m...@himikeb.com Subject: [Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart. Date: Mon, 09 Mar 2009 20:27:08 - 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 :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 :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 occurring. 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. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
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 :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 :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 occurring. 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. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I have changed the Intel Corporation PRO/Wireless Mini PCI adapter to an Atheros wifi-card. After that change no problems at all. So dont try too much with the Intel Corporation PRO/Wireless Mini PCI adapter. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
** Changed in: intellinuxwireless Bugwatch: Bughost.org tracker #329 = Intel Wireless Linux Bugzilla #1840 Status: In Progress = Unknown -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
** Changed in: intellinuxwireless Status: Unknown = Confirmed -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I have two Thinkpad X31 with Ubuntu 8.04 installed. They have different wifi-cards One with: Ambit Microsystems Corp. Thinkpad 11 b/g wireless Mini PCI adapter. With that laptop I have no connections problem to the wifi-router. Other one with: Intel Corporation PRO/Wireless Mini PCI adapter. Here I cannot connect when the wifi-router is locked with password. Unlocked wifi-router work without problem. As soon as I lock the router with password syslog says. ipw2100: Fatal interrupt. Scheduling firmware restart. And I cannot ping the IP-adress of the router. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I can confirm the behaviour that Mr. Mike descibed on 2008-11-16 [1] with my HP nc4010. Ubuntu Hardy worked without problems, Windows Vista, too (dual boot system). After updating to Intrepid I had some problems with network- manager-kde (I have kubuntu). I switched to network-manager-gnome which worked at the beginning. But after a few days, I cannot connect to wireless lans anymore and I see the Fatal interrupt. Scheduling firmware restart messages. Reloading the module does not help, booting the 2.6.24 kernel from hardy does not help, even in Windows Vista wireless is no more working. Thanks for any help, let me know if I should post more details. [1] https://bugs.launchpad.net/intellinuxwireless/+bug/24776/comments/41 -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
My ipw2100 works fine in intrepid with wireless sequrity on my T41. The problem I'm having are the fatal irq resets. On 11/16/08, Mr. Mike [EMAIL PROTECTED] wrote: I'm also having problems with my ipw2100 on a T41, and getting the firmware restart messages, but in dmesg, the firmware appears to load. I wonder if there might be another problem (this is Intrepid 2.6.27) [EMAIL PROTECTED]:~/Downloads$ sudo iwconfig eth4 key 11122233344455566677788899 Error for wireless request Set Encode (8B2A) : SET failed on device eth4 ; Operation not supported. [EMAIL PROTECTED]:~/Downloads$ sudo iwconfig eth4 eth4 IEEE 802.11b ESSID:himikeb4 Nickname:ipw2100 Mode:Managed Frequency:2.422 GHz Access Point: 00:12:88:DC:D0:E9 Bit Rate=11 Mb/s Tx-Power:16 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off It seems that it is not setting the wireless key. Wireless was working great in 2.6.24. Also, lsmod seems to show 0 next to ipw2100, not sure if that is significant. I've tried disabling/enabling using the hotkey (I saw this somewhere else), and rmmod / modprobe ipw2100, with no luck. sudo lspci -vvnn: 02:02.0 Network controller [0280]: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter [8086:1043] (rev 04) Subsystem: Intel Corporation Device [8086:2551] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 (500ns min, 8500ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 11 Region 0: Memory at c0214000 (32-bit, non-prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Kernel driver in use: ipw2100 Kernel modules: ipw2100 More interesting stuff from dmesg: [ 3179.878932] eth4: could not initialize WEP: load module ieee80211_crypt_wep [ 3365.928077] ipw2100: exit - failed to send CARD_DISABLE command [ 3531.348096] ipw2100: Fatal interrupt. Scheduling firmware restart. Thanks for looking into this, let me know if I should post more debug stuff. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a direct subscriber of the bug. -- Sent from Google Mail for mobile | mobile.google.com -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I'm also having problems with my ipw2100 on a T41, and getting the firmware restart messages, but in dmesg, the firmware appears to load. I wonder if there might be another problem (this is Intrepid 2.6.27) [EMAIL PROTECTED]:~/Downloads$ sudo iwconfig eth4 key 11122233344455566677788899 Error for wireless request Set Encode (8B2A) : SET failed on device eth4 ; Operation not supported. [EMAIL PROTECTED]:~/Downloads$ sudo iwconfig eth4 eth4 IEEE 802.11b ESSID:himikeb4 Nickname:ipw2100 Mode:Managed Frequency:2.422 GHz Access Point: 00:12:88:DC:D0:E9 Bit Rate=11 Mb/s Tx-Power:16 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off It seems that it is not setting the wireless key. Wireless was working great in 2.6.24. Also, lsmod seems to show 0 next to ipw2100, not sure if that is significant. I've tried disabling/enabling using the hotkey (I saw this somewhere else), and rmmod / modprobe ipw2100, with no luck. sudo lspci -vvnn: 02:02.0 Network controller [0280]: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter [8086:1043] (rev 04) Subsystem: Intel Corporation Device [8086:2551] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 (500ns min, 8500ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 11 Region 0: Memory at c0214000 (32-bit, non-prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Kernel driver in use: ipw2100 Kernel modules: ipw2100 More interesting stuff from dmesg: [ 3179.878932] eth4: could not initialize WEP: load module ieee80211_crypt_wep [ 3365.928077] ipw2100: exit - failed to send CARD_DISABLE command [ 3531.348096] ipw2100: Fatal interrupt. Scheduling firmware restart. Thanks for looking into this, let me know if I should post more debug stuff. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I will test this with the linux-image-2.6.27-7-generic as I am having the same dmesg issues, and a driver that keeps resetting my ipw2100 device. It's installed, rebooting now. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Ok, after the reboot, the driver failed to load because of missing firmware... [ 116.811667] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2 [ 116.811685] ipw2100: Copyright(c) 2003-2006 Intel Corporation [ 116.814957] ipw2100 :02:02.0: PCI INT A - Link[LNKC] - GSI 11 (level, low) - IRQ 11 [ 116.816258] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection [ 116.816990] firmware: requesting ipw2100-1.3.fw [ 116.821452] ipw2100: eth1: Firmware 'ipw2100-1.3.fw' not available or load failed. [ 116.821472] ipw2100: eth1: ipw2100_get_firmware failed: -2 [ 116.821482] ipw2100: eth1: Failed to power on the adapter. [ 116.821488] ipw2100: eth1: Failed to start the firmware. [ 116.821496] ipw2100Error calling register_netdev. [ 116.823746] ipw2100 :02:02.0: PCI INT A disabled [ 116.826274] ipw2100: probe of :02:02.0 failed with error -5 Then I remembered where the firmware was installed in /lib/firmware /$KERNEL-VERSION The 2.6.27-7 version didn't have the ipw2100 firmware, so I copied it over from 2.6.42-21... cp 2.6.24-21-generic/ipw2100-1.3* 2.6.27-7-generic/ Then reloaded the ipw2100 module. At this point the card started up fine and I was able to connect to my WPA2 authenticated access point with out any problems. I'm not sure if I should be using that version of the firmware, but as long as this bug goes away, I really don't care. I will keep an eye out for the Fatal Interrupt error and report whether or not the problem persists. -Rick -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
It's still happening with the 2.6.27-7-generic kernel... [ 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 :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. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I just recently installed Hardy on a Compaq X1000 that has an ip2100. I have a similar set of symptoms: every now and then the Network Manager shows that the connection is gone (0%) and this usually lasts for 2-15 seconds before it recovers. Sometimes it has to go through the whole re- establishing process (spinning icon) to get DHCP again. When that happens I see the following sort of thing in syslog: Sep 22 15:43:15 dot NetworkManager: info Supplicant state changed: 1 Sep 22 15:43:16 dot NetworkManager: info Supplicant state changed: 0 Sep 22 15:43:18 dot kernel: [21871.333696] ipw2100: Fatal interrupt. Scheduling firmware restart. Sep 22 15:43:18 dot kernel: [21871.361300] ipw2100: Fatal interrupt. Scheduling firmware restart. Sep 22 15:43:18 dot NetworkManager: info Supplicant state changed: 1 Sep 22 15:43:21 dot NetworkManager: info Supplicant state changed: 0 Sep 22 15:43:22 dot kernel: [21875.901221] ipw2100: Fatal interrupt. Scheduling firmware restart. Sep 22 15:43:22 dot kernel: [21875.922782] ipw2100: Fatal interrupt. Scheduling firmware restart. Sep 22 15:43:22 dot NetworkManager: info Supplicant state changed: 1 Sep 22 15:43:26 dot NetworkManager: info Supplicant state changed: 0 Sep 22 15:43:28 dot kernel: [21882.066286] NETDEV WATCHDOG: eth1: transmit timed out Sep 22 15:43:29 dot NetworkManager: info Supplicant state changed: 1 I've attached the output from: uname -a; cat /proc/version_signature; dmesg; sudo lspci -vvnn ** Attachment added: uname -a; cat /proc/version_signature; dmesg; sudo lspci -vvnn http://launchpadlibrarian.net/17846106/output -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Hi all. This bug is ancient but PLEASE NOTICE the following, maybe somebody should report upstream (I don't even have the time to write this :) I discovered this bug yesterday. I have an old laptop running ipw2100 and connected to any kind of network. Then yesterday I couldn't and discovered this scheduling firmware restart in the logs. This machine has windows, I rebooted and... IT DOES NOT WORK UNDER WINDOWS, TOO! So this must be a problem of the firmware. Can somebody confirm that it doesn't work under windows, too? If so, it is intel (if they care at all) that has to upgrade the firmware. I will try tonight if getting far from the AP helps. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test: 1) If you are comfortable installing packages on your own, the linux- image-2.6.27-* package is currently available for you to install and test. --or-- 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD. Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback. ** Tags added: cft-2.6.27 -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I have the same on my Dell D800 with Intel Pro 2100. I was not able to get it to work with WPA-PSK. In order to test I created a wpa_supplicant.conf file and started the wireless network manually. I indeed got the same error messages as you get: ipw2100: Fatal interrupt: Scheduling firmware restart I then started to play with the signal strength setting on my Cisco ap1231 access point. To no avail. The AP has a b/g radio in it, so I decided to turn off all but 1 and 11 mbit/s speeds and leave the other options as enabled, but only 1 and 11 required. The link came straight up. Before that I had all speeds set to required. So it seems like there is something fishy about speed negotiation when you're running a 802.11g network. I've attached the output of: uname -a uname-a.log cat /proc/version_signature version.log dmesg dmesg.log sudo lspci -vvnn lspci-vvnn.log ** Attachment added: debug information http://launchpadlibrarian.net/1520/bugreport.tgz -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
As mentioned above by moniker, disabling Frame Burst on the access point solved the problem right away for me (Linksys WRT54G running DD- WRT). -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
Confirmed for Hardy Alpha 6. After a long time trying to figure it out. Reloading the driver seems to do the trick for me. sudo modprobe -r ipw2100 sudo modproble -a ipw2100 -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I mailed the driver contact at Intel with a link to this page and to their bugzilla link I gave above, just saying that a lot of people had problems and were keen to contribute to a fix if we could. I got a mail back saying:- A community member recently backported a fix for RX overrruns in the ipw2200 driver. I assume the same problem may exist in the ipw2100 driver. If you are interested you can try to backport the fix to the ipw2100 driver ... details are here: http://marc.info/?l=linux-wirelessm=120302948521611w=2 This is beyond my skills but might be useful to someone? -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
** Changed in: intellinuxwireless Status: Unknown = In Progress -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
** Changed in: linux (Fedora) Status: Unknown = Invalid -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
I can confirm, that this problem occurs on the same machine as reported above (Samsung X11) using OpenSuse 10.2. Also the Fabio-workaround works there. So this is really an ipw2100 problem, rather than an ubuntu problem. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
** Changed in: linux (Ubuntu) Importance: Undecided = Medium Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team) Status: New = Triaged ** Changed in: linux Status: New = Invalid -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
As Brian and Enrico have pointed out, this is a known issue upstream. However, it seems the upstream bugzilla report has not had a comment since almost 2 yrs ago. It would be helpful if someone still experiencing this issue would post that this is still an issue to the upstream bug report. It would also be helpful to probably add the output of 'modinfo ipw2100' so they can see the version of the driver you are running etc. I've assigned this to the ubuntu-kernel-team so that they are aware of the issue upstream and needs to be resolved there. Thanks. -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24776] Re: ipw2100 - Fatal interrupt. Scheduling firmware restart.
** Also affects: linux (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=149968 Importance: Unknown Status: Unknown -- ipw2100 - Fatal interrupt. Scheduling firmware restart. https://bugs.launchpad.net/bugs/24776 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
