From: Greg KH <greg@kroah.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, vojtech@suse.cz
Subject: Re: [OOPS/HACK] atmel_cs and the latest changes in sysfs/symlink.c
Date: Fri, 7 May 2004 16:25:10 -0700 [thread overview]
Message-ID: <20040507232510.GO14660@kroah.com> (raw)
In-Reply-To: <200405050208.11348.dtor_core@ameritech.net>
On Wed, May 05, 2004 at 02:08:11AM -0500, Dmitry Torokhov wrote:
> On Tuesday 04 May 2004 04:04 pm, Greg KH wrote:
> > On Sun, Apr 25, 2004 at 04:48:07PM -0500, Dmitry Torokhov wrote:
> > >
> > > No, I am still getting the oops.. hmm.. it seems a little bit different,
> > > but still in the hiddev. I investigated further and the oops only happens
> > > if I yank a HID device connected to an USB hub or if I yank entire hub with
> > > a HID device connected to it. Tried with APC UPS and MS Intellimouse
> > > Explorer. If they are connected directly to the laptop's ports everything is
> > > fine, also other devices (USB printer for example) handle hub disconnection
> > > just fine. It does not matter if I have device open or closed for oops to
> > > happen. And, for the record, oops itself:
> >
> > Are you still getting this in the 2.6.6-rc3 kernel?
> >
> > How about the latest -mm release?
> >
>
> With tonight's bk pull + USB patch from 2.6.6-rc3-mm1 I am still getting the
> following oops when pulling a HID device out of a hub:
Ick, I'll work on trying to duplicate this and see if I can figure it
out...
thanks for letting me know.
greg k-h
next prev parent reply other threads:[~2004-05-08 0:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 6:42 [OOPS/HACK] atmel_cs and the latest changes in sysfs/symlink.c Dmitry Torokhov
2004-04-23 12:25 ` Marcel Holtmann
2004-04-23 13:02 ` Dmitry Torokhov
2004-04-23 14:26 ` Marcel Holtmann
2004-04-23 16:55 ` Dmitry Torokhov
2004-04-23 17:16 ` Greg KH
2004-04-23 18:50 ` Marcel Holtmann
2004-04-23 19:46 ` Greg KH
2004-04-23 20:35 ` Russell King
2004-04-23 21:02 ` Marcel Holtmann
2004-04-23 15:31 ` Greg KH
2004-04-23 17:19 ` Greg KH
2004-04-23 18:03 ` Greg KH
2004-04-24 6:44 ` Dmitry Torokhov
2004-04-25 2:49 ` Greg KH
2004-04-25 21:48 ` Dmitry Torokhov
2004-05-04 21:04 ` Greg KH
2004-05-05 7:08 ` Dmitry Torokhov
2004-05-07 23:25 ` Greg KH [this message]
2004-04-26 10:19 ` Vojtech Pavlik
2004-04-23 19:55 ` Russell King
2004-04-23 20:14 ` Marcel Holtmann
2004-04-23 20:39 ` Russell King
2004-04-25 21:53 ` Dmitry Torokhov
2004-04-25 22:58 ` Russell King
2004-04-26 10:35 ` Marcel Holtmann
2004-04-26 12:32 ` Dmitry Torokhov
2004-04-26 13:09 ` Marcel Holtmann
2004-04-27 5:57 ` Dmitry Torokhov
2004-04-26 12:26 ` Dmitry Torokhov
2004-04-23 15:28 ` Greg KH
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=20040507232510.GO14660@kroah.com \
--to=greg@kroah.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=vojtech@suse.cz \
/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