Bug 129104
Summary: | kernel-2.6.7-1.494.2.2 breaks airo_cs | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Matthew Saltzman <mjs> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | pfrields, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-11-27 22:51:20 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
Matthew Saltzman
2004-08-04 02:25:58 UTC
I have a Thinkpad R40 and a Cisco Airo 350 mini-pci with Firmware Version: 5b00.08 and using the same kernel the computer will boot but is not able to use the card correctly. I got it working using kernel-2.6.5-1.358. When trying to unload the module on 2.6.7 I get: Aug 10 10:47:42 borg kernel: airo: Unregistering eth1 Aug 10 10:47:42 borg net.agent[4198]: remove event not handled Aug 10 10:47:52 borg kernel: unregister_netdevice: waiting for eth1 to become free. Usage count = 7 Regards Mirko My problem persists with kernel-2.6.8-1.521. Starting eth1 at boot results in a hang with the indicator light flashing rapidly. Starting by hand after boot completes works fine. kernel-2.6.6-1.435.2.3 works fine. This problem appears to be related to Bug #112824 and some others regarding hardware initialization and hotplugging. Following the suggestion there, I upgraded initscripts to initscripts-7.77-1 from the development tree (and mkinitrd to the devel mkinitrd-4.1.9-1 to satisfy the dependency). Now eth1 starts properly on boot. Is the proper action to mark this as a dup of 112824? Also that bug is listed as an RFE, but it seems like it ought to be a bugfix and rolled out as an update. mass update for old bugs: Is this still a problem in the 2.6.9 based kernel update ? Works perfectly in FC3. |