https://bugzilla.novell.com/show_bug.cgi?id=343904#c13
--- Comment #13 from Camaleon -- 2007-11-29 14:05:36 MST ---
Good news! :-)
After performed a system update (about ~250 MB. of data) now channel bonding
can be configured by yast with no problems at all!
The system does not lock neither freeze and dmesg shows no interesthing data
after bonding configuration... So it seem I was being bitten by a kernel bug
that afected intel cards module (e1000) while bonding.
Anyway, I put here all the tests I have made now... all it seems o.k.:
- ifconfig
bond0 Link encap:Ethernet HWaddr 00:30:48:76:BF:52
inet addr:10.0.0.11 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe76:bf52/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:476 errors:0 dropped:0 overruns:0 frame:0
TX packets:454 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:45030 (43.9 Kb) TX bytes:110243 (107.6 Kb)
eth0 Link encap:Ethernet HWaddr 00:30:48:76:BF:52
inet6 addr: fe80::230:48ff:fe76:bf52/64 Scope:Link
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:148 errors:0 dropped:0 overruns:0 frame:0
TX packets:137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14753 (14.4 Kb) TX bytes:12405 (12.1 Kb)
Base address:0x2000 Memory:d6000000-d6020000
eth1 Link encap:Ethernet HWaddr 00:30:48:76:BF:52
inet6 addr: fe80::230:48ff:fe76:bf52/64 Scope:Link
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:328 errors:0 dropped:0 overruns:0 frame:0
TX packets:317 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:30277 (29.5 Kb) TX bytes:97838 (95.5 Kb)
Base address:0x2040 Memory:d6020000-d6040000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:600 (600.0 b) TX bytes:600 (600.0 b)
- cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.1.3 (June 13, 2007)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth1
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth0
MII Status: up
Link Failure Count: 1
Permanent HW addr: 00:30:48:76:bf:52
Slave Interface: eth1
MII Status: up
Link Failure Count: 1
Permanent HW addr: 00:30:48:76:bf:53
- rcnetwork status
Checking optional network interfaces:
bond0
bond0 IP address: 10.0.0.11/24 running
Interface bonding_masters is not available dead
eth0 device: Intel Corporation 82541GI Gigabit Ethernet Controller
(rev 05)
eth0 is still used from interfaces bond0 running
eth1 device: Intel Corporation 82541GI Gigabit Ethernet Controller
(rev 05)
eth1 is still used from interfaces bond0 running
Checking mandatory network interfaces:
lo
IP address: 127.0.0.1/8 running
Checking service network . . . . . . . . . . . . . . . running
Please note the result of this last command, it says "Interface bonding_masters
is not available... dead" but I don't know if this is a normal behaviour or
what are the side effects of this message as anything else seems to be working
o.k.
Also, "rcnetwork restart" can be performed with not problems at all and network
service come to live again.
- ping -c 3 google.com
While pinging, I disconnected one network cable (eth0) and the ping continues.
Also, while removing eth1... and /var/log/messages it says:
Nov 29 21:19:14 linux01 kernel: e1000: eth1: e1000_watchdog_task: NIC Link is
Down
Nov 29 21:19:14 linux01 kernel: bonding: bond0: link status definitely down for
interface eth1, disabling it
Nov 29 21:19:27 linux01 kernel: e1000: eth1: e1000_watchdog_task: NIC Link is
Up 1000 Mbps Full Duplex, Flow Control: RX/
TX
Nov 29 21:19:27 linux01 kernel: bonding: bond0: link status definitely up for
interface eth1.
Nov 29 21:19:31 linux01 kernel: e1000: eth0: e1000_watchdog_task: NIC Link is
Down
Nov 29 21:19:31 linux01 kernel: bonding: bond0: link status definitely down for
interface eth0, disabling it
Nov 29 21:19:31 linux01 kernel: bonding: bond0: making interface eth1 the new
active one.
Nov 29 21:19:44 linux01 kernel: e1000: eth0: e1000_watchdog_task: NIC Link is
Up 1000 Mbps Full Duplex, Flow Control: RX/
TX
Nov 29 21:19:44 linux01 kernel: bonding: bond0: link status definitely up for
interface eth0.
I added in /etc/modprobe.conf.local the following data:
alias bond0 bonding
options bonding miimon=100 mode=active-backup
Because after Yast configuration, /var/log/messages displayed:
kernel: bonding: Warning: either miimon or arp_interval and arp_ip_target
module parameters must
be specified, otherwise bonding will not detect link failures! see bonding.txt
for details.
After adding the lines, no more such messages were displayed.
So well, unless you may need further information about the message displayed
with "rcnetwork status" about "bonding_masters not availabe" I think this bug
can be closed.
I going to keep an eye on this machine, but the problem was just my fault as I
had to update the whole system immediately after the installation... so it
seems my friend was on the right path by advising me to update!
Thanks for all!
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.