From mboxrd@z Thu Jan 1 00:00:00 1970 From: Li Zefan Subject: Re: [-mm] sysfs: duplicate filename 'acpi' can not be created Date: Wed, 20 Aug 2008 13:48:53 +0800 Message-ID: <48ABB045.3040800@cn.fujitsu.com> References: <48ABACF2.4060503@cn.fujitsu.com> <20080819224732.5b1393c1.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from cn.fujitsu.com ([222.73.24.84]:58717 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1751364AbYHTFuZ (ORCPT ); Wed, 20 Aug 2008 01:50:25 -0400 In-Reply-To: <20080819224732.5b1393c1.akpm@linux-foundation.org> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Andrew Morton Cc: LKML , linux-acpi@vger.kernel.org Andrew Morton wrote: > On Wed, 20 Aug 2008 13:34:42 +0800 Li Zefan wrote: > >> When I compiled latest -mm and booted up: >> >> ------------[ cut here ]------------ >> WARNING: at fs/sysfs/dir.c:463 sysfs_add_one+0x27/0x2f() >> sysfs: duplicate filename 'acpi' can not be created >> Modules linked in: >> Pid: 1, comm: swapper Not tainted 2.6.27-rc3-mm1 #2 >> [] warn_slowpath+0x61/0x83 >> [] __lock_acquire+0x601/0x658 >> [] ifind+0x13/0x79 >> [] _spin_unlock+0x14/0x1c >> [] ifind+0x73/0x79 >> [] sysfs_find_dirent+0x13/0x23 >> [] sysfs_add_one+0x27/0x2f >> [] create_dir+0x3c/0x81 >> [] sysfs_create_dir+0x29/0x3b >> [] _spin_unlock+0x14/0x1c >> [] kobject_add_internal+0xb1/0x14a >> [] kobject_init_and_add+0x29/0x2c >> [] kernel_param_sysfs_setup+0x4f/0x9f >> [] param_sysfs_init+0xf0/0x147 >> [] _stext+0x3a/0x12f >> [] param_sysfs_init+0x0/0x147 >> [] try_to_wake_up+0x146/0x14f >> [] __create_workqueue_key+0xa0/0x13c >> [] kernel_init+0x18d/0x1f1 >> [] kernel_init+0x0/0x1f1 >> [] kernel_thread_helper+0x7/0x10 >> ======================= >> ---[ end trace 4eaa2a86a8e2da22 ]--- >> kobject_add_internal failed for acpi with -EEXIST, don't try to register things with the same name in the same directory. >> Pid: 1, comm: swapper Tainted: G W 2.6.27-rc3-mm1 #2 >> [] kobject_add_internal+0x114/0x14a >> [] kobject_init_and_add+0x29/0x2c >> [] kernel_param_sysfs_setup+0x4f/0x9f >> [] param_sysfs_init+0xf0/0x147 >> [] _stext+0x3a/0x12f >> [] param_sysfs_init+0x0/0x147 >> [] try_to_wake_up+0x146/0x14f >> [] __create_workqueue_key+0xa0/0x13c >> [] kernel_init+0x18d/0x1f1 >> [] kernel_init+0x0/0x1f1 >> [] kernel_thread_helper+0x7/0x10 >> ======================= >> Module 'acpi' failed to be added to sysfs, error number -17 >> The system will be unstable now. > > The only acpi-specific patches in mm(otm) are > > acpi-add-checking-for-null-early-param.patch > acpi-avoid-dropping-rapid-hotkey-events-or-other-gpes-on-asus-eeepc.patch > mm-only-enforce-acpi-resource-conflict-checks.patch > > so I'd say you've hit a linux-next regression there. > > Random-possible-feel-it-in-my-water-guess: do you have CONFIG_FASTBOOT > set and if so, does unsetting it fix things? > I've just looked into my config file: # CONFIG_FASTBOOT is not set