|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_nofl
On Wed, May 05, 2010 at 11:18:52PM -0400, Gerry Reno wrote:
> On 05/05/2010 01:54 PM, Konrad Rzeszutek Wilk wrote:
>>> Finally, my serial port header cables showed up so I installed them and
>>> now have some console output.
>>>
>>> Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 2.6.32.10
>>>
>>> After playing around with the order of the consoles on the xen and
>>> kernel lines I am able to get a login prompt but only after quite a long
>>> time (4-5 mins). It seems like something is stealing processor cycles.
>>> And the behavior is not consistent, on different boots I get different
>>> errors at times.
>>>
>>>
>>> Case 1: pv_ops domU kernel 2.6.32.10 (no xen dom0)
>>>
>>> The kernel shows a lot of errors and just hangs.
>>>
>>>
>>>
>>> Attached: console output for both cases plus menu.lst
>>>
>>> -Gerry
>>>
>>>
>>>
>>>
>>
>>> [ 1.616751] pci 0000:00:0a.0: PCI INT A -> GSI 18 (level, low) -> IRQ
>>> 18
>>> [ 1.623549] NET: Registered protocol family 2
>>> [ 1.628090] IP route cache hash table entries: 262144 (order: 9, 2097152
>>> bytes)
>>> [ 1.636549] ------------[ cut here ]------------
>>> [ 1.641209] WARNING: at mm/vmalloc.c:110
>>> vmap_page_range_noflush+0x301/0x380()
>>> [ 1.648440] Hardware name: GA-MA790GP-UD4H
>>> [ 1.652582] Modules linked in:
>>> [ 1.655710] Pid: 1, comm: swapper Not tainted 2.6.32.10 #12
>>> [ 1.661321] Call Trace:
>>> [ 1.663801] [<ffffffff8106602b>] warn_slowpath_common+0x7b/0xc0
>>> [ 1.669819] [<ffffffff81066084>] warn_slowpath_null+0x14/0x20
>>> [ 1.675698] [<ffffffff8111bb31>] vmap_page_range_noflush+0x301/0x380
>>> [ 1.682164] [<ffffffff8111bbe2>] map_vm_area+0x32/0x50
>>> [ 1.687402] [<ffffffff8111d010>] __vmalloc_area_node+0x100/0x190
>>> [ 1.693535] [<ffffffff81898700>] ? alloc_large_system_hash+0x15e/0x222
>>> [ 1.700172] [<ffffffff8111cf02>] __vmalloc_node+0xa2/0xb0
>>> [ 1.705671] [<ffffffff81898700>] ? alloc_large_system_hash+0x15e/0x222
>>> [ 1.712324] [<ffffffff818b4a72>] ? inet_init+0x0/0x209
>>> [ 1.717562] [<ffffffff8111d282>] __vmalloc+0x22/0x30
>>> [ 1.722653] [<ffffffff81898700>] alloc_large_system_hash+0x15e/0x222
>>> [ 1.729916] [<ffffffff818b4a72>] ? inet_init+0x0/0x209
>>> [ 1.735186] [<ffffffff818b4a72>] ? inet_init+0x0/0x209
>>> [ 1.740438] [<ffffffff818b44b6>] tcp_init+0xa3/0x383
>>> [ 1.745505] [<ffffffff818b4bbd>] inet_init+0x14b/0x209
>>> [ 1.750772] [<ffffffff8100a04c>] do_one_initcall+0x3c/0x1a0
>>> [ 1.756451] [<ffffffff8187972c>] kernel_init+0x15a/0x1b0
>>> [ 1.761890] [<ffffffff810150ea>] child_rip+0xa/0x20
>>> [ 1.766870] [<ffffffff818795d2>] ? kernel_init+0x0/0x1b0
>>> [ 1.772307] [<ffffffff810150e0>] ? child_rip+0x0/0x20
>>> [ 1.777461] ---[ end trace e93713a9d40cd06c ]---
>>> [ 1.782160] general protection fault: 0000 [#1] SMP
>>>
>> This is the same error I've gotten. Now thought I can't reproduce it (after
>> I slimmed down the .config to build less modules).
>>
>> Try 'nopat' as a command line parameter.
>>
>> Also, you might want to update your kernel. The 2.6.32.12 is out
>>
>>
> Thanks. I tried 'nopat' but that did not seem to change anything.
>
> I also tried 'git pull' for xen/stable but it says 'Already up to date'.
> So where do I find the 2.6.32.12?
>
You should be using xen/stable-2.6.32.x branch.
changelog:
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen/stable-2.6.32.x
-- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core, Konrad Rzeszutek Wilk
- Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core, Gerry Reno
- Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core, Konrad Rzeszutek Wilk
- Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core, Gerry Reno
- Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core, Gerry Reno
- Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush, Konrad Rzeszutek Wilk
- Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush, Gerry Reno
- Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush,
Pasi Kärkkäinen <=
- Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush, Jeremy Fitzhardinge
- Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush, Gerry Reno
- Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush, Gerry Reno
- Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush, Gerry Reno
- Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush, Pasi Kärkkäinen
- Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush, Boris Derzhavets
- Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush, Gerry Reno
- Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush, Gerry Reno
- Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush, Boris Derzhavets
- Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush, Konrad Rzeszutek Wilk
|
|
|
|
|