All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: maximilian attems <max@stro.at>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Greg KH <gregkh@suse.de>
Subject: Re: e1000e oops, sysfs related?
Date: Fri, 05 Oct 2007 09:37:12 -0700	[thread overview]
Message-ID: <47066838.7030209@intel.com> (raw)
In-Reply-To: <20071005131115.GA31453@stro.at>

maximilian attems wrote:
> Linux tau 2.6.23-rc8-mm2-686 #1 SMP Wed Oct 3 23:56:32 CEST 2007 i686
> GNU/Linux
> 
> eth0 renamed to eth1
> sysfs: duplicate filename 'eth1' can not be created
> WARNING: at fs/sysfs/dir.c:433 sysfs_add_one()
>  [<c0104f9c>] dump_trace+0x68/0x1d5
>  [<c0105121>] show_trace_log_lvl+0x18/0x2c
>  [<c0105b9b>] show_trace+0xf/0x11
>  [<c0105c81>] dump_stack+0x12/0x14
>  [<c01ac02e>] sysfs_add_one+0x54/0xb8
>  [<c01acc2a>] sysfs_create_link+0xb3/0x125
>  [<c023c05f>] device_rename+0x13d/0x196
>  [<c025a970>] dev_change_name+0x137/0x205
>  [<c025b12c>] dev_ioctl+0x357/0x44f
>  [<c017b05f>] do_ioctl+0x1f/0x62
>  [<c017b2d9>] vfs_ioctl+0x237/0x249
>  [<c017b330>] sys_ioctl+0x45/0x5d
>  [<c0103eda>] syscall_call+0x7/0xb
>  [<b7edbde4>] 0xb7edbde4
>  =======================
> net eth1: device_rename: sysfs_create_symlink failed (-17)
> 
> 00:19.0 Ethernet controller [0200]: Intel Corporation 82801I (ICH9 Family) Gigabit Ethernet Controller [8086:294c] (rev 02)
>         Subsystem: Intel Corporation Unknown device [8086:0001]
>         Flags: bus master, fast devsel, latency 0, IRQ 218
>         Memory at 50380000 (32-bit, non-prefetchable) [size=128K]
>         Memory at 503a4000 (32-bit, non-prefetchable) [size=4K]
>         I/O ports at 20e0 [size=32]
>         Capabilities: [c8] Power Management version 2
>         Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
>         Capabilities: [e0] Vendor Specific Information
> 
> 
> no idea if aboves belongs to netdev or sysfs dep.

I'm seeing the same when removing/inserting network drivers frequently, ixgbe does
the same thing: (git://davem/net-2.6.24)

ixgbe 0000:01:00.0: (PCI Express:2.5Gb/s:Width x8) 00:1a:64:3b:81:c3
ixgbe 0000:01:00.0: MAC: 0, PHY: 0, PBA No: d95854-003
ixgbe 0000:01:00.0: Intel(R) 10 Gigabit Network Connection
net eth2: device_rename: sysfs_create_symlink failed (-17)

but I can't make it throw a stack trace.

perhaps one of the sysfs knowledgeable people can take a look at this. We might be
doing something wrong in e1000e / ixgbe at setup time, but I have no idea what.

Auke

> 

  reply	other threads:[~2007-10-05 16:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 13:11 e1000e oops maximilian attems
2007-10-05 16:37 ` Kok, Auke [this message]
2007-10-05 21:21   ` e1000e oops, sysfs related? Eric W. Biederman
2007-10-05 20:53 ` e1000e oops David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47066838.7030209@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@stro.at \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.