From: Gerhard Mack <gmack@innerfire.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc3: sysfs_remove_bin_file: bad dentry or inode or no such file: "descriptors"
Date: Sun, 2 Sep 2007 08:35:51 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.0.999.0709020835160.4961@mtl.rackplans.net> (raw)
In-Reply-To: <20070902045349.b59af405.akpm@linux-foundation.org>
On Sun, 2 Sep 2007, Andrew Morton wrote:
> > On Tue, 14 Aug 2007 23:36:32 -0400 (EDT) Gerhard Mack <gmack@innerfire.net> wrote:
> > hello,
> >
> > Got this when I booted into 2.6.23-rc3: Let me know if more info is
> > needed.
> >
> > Gerhard
> >
> >
> > sysfs_remove_bin_file: bad dentry or inode or no such file: "descriptors"
> >
> > Call Trace:
> > [<ffffffff80480117>] usb_remove_sysfs_dev_files+0x89/0x9d
> > [<ffffffff8047cf29>] usb_unbind_device+0x15/0x19
> > [<ffffffff803f855e>] __device_release_driver+0x8e/0xb0
> > [<ffffffff803f8953>] device_release_driver+0x2c/0x44
> > [<ffffffff803f7e56>] bus_remove_device+0x6e/0x7d
> > [<ffffffff803f6641>] device_del+0x1ec/0x268
> > [<ffffffff80477af3>] usb_disconnect+0xbc/0x149
> > [<ffffffff804782c2>] hub_thread+0x3f8/0xba5
> > [<ffffffff805e3463>] thread_return+0x57/0xdf
> > [<ffffffff80244f0b>] autoremove_wake_function+0x0/0x2e
> > [<ffffffff80477eca>] hub_thread+0x0/0xba5
> > [<ffffffff80244df3>] kthread+0x47/0x74
> > [<ffffffff8020c588>] child_rip+0xa/0x12
> > [<ffffffff8021b96a>] flat_send_IPI_mask+0x0/0x4c
> > [<ffffffff80244dac>] kthread+0x0/0x74
> > [<ffffffff8020c57e>] child_rip+0x0/0x12
> >
>
> Is this still happening in 2.6.23-rc4 or later?
2.6.23-rc4 is fixed and so is 2.6.23-rc5.
Thanks,
Gerhard
--
Gerhard Mack
gmack@innerfire.net
<>< As a computer I find your faith in technology amusing.
prev parent reply other threads:[~2007-09-02 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 3:36 Gerhard Mack
2007-09-02 11:53 ` Andrew Morton
2007-09-02 12:35 ` Gerhard Mack [this message]
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=alpine.DEB.0.999.0709020835160.4961@mtl.rackplans.net \
--to=gmack@innerfire.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®