[Xen-devel] Re: [PATCH] xen/gntdev: Fix sleep-inside-spinlock

[Dario Faggioli <raistlin@xxxxxxxx>]

On Thu, 2011-10-13 at 11:40 -0400, Konrad Rzeszutek Wilk wrote:
> Dario, does the patch fix the problem for you?
> 
Here I am, and sorry for being late, I had issues with a testbox and
needed to setup a new one.

Actually, I was just trying to check that, but I'm now hitting this when
trying to boot a PV-guest:
[    6.129478] BUG: scheduling while atomic: swapper/0/0x10000002
[    6.129483] no locks held by swapper/0.
[    6.129487] Pid: 0, comm: swapper Not tainted 3.1.0-rc9+ #14
[    6.129492] Call Trace:
[    6.129504]  [<ffffffff81054550>] __schedule_bug+0x80/0x85
[    6.129513]  [<ffffffff81b7fc73>] __schedule+0xa5/0x6ad
[    6.129520]  [<ffffffff8105aed1>] __cond_resched+0x2a/0x35
[    6.129525]  [<ffffffff81b802f6>] _cond_resched+0x2c/0x37
[    6.129533]  [<ffffffff810dedce>] __alloc_pages_nodemask+0xa5/0x73a
[    6.129542]  [<ffffffff810082c5>] ? p2m_top_index+0x9/0x1f
[    6.129547]  [<ffffffff8100849b>] ? get_phys_to_machine+0x1f/0x62
[    6.129556]  [<ffffffff8143ee6d>] ? trace_hardirqs_off_thunk+0x3a/0x3c
[    6.129562]  [<ffffffff8143ee2e>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[    6.129568]  [<ffffffff81b831b4>] ? retint_restore_args+0x13/0x13
[    6.129573]  [<ffffffff810082c5>] ? p2m_top_index+0x9/0x1f
[    6.129581]  [<ffffffff8110d445>] alloc_page_interleave+0x39/0x86
[    6.129587]  [<ffffffff81004e0d>] ? xen_make_pte+0x8a/0x8e
[    6.129592]  [<ffffffff8110d501>] alloc_pages_current+0x6f/0xbf
[    6.129598]  [<ffffffff810dd92a>] __get_free_pages+0xe/0x3d
[    6.129605]  [<ffffffff8103acc0>] pte_alloc_one_kernel+0x15/0x17
[    6.129611]  [<ffffffff810f56d9>] __pte_alloc_kernel+0x1b/0xf4
[    6.129617]  [<ffffffff8110292a>] vmap_page_range_noflush+0x1c5/0x317
[    6.129623]  [<ffffffff81102aae>] ? map_vm_area+0x32/0x46
[    6.129629]  [<ffffffff8100763d>] ? xen_force_evtchn_callback+0xd/0xf
[    6.129634]  [<ffffffff81102aae>] map_vm_area+0x32/0x46
[    6.129640]  [<ffffffff81103a94>] __vmalloc_node_range+0x194/0x1d6
[    6.129648]  [<ffffffff8254a0a5>] ? alloc_large_system_hash+0x14c/0x203
[    6.129654]  [<ffffffff81007d4f>] ? xen_restore_fl_direct_reloc+0x4/0x4
[    6.129660]  [<ffffffff81103b0b>] __vmalloc_node+0x35/0x37
[    6.129666]  [<ffffffff8254a0a5>] ? alloc_large_system_hash+0x14c/0x203
[    6.129672]  [<ffffffff81103cd3>] __vmalloc+0x20/0x22
[    6.129677]  [<ffffffff8254a0a5>] alloc_large_system_hash+0x14c/0x203
[    6.129683]  [<ffffffff8254e4bb>] vfs_caches_init+0x9d/0x10f
[    6.129690]  [<ffffffff82529da9>] start_kernel+0x378/0x3b5
[    6.129696]  [<ffffffff825292cd>] x86_64_start_reservations+0xb8/0xbc
[    6.129702]  [<ffffffff8252cfc7>] xen_start_kernel+0x5ab/0x5b2

So, am I doing something stupid (e.g., VM config file, which is
attached) or this is a different thing as a whole? :-O

I have to say that I updated both Linux and xen-unstable in these days.

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
----------------------------------------------------------------------
Dario Faggioli, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
PhD Candidate, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa  (Italy)

Debian-squeeze.pv
Description: Text document

signature.asc
Description: This is a digitally signed message part

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