Re: percpu allocation failures in kvm

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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: G        W    3.7.0-ama+ #5
> [   10.230060] Call Trace:
> [   10.230070]  [<ffffffff81129efb>] pcpu_alloc+0x9db/0xa40
> [   10.230074]  [<ffffffff810a81ad>] ? find_symbol_in_section+0x4d/0x140
> [   10.230077]  [<ffffffff810a8160>] ? finished_loading+0x50/0x50
> [   10.230080]  [<ffffffff810a8af0>] ? each_symbol_section+0x30/0x70
> [   10.230083]  [<ffffffff810a8b61>] ? find_symbol+0x31/0x60
> [   10.230086]  [<ffffffff8112a1f3>] __alloc_reserved_percpu+0x13/0x20
> [   10.230089]  [<ffffffff810ab48d>] load_module+0x3ed/0x1b50
> [   10.230093]  [<ffffffff81075c3b>] ? __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 kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux