From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751691AbXC3OUh (ORCPT ); Fri, 30 Mar 2007 10:20:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751710AbXC3OUh (ORCPT ); Fri, 30 Mar 2007 10:20:37 -0400 Received: from ns1.suse.de ([195.135.220.2]:50331 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751674AbXC3OUg (ORCPT ); Fri, 30 Mar 2007 10:20:36 -0400 Date: Fri, 30 Mar 2007 07:18:56 -0700 From: Greg KH To: Ingo Molnar Cc: Adrian Bunk , Linus Torvalds , Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: [bug] fixed_init(): BUG: at drivers/base/core.c:120 device_release(), was: "2.6.21-rc5: known regressions" Message-ID: <20070330141856.GB10387@suse.de> References: <20070327015929.GY16477@stusta.de> <20070330120416.GA19373@elte.hu> <20070330120657.GA21271@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070330120657.GA21271@elte.hu> User-Agent: Mutt/1.5.14 (2007-02-12) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 30, 2007 at 02:06:57PM +0200, Ingo Molnar wrote: > > there's a new type of message in allyesconfig-bzImage bootup test: > > Calling initcall 0xc1b6d692: fixed_init+0x0/0x33() > Fixed PHY: Registered new driver > Device 'fixed@100:1' does not have a release() function, it is broken and must be fixed. > BUG: at drivers/base/core.c:120 device_release() > [] show_trace_log_lvl+0x19/0x2e > [] show_trace+0x12/0x14 > [] dump_stack+0x14/0x16 > [] device_release+0x7c/0x7e > [] kobject_cleanup+0x44/0x5e > [] kobject_release+0xb/0xd > [] kref_put+0x63/0x71 > [] kobject_put+0x14/0x16 > [] put_device+0x11/0x13 > [] device_unregister+0x12/0x15 > [] fixed_mdio_register_device+0x210/0x23b > [] fixed_init+0x1e/0x33 > [] init+0x15d/0x2bd > [] kernel_thread_helper+0x7/0x10 > ======================= > Device 'fixed@10:1' does not have a release() function, it is broken and must be fixed. > BUG: at drivers/base/core.c:120 device_release() > [] show_trace_log_lvl+0x19/0x2e > [] show_trace+0x12/0x14 > [] dump_stack+0x14/0x16 > [] device_release+0x7c/0x7e > [] kobject_cleanup+0x44/0x5e > [] kobject_release+0xb/0xd > [] kref_put+0x63/0x71 > [] kobject_put+0x14/0x16 > [] put_device+0x11/0x13 > [] device_unregister+0x12/0x15 > [] fixed_mdio_register_device+0x210/0x23b > [] fixed_init+0x2f/0x33 > [] init+0x15d/0x2bd > [] kernel_thread_helper+0x7/0x10 That means that whatever driver has fixed_mdio_register_device() in it is broken and needs to be fixed. It is independant from your previous question about unregistering the device from within module_init(). thanks, greg k-h