Operating System - Linux
1819875 Members
3046 Online
109607 Solutions
New Discussion юеВ

Service network restart fails

 
Mr. Barnes
New Member

Service network restart fails

Hello everyone,

I am attempting to restart the network on a DL380 G5 server that is running Linux v3 update 8 64. When I issue the command I receive this message "SIOCSIFFLAGS: Device or resource busy". I then loose all network connectivity. The only way that I can regain my connection is by restarting the server. The network card is a BCM5706. Below is the latest driver and firmware level. I have replaced the NIC card 3 times, however the problem still exists. This server is identical to another server that I have with the exception that this server has an additional SCSI card that is being used to connect a tape drive to. The other works fine when I attempt a network restart.

driver: bnx2
version: 1.4.52d
firmware-version: 1.9.6
bus-info: 18:04.0

Here is an excerp from /var/log/messages after the service restart:

Aug 28 15:54:29 hpmdb01 kernel: ip_tables: (C) 2000-2002 Netfilter core team
Aug 28 15:54:29 hpmdb01 kernel: bnx2: Chip reset did not complete
Aug 28 15:54:29 hpmdb01 ifup: SIOCSIFFLAGS: Device or resource busy
Aug 28 15:54:29 hpmdb01 ifup: Failed to bring up eth0.
Aug 28 15:54:29 hpmdb01 network: Bringing up interface eth0: failed

Here is an excerp from /var/log/messages after a server reboot:

Aug 28 15:58:55 hpmdb01 network: Setting network parameters: succeeded
Aug 28 15:58:55 hpmdb01 network: Bringing up loopback interface: succeeded
Aug 28 15:58:57 hpmdb01 ifup: Enslaving eth1 to bond0
Aug 28 15:58:57 hpmdb01 ifup: Enslaving eth2 to bond0
Aug 28 15:58:57 hpmdb01 network: Bringing up interface bond0: succeeded
Aug 28 15:58:59 hpmdb01 network: Bringing up interface eth0: succeeded
Aug 28 15:59:02 hpmdb01 insmod: /lib/modules/2.4.21-47.0.1.EL/kernel/drivers/parport/parport_pc.o: init_module: No such device
Aug 28 15:59:02 hpmdb01 insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Aug 28 15:59:02 hpmdb01 insmod: /lib/modules/2.4.21-47.0.1.EL/kernel/drivers/parport/parport_pc.o: insmod parport_lowlevel failed
Aug 28 15:59:02 hpmdb01 kernel: lp: driver loaded but no devices found
Aug 28 15:59:02 hpmdb01 kernel: usb.c: registered new driver serial

Attached is a copy of the messages file. Any help is greatly appreciated!
4 REPLIES 4
Ivan Ferreira
Honored Contributor

Re: Service network restart fails

Please ensure that you have the right HWADDR setting in /etc/sysconfig/network-scripts/ifcfg-ethX|ifcfg-bondX files. The other server, where it works, also has a bond device?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Alexander Chuzhoy
Honored Contributor

Re: Service network restart fails

What NIC card you replaced - the onboard one?

If the /etc/modules.conf file is identical on both servers and you indeed use the same network driver and hardware, then I'd suggest you to try to boot the "problematic" server without the SCSI card and see if the problem persists. You can also try to "play" with the IRQ settings in the BIOS.
Mr. Barnes
New Member

Re: Service network restart fails

The dual port onboard NIC serves as eth2 and eth3. The dual port PCI NIC serves as eth0 and eth1. Both servers have eth1 and eth2 configured as the private interconnect. The IRQ's are exactly the same between both servers. I removed the HWADDRESS setting on both servers. Does it need to be there? I also tried booting without the SCSI card, and the problem still exists...
Ivan_win
Occasional Contributor

Re: Service network restart fails

Hello,
It seems we have the same problem on a HP DL580 G4 running SLES 10 SP1.
The server holds an HP multifunction NC380T PCI-E 1000TX 2ports card(2x BCM5706).
When I attempt a network restart, I get the message : "SIOCSIFFLAGS: Device or resource busy".
When I look in dmesg:
"bnx2: Chip reset did not complete"
The others cards are up.
We have 6 out of 24 DL580 where we get this error.

Best regards