Bug 744367

Summary: After linux server restart, the networ doesn't work.
Product: Red Hat Enterprise Linux 5 Reporter: William Du <wdu001>
Component: initscriptsAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED INSUFFICIENT_DATA QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.0CC: dcbw, initscripts-maint-list, jklimes, nbronson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-11 09:52:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
poweron_no_network
none
configure files on the server none

Description William Du 2011-10-08 05:34:23 UTC
Created attachment 526996 [details]
poweron_no_network

Description of problem:

After linux server restart, the networ doesn't work.

Version-Release number of selected component (if applicable):
Linux comQD01 2.6.18-238.1.1.el5 #1 SMP Tue Jan 4 13:32:19 EST 2011 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:
Just reboot the server.

Steps to Reproduce:
1.
2.
3.
  
Actual results:

Sometimes, the network can't ping out, some time is can.
Our server is HP 380.

After check dsmesg and diff the two outputs:

For the normal case,
when linux start up, it bond the eth0 - eth 3 port with Base_T port.

For the failed case, linux bond the eth0 - eth3 port with PCI's eth ports.
With this error, the network proxy won't work.
And I also find some EXT3-fs errors:
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.


Expected results:

recover the eth port bonding to bond eth0 - eth3 with base_t ports.

Additional info:

Here's the dmesg log related to network.
ata2: SATA link down (SStatus 4 SControl 300)
  Vendor: hp        Model: DVD A  DS8A5LH    Rev: 1HE3
  Type:   CD-ROM                             ANSI SCSI revision: 05
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: dm-devel
device-mapper: dm-raid45: initialized v0.2594l
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
SELinux:  Disabled at runtime.
SELinux:  Unregistering netfilter hooks
type=1404 audit(1317779648.380:2): selinux=0 auid=4294967295 ses=4294967295
input: PC Speaker as /class/input/input2
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
e1000e: Intel(R) PRO/1000 Network Driver - 1.2.7-k2
e1000e: Copyright (c) 1999 - 2010 Intel Corporation.
e1000e 0000:0f:00.0: Disabling ASPM  L1
GSI 22 sharing vector 0xB2 and IRQ 22
ACPI: PCI Interrupt 0000:0f:00.0[B] -> GSI 38 (level, low) -> IRQ 178
PCI: Setting latency timer of device 0000:0f:00.0 to 64
EDAC MC: Ver: 2.0.1 Jan  4 2011
Floppy drive(s): fd0 is 1.44M
eth0: (PCI Express:2.5GB/s:Width x4) 00:26:55:e7:84:bd
eth0: Intel(R) PRO/1000 Network Connection
eth0: MAC: 0, PHY: 4, PBA No: d98771-008
e1000e 0000:0f:00.1: Disabling ASPM  L1
GSI 23 sharing vector 0xC2 and IRQ 23
ACPI: PCI Interrupt 0000:0f:00.1[A] -> GSI 39 (level, low) -> IRQ 194
PCI: Setting latency timer of device 0000:0f:00.1 to 64
eth1: (PCI Express:2.5GB/s:Width x4) 00:26:55:e7:84:bc
eth1: Intel(R) PRO/1000 Network Connection
eth1: MAC: 0, PHY: 4, PBA No: d98771-008
e1000e 0000:10:00.0: Disabling ASPM  L1
GSI 24 sharing vector 0xD2 and IRQ 24
ACPI: PCI Interrupt 0000:10:00.0[B] -> GSI 37 (level, low) -> IRQ 210
PCI: Setting latency timer of device 0000:10:00.0 to 64
eth2: (PCI Express:2.5GB/s:Width x4) 00:26:55:e7:84:bf
eth2: Intel(R) PRO/1000 Network Connection
eth2: MAC: 0, PHY: 4, PBA No: d98771-008
e1000e 0000:10:00.1: Disabling ASPM  L1
GSI 25 sharing vector 0xE2 and IRQ 25
ACPI: PCI Interrupt 0000:10:00.1[A] -> GSI 30 (level, low) -> IRQ 226
PCI: Setting latency timer of device 0000:10:00.1 to 64
eth3: (PCI Express:2.5GB/s:Width x4) 00:26:55:e7:84:be
eth3: Intel(R) PRO/1000 Network Connection
eth3: MAC: 0, PHY: 4, PBA No: d98771-008
Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.8-rh (Oct 11, 2010)
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:02:00.0 to 64
EDAC i7core: Driver loaded.
eth4: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f4000000, IRQ 169, node addr 984be107fdb2
ACPI: PCI Interrupt 0000:02:00.1[B] -> GSI 17 (level, low) -> IRQ 170
PCI: Setting latency timer of device 0000:02:00.1 to 64
eth5: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f2000000, IRQ 170, node addr 984be107fdb4
GSI 26 sharing vector 0x33 and IRQ 26
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 18 (level, low) -> IRQ 51
PCI: Setting latency timer of device 0000:03:00.0 to 64
eth6: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f8000000, IRQ 51, node addr 984be107fdb6
GSI 27 sharing vector 0x3B and IRQ 27
ACPI: PCI Interrupt 0000:03:00.1[B] -> GSI 19 (level, low) -> IRQ 59
PCI: Setting latency timer of device 0000:03:00.1 to 64
eth7: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f6000000, IRQ 59, node addr 984be107fdb8
ACPI: PCI Interrupt 0000:01:04.2[B] -> GSI 22 (level, low) -> IRQ 122
scsi 0:0:0:0: Attached scsi generic sg0 type 5
sr0: scsi3-mmc drive: 24x/8x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 0:0:0:0: Attached scsi CD-ROM sr0
floppy0: no floppy controllers found
work still pending
Floppy drive(s): fd0 is 1.44M
floppy0: no floppy controllers found
work still pending
lp: driver loaded but no devices found
ACPI: Power Button (FF) [PWRF]
ACPI: Mapper loaded
dell-wmi: No known WMI GUID foun

Comment 1 Grant Gainey 2011-10-09 00:20:54 UTC
Redirecting to the appropriate product/component

Comment 2 Jirka Klimes 2011-10-10 12:25:28 UTC
The proper component would be initscripts here, I guess, because NetworkManager is not used.

Nonetheless, would you attach /var/log/messages file and relevant icfg files (/etc/sysconfig/network-scripts/ifcfg-eth0, eth3, ...).

Comment 3 William Du 2011-10-10 15:42:17 UTC
Created attachment 527259 [details]
configure files on the server

Comment 4 William Du 2011-10-10 15:44:23 UTC
Klimes,

I can't get messages file today, I could try to get it tomorrow.
for configuration files, I attached them.

we configured bond manually, please help to check.
Thanks a log.

Comment 5 William Du 2011-10-13 07:40:32 UTC
Klimes,

I can't get messages file today, I could try to get it tomorrow.
for configuration files, I attached them.

we configured bond manually, please help to check.
Thanks a log.

Comment 6 Jirka Klimes 2011-10-20 08:28:12 UTC
Could you try latest test kernel from http://people.redhat.com/jwilson/el5/ ?

Also see bug https://bugzilla.redhat.com/show_bug.cgi?id=680411. It's been reported against the same kernel version as yours. There are also some debugging tips there.

Comment 7 Dan Williams 2013-02-19 17:10:59 UTC
Any update on this issue?

Comment 8 Lukáš Nykrýn 2013-03-11 09:52:36 UTC
This bug is now more then a year in needinfo state. Closing as INSUFFICIENT_DATA.