Bug 69738 - pegasus usb ethernet device not configured on reinsertion
Summary: pegasus usb ethernet device not configured on reinsertion
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 8.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Pete Zaitcev
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-24 21:27 UTC by Mike McLean
Modified: 2007-04-18 16:44 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-04-19 18:46:46 UTC
Embargoed:


Attachments (Terms of Use)
section of /var/log/messages (3.83 KB, text/plain)
2002-07-24 21:35 UTC, Mike McLean
no flags Details

Description Mike McLean 2002-07-24 21:27:28 UTC
* Milan-re0724.nightly
* kernel-2.4.8-7.80

In the initial insertion of the usb device everything goes well. (Well except
for an extraneous message on the console).  The module inserts, the device
works, and everything is happy.

If you unplug the device things also work as expected.  The ethernet device
disappears and life moves on.

BUT, if you then reinsert the device nothing happens (well the kernel detects
it, but the driver apparently does nothing).  No ethernet device appears.

otoh, if you rmmod pegasus before reinsertion, then things go smoothly.

Comment 1 Mike McLean 2002-07-24 21:35:05 UTC
see bug 69739 for details on the extraneous console messages.

The device in question is a Belkin F5D5050 USB Ethernet Adapter.


Comment 2 Mike McLean 2002-07-24 21:35:49 UTC
Created attachment 66865 [details]
section of /var/log/messages

Comment 3 Mike McLean 2002-07-24 21:45:42 UTC
I took the following actions during this syslog:

% insmod dummy   (testing something else)
% rmmod dummy
% ifdown eth0
(insert device)
% ifdown eth2 
% ifup eth2
% ping hank   (successful)
% ifdown eth2
(remove device)
% rmmod pegasus
(reinsert device)
% ping hank   (successful)
% ifdown eth2
(remove device)
(reinsert device)
% ip link list  (no eth2 visible)


Comment 4 Pete Zaitcev 2003-10-06 23:15:08 UTC
How is the situation now (RHL 9 w/ 2.4.20-20.9)?



Comment 5 Pete Zaitcev 2004-04-19 18:46:46 UTC
This was needinfo-ed since last October, Mike. I'll just close
for now then.


Comment 6 Mike McLean 2004-04-19 19:21:26 UTC
fwiw, this seems to be fixed in FC1.


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