From: Tino Keitel <tino.keitel@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: broken access to a USB HID device after suspend
Date: Wed, 12 Mar 2008 23:33:25 +0100 [thread overview]
Message-ID: <20080312223325.GA2290@dose.home.local> (raw)
In-Reply-To: <Pine.LNX.4.64.0803122217580.7266@twin.jikos.cz>
On Wed, Mar 12, 2008 at 22:23:46 +0100, Jiri Kosina wrote:
> On Wed, 12 Mar 2008, Tino Keitel wrote:
>
> > I use a tool called hidmon to control the parameters of my LCD in shell
> > scripts. I just had the case where this tool didn't work after suspend
> > to RAM. I just got this error message:
> >
> > hid_force_open failed with return code 13
> >
> > The kernel log contains lines like this:
> >
> > usb 1-1.3: usbfs: USBDEVFS_CONTROL failed cmd hidmon rqt 129 rq 6 len 9 ret -110
> >
> > Unplugging and replugging the USB cable of the LCD didn't work.
> > However, after a further suspend/resume cycle it works.
> >
> > This is Linux 2.6.25-rc5. The behaviour is not repoducible, though.
> > However, I just mention it for the case that this might ring a bell
> > somewhere.
>
> This in fact looks like a problem with usbdevfs and/or libusb library, not
> the in-kernel HID drvier.
>
> Did this work before? In 2.6.24? 2.6.23? Alan (added to CC, as well as USB
It worked in 2.6.24 and several 2.6.25-rc kernels, including the
currently running 2.6.25-rc5.
Regards,
Tino
next prev parent reply other threads:[~2008-03-12 22:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 19:34 Tino Keitel
2008-03-12 21:23 ` Jiri Kosina
2008-03-12 21:44 ` Alan Stern
2008-03-12 22:44 ` Tino Keitel
2008-03-13 14:59 ` Alan Stern
2008-03-13 15:14 ` Tino Keitel
2008-03-13 18:59 ` Alan Stern
2008-03-14 7:13 ` Tino Keitel
2008-03-14 7:17 ` Tino Keitel
2008-03-14 14:36 ` Alan Stern
2008-03-14 15:00 ` Tino Keitel
2008-03-14 14:34 ` Alan Stern
2008-03-14 15:02 ` Tino Keitel
2008-03-18 19:12 ` Tino Keitel
2008-03-18 19:24 ` Alan Stern
2008-03-12 22:33 ` Tino Keitel [this message]
2008-03-12 22:35 ` Jiri Kosina
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=20080312223325.GA2290@dose.home.local \
--to=tino.keitel@gmx.de \
--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®