From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alexander Beregalov" Subject: next-20081121:WARNING: at drivers/dma/dmaengine.c:665 dma_async_device_unregister() Date: Fri, 21 Nov 2008 13:40:39 +0300 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from yx-out-2324.google.com ([74.125.44.30]:38007 "EHLO yx-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755285AbYKUKkk (ORCPT ); Fri, 21 Nov 2008 05:40:40 -0500 Received: by yx-out-2324.google.com with SMTP id 8so388042yxm.1 for ; Fri, 21 Nov 2008 02:40:39 -0800 (PST) Content-Disposition: inline Sender: linux-next-owner@vger.kernel.org List-ID: To: linux-next@vger.kernel.org, LKML , maciej.sosnowski@intel.com, dan.j.williams@intel.com Hi It occured during shutdown process: sd 0:2:0:0: [sda] Synchronizing SCSI cache ioatdma 0000:00:08.0: Removing dma and dca services ------------[ cut here ]------------ WARNING: at drivers/dma/dmaengine.c:665 dma_async_device_unregister+0x90/0xd0() dma_async_device_unregister called while 1 clients hold a reference Modules linked in: Pid: 12246, comm: reboot Tainted: G W 2.6.28-rc5-next-20081121 #8 Call Trace: [] warn_slowpath+0xae/0xd5 [] ? add_partial+0x1a/0x50 [] ? dma_async_device_unregister+0x22/0xd0 [] ? trace_hardirqs_on_caller+0x1f/0x153 [] ? __mutex_lock_common+0x371/0x3be [] ? dma_async_device_unregister+0x22/0xd0 [] ? trace_hardirqs_on_caller+0x1f/0x153 [] ? trace_hardirqs_on+0xd/0xf [] ? __mutex_unlock_slowpath+0x13c/0x145 [] dma_async_device_unregister+0x90/0xd0 [] ioat_dma_remove+0x1c/0xd0 [] ioat_shutdown_functionality+0x66/0x74 [] pci_device_shutdown+0x24/0x38 [] device_shutdown+0x50/0x99 [] kernel_restart_prepare+0x27/0x2e [] kernel_restart+0x11/0x44 [] sys_reboot+0x11d/0x149 [] ? hrtimer_nanosleep+0x104/0x119 [] ? hrtimer_wakeup+0x0/0x21 [] ? do_nanosleep+0x50/0xb6 [] ? trace_hardirqs_on_caller+0x1f/0x153 [] ? trace_hardirqs_on_thunk+0x3a/0x3f [] system_call_fastpath+0x16/0x1b ---[ end trace 4eaa2a86a8e2da22 ]--- ------------[ cut here ]------------ WARNING: at drivers/base/core.c:122 device_release+0x66/0x68() Device 'dma0chan0' does not have a release() function, it is broken and must be fixed. Modules linked in: Pid: 12246, comm: reboot Tainted: G W 2.6.28-rc5-next-20081121 #8 Call Trace: [] warn_slowpath+0xae/0xd5 [] ? release_sysfs_dirent+0x7d/0x9d [] ? __sysfs_put+0x18/0x1a [] ? sysfs_addrm_finish+0x233/0x27b [] ? ifind+0x2c/0x84 [] ? trace_hardirqs_on+0xd/0xf [] ? mutex_trylock+0x146/0x15a [] ? sysfs_addrm_start+0x78/0xa5 [] ? sysfs_addrm_start+0x78/0xa5 [] ? kobj_kset_leave+0x1e/0x57 [] device_release+0x66/0x68 [] kobject_release+0x52/0x68 [] ? kobject_release+0x0/0x68 [] kref_put+0x43/0x4f [] kobject_put+0x47/0x4b [] put_device+0x15/0x17 [] device_unregister+0x19/0x1e [] dma_async_device_unregister+0xa4/0xd0 [] ioat_dma_remove+0x1c/0xd0 [] ioat_shutdown_functionality+0x66/0x74 [] pci_device_shutdown+0x24/0x38 [] device_shutdown+0x50/0x99 [] kernel_restart_prepare+0x27/0x2e [] kernel_restart+0x11/0x44 [] sys_reboot+0x11d/0x149 [] ? hrtimer_nanosleep+0x104/0x119 [] ? hrtimer_wakeup+0x0/0x21 [] ? do_nanosleep+0x50/0xb6 [] ? trace_hardirqs_on_caller+0x1f/0x153 [] ? trace_hardirqs_on_thunk+0x3a/0x3f [] system_call_fastpath+0x16/0x1b ---[ end trace 4eaa2a86a8e2da22 ]--- ------------[ cut here ]------------ WARNING: at drivers/base/core.c:122 device_release+0x66/0x68() Device 'dma0chan1' does not have a release() function, it is broken and must be fixed. Modules linked in: Pid: 12246, comm: reboot Tainted: G W 2.6.28-rc5-next-20081121 #8 I guess it was tainted by previous warning on hpet: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0 hpet0: 3 comparators, 64-bit 14.318180 MHz counter ODEBUG: object is on stack, but not annotated ------------[ cut here ]------------ WARNING: at lib/debugobjects.c:251 __debug_object_init+0x2bf/0x36d() Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.28-rc5-next-20081121 #8 Call Trace: