From: "Carlos Jiménez" <lordeath@linuxspain.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: UHCI-HCD && mosedev on 2.6.0-test11
Date: Tue, 16 Dec 2003 01:55:34 +0100 [thread overview]
Message-ID: <1071536070.12406.5.camel@localhost> (raw)
Hello,
I have an usbmouse that works on 2.4.x kernel series.
now on 2.6.0 usb module hangs, and does not work with it.
Tests are made on centrino laptop (00:1d.0 USB Controller: Intel Corp.
82801DB USB) on 2.6.0-test[9-11] series on gentoo linux.
Error:
Dec 16 01:41:42 kardon kernel: usb 2-2: USB disconnect, address 2
Dec 16 01:41:42 kardon kernel: printing eip:
Dec 16 01:41:42 kardon kernel: c0159683
Dec 16 01:41:42 kardon kernel: Oops: 0000 [#1]
Dec 16 01:41:42 kardon kernel: CPU: 0
Dec 16 01:41:42 kardon kernel: EIP: 0060:[<c0159683>] Not tainted
Dec 16 01:41:42 kardon kernel: EFLAGS: 00010296
Dec 16 01:41:42 kardon kernel: EIP is at __lookup_hash+0x1b/0xd0
Dec 16 01:41:42 kardon kernel: eax: cf411e98 ebx: 12fd28db ecx:
ffffffff edx: 01b9ec71
Dec 16 01:41:42 kardon kernel: esi: c03a7218 edi: 00000000 ebp:
00000000 esp: cf411e5c
Dec 16 01:41:42 kardon kernel: ds: 007b es: 007b ss: 0068
Dec 16 01:41:42 kardon kernel: Process khubd (pid: 2642,
threadinfo=cf410000 task=cf830cc0)
Dec 16 01:41:42 kardon kernel: Stack: c036f8c0 cf411e8c 00000000
12fd28db c03a7218 c034053c ce5ae528 c0159757
Dec 16 01:41:42 kardon kernel: cf411e98 00000000 00000000
c017a998 cf411e98 00000000 00000282 c0340537
Dec 16 01:41:42 kardon kernel: 00000005 12fd28db 00000282
cdf5a894 ce5ae400 c017be33 00000000 c0340537
Dec 16 01:41:42 kardon kernel: Call Trace:
Dec 16 01:41:42 kardon kernel: [<c0159757>] lookup_hash+0x1f/0x23
Dec 16 01:41:42 kardon kernel: [<c017a998>] sysfs_get_dentry+0x6a/0x70
Dec 16 01:41:42 kardon kernel: [<c017be33>]
sysfs_remove_group+0x65/0x6a
Dec 16 01:41:42 kardon kernel: [<c023e662>] dpm_sysfs_remove+0x1a/0x20
Dec 16 01:41:42 kardon kernel: [<c023e12b>] device_pm_remove+0x26/0x71
Dec 16 01:41:42 kardon kernel: [<c023bcff>] device_del+0x65/0x9b
Dec 16 01:41:42 kardon kernel: [<d1adfbd4>]
usb_disable_device+0xdb/0x116 [usbcore]
Dec 16 01:41:42 kardon kernel: [<d1ad9c85>] usb_disconnect+0x9f/0x12f
[usbcore]
Dec 16 01:41:42 kardon kernel: [<d1adc790>]
hub_port_connect_change+0x399/0x39e [usbcore]
Dec 16 01:41:42 kardon kernel: [<d1adcb9c>] hub_events+0x407/0x470
[usbcore]
Dec 16 01:41:42 kardon kernel: [<d1adcc32>] hub_thread+0x2d/0xf7
[usbcore]
Dec 16 01:41:42 kardon kernel: [<c011a1f4>]
default_wake_function+0x0/0x12
Dec 16 01:41:42 kardon kernel: [<d1adcc05>] hub_thread+0x0/0xf7
[usbcore]
Dec 16 01:41:42 kardon kernel: [<c0107289>]
kernel_thread_helper+0x5/0xb
Dec 16 01:41:42 kardon kernel:
Dec 16 01:41:42 kardon kernel: Code: 8b 77 08 89 6c 24 08 c7 44 24 04 01
00 00 00 89 34 24 e8 30
Dec 16 01:41:42 kardon kernel: <7>drivers/usb/host/uhci-hcd.c: efe0:
suspend_hc
Any ideas tos solve it? tnx
next reply other threads:[~2003-12-16 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 0:55 Carlos Jiménez [this message]
2003-12-16 17:46 ` UHCI-HCD && mosedev on 2.6.0-test11 Greg KH
2003-12-17 0:33 ` Carlos Jiménez
2003-12-17 0:55 ` Greg KH
2003-12-17 10:18 ` Carlos Jiménez
2003-12-19 12:13 ` Carlos Jiménez
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=1071536070.12406.5.camel@localhost \
--to=lordeath@linuxspain.net \
--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