linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Maneesh Soni <maneesh@in.ibm.com>
Cc: Mike Gorse <mgorse@mgorse.dhs.org>,
	linux-kernel@vger.kernel.org, Patrick Mochel <mochel@osdl.org>
Subject: Re: Oops w/sysfs when closing a disconnected usb serial device
Date: Fri, 5 Dec 2003 15:36:18 -0800	[thread overview]
Message-ID: <20031205233618.GB14162@kroah.com> (raw)
In-Reply-To: <20031202071112.GA20864@in.ibm.com>

On Tue, Dec 02, 2003 at 12:41:13PM +0530, Maneesh Soni wrote:
> Hi Mike,
> 
> I think now I understand the problem better. It looks to me a case of
> parent kobject going away before child. 

Yes, but I don't see how that is happening in the usb code :(

> As we have 
> 
> > sysfs 1-1: removing dir
> >  o 1-1:1.0 (10): <7>removing<7> done
> 
> and then
> > sysfs 1-1:1.0: removing dir
> 
> Its good that you enabled debug printks. We can see error 
> 
> > usb 1-1: hcd_unlink_urb d3d33f60 fail -22

This isn't an error, it can be ignored.  It just means that the driver
told the usb core to unlink a urb that was already unlinked.  Very
common thing.

> I think Greg or Pat can help you better in this case. I have no idea if 
> this error is creating this problem.

It's not this error, but something else.  The usb-serial code hasn't
changed in a while.  Can you try figuring out what kernel version this
bug shows up in?

thanks,

greg k-h

  reply	other threads:[~2003-12-05 23:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01  0:18 Mike Gorse
2003-12-01  9:38 ` Maneesh Soni
2003-12-01 23:55   ` Mike Gorse
2003-12-02  7:11     ` Maneesh Soni
2003-12-05 23:36       ` Greg KH [this message]
2003-12-06  1:38     ` Greg KH
2003-12-06  2:16       ` Mike Gorse
2003-12-07  2:58         ` Greg KH
2003-12-07  3:09           ` Mike Gorse
2003-12-06  0:56   ` Greg KH
2003-12-08  4:56     ` Maneesh Soni

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=20031205233618.GB14162@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneesh@in.ibm.com \
    --cc=mgorse@mgorse.dhs.org \
    --cc=mochel@osdl.org \
    --subject='Re: Oops w/sysfs when closing a disconnected usb serial device' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).