Re: percpu allocation failures in kvm

2012-12-14 Thread Andy Lutomirski
On Fri, Dec 14, 2012 at 5:03 PM, Marcelo Tosatti  wrote:
> On Thu, Dec 13, 2012 at 09:43:23PM -0800, Andy Lutomirski wrote:
>> On 3.7.0 + irrelevant patches, I get this on boot.  I've seen it on
>> and off on earlier kernels, I think (although I'm not currently
>> getting it on 3.5).
>>
>> [   10.230054] PERCPU: allocation failed, size=304 align=32, alloc
>> from reserved chunk failed
>> [   10.230059] Pid: 1026, comm: modprobe Tainted: GW3.7.0-ama+ #5
>> [   10.230060] Call Trace:
>> [   10.230070]  [] pcpu_alloc+0x9db/0xa40
>> [   10.230074]  [] ? find_symbol_in_section+0x4d/0x140
>> [   10.230077]  [] ? finished_loading+0x50/0x50
>> [   10.230080]  [] ? each_symbol_section+0x30/0x70
>> [   10.230083]  [] ? find_symbol+0x31/0x60
>> [   10.230086]  [] __alloc_reserved_percpu+0x13/0x20
>> [   10.230089]  [] load_module+0x3ed/0x1b50
>> [   10.230093]  [] ? __srcu_read_unlock+0x4b/0x70
>>
>> --Andy
>
> You're loading the kvm module, or loading some other module inside
> a kvm guest?
>

This is loading the kvm module on startup.  There are no guests.

-- 
Andy Lutomirski
AMA Capital Management, LLC
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: percpu allocation failures in kvm

2012-12-14 Thread Marcelo Tosatti
On Thu, Dec 13, 2012 at 09:43:23PM -0800, Andy Lutomirski wrote:
> On 3.7.0 + irrelevant patches, I get this on boot.  I've seen it on
> and off on earlier kernels, I think (although I'm not currently
> getting it on 3.5).
> 
> [   10.230054] PERCPU: allocation failed, size=304 align=32, alloc
> from reserved chunk failed
> [   10.230059] Pid: 1026, comm: modprobe Tainted: GW3.7.0-ama+ #5
> [   10.230060] Call Trace:
> [   10.230070]  [] pcpu_alloc+0x9db/0xa40
> [   10.230074]  [] ? find_symbol_in_section+0x4d/0x140
> [   10.230077]  [] ? finished_loading+0x50/0x50
> [   10.230080]  [] ? each_symbol_section+0x30/0x70
> [   10.230083]  [] ? find_symbol+0x31/0x60
> [   10.230086]  [] __alloc_reserved_percpu+0x13/0x20
> [   10.230089]  [] load_module+0x3ed/0x1b50
> [   10.230093]  [] ? __srcu_read_unlock+0x4b/0x70
> 
> --Andy

You're loading the kvm module, or loading some other module inside
a kvm guest?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: percpu allocation failures in kvm

2012-12-14 Thread Marcelo Tosatti
On Thu, Dec 13, 2012 at 09:43:23PM -0800, Andy Lutomirski wrote:
 On 3.7.0 + irrelevant patches, I get this on boot.  I've seen it on
 and off on earlier kernels, I think (although I'm not currently
 getting it on 3.5).
 
 [   10.230054] PERCPU: allocation failed, size=304 align=32, alloc
 from reserved chunk failed
 [   10.230059] Pid: 1026, comm: modprobe Tainted: GW3.7.0-ama+ #5
 [   10.230060] Call Trace:
 [   10.230070]  [81129efb] pcpu_alloc+0x9db/0xa40
 [   10.230074]  [810a81ad] ? find_symbol_in_section+0x4d/0x140
 [   10.230077]  [810a8160] ? finished_loading+0x50/0x50
 [   10.230080]  [810a8af0] ? each_symbol_section+0x30/0x70
 [   10.230083]  [810a8b61] ? find_symbol+0x31/0x60
 [   10.230086]  [8112a1f3] __alloc_reserved_percpu+0x13/0x20
 [   10.230089]  [810ab48d] load_module+0x3ed/0x1b50
 [   10.230093]  [81075c3b] ? __srcu_read_unlock+0x4b/0x70
 
 --Andy

You're loading the kvm module, or loading some other module inside
a kvm guest?

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: percpu allocation failures in kvm

2012-12-14 Thread Andy Lutomirski
On Fri, Dec 14, 2012 at 5:03 PM, Marcelo Tosatti mtosa...@redhat.com wrote:
 On Thu, Dec 13, 2012 at 09:43:23PM -0800, Andy Lutomirski wrote:
 On 3.7.0 + irrelevant patches, I get this on boot.  I've seen it on
 and off on earlier kernels, I think (although I'm not currently
 getting it on 3.5).

 [   10.230054] PERCPU: allocation failed, size=304 align=32, alloc
 from reserved chunk failed
 [   10.230059] Pid: 1026, comm: modprobe Tainted: GW3.7.0-ama+ #5
 [   10.230060] Call Trace:
 [   10.230070]  [81129efb] pcpu_alloc+0x9db/0xa40
 [   10.230074]  [810a81ad] ? find_symbol_in_section+0x4d/0x140
 [   10.230077]  [810a8160] ? finished_loading+0x50/0x50
 [   10.230080]  [810a8af0] ? each_symbol_section+0x30/0x70
 [   10.230083]  [810a8b61] ? find_symbol+0x31/0x60
 [   10.230086]  [8112a1f3] __alloc_reserved_percpu+0x13/0x20
 [   10.230089]  [810ab48d] load_module+0x3ed/0x1b50
 [   10.230093]  [81075c3b] ? __srcu_read_unlock+0x4b/0x70

 --Andy

 You're loading the kvm module, or loading some other module inside
 a kvm guest?


This is loading the kvm module on startup.  There are no guests.

-- 
Andy Lutomirski
AMA Capital Management, LLC
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/