Re: XENUs crash on network activity.

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Sat, May 27, 2006 at 12:16:59AM +0200, Marcin Jessa wrote:
> Hi guys.
> 
> I updated my XEN2 kernels/base today to 3.99.20.
> Whenever I try to connect to the world outside from my XENUs they just
> reboot. Simple links or ftp will take down entire host...
> Both of my XENU hosts run in vnode devices and their virtual network
> interfaces are bridged with the same bridge0.
> # brconfig -a
> bridge0: flags=41<UP,RUNNING>
>         Configuration:
>                 priority 32768 hellotime 2 fwddelay 15 maxage 20
>                 ipfilter disabled flags 0x0
>         Interfaces:
>                 xvif2.0 flags=3<LEARNING,DISCOVER>
>                         port 8 priority 128
>                 xvif1.0 flags=3<LEARNING,DISCOVER>
>                         port 7 priority 128
>                 vlan0 flags=3<LEARNING,DISCOVER>
>                         port 4 priority 128
>         Address cache (max cache: 100, timeout: 1200):
>                 00:0c:42:04:90:81 vlan0 963 flags=0<>
>                 aa:00:00:50:02:f0 xvif2.0 879 flags=0<>
>                 aa:00:00:50:02:b3 xvif1.0 264 flags=0<>
> 
> The VLAN0 interface is 'attached' to re0 nic.
> 
> This setup worked very well until the kernel upgrade.
> This is what happens when I log in to console and run ftp to fetch a
> simple FDF document:
> 
> # ftp
> http://www.yazzy.org/docs/Operating_Systems/BSD/NetBSD/Linux_to_Net>
> Requesting
> http://www.yazzy.org/docs/Operating_Systems/BSD/NetBSD/Linux_to_NetBSD.pdf
>   0% |                                     |     0       0.00 KB/s   
> --:-- ETA
> fatal page fault in supervisor mode 
> trap type 6 code 0 eip c0108efb cs 9 eflags 10206 cr2 0 ilevel 2 
> panic: trap 
> syncing disks... 3 3 3 3 3 1 done
> 
> dumping to dev 142,1 offset 328719
> dump device bad
> 
> rebooting...

I don't get a crash but a hang, which looks like a loop on ipintr.
Could you try the kernel from
ftp://ftp.fr.netbsd.org/pub/NetBSD-daily/HEAD/200605220000Z/i386/binary/kernel/netbsd-XENU.gz
and see if it works for you ? This would help narrow down the change that
cause problem.

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--