login
Header Space

 
 

Re: e1000e oops, sysfs related?

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Kok, Auke <auke-jan.h.kok@...>
Cc: maximilian attems <max@...>, <netdev@...>, <linux-kernel@...>, Greg KH <gregkh@...>
Date: Friday, October 5, 2007 - 5:21 pm

"Kok, Auke" <auke-jan.h.kok@intel.com> writes:



To reach this path you need to run the equivalent of:
ip link set eth0 name eth1

I have seen this a bit and my memory is that the error is generally
harmless.  It is trying to create a symlink with the same name as the
directory or something like that.  Which makes with one setting of
CONFIG_SYSFS_DEPRECATED but not the other.

So I don't believe this is a driver bug, and I suspect the renames
come from using something like /etc/mactab which forces ethernet
devices with specific mac addresses to specific ethernet device
names.

With whatever is sitting in my development tree I'm pretty certain
this error isn't present.  I don't recall if I did anything specific
to fix this though.  In particular I don't recall if this still
happens with gregkh's queued sysfs patches applied.

Eric
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
e1000e oops, maximilian attems, (Fri Oct 5, 9:11 am)
Re: e1000e oops, David Miller, (Fri Oct 5, 4:53 pm)
Re: e1000e oops, sysfs related?, Kok, Auke, (Fri Oct 5, 12:37 pm)
Re: e1000e oops, sysfs related?, Eric W. Biederman, (Fri Oct 5, 5:21 pm)
speck-geostationary