[Xen-bugs] [Bug 753] bonding + vlans + bridging

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=753





------- Comment #8 from mangoo@xxxxxxxx  2006-09-13 06:01 -------
Hmm, the issue seems to be deeper.

My script when starting xend without bonding looks like that:


#!/bin/sh -x

dir=$(dirname "$0")

# below is needed, as oopses/panics occured when it was not there
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0 

# VLANs and attached bridges
"$dir/network-bridge" "$@" vifnum=1 netdev=eth0.100 bridge=xenbr100 
"$dir/network-bridge" "$@" vifnum=2 netdev=eth0.101 bridge=xenbr101
"$dir/network-bridge" "$@" vifnum=3 netdev=eth0.102 bridge=xenbr102


With bonding, I needed to change the script:

#!/bin/sh -x

dir=$(dirname "$0")

"$dir/network-bridge" "$@" vifnum=0 netdev=bond0 bridge=xenbr0 

# needed, as bonding is changed, otherwise no connectivity
ifenslave pbond0 eth0 eth1

# script executes fine up to this point

# below ths point, kernel oopses, but doesn't panic
"$dir/network-bridge" "$@" vifnum=1 netdev=bond0.100 bridge=xenbr100 
"$dir/network-bridge" "$@" vifnum=2 netdev=bond0.101 bridge=xenbr101
"$dir/network-bridge" "$@" vifnum=3 netdev=bond0.102 bridge=xenbr102


This is the oops (the oops happens whether I use "ifenslave pbond0..." or not):

Sep 13 14:39:37 syn2 ifplugd(xenbr100)[3692]: ifplugd 0.28 initializing.
Sep 13 14:39:37 syn2 ifplugd(xenbr100)[3692]: Using interface
xenbr100/00:00:00:00:00:00 with driver <bridge> (version: 2.1)
Sep 13 14:39:37 syn2 ifplugd(xenbr100)[3692]: Using detection mode: SIOCETHTOOL
Sep 13 14:39:37 syn2 ifplugd(xenbr100)[3692]: Initialization complete, link
beat detected.
Sep 13 14:39:37 syn2 ifplugd(xenbr100)[3692]: Executing
'/etc/ifplugd/ifplugd.action xenbr100 up'.
Sep 13 14:39:37 syn2 ifplugd(xenbr100)[3692]: Program executed successfully.
Sep 13 14:39:37 syn2 kernel: bond0.100: del 33:33:ff:0e:7d:2c mcast address
from vlan interface
Sep 13 14:39:37 syn2 kernel: bond0.100: del 33:33:ff:0e:7d:2c mcast address
from master interface
Sep 13 14:39:37 syn2 kernel: bond0.100: del 33:33:00:00:00:01 mcast address
from vlan interface
Sep 13 14:39:37 syn2 kernel: bond0.100: del 33:33:00:00:00:01 mcast address
from master interface
Sep 13 14:39:37 syn2 kernel: bonding: Warning: Cannot create
/proc/net/bonding/<NULL>
Sep 13 14:39:37 syn2 kernel: Unable to handle kernel NULL pointer dereference
at virtual address 00000228
Sep 13 14:39:37 syn2 kernel:  printing eip:
Sep 13 14:39:37 syn2 kernel: c01acc83
Sep 13 14:39:37 syn2 kernel: *pde = ma 00000000 pa fffff000
Sep 13 14:39:37 syn2 kernel: Oops: 0000 [#1]
Sep 13 14:39:37 syn2 kernel: SMP
Sep 13 14:39:37 syn2 kernel: Modules linked in: bridge crc32c libcrc32c ipv6
iscsi_tcp libiscsi scsi_transport_iscsi tg3 bonding 8021q loop hw_random tsdev
ext3 jbd sd_mod ahci ata_piix libata scsi_mod raid1 md_mod
Sep 13 14:39:37 syn2 kernel: CPU:    0
Sep 13 14:39:37 syn2 kernel: EIP:    0061:[sysfs_remove_group+35/128]    Not
tainted VLI
Sep 13 14:39:37 syn2 kernel: EIP:    0061:[<c01acc83>]    Not tainted VLI
Sep 13 14:39:37 syn2 kernel: EFLAGS: 00010202   (2.6.16-xen #6)
Sep 13 14:39:37 syn2 kernel: EIP is at sysfs_remove_group+0x23/0x80
Sep 13 14:39:37 syn2 kernel: eax: 00000000   ebx: c92127a0   ecx: 00000007  
edx: 000001f8
Sep 13 14:39:37 syn2 kernel: esi: c6491a80   edi: c920a498   ebp: c6491810  
esp: c43abe48
Sep 13 14:39:37 syn2 kernel: ds: 007b   es: 007b   ss: 0069
Sep 13 14:39:37 syn2 kernel: Process ip (pid: 3749, threadinfo=c43aa000
task=c1215030)
Sep 13 14:39:37 syn2 kernel: Stack: <0>c43abe54 c91feaaf 00000007 c9212d24
0000000a c920946f 000001f8 c92127a0
Sep 13 14:39:37 syn2 kernel:        c9203084 c6491a80 c6491800 c9212664
c6491800 c012e01d c9212664 0000000a
Sep 13 14:39:37 syn2 kernel:        c6491800 0000000a c6491800 fc3591d7
c02add53 c0435940 0000000a c6491800
Sep 13 14:39:37 syn2 kernel: Call Trace:
Sep 13 14:39:38 syn2 kernel:  [<c91feaaf>] bond_create_proc_entry+0x8f/0xa0
[bonding]
Sep 13 14:39:38 syn2 kernel:  [<c920946f>] bond_destroy_sysfs_entry+0x1f/0x30
[bonding]
Sep 13 14:39:38 syn2 kernel:  [<c9203084>] bond_netdev_event+0x84/0xc0
[bonding]
Sep 13 14:39:38 syn2 kernel:  [notifier_call_chain+45/80]
notifier_call_chain+0x2d/0x50
Sep 13 14:39:38 syn2 kernel:  [<c012e01d>] notifier_call_chain+0x2d/0x50
Sep 13 14:39:38 syn2 kernel:  [dev_change_name+387/512]
dev_change_name+0x183/0x200
Sep 13 14:39:38 syn2 kernel:  [<c02add53>] dev_change_name+0x183/0x200
Sep 13 14:39:38 syn2 kernel:  [find_get_page+36/128] find_get_page+0x24/0x80
Sep 13 14:39:38 syn2 kernel:  [<c0142bd4>] find_get_page+0x24/0x80
Sep 13 14:39:38 syn2 kernel:  [dev_ifsioc+396/912] dev_ifsioc+0x18c/0x390
Sep 13 14:39:38 syn2 kernel:  [<c02adf5c>] dev_ifsioc+0x18c/0x390
Sep 13 14:39:38 syn2 kernel:  [dev_ioctl+891/1072] dev_ioctl+0x37b/0x430
Sep 13 14:39:38 syn2 kernel:  [<c02ae52b>] dev_ioctl+0x37b/0x430
Sep 13 14:39:38 syn2 kernel:  [fd_install+44/112] fd_install+0x2c/0x70
Sep 13 14:39:38 syn2 kernel:  [<c016567c>] fd_install+0x2c/0x70
Sep 13 14:39:38 syn2 kernel:  [do_ioctl+53/160] do_ioctl+0x35/0xa0
Sep 13 14:39:39 syn2 kernel:  [<c017af35>] do_ioctl+0x35/0xa0
Sep 13 14:39:39 syn2 kernel:  [vfs_ioctl+93/816] vfs_ioctl+0x5d/0x330
Sep 13 14:39:39 syn2 kernel:  [<c017affd>] vfs_ioctl+0x5d/0x330
Sep 13 14:39:39 syn2 kernel:  [sys_ioctl+136/160] sys_ioctl+0x88/0xa0
Sep 13 14:39:39 syn2 kernel:  [<c017b358>] sys_ioctl+0x88/0xa0
Sep 13 14:39:39 syn2 kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Sep 13 14:39:39 syn2 kernel:  [<c0105109>] syscall_call+0x7/0xb
Sep 13 14:39:39 syn2 kernel: Code: 83 c4 08 5b 5e c3 89 f6 57 53 83 ec 0c 8b 5c
24 1c 8b 54 24 18 8b 3b 85 ff 74 4d 31 c0 b9 ff ff ff ff f2 ae f7 d1 49 89 4c
24 08 <8b> 42 30 89 44 24 04 8b 03 89 04 24 e8 bc 9a fc ff 89 c7 89 f8
Sep 13 14:39:47 syn2 kernel:  <7>xenbr100: no IPv6 routers present


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs