#6 cant use bonding on IBM x440 with linux 2.6.5 and e1000

open
nobody
None
5
2004-04-05
2004-04-05
Imre Oolberg
No

Hi!

We use linux 2.6.5 kernel from http://www.kernel.org/
and Intel on IBM x440 computer and tried to set up
Linux Channel Bonding using all four ports on Intel
PRO/1000 MT Quad Port Server Adapter. As a result we
couldnt make it work, but we grabed the kernel output
to the syslog and hope it could help you solve the
problem should other user report silmilar situations!

After booting the computer we isseued following commands

# modprobe e1000
# modprobe bonding
# rmmod bonding
# modprobe bonding miimon=100
# ifconfig bond0 10.0.16.1 up
# ifconfig eth2 up
# ifconfig eth3 up
# ifconfig eth4 up
# ifconfig eth5 up
# ifconfig eth2 mtu 15000
# ifconfig eth3 mtu 15000
# ifconfig eth4 mtu 15000
# ifconfig eth5 mtu 15000
# ifconfig bond0 mtu 15000
# ifenslave bond0 eth2 eth3 eth4 eth5

and got this output

Apr 5 17:50:22 ma kernel: Intel(R) PRO/1000 Network
Driver - version 5.2.30.1-k2
Apr 5 17:50:22 ma kernel: Copyright (c) 1999-2004
Intel Corporation.
Apr 5 17:50:22 ma kernel: eth2: Intel(R) PRO/1000
Network Connection
Apr 5 17:50:22 ma kernel: eth3: Intel(R) PRO/1000
Network Connection
Apr 5 17:50:23 ma kernel: eth4: Intel(R) PRO/1000
Network Connection
Apr 5 17:50:23 ma kernel: eth5: Intel(R) PRO/1000
Network Connection
Apr 5 17:50:49 ma kernel: Ethernet Channel Bonding
Driver: v2.6.0 (January 14, 2004)
Apr 5 17:50:49 ma kernel: bonding: Warning: either
miimon or arp_interval and arp_ip_target module
parameters must be specified, otherwi
se bonding will not detect link failures! see
bonding.txt for details.
Apr 5 17:55:10 ma kernel: Ethernet Channel Bonding
Driver: v2.6.0 (January 14, 2004)
Apr 5 17:55:10 ma kernel: bonding: MII link monitoring
set to 100 ms
Apr 5 17:56:48 ma kernel: Debug: sleeping function
called from invalid context at include/asm/uaccess.h:473
Apr 5 17:56:48 ma kernel: in_atomic():1, irqs_disabled():0
Apr 5 17:56:48 ma kernel: Call Trace:
Apr 5 17:56:48 ma kernel: [__might_sleep+163/176]
__might_sleep+0xa3/0xb0
Apr 5 17:56:48 ma kernel: [pg0+943529224/1068793856]
e1000_ethtool_ioctl+0x7c/0x10c4 [e1000]
Apr 5 17:56:48 ma kernel: [__elv_add_request+41/48]
__elv_add_request+0x29/0x30
Apr 5 17:56:48 ma kernel: [__make_request+1167/1348]
__make_request+0x48f/0x544
Apr 5 17:56:48 ma kernel:
[generic_make_request+452/472]
generic_make_request+0x1c4/0x1d8
Apr 5 17:56:48 ma kernel: [buffered_rmqueue+427/448]
buffered_rmqueue+0x1ab/0x1c0
Apr 5 17:56:48 ma kernel: [__alloc_pages+182/776]
__alloc_pages+0xb6/0x308
Apr 5 17:56:48 ma kernel: [do_anonymous_page+626/640]
do_anonymous_page+0x272/0x280
Apr 5 17:56:48 ma kernel: [do_no_page+83/920]
do_no_page+0x53/0x398
Apr 5 17:56:48 ma kernel: [handle_mm_fault+145/340]
handle_mm_fault+0x91/0x154
Apr 5 17:56:48 ma kernel: [do_page_fault+319/1224]
do_page_fault+0x13f/0x4c8
Apr 5 17:56:48 ma kernel: [do_page_fault+0/1224]
do_page_fault+0x0/0x4c8
Apr 5 17:56:48 ma kernel: [vma_link+114/164]
vma_link+0x72/0xa4
Apr 5 17:56:48 ma kernel: [do_mmap_pgoff+1197/1536]
do_mmap_pgoff+0x4ad/0x600
Apr 5 17:56:48 ma kernel: [error_code+45/56]
error_code+0x2d/0x38
Apr 5 17:56:48 ma kernel: [__copy_to_user_ll+96/108]
__copy_to_user_ll+0x60/0x6c
Apr 5 17:56:48 ma kernel: [create_elf_tables+926/940]
create_elf_tables+0x39e/0x3ac
Apr 5 17:56:48 ma kernel: [load_elf_binary+2251/2824]
load_elf_binary+0x8cb/0xb08
Apr 5 17:56:48 ma kernel: [load_elf_binary+0/2824]
load_elf_binary+0x0/0xb08
Apr 5 17:56:48 ma kernel: [schedule+1415/1648]
schedule+0x587/0x670
Apr 5 17:56:48 ma kernel: [__delay+16/20]
__delay+0x10/0x14
Apr 5 17:56:48 ma kernel: [__const_udelay+41/48]
__const_udelay+0x29/0x30
Apr 5 17:56:48 ma kernel: [pg0+943508016/1068793856]
e1000_read_phy_reg_ex+0x48/0xa4 [e1000]
Apr 5 17:56:48 ma kernel: [pg0+943507935/1068793856]
e1000_read_phy_reg+0x37/0x40 [e1000]
Apr 5 17:56:48 ma kernel: [pg0+943498379/1068793856]
e1000_ioctl+0x2f/0x3c [e1000]
Apr 5 17:56:48 ma kernel: [pg0+944113723/1068793856]
bond_update_speed_duplex+0xaf/0x104 [bonding]
Apr 5 17:56:48 ma kernel: [__dev_mc_upload+30/36]
__dev_mc_upload+0x1e/0x24
Apr 5 17:56:48 ma kernel: [pg0+944117084/1068793856]
bond_enslave+0x464/0x728 [bonding]
Apr 5 17:56:48 ma kernel: [pg0+944117150/1068793856]
bond_enslave+0x4a6/0x728 [bonding]
Apr 5 17:56:48 ma kernel: [dev_get_by_name+39/84]
dev_get_by_name+0x27/0x54
Apr 5 17:56:48 ma kernel: [pg0+944126881/1068793856]
bond_do_ioctl+0x3a9/0x3fc [bonding]
Apr 5 17:56:48 ma kernel: [dev_ifsioc+778/808]
dev_ifsioc+0x30a/0x328
Apr 5 17:56:48 ma kernel: [dev_ioctl+826/940]
dev_ioctl+0x33a/0x3ac
Apr 5 17:56:48 ma kernel: [sock_ioctl+99/740]
sock_ioctl+0x63/0x2e4
Apr 5 17:56:48 ma kernel: [sys_ioctl+573/660]
sys_ioctl+0x23d/0x294
Apr 5 17:56:48 ma kernel: [error_code+45/56]
error_code+0x2d/0x38
Apr 5 17:56:48 ma kernel: [syscall_call+7/11]
syscall_call+0x7/0xb
Apr 5 17:56:48 ma kernel:
Apr 5 17:56:48 ma kernel: bonding: bond0: enslaving
eth2 as an active interface with a down link.
Apr 5 17:56:48 ma kernel: bonding: bond0: enslaving
eth3 as an active interface with a down link.
Apr 5 17:56:48 ma kernel: bonding: bond0: enslaving
eth4 as an active interface with a down link.
Apr 5 17:56:48 ma kernel: bonding: bond0: enslaving
eth5 as an active interface with a down link.
Apr 5 17:56:49 ma kernel: Debug: sleeping function
called from invalid context at include/asm/uaccess.h:473
Apr 5 17:56:49 ma kernel: in_atomic():1, irqs_disabled():0
Apr 5 17:56:49 ma kernel: Call Trace:
Apr 5 17:56:49 ma kernel: [__might_sleep+163/176]
__might_sleep+0xa3/0xb0
Apr 5 17:56:49 ma kernel: [pg0+943529224/1068793856]
e1000_ethtool_ioctl+0x7c/0x10c4 [e1000]
Apr 5 17:56:49 ma kernel: [do_bindings+249/720]
do_bindings+0xf9/0x2d0
Apr 5 17:56:49 ma kernel: [ip_nat_fn+480/492]
ip_nat_fn+0x1e0/0x1ec
......

Hope it helps!

Best Regards,
Imre

Discussion