While trying to attach/detach a device using libvirt/kvm, the following messages appeared in the log files:
[ 340.161543] ------------[ cut here ]------------
[ 340.161605] WARNING: at /build/buildd/linux-2.6.32/arch/x86/include/asm/dma-mapping.h:154 ___free_dma_mem_cluster+0x102/0x110 [sym53c8xx]()
[ 340.161619] Hardware name:
[ 340.161627] Modules linked in: serio_raw psmouse virtio_balloon acpiphp fbcon tileblit font bitblit softcursor floppy vga16fb vgastate virtio_pci e1000 virtio_ring sym53c8xx virtio scsi_transport_spi
[ 340.161663] Pid: 24, comm: kacpi_notify Not tainted 2.6.32-10-server #14-Ubuntu
[ 340.161672] Call Trace:
[ 340.161719] [<ffffffff8106510b>] warn_slowpath_common+0x7b/0xc0
[ 340.161727] [<ffffffff81065164>] warn_slowpath_null+0x14/0x20
[ 340.161732] [<ffffffffa0020142>] ___free_dma_mem_cluster+0x102/0x110 [sym53c8xx]
[ 340.161737] [<ffffffffa001ff12>] __sym_mfree+0xd2/0x100 [sym53c8xx]
[ 340.161742] [<ffffffffa001ffa9>] __sym_mfree_dma+0x69/0x100 [sym53c8xx]
[ 340.161747] [<ffffffffa001832f>] sym_hcb_free+0x8f/0x1f0 [sym53c8xx]
[ 340.161751] [<ffffffffa0015736>] sym_free_resources+0x46/0x90 [sym53c8xx]
[ 340.161755] [<ffffffffa0015833>] sym_detach+0xb3/0xe0 [sym53c8xx]
[ 340.161759] [<ffffffffa00177fb>] sym2_remove+0x3b/0x60 [sym53c8xx]
[ 340.161782] [<ffffffff812c9e84>] pci_device_remove+0x34/0x60
[ 340.161798] [<ffffffff81363a8f>] __device_release_driver+0x6f/0xe0
[ 340.161802] [<ffffffff81363bfd>] device_release_driver+0x2d/0x40
[ 340.161805] [<ffffffff81362c1a>] bus_remove_device+0x9a/0xc0
[ 340.161819] [<ffffffff81360e67>] device_del+0x127/0x1b0
[ 340.161822] [<ffffffff81360f06>] device_unregister+0x16/0x30
[ 340.161830] [<ffffffff812c40e9>] pci_stop_bus_device+0x69/0x80
[ 340.161839] [<ffffffffa00ba4fa>] disable_device+0x8a/0x1a0 [acpiphp]
[ 340.161853] [<ffffffff812f8c90>] ? acpi_ns_handle_to_pathname+0x50/0x5f
[ 340.161858] [<ffffffffa00ba640>] acpiphp_disable_slot+0x30/0x60 [acpiphp]
[ 340.161862] [<ffffffffa00bb133>] handle_hotplug_event_func+0xe3/0x1c0 [acpiphp]
[ 340.161870] [<ffffffff812de401>] ? acpi_os_execute_deferred+0x0/0x36
[ 340.161874] [<ffffffff812e0175>] ? acpi_bus_get_device+0x2a/0x3d
[ 340.161877] [<ffffffff812de401>] ? acpi_os_execute_deferred+0x0/0x36
[ 340.161881] [<ffffffff812ee30a>] acpi_ev_notify_dispatch+0x64/0x72
[ 340.161884] [<ffffffff812de42a>] acpi_os_execute_deferred+0x29/0x36
[ 340.161895] [<ffffffff8107e767>] run_workqueue+0xc7/0x1a0
[ 340.161899] [<ffffffff8107e8e3>] worker_thread+0xa3/0x110
[ 340.161902] [<ffffffff81083300>] ? autoremove_wake_function+0x0/0x40
[ 340.161906] [<ffffffff8107e840>] ? worker_thread+0x0/0x110
[ 340.161912] [<ffffffff81082f86>] kthread+0x96/0xa0
[ 340.161927] [<ffffffff810141ea>] child_rip+0xa/0x20
[ 340.161930] [<ffffffff81082ef0>] ? kthread+0x0/0xa0
[ 340.161933] [<ffffffff810141e0>] ? child_rip+0x0/0x20
[ 340.161939] ---[ end trace e6ec80df0c4cbc75 ]---
I've attached the complete apport crash report.
Hi Mathias,
This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://
If it remains an issue, could you run the following command from a Terminal (Applications-
apport-collect -p linux 506698
Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/
Thanks in advance.
[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]