public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Miles Lane <miles.lane@gmail.com>, Andrew Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Nonfunctional ethernet (was Re: 2.6.21-rc7-mm1 + sysfs-oops-workaround.patch -- INFO: possible recursive locking detected)
Date: Thu, 26 Apr 2007 07:45:02 +0800	[thread overview]
Message-ID: <1177544702.4668.9.camel@daplas> (raw)
In-Reply-To: <1177512528.4856.15.camel@daplas>

On Wed, 2007-04-25 at 22:48 +0800, Antonino A. Daplas wrote:
> On Wed, 2007-04-25 at 14:18 +0900, Tejun Heo wrote:
> > Miles Lane wrote:

> eth0 renamed to eth54
> BUG: atomic counter underflow at:
>  [<c0104378>] show_trace_log_lvl+0x1a/0x30
>  [<c0104ec9>] show_trace+0x12/0x14
>  [<c0104f22>] dump_stack+0x16/0x18
>  [<c01bd575>] _atomic_dec_and_lock+0x29/0x4c
>  [<c0174388>] dput+0x34/0x103
>  [<c019d181>] sysfs_drop_dentry+0x141/0x149
>  [<c019d212>] sysfs_hash_and_remove+0x89/0x10e
>  [<c019f1fc>] sysfs_remove_link+0xe/0x10
>  [<c0221839>] device_rename+0x110/0x181
>  [<c025420a>] dev_change_name+0x11e/0x1ca
>  [<c02545e6>] dev_ifsioc+0x330/0x3d7
>  [<c0254d25>] dev_ioctl+0x350/0x46e
>  [<c0249792>] sock_ioctl+0x1be/0x1ca
>  [<c016f3c0>] do_ioctl+0x1c/0x53
>  [<c016f5e3>] vfs_ioctl+0x1ec/0x203
>  [<c016f643>] sys_ioctl+0x49/0x62
>  [<c0103cde>] sysenter_past_esp+0x5f/0x99
>  =======================

The above tracing was caused by CONFIG_SYSFS_DEPRECATED=y and by setting
this to n, the tracing disappeared..  Still, all my network cards are
non-functional.  Entries in /sys/class/net are bogus:

/ # cd /sys/class/net/
/sys/class/net # ls
eth1  eth44  eth54  lo

/sys/class/net # cd eth1
-bash: cd: eth1: No such file or directory

/sys/class/net # ls -l eth1
lrwxrwxrwx 1 root root 0 Apr 26 07:15 eth1 ->
../../devices/pci0000:00/0000:00:12.0/net/eth0

/sys/class/net # cd ../../devices/pci0000\:00/0000\:00\:12.0/net/eth0
-bash: cd: ../../devices/pci0000:00/0000:00:12.0/net/eth0: No such file
or directory

Do you know of any patches I need to revert/apply?  Anyway, I have to
boot back to this kernel and find out more what's going on.

Tony



  reply	other threads:[~2007-04-25 23:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25  5:15 2.6.21-rc7-mm1 + sysfs-oops-workaround.patch -- INFO: possible recursive locking detected Miles Lane
2007-04-25  5:18 ` Tejun Heo
2007-04-25 14:48   ` Antonino A. Daplas
2007-04-25 23:45     ` Antonino A. Daplas [this message]
2007-04-26  1:02       ` Nonfunctional ethernet (was Re: 2.6.21-rc7-mm1 + sysfs-oops-workaround.patch -- INFO: possible recursive locking detected) Antonino A. Daplas
2007-04-26  1:13         ` Andrew Morton
2007-04-26  2:26           ` Tejun Heo
2007-04-26  2:53             ` Andrew Morton
2007-04-26 14:50   ` [PATCH] sysfs: use different lockdep subclass for s_active deactivation Tejun Heo
2007-04-26 15:22     ` Greg KH
2007-04-26 17:21     ` Miles Lane
2007-04-26 17:33       ` Tejun Heo
2007-04-26 18:51         ` Miles Lane

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=1177544702.4668.9.camel@daplas \
    --to=adaplas@gmail.com \
    --cc=akpm@osdl.org \
    --cc=htejun@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles.lane@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox