[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Re: "ACPI: Unable to start the ACPI Interpreter"
Just a follow up. I found out that the boot failure's due to a unsupported (faulty?) PATA controller. Removed it and the system actually boots. The SCI allocation failure still occurs though. Apparently this also occurs with the Debian experimental 3.0 kernel too. Here's the full backtrace from dmesg: [ 3.934034] bio: create slab <bio-0> at 0 [ 3.936216] ACPI: SCI (IRQ9) allocation failed [ 3.936259] ACPI Exception: AE_NOT_ACQUIRED, Unable to install System Control Interrupt handler (20110413/evevent-119) [ 3.936264] ACPI: Unable to start the ACPI Interpreter [ 3.974522] ============================================================================= [ 3.974570] BUG Acpi-ParseExt: Objects remaining on kmem_cache_close() [ 3.974613] ----------------------------------------------------------------------------- [ 3.974614] [ 3.974694] INFO: Slab 0xffffea0000a57308 objects=56 used=1 fp=0xffff88002f4577e0 flags=0x100000000000080 [ 3.974743] Pid: 1, comm: swapper Not tainted 3.0.0-rc4-amd64+ #1 [ 3.974745] Call Trace: [ 3.974753] [<ffffffff810e5f13>] ? slab_err+0x93/0xb5 [ 3.974758] [<ffffffff81006b4d>] ? xen_force_evtchn_callback+0x9/0xa [ 3.974762] [<ffffffff810071b2>] ? check_events+0x12/0x20 [ 3.974766] [<ffffffff810e8ff9>] ? kmem_cache_destroy+0x170/0x2dc [ 3.974770] [<ffffffff816c1db2>] ? acpi_sleep_proc_init+0x27/0x27 [ 3.974774] [<ffffffff811cf965>] ? acpi_os_delete_cache+0x6/0xa [ 3.974779] [<ffffffff811eedee>] ? acpi_ut_delete_caches+0x6a/0x7a [ 3.974783] [<ffffffff811efd3f>] ? acpi_terminate+0x3e/0x49 [ 3.974786] [<ffffffff816c2000>] ? acpi_init+0x24e/0x297 [ 3.974791] [<ffffffff8122f708>] ? __class_create+0x3d/0x61 [ 3.974795] [<ffffffff810f0c30>] ? mount_fs+0x144/0x144 [ 3.974799] [<ffffffff816bf936>] ? video_setup+0x75/0x75 [ 3.974803] [<ffffffff816bf99c>] ? fbmem_init+0x66/0x95 [ 3.974806] [<ffffffff81002086>] ? do_one_initcall+0x76/0x12c [ 3.974810] [<ffffffff81696bf4>] ? kernel_init+0xbd/0x137 [ 3.974815] [<ffffffff813278a4>] ? kernel_thread_helper+0x4/0x10 [ 3.974819] [<ffffffff813269b3>] ? int_ret_from_sys_call+0x7/0x1b [ 3.974823] [<ffffffff813216e5>] ? retint_restore_args+0x5/0x6 [ 3.974826] [<ffffffff813278a0>] ? gs_change+0x13/0x13 [ 3.974830] INFO: Object 0xffff88002f457900 @offset=2304 [ 3.974873] SLUB Acpi-ParseExt: kmem_cache_destroy called for cache that still has objects. [ 3.974920] Pid: 1, comm: swapper Not tainted 3.0.0-rc4-amd64+ #1 [ 3.974922] Call Trace: [ 3.974925] [<ffffffff810e9116>] ? kmem_cache_destroy+0x28d/0x2dc [ 3.974928] [<ffffffff816c1db2>] ? acpi_sleep_proc_init+0x27/0x27 [ 3.974931] [<ffffffff811cf965>] ? acpi_os_delete_cache+0x6/0xa [ 3.974934] [<ffffffff811eedee>] ? acpi_ut_delete_caches+0x6a/0x7a [ 3.974938] [<ffffffff811efd3f>] ? acpi_terminate+0x3e/0x49 [ 3.974941] [<ffffffff816c2000>] ? acpi_init+0x24e/0x297 [ 3.974944] [<ffffffff8122f708>] ? __class_create+0x3d/0x61 [ 3.974947] [<ffffffff810f0c30>] ? mount_fs+0x144/0x144 [ 3.974950] [<ffffffff816bf936>] ? video_setup+0x75/0x75 [ 3.974953] [<ffffffff816bf99c>] ? fbmem_init+0x66/0x95 [ 3.974956] [<ffffffff81002086>] ? do_one_initcall+0x76/0x12c [ 3.974960] [<ffffffff81696bf4>] ? kernel_init+0xbd/0x137 [ 3.974963] [<ffffffff813278a4>] ? kernel_thread_helper+0x4/0x10 [ 3.974966] [<ffffffff813269b3>] ? int_ret_from_sys_call+0x7/0x1b [ 3.974970] [<ffffffff813216e5>] ? retint_restore_args+0x5/0x6 [ 3.974973] [<ffffffff813278a0>] ? gs_change+0x13/0x13 On 25 June 2011 02:55, Liwei <xieliwei@xxxxxxxxx> wrote: > Hello list, > Just for fun, I tried compiling the 3.0-rc4 kernel from Jeremy's > git repo. Compilation and installation were successful, so does > booting into the kernel without xen. > With xen however, I get the following: > > ACPI: SCI (IRQ9) allocation failed > ACPI: Unable to start the ACPI Interpreter > ============================================================================= > BUG Acpi-ParseExt: Objects remaining on kmem_cache_close() > ----------------------------------------------------------------------------- > > INFO: Slab 0xffffea0000a57308 objects=56 used=1 fp=0xffff88002f4577e0 > flags=0x1000000000000080 > INFO: Object 0xffff88002f457900 @offset=2304 > SLUB Acpi-ParseExt: kmem_cache_destroy called for cache that still has > objects. > SLUB: Unable to add boot slab alias [some weird characters] to sysfs > Loading, please wait... > > There could be some mix ups between "0" and "8" in the hex values > as the above were transcribed from a cameraphone photo. The system > continues to boot, but fails badly trying to start udev, stuck with > the following (with varying device IDs): > > ... > udevd[80]: timeout: killing '/sbin/modprobe -b > pci:v000011ABd00006440sv0000d00006440bc01sc00i00' [92] > ... > > Not looking for a solution here, just reporting this to the devs. > Attached is the kernel .config file. Running on xen-unstable compiled > today. > > Liwei > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |