Michel Briand
2010-Oct-30 12:21 UTC
[Pkg-xen-devel] Bug#601869: xen-hypervisor-4.0-amd64: xen boot reports a kernel trace : memory problem
Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: normal Hello, I've this message in dmesg that I can't understand: [ 4.032472] ------------[ cut here ]------------ [ 4.032521] WARNING: at /build/buildd-linux-2.6_2.6.32-26-amd64-KkHF2p/linux-2.6-2.6.32/debian/build/source_amd64_xen/mm/page_alloc.c:1833 __alloc_pages_nodemask+0x177/0x5f5() [ 4.032590] Hardware name: MS-7311 [ 4.032630] Modules linked in: processor(+) button soundcore snd_page_alloc i2c_core acpi_processor usbhid hid xfs exportfs dm_mod usb_storage sd_mod crc_t10dif uhci_hcd fan ahci firewire_ohci ehci_hcd r8169 mii firewire_core crc_itu_t libata thermal floppy thermal_sys e1000e scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan] [ 4.033512] Pid: 431, comm: modprobe Not tainted 2.6.32-5-xen-amd64 #1 [ 4.033512] Call Trace: [ 4.033512] [<ffffffff810bad5a>] ? __alloc_pages_nodemask+0x177/0x5f5 [ 4.033512] [<ffffffff810bad5a>] ? __alloc_pages_nodemask+0x177/0x5f5 [ 4.033512] [<ffffffff8104ec7c>] ? warn_slowpath_common+0x77/0xa3 [ 4.033512] [<ffffffff810bad5a>] ? __alloc_pages_nodemask+0x177/0x5f5 [ 4.033512] [<ffffffff810ba13b>] ? __get_free_pages+0x9/0x46 [ 4.033512] [<ffffffff810e89c9>] ? __kmalloc+0x3f/0x141 [ 4.033512] [<ffffffff811d9594>] ? acpi_ex_load_op+0xbc/0x269 [ 4.033512] [<ffffffff811d95ae>] ? acpi_ex_load_op+0xd6/0x269 [ 4.033512] [<ffffffff811da637>] ? acpi_ex_resolve_to_value+0x1fb/0x20c [ 4.033512] [<ffffffff811d3b1b>] ? acpi_ds_exec_end_op+0xe7/0x3b8 [ 4.033512] [<ffffffff811e4f92>] ? acpi_ps_parse_loop+0x7c0/0x946 [ 4.033512] [<ffffffff811e40d8>] ? acpi_ps_parse_aml+0x8f/0x2ca [ 4.033512] [<ffffffff811e5762>] ? acpi_ps_execute_method+0x1e7/0x2b1 [ 4.033512] [<ffffffff811e1219>] ? acpi_ns_evaluate+0xe1/0x19e [ 4.033512] [<ffffffff811e0cb6>] ? acpi_evaluate_object+0xf7/0x1ec [ 4.033512] [<ffffffff810244e7>] ? init_intel_pdc+0x101/0x20c [ 4.033512] [<ffffffffa01b3bd1>] ? xen_acpi_processor_add+0x2c2/0x405 [processor] [ 4.033512] [<ffffffff811cb363>] ? acpi_device_probe+0x4a/0x10e [ 4.033512] [<ffffffff8122fc3c>] ? driver_probe_device+0xa3/0x14b [ 4.033512] [<ffffffff8122fd33>] ? __driver_attach+0x4f/0x6f [ 4.033512] [<ffffffff8122fce4>] ? __driver_attach+0x0/0x6f [ 4.033512] [<ffffffff8122f50b>] ? bus_for_each_dev+0x43/0x74 [ 4.033512] [<ffffffff8122eecb>] ? bus_add_driver+0xaf/0x1f8 [ 4.033512] [<ffffffff8122ffeb>] ? driver_register+0xa7/0x111 [ 4.033512] [<ffffffffa01ba000>] ? acpi_processor_init+0x0/0x12f [processor] [ 4.033512] [<ffffffffa01ba0ad>] ? acpi_processor_init+0xad/0x12f [processor] [ 4.033512] [<ffffffff81069581>] ? __blocking_notifier_call_chain+0x51/0x5f [ 4.033512] [<ffffffff8100a065>] ? do_one_initcall+0x64/0x174 [ 4.033512] [<ffffffff8107b4f8>] ? sys_init_module+0xc5/0x21a [ 4.033512] [<ffffffff81011b42>] ? system_call_fastpath+0x16/0x1b [ 4.033512] ---[ end trace 5ffea4bc40debc2d ]--- Best regards, Michel -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR at euro, LC_CTYPE=fr_FR at euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash xen-hypervisor-4.0-amd64 depends on no packages. Versions of packages xen-hypervisor-4.0-amd64 recommends: ii xen-utils-4.0 4.0.1-1 XEN administrative tools Versions of packages xen-hypervisor-4.0-amd64 suggests: ii xen-docs-4.0 4.0.1-1 Documentation for Xen -- no debconf information
Debian Bug Tracking System
2012-Jul-10 00:45 UTC
[Pkg-xen-devel] Bug#601869: marked as done (xen-hypervisor-4.0-amd64: xen boot reports a kernel trace : memory problem)
Your message dated Mon, 09 Jul 2012 18:42:49 -0600 with message-id <1341880969.8586.22.camel at hastur.hellion.org.uk> and subject line Sorry, but binary only nvidia driver is not supportable under Xen. has caused the Debian Bug report #601869, regarding xen-hypervisor-4.0-amd64: xen boot reports a kernel trace : memory problem to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 601869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601869 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Michel Briand <michelbriand at free.fr> Subject: xen-hypervisor-4.0-amd64: xen boot reports a kernel trace : memory problem Date: Sat, 30 Oct 2010 14:21:35 +0200 Size: 5368 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120710/80dfece7/attachment.mht> -------------- next part -------------- An embedded message was scrubbed... From: Ian Campbell <ijc at hellion.org.uk> Subject: Sorry, but binary only nvidia driver is not supportable under Xen. Date: Mon, 09 Jul 2012 18:42:49 -0600 Size: 2427 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120710/80dfece7/attachment-0001.mht>
Possibly Parallel Threads
- Bug#601869: nvidia-glx: problem confirmed in with latest xen hypervisor
- Bug#601869: Sorry, but binary only nvidia driver is not supportable under Xen.
- Bug#508429: BUG: unable to handle kernel paging request
- Possible locking problem in DLM code
- WG: Dom0 kernel crashes when dom0_mem= is used!