LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Enterprise Linux Forums > Linux - Enterprise
User Name
Password
Linux - Enterprise This forum is for all items relating to using Linux in the Enterprise.

Notices


Reply
  Search this Thread
Old 06-16-2008, 10:35 PM   #1
hunter_cao7
LQ Newbie
 
Registered: Nov 2007
Location: linux m
Posts: 18

Rep: Reputation: 0
Exclamation RHEL AS4UP2 64bit crash


I have the same configuration of three machines (asus rs162-e4), each machine NIC card redundancy bonding, have been normal working half a year. Have recently appeared similar to the Dead. As /var/log/messages in the log records and networks Card, I cancel the bond, of which only one card to work. Observation now.

I analysis, may be related to the stability of the NIC, I do not know linux bonding dirvver in redundant when the need to meet the conditions. Use a separate NIC now maintain normal ..


Hardware list:
Intel 82563eb NIC,e1000-7.0.38 driver


console information:
...
Code:48 39 f8 72 f4 c3 65 8b 04 25 34 00 00 00 48 98 48 c1 c0 08
kernel panic - not syncing nmi watchdog
call Trace: <IRQ><ffffffffa00abdbd>
fs:00016T0(0000)
cs:0100 DS:0018 ES:0018 CR0 8T0,8005003b
<ffffffff80131931>{try_to_wake_up+734}
<ffffffff80110aed>{error_exit+0}
<smp_call_function_interrupt+133}
<ffffffff801368da>{panic+235}
....
I can understand the above information, but I stress tests hardware too high, there were also similar to the screen.


/ var / log / messages:

Jun 3 11:13:02 server1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 3 11:13:02 server1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 3 11:13:02 server1 kernel: bonding: Warning: the permanent HWaddr of eth0 - 00:1D:60:14:74:99 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jun 3 11:13:02 server1 kernel: bonding: bond0: releasing backup interface eth0
Jun 3 11:13:02 server1 net.agent[25997]: remove event not handled
Jun 3 11:13:02 server1 net.agent[26001]: remove event not handled
Jun 3 11:13:02 server1 kernel: bonding: bond0: releasing active interface eth1
Jun 3 11:13:02 server1 kernel: bonding: bond0: now running without any active interface !
Jun 3 11:13:02 server1 net.agent[26021]: remove event not handled
Jun 3 11:13:02 server1 net.agent[26020]: remove event not handled
Jun 3 11:14:17 server1 login(pam_unix)[8675]: session opened for user root by LOGIN(uid=0)
Jun 3 11:14:17 server1 -- root[8675]: ROOT LOGIN ON tty1
Jun 3 11:14:34 server1 kernel: Intel(R) PRO/1000 Network Driver - version 7.3.15-NAPI
Jun 3 11:14:34 server1 kernel: Copyright (c) 1999-2006 Intel Corporation.
Jun 3 11:14:34 server1 kernel: ACPI: PCI interrupt 0000:07:00.0[A] -> GSI 16 (level, low) -> IRQ 169
Jun 3 11:14:34 server1 kernel: e1000: 0000:07:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x4) 00:1d
:60:14:74:99
Jun 3 11:14:34 server1 kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
Jun 3 11:14:34 server1 kernel: ACPI: PCI interrupt 0000:07:00.1[B] -> GSI 17 (level, low) -> IRQ 177
Jun 3 11:14:34 server1 kernel: e1000: 0000:07:00.1: e1000_probe: (PCI Express:2.5Gb/s:Width x4) 00:1d
:60:14:74:98
Jun 3 11:14:34 server1 kernel: e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
Jun 3 11:14:34 server1 kernel: bonding: bond0: enslaving eth0 as a backup interface with a down link.
Jun 3 11:14:34 server1 kernel: bonding: bond0: enslaving eth1 as a backup interface with a down link.
Jun 3 11:14:38 server1 kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
Jun 3 11:14:38 server1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 3 11:14:38 server1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 3 11:14:50 server1 kernel: e1000: eth1: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
Jun 3 11:14:50 cn-app05 kernel: e1000: eth1: e1000_watchdog: 10/100 speed: disabling TSO
Jun 3 11:14:50 server1 kernel: bonding: bond0: link status definitely up for interface eth1.
Jun 3 11:14:56 server1 kernel: bonding: bond0: released all slaves
Jun 3 11:14:56 server1 network: Shutting down interface bond0: succeeded
 
Old 06-17-2008, 01:55 AM   #2
hunter_cao7
LQ Newbie
 
Registered: Nov 2007
Location: linux m
Posts: 18

Original Poster
Rep: Reputation: 0
e1000 bonding log

Hi,NIC is the support of linux bonding instability?

/var/log/messages:

Jun 16 15:53:57 server1 kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
Jun 16 15:53:57 server1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 16 15:53:57 server1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jun 16 15:53:57 server1 kernel: e1000: eth1: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
Jun 16 15:53:57 server1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jun 16 15:53:57 server1 kernel: i2c /dev entries driver
Jun 16 15:53:57 server1 kernel: NET: Registered protocol family 10
Jun 16 15:53:57 server1 kernel: Disabled Privacy Extensions on device ffffffff803f9de0(lo)
Jun 16 15:53:57 server1 kernel: IPv6 over IPv4 tunneling driver
Jun 16 15:53:58 server1 login(pam_unix)[2688]: session opened for user root by LOGIN(uid=0)
Jun 16 15:53:58 server1 -- root[2688]: ROOT LOGIN ON tty1
Jun 16 15:54:52 server1 sshd(pam_unix)[3386]: session opened for user root by root(uid=0)
Jun 16 15:55:01 server1 crond(pam_unix)[3419]: session opened for user root by (uid=0)
Jun 16 15:55:01 server1 crond(pam_unix)[3419]: session closed for user root
Jun 16 15:55:02 server1 snmpd[2498]: Received SNMP packet(s) from 172.21.129.63
Jun 16 15:55:53 server1 network: Shutting down interface eth0: succeeded
Jun 16 15:55:53 server1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 16 15:55:53 server1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 16 15:55:53 server1 kernel: bonding: bond0: link status definitely down for interface eth1, disabling it
Jun 16 15:55:53 server1 kernel: bonding: bond0: now running without any active interface !
Jun 16 15:55:53 server1 network: Shutting down interface eth1: succeeded
Jun 16 15:55:53 server1 network: Shutting down loopback interface: succeeded
Jun 16 15:56:00 server1 kernel: bonding: bond0: released all slaves
Jun 16 15:56:00 server1 net.agent[3577]: remove event not handled
Jun 16 15:56:00 server1 net.agent[3581]: remove event not handled
Jun 16 15:56:10 server1 kernel: unregister_netdevice: waiting for bond0 to become free. Usage count = 1
Jun 16 15:57:20 server1 network: Shutting down loopback interface: succeeded

Last edited by hunter_cao7; 06-17-2008 at 01:57 AM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Installing Ruby on RHEL 4 64bit Neruocomp Linux - Software 2 09-26-2012 05:43 PM
RHEL 4 64bit Workstation mccartjd Linux - Newbie 3 05-06-2008 06:26 PM
Using RHEL 64bit Not sure how to unlock an account mccartjd Linux - Newbie 2 04-24-2008 06:26 AM
Ati 64bit proprietary drivers crash linux slantoflight Linux - Hardware 7 07-30-2006 03:34 PM
RHEL 4 hangs on AMD 64bit PC sushil_gambhir Red Hat 2 06-08-2006 11:18 PM

LinuxQuestions.org > Forums > Enterprise Linux Forums > Linux - Enterprise

All times are GMT -5. The time now is 08:22 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration