xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: Carsten Schiers <carsten@schiers.de>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: AW: Re: Xen BUG in mm / Xen 4.0.1 with 2.6.32.18/21 pvops Kernel?
Date: Fri, 10 Sep 2010 09:22:37 +0100	[thread overview]
Message-ID: <4C8A06ED02000078000155E5@vpn.id2.novell.com> (raw)
In-Reply-To: <H000006700083071.1284059062.uhura.space.zz@MHS>

>>> On 09.09.10 at 21:04, "Carsten Schiers" <carsten@schiers.de> wrote:
> [    3.711073] WARNING: at mm/page_alloc.c:1820 
> __alloc_pages_nodemask+0x1b5/0x603()

Is it this warning

	if (order >= MAX_ORDER) {
		WARN_ON_ONCE(!(gfp_mask & __GFP_NOWARN));
		return NULL;
	}

according to your sources? And do you not see it with a native
kernel?

Jan

> [    3.711073] Hardware name: To Be Filled By O.E.M.
> [    3.711073] Modules linked in:
> [    3.711073] Pid: 1, comm: swapper Not tainted 2.6.32.21 #1
> [    3.711073] Call Trace:
> [    3.711073]  [<ffffffff810478da>] warn_slowpath_common+0x77/0x8f
> [    3.711073]  [<ffffffff81047901>] warn_slowpath_null+0xf/0x11
> [    3.711073]  [<ffffffff810afcae>] __alloc_pages_nodemask+0x1b5/0x603
> [    3.711073]  [<ffffffff81030e41>] ? __ioremap_caller+0x291/0x2f7
> [    3.711073]  [<ffffffff8146bed2>] ? _spin_unlock_irqrestore+0x48/0x4b
> [    3.711073]  [<ffffffff81459bc1>] ? acpi_os_map_memory+0x12/0x1b
> [    3.711073]  [<ffffffff810b010e>] __get_free_pages+0x12/0x4f
> [    3.711073]  [<ffffffff810daae5>] __kmalloc+0x42/0x180
> [    3.711073]  [<ffffffff81253f53>] acpi_os_allocate+0x33/0x35
> [    3.711073]  [<ffffffff8125402d>] acpi_ex_load_op+0xd8/0x263
> [    3.711073]  [<ffffffff812567ae>] acpi_ex_opcode_1A_1T_0R+0x25/0x4b
> [    3.711073]  [<ffffffff8124e020>] acpi_ds_exec_end_op+0xea/0x3d6
> [    3.711073]  [<ffffffff8125feef>] acpi_ps_parse_loop+0x7bb/0x940
> [    3.711073]  [<ffffffff8124e8f5>] ? 
> acpi_ds_call_control_method+0x174/0x1e3
> [    3.711073]  [<ffffffff8125eff5>] acpi_ps_parse_aml+0x9a/0x2d9
> [    3.711073]  [<ffffffff8126073a>] acpi_ps_execute_method+0x1e4/0x2b6
> [    3.711073]  [<ffffffff8125bec9>] acpi_ns_evaluate+0xe1/0x1a8
> [    3.711073]  [<ffffffff8125b910>] acpi_evaluate_object+0xf9/0x1f2
> [    3.711073]  [<ffffffff81023da1>] ? init_intel_pdc+0xd1/0x191
> [    3.711073]  [<ffffffff81269ec7>] acpi_processor_set_pdc+0x3c/0x3e
> [    3.711073]  [<ffffffff8146988d>] xen_acpi_processor_add+0x303/0x43a
> [    3.711073]  [<ffffffff812453a7>] acpi_device_probe+0x4b/0x11d
> [    3.711073]  [<ffffffff812f7f70>] driver_probe_device+0x9a/0x11f
> [    3.711073]  [<ffffffff812f804d>] __driver_attach+0x58/0x7c
> [    3.711073]  [<ffffffff812f7ff5>] ? __driver_attach+0x0/0x7c
> [    3.711073]  [<ffffffff812f75ce>] bus_for_each_dev+0x4e/0x83
> [    3.711073]  [<ffffffff812f7def>] driver_attach+0x19/0x1b
> [    3.711073]  [<ffffffff812f7a47>] bus_add_driver+0xb1/0x1fe
> [    3.711073]  [<ffffffff812f8311>] driver_register+0x99/0x10a
> [    3.711073]  [<ffffffff8173c1c1>] ? acpi_processor_init+0x0/0x128
> [    3.711073]  [<ffffffff81245de0>] acpi_bus_register_driver+0x3e/0x40
> [    3.711073]  [<ffffffff8126cd2a>] xen_acpi_processor_init+0x10/0x12
> [    3.711073]  [<ffffffff8173c26f>] acpi_processor_init+0xae/0x128
> [    3.711073]  [<ffffffff81245de0>] ? 
> acpi_bus_register_driver+0x3e/0x40
> [    3.711073]  [<ffffffff8173c14b>] ? acpi_video_init+0x0/0x76
> [    3.711073]  [<ffffffff8100a05f>] do_one_initcall+0x59/0x170
> [    3.711073]  [<ffffffff817176fe>] kernel_init+0x153/0x1a9
> [    3.711073]  [<ffffffff81013caa>] child_rip+0xa/0x20
> [    3.711073]  [<ffffffff81012e61>] ? int_ret_from_sys_call+0x7/0x1b
> [    3.711073]  [<ffffffff8101361d>] ? retint_restore_args+0x5/0x6
> [    3.711073]  [<ffffffff81013ca0>] ? child_rip+0x0/0x20
> [    3.711073] ---[ end trace a7919e7f17c0a725 ]---

  reply	other threads:[~2010-09-10  8:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 12:15 Xen BUG in mm / Xen 4.0.1 with 2.6.32.18/21 pvops Kernel? Carsten Schiers
2010-09-08 12:51 ` Jan Beulich
2010-09-08 20:15   ` AW: " Carsten Schiers
2010-09-09  9:57     ` Jan Beulich
2010-09-09 18:27       ` Carsten Schiers
2010-09-09 18:40         ` Carsten Schiers
2010-09-09 19:04           ` Carsten Schiers
2010-09-10  8:22             ` Jan Beulich [this message]
2010-09-10  8:45           ` Jan Beulich
2010-09-14  9:10             ` Carsten Schiers
2010-09-14  9:33               ` Jan Beulich
2010-09-14 21:19                 ` AW: Re: ACPI problem, was " Carsten Schiers
2010-09-14 22:05                   ` Jeremy Fitzhardinge
2010-09-15  1:20                     ` Yu, Ke
2010-09-15  2:02                       ` Wang, Winston L
2010-09-15  5:37                         ` Jiang, Yunhong
2010-09-15  7:22                           ` AW: " Carsten Schiers
2010-09-15  7:38                             ` Jiang, Yunhong
2010-09-15  8:15                             ` AW: " Jan Beulich
2010-09-15  8:28                               ` Carsten Schiers
2010-09-15  8:36                               ` Jiang, Yunhong
2010-09-15  8:50                               ` Jiang, Yunhong
2010-10-19  9:59                                 ` 2.6.34.7 with SUSE patches: Invalid Kernel Carsten Schiers
2010-10-20 16:54                                   ` Jeremy Fitzhardinge
2010-09-15 17:01                           ` AW: Re: ACPI problem, was Xen BUG in mm / Xen 4.0.1 with 2.6.32.18/21 pvops Kernel? Jeremy Fitzhardinge
2010-09-10  8:48         ` AW: " Jan Beulich
2010-09-08 20:16   ` Carsten Schiers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C8A06ED02000078000155E5@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=carsten@schiers.de \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).