From: Tino Keitel <tino.keitel@gmx.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: broken access to a USB HID device after suspend
Date: Fri, 14 Mar 2008 08:13:36 +0100 [thread overview]
Message-ID: <20080314071336.GA14550@dose.home.local> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0803131450370.5744-100000@iolanthe.rowland.org>
On Thu, Mar 13, 2008 at 14:59:48 -0400, Alan Stern wrote:
[...]
> > Well, it seems to be "fixed" by a suspend/resume cycle. Do you have
> > a
> > hint how I could try to fix it without suspend/resume, to test if
> > it is
> > really the LCD's fault?
>
> Testing has to come before fixing -- you can't fix the problem if you
> don't know which component is at fault. For all we know, the
> hardware
> could be fine and the problem could lie in your application.
I meant a method other than suspend/resume to fix the broken behaviour,
so that we get an indication where the problem exactly is.
>
> All I can think of for testing is to use usbmon to record the data
> transfers when those -110 errors come up.
Well, I still don't have USB_DEBUG or usbmon enabled, but I just got
that error again. I pulled the power plug from the LCD and replugged
it, without success. Then I did a suspend/resume cycle, and it worked.
Regards,
Tino
next prev parent reply other threads:[~2008-03-14 7:13 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 [this message]
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
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=20080314071336.GA14550@dose.home.local \
--to=tino.keitel@gmx.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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®