From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Jiri Kosina <jikos@jikos.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.22-rc3 breaks USB: Unable to get HID descriptor (error sending control message: Operation not permitted)
Date: Sun, 3 Jun 2007 06:36:01 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706030634400.3574@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0706031146470.29896@twin.jikos.cz>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 809 bytes --]
On Sun, 3 Jun 2007, Jiri Kosina wrote:
> On Sat, 2 Jun 2007, Justin Piszcz wrote:
>
>> p34:~# /lib/nut/newhidups -u nut -DDDDDD auto
>> Checking device (050D/0912) (005/002)
>> - VendorID: 050d
>> - ProductID: 0912
>> - Manufacturer: unknown
>> - Product: unknown
>> - Serial Number: unknown
>> - Bus: 005
>> Trying to match device
>> Device matches
>> failed to claim USB device, trying 2 more time(s)...
>> detaching kernel driver from USB device...
>
> Could you please provide strace outputs (or put it on the web somewhere if
> it's too big) for the failing and succeeding claiming of the device?
>
> Thanks,
>
> --
> Jiri Kosina
>
Sure, they are attached:
$ du -sh nut*
4.0K nut-bad.txt.bz2 (2.6.22-rc3)
12K nut-good.txt.bz2 (2.6.21.3)
Let me know if they are of any use.
Thanks,
Justin.
[-- Attachment #2: Type: APPLICATION/octet-stream, Size: 3164 bytes --]
[-- Attachment #3: Type: APPLICATION/octet-stream, Size: 8349 bytes --]
next prev parent reply other threads:[~2007-06-03 10:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 22:43 Justin Piszcz
2007-06-03 9:49 ` Jiri Kosina
2007-06-03 10:36 ` Justin Piszcz [this message]
2007-06-03 10:54 ` Oliver Neukum
2007-06-03 12:29 ` Justin Piszcz
2007-06-03 11:00 ` Jiri Kosina
2007-06-03 11:16 ` Justin Piszcz
2007-06-03 11:22 ` Jiri Kosina
2007-06-03 11:52 ` Justin Piszcz
2007-06-03 12:35 ` Kay Sievers
2007-06-03 12:40 ` Justin Piszcz
2007-06-03 12:44 ` Justin Piszcz
2007-06-03 16:51 ` Kay Sievers
2007-06-03 9:55 ` Jiri Kosina
2007-06-03 10:48 ` [linux-usb-devel] " Oliver Neukum
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=Pine.LNX.4.64.0706030634400.3574@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=jikos@jikos.cz \
--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®