From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755756AbXJ2Vff (ORCPT ); Mon, 29 Oct 2007 17:35:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753270AbXJ2VfQ (ORCPT ); Mon, 29 Oct 2007 17:35:16 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:58337 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755127AbXJ2VfO (ORCPT ); Mon, 29 Oct 2007 17:35:14 -0400 Message-ID: <4726520F.1020605@garzik.org> Date: Mon, 29 Oct 2007 17:35:11 -0400 From: Jeff Garzik User-Agent: Thunderbird 2.0.0.5 (X11/20070727) MIME-Version: 1.0 To: Ingo Molnar CC: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, "David S. Miller" Subject: Re: [bug, 2.6.24-rc1] sysfs: duplicate filename 'eth0' can not be created References: <20071029211746.GA19876@elte.hu> In-Reply-To: <20071029211746.GA19876@elte.hu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) X-Spam-Report: SpamAssassin version 3.1.9 on srv5.dvmed.net summary: Content analysis details: (-4.4 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Ingo Molnar wrote: > hm, this seems to have popped up in the last few days, never had it > before: > > sysfs: duplicate filename 'eth0' can not be created > WARNING: at fs/sysfs/dir.c:424 sysfs_add_one() > > Call Trace: > [] sysfs_add_one+0x54/0xbd > [] sysfs_create_link+0xc6/0x11d > [] device_rename+0x175/0x1d6 > [] dev_change_name+0x118/0x211 > [] dev_ioctl+0x4fa/0x5f8 > [] netlink_insert+0x13c/0x14b > [] do_page_fault+0x3eb/0x73f > [] sock_ioctl+0x1f2/0x200 > [] do_ioctl+0x21/0x6b > [] vfs_ioctl+0x243/0x25c > [] sys_ioctl+0x51/0x71 > [] system_call+0x7e/0x83 > > net eth0: device_rename: sysfs_create_symlink failed (-17) > > 32-bit bzImage kernel - config attached. (The 64-bit kernel even lost > connectivity due to this and ifcfg-eth0 got renamed to ifcfg-eth0.bak by > kudzu.) > > detected order of the interfaces is: > > forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x5043 @1 > eth1: RealTek RTL8139 at 0xffffc200001f2000 > > and that's the ordering in /etc/sysconfig/network-scripts as well. Does your setup do anything like try to rename the interfaces? I cannot think of anything that changed recently in this area in net, off the top of my head. Jeff