Attachment 294816 Details for Bug 432622 – 'service network start' kernel messages

'service network start' kernel messages

dmesg-2.txt (text/plain), 2.95 KB, created by Juanjo Villaplana on 2008-02-13 17:38:25 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Juanjo Villaplana

Created: 2008-02-13 17:38:25 UTC

Size: 2.95 KB

patch

obsolete

>Ethernet Channel Bonding Driver: v2.6.3-rh (June 8, 2005)
>bonding: MII link monitoring set to 100 ms
>divert: allocating divert_blk for bond0
>Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.5.11-rh (June 4, 2007)
>ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 169
>divert: allocating divert_blk for eth0
>eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B1) PCI-X 64-bit 133MHz found at mem f8000000, IRQ 169, node addr 0019bbc7a872
>ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 17 (level, low) -> IRQ 177
>divert: allocating divert_blk for eth1
>eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B1) PCI-X 64-bit 133MHz found at mem fa000000, IRQ 177, node addr 0019bbc7a870
>bnx2: eth0: using MSI
>ADDRCONF(NETDEV_UP): eth0: link is not ready
>bonding: bond0: enslaving eth0 as a backup interface with a down link.
>bnx2: eth1: using MSI
>ADDRCONF(NETDEV_UP): eth1: link is not ready
>bonding: bond0: enslaving eth1 as a backup interface with a down link.
>bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex
>ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>bonding: bond0: link status definitely up for interface eth0.
>bonding: bond0: making interface eth0 the new active one.
>bonding: bond0: first active interface up!
>bnx2: eth1 NIC Link is Up, 1000 Mbps full duplex
>bonding: bond0: link status definitely up for interface eth1.
>ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
>bond0: no IPv6 routers present
>eth0: no IPv6 routers present
>eth1: no IPv6 routers present
>bonding: Warning: the permanent HWaddr of eth0 - 00:19:BB:C7:A8:72 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
>bonding: bond0: releasing active interface eth0
>bonding: bond0: making interface eth1 the new active one.
>bnx2: eth0: using MSI
>ADDRCONF(NETDEV_UP): eth0: link is not ready
>bonding: bond0: enslaving eth0 as a backup interface with a down link.
>bonding: bond0: releasing active interface eth1
>bnx2: eth1: using MSI
>ADDRCONF(NETDEV_UP): eth1: link is not ready
>bonding: bond0: enslaving eth1 as a backup interface with a down link.
>divert: allocating divert_blk for vlan8
>ADDRCONF(NETDEV_UP): vlan8: link is not ready
>bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex
>bonding: bond0: link status definitely up for interface eth0.
>bonding: bond0: making interface eth0 the new active one.
>bonding: bond0: first active interface up!
>ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>bnx2: eth1 NIC Link is Up, 1000 Mbps full duplex
>bonding: bond0: link status definitely up for interface eth1.
>ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
>vlan8: add 01:00:5e:00:00:01 mcast address to master interface
>ADDRCONF(NETDEV_CHANGE): vlan8: link becomes ready
>vlan8: add 33:33:00:00:00:01 mcast address to master interface
>vlan8: add 33:33:ff:c7:a8:72 mcast address to master interface
>bonding: bond0: link status definitely down for interface eth0, disabling it
>bonding: bond0: making interface eth1 the new active one.
>eth1: no IPv6 routers present
>vlan8: no IPv6 routers present

Actions: View

Attachments on bug 432622: 294772 | 294773 | 294774 | 294775 | 294776 | 294777 | 294783 | 294816 | 294817 | 294818 | 294820