RE: [Xen-devel] kernel BUG at arch/xen/i386/mm/hypervisor.c:354, (xen_create _contiguous_region)!

["Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>]

This is believed fixed, at least in the staging tree.
It was introduced as a result of the change to avoid the alignment problem 
introduced by setting CONFIG_DEBUG_SLABALLOC=y in Fedora kernels.

Pretty much all the bugs that have been filed today are different incarnations 
of this issue.

It's quite interesting in that it's the first example of a regression that 
survived the mini-XenRT test run but blew up badly on the long overnight run. 
It was probably fixed before anyone in the US woke up, but there was a backlog 
in the staging tree...

[see the xenrt web page for the full horror of last nights run!]

Ian 

> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=395
> 
> The guest domain crashed during the routine daily tests that I ran.
> 
> Machine: IBM ThinkCentre, 1GB of RAM with FC3 based setup.
> 
> Xen build, PAE enabled using changeset:   7701:abbe3df33774
> 
> [root@thinkcentre-dom0 xen-unstable.hg]# cat /proc/cpuinfo
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 15
> model           : 3
> model name      : Intel(R) Pentium(R) 4 CPU 3.00GHz
> stepping        : 4
> cpu MHz         : 2992.638
> cache size      : 1024 KB
> fdiv_bug        : no
> hlt_bug         : yes
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 3
> wp              : yes
> flags           : fpu tsc msr pae mce cx8 apic mtrr mca cmov 
> pat pse36 
> clflush
> dts acpi mmx fxsr sse sse2 ss ht tm pbe pni monitor ds_cpl cid xtpr
> bogomips        : 5976.88
> 
> Problem:
> 
> kernel BUG at arch/xen/i386/mm/hypervisor.c:354 (xen_create 
> _contiguous_region)!
>  Ä<c011847b>Ü xen_create_contiguous_region+0x2eb/0x360
>  Ä<c026761e>Ü net_rx_action+0x13e/0x220
>  Ä<c01072d9>Ü skbuff_ctor+0x69/0x70
>  Ä<c014d965>Ü cache_init_objs+0x55/0x90
>  Ä<c014db8c>Ü cache_grow+0x13c/0x240
>  Ä<c014deb6>Ü cache_alloc_refill+0x226/0x260  Ä<c014e14c>Ü 
> kmem_cache_alloc+0x9c/0xb0  Ä<c02601cd>Ü 
> alloc_skb_from_cache+0x4d/0x100  Ä<c01071cb>Ü 
> alloc_skb+0x9b/0xc0  Ä<c025ee90>Ü 
> sock_alloc_send_pskb+0xc0/0x1d0  Ä<c025efcd>Ü 
> sock_alloc_send_skb+0x2d/0x40  Ä<c02aff19>Ü 
> unix_stream_sendmsg+0x199/0x470  Ä<c02c52a2>Ü 
> schedule+0x3f2/0x780  Ä<c025be31>Ü sock_aio_write+0x101/0x120 
>  Ä<c01778df>Ü pipe_wait+0x8f/0xb0  Ä<c0169c39>Ü 
> do_sync_write+0xc9/0x110  Ä<c0177c0a>Ü pipe_readv+0x2ba/0x360 
>  Ä<c0139200>Ü autoremove_wake_function+0x0/0x60  Ä<c0199c9a>Ü 
> dnotify_parent+0x3a/0xe0  Ä<c0177ce8>Ü pipe_read+0x38/0x40  
> Ä<c0169d2c>Ü vfs_write+0xac/0x160  Ä<c0169eb1>Ü 
> sys_write+0x51/0x80  Ä<c010a1e9>Ü syscall_call+0x7/0xb Kernel 
> panic - not syncing: BUG!
> 
> --
> Regards,
> 
> David F Barrera
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 

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