Bug 33188 - CIPE unable to ifup after ifdown without module reload
Summary: CIPE unable to ifup after ifdown without module reload
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel   
(Show other bugs)
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-03-26 06:27 UTC by Scott Schmit
Modified: 2007-04-18 16:32 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-03-26 06:27:14 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Scott Schmit 2001-03-26 06:27:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.1-0.1.9 i686; Nav)

If I bring up several cipe interfaces and later bring some of them down and
back up (several times even, for example, as I tweak ip-up and ip-down
scripts), an interface will eventually refuse to load--complaining of
'opendev: alloc: Device or resource busy' or similar.

The only way I can get rid of this error is to ifconfig down all my cipe
interfaces, remove the module, reinsert the module, and bring up the
interfaces again. This is not really acceptable as it may be indicative of
more serious problems.

Further anecdotal evidence:
[01:02:08] <jeremy> draco: yes, cipe likes to have its module removed and
 reinserted between interface down/up :(

Reproducible: Didn't try (having my network be connected somewhat sanely
is more important, and I figured I'd file the bug now so you're aware of
Steps to Reproduce:
1. Set up several cipe interfaces between several computers
2. Bring various interfaces up and down, in various combonations (from a
single machine)
3. Also try setting up a single interface and bringing it up and down

Actual Results:  ifconfig shows the interface did not come up, though it
should have. The module has to be reloaded to get the expected behavior
(just working)

Comment 1 Bill Nottingham 2001-03-26 17:07:34 UTC
This should be fixed in the current rahwide kernel.

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