From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Greg KH <greg@kroah.com>
Cc: linux-usb-devel@lists.sourceforge.net, vojtech@suse.cz,
Marcel Holtmann <marcel@holtmann.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Simon Kelley <simon@thekelleys.org.uk>
Subject: Re: [OOPS/HACK] atmel_cs and the latest changes in sysfs/symlink.c
Date: Sat, 24 Apr 2004 01:44:04 -0500 [thread overview]
Message-ID: <200404240144.05004.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040423180342.GA14533@kroah.com>
On Friday 23 April 2004 01:03 pm, Greg KH wrote:
> On Fri, Apr 23, 2004 at 10:19:53AM -0700, Greg KH wrote:
> > On Fri, Apr 23, 2004 at 08:31:11AM -0700, Greg KH wrote:
> > >
> > > No, we need to oops, as that's a real bug. Can you post the whole oops
> > > that was generated with this usb problem? I can't seem to duplicate
> > > this here.
> >
> > Nevermind I dug up a device here that causes this problem. I'll track
> > it down...
>
> Ok, here's a patch that fixes it for me. I was waiting for a good
> reason to finally get rid of this fake usb_interface structure, and now
> I have it :)
>
Yes, it does fix it for me, thanks a lot!
Now if somebody could fix the following oops...
Unable to handle kernel paging request at virtual address e1b1a120
printing eip:
e1b1504a
*pde = 1fe1d067
*pte = 00000000
Oops: 0002 [#1]
PREEMPT
CPU: 0
EIP: 0060:[<e1b1504a>] Tainted: P
EFLAGS: 00010246 (2.6.6-rc2)
EIP is at hiddev_cleanup+0x2a/0x40 [usbhid]
eax: 00000060 ebx: d7215640 ecx: 00000000 edx: e18728f4
esi: e1b19b80 edi: dfe30800 ebp: df2bfe50 esp: df2bfe44
ds: 007b es: 007b ss: 0068
Process khubd (pid: 400, threadinfo=df2be000 task=df3a5230)
Stack: d7922680 e1b19c7c d3e8e000 df2bfe64 e1b14ac8 d7215640 e1b19b80 d7922680
df2bfe80 e1859106 d7922680 d7922680 d44f9da0 d7922690 e1b19ba0 df2bfe98
c0210bc6 d7922690 d79226b8 d7922690 dfe308cc df2bfeb0 c0210d03 d7922690
Call Trace:
[<e1b14ac8>] hid_disconnect+0xb8/0xe0 [usbhid]
[<e1859106>] usb_unbind_interface+0x76/0x80 [usbcore]
[<c0210bc6>] device_release_driver+0x66/0x70
[<c0210d03>] bus_remove_device+0x53/0xa0
[<c020fbdd>] device_del+0x5d/0xa0
[<c020fc34>] device_unregister+0x14/0x30
[<e185f480>] usb_disable_device+0x70/0xb0 [usbcore]
[<e1859d16>] usb_disconnect+0xa6/0x100 [usbcore]
[<e1859d58>] usb_disconnect+0xe8/0x100 [usbcore]
[<e185bfef>] hub_port_connect_change+0x28f/0x2a0 [usbcore]
[<e185b971>] hub_port_status+0x41/0xb0 [usbcore]
[<e185c343>] hub_events+0x343/0x3b0 [usbcore]
[<e185c3e5>] hub_thread+0x35/0xf0 [usbcore]
[<c0115ef0>] default_wake_function+0x0/0x20
[<e185c3b0>] hub_thread+0x0/0xf0 [usbcore]
[<c01032e5>] kernel_thread_helper+0x5/0x10
--
Dmitry
next prev parent reply other threads:[~2004-04-24 6:44 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 [this message]
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
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=200404240144.05004.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
--cc=simon@thekelleys.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.