Bug 211275 - xircom_cb does not unload (unregister_netdev waiting for eth0 to become free) or get new IP properly
Summary: xircom_cb does not unload (unregister_netdev waiting for eth0 to become free)...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Neil Horman
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-18 12:12 UTC by Bruce Allen
Modified: 2007-11-30 22:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-08-07 21:22:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bruce Allen 2006-10-18 12:12:05 UTC
Description of problem:

Problem not present with 2.6.15.  Problem present in 2.6.17 and 2.6.18.

I am using xircom_cb with a Xircom RBEM56G-100 card.  I can assign IP
information to the ethernet port exactly once.  After that, any attempt to
assign new IP info fails.  A reboot is required to change the IP!

Any attempt to unload the card results in a steady stream of messages:
unregister_netdevice: waiting for eth0 to become free.

Version-Release number of selected component (if applicable):

Updated stock FC5

How reproducible:


Steps to Reproduce:
1.  dhclient eth0   (gets IP)
2.  plug into a different DHCP server
3.  killall dhclient; dhclient eth0 (FAILS)
4.  pccardctl eject 0 (produces unregister_netdev errors)

I am using the latest pcmciautils package.
Kernel has acpi=off
I have seen the 'udev hang on boot' error one time with 2.6.18, but it
is not reproducible.

Comment 1 John W. Linville 2006-10-25 15:22:08 UTC
Fedora-netdev kernels are available here:

   http://people.redhat.com/linville/kernels/fedora-netdev/

Please give those a try to verify that this problem continues to exist there, 
and post the results here...thanks!

Comment 2 John W. Linville 2007-08-07 21:22:47 UTC
Closed due to lack of response...please reopen if/when the requested info 
becomes available.


Note You need to log in before you can comment on or make changes to this bug.