- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- SIOCSIFFLAGS: Device or resource busy
Operating System - Linux
1820399
Members
3298
Online
109624
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2009 10:12 AM
тАО05-12-2009 10:12 AM
SIOCSIFFLAGS: Device or resource busy
I installed RedHat 5.3 on PloLian ML370 (S/N USE904N35C) and got an error when boot or trying to activate eth0 network card.
Error:
SIOCSIIFFLAGS: Device or resource busy
Error:
SIOCSIIFFLAGS: Device or resource busy
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2009 10:54 AM
тАО05-12-2009 10:54 AM
Re: SIOCSIFFLAGS: Device or resource busy
The network-related IOCTL call returned an error... which means there might be something wrong with the driver of the network card.
Please examine the kernel message buffer (you can view it with command "dmesg | less"). Does it contain any eth0-related error messages?
MK
Please examine the kernel message buffer (you can view it with command "dmesg | less"). Does it contain any eth0-related error messages?
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2009 06:05 AM
тАО05-13-2009 06:05 AM
Re: SIOCSIFFLAGS: Device or resource busy
Thanks for your reply Matti. I don't think it's a driver because I have two adentical network cards in and second one works just fine. Any other ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2009 12:20 PM
тАО05-13-2009 12:20 PM
Re: SIOCSIFFLAGS: Device or resource busy
OK. Then it might be a hardware problem.
There is only a limited set of error codes the driver can report to the user-space utilities. "Device or resource busy" (error code "EBUSY") is not very specific, so very little information can be gleaned about it alone.
If the driver wants to report a more verbose description of the problem, the report must go through the kernel logging subsystem... which means it will show up in the dmesg listing.
If the problem is hardware- or driver-related, the dmesg listing usually contains more detailed information about it.
MK
There is only a limited set of error codes the driver can report to the user-space utilities. "Device or resource busy" (error code "EBUSY") is not very specific, so very little information can be gleaned about it alone.
If the driver wants to report a more verbose description of the problem, the report must go through the kernel logging subsystem... which means it will show up in the dmesg listing.
If the problem is hardware- or driver-related, the dmesg listing usually contains more detailed information about it.
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP