mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Thu, 13 Mar 2008 16:14:03 +0100	[thread overview]
Message-ID: <20080313151403.GA5667@dose.home.local> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0803131049510.4474-100000@iolanthe.rowland.org>

On Thu, Mar 13, 2008 at 10:59:26 -0400, Alan Stern wrote:
> On Wed, 12 Mar 2008, Tino Keitel wrote:
> 
> > On Wed, Mar 12, 2008 at 17:44:56 -0400, Alan Stern wrote:
> > 
> > [...]
> > 
> > > Tino, it would help to see a kernel log showing what happened during 
> > > the suspend, resume, and failure of hidmon.  It would help even more if 
> > > you test under a kernel with CONFIG_USB_DEBUG enabled.
> > 
> > A full kernel log is available at http://tikei.de/dmesg
> > 
> > > 
> > > Even if you can't reproduce the problem, do you have the complete 
> > > kernel log from before?
> > > 
> > > Is it possible that this is really a problem with the LCD device, not 
> > > with the kernel?  I ask because if the device was working properly then 
> > > unplugging and replugging the USB cable should do a complete reset.
> > 
> > I did the following:
> > 
> > - suspended the computer
> > 
> > - switched off the LCD
> 
> And switched it back on at some point?

Err, yes, right after resume.

> 
> > - resumed the computer
> > 
> > - tried to use hidmon, got the error
> > 
> > - unplugged the LCD
> > 
> > - plugged in the LCD
> > 
> > - tried to use hidmon again, got the error again
> > 
> > - suspended the computer
> > 
> > - resumed the computer
> > 
> > - tried to use hidmon again, and it worked
> > 
> > Note that I didn't switch off the LCD during the second suspend, in the
> > case that matters.
> 
> Well, this isn't what your log shows.
> 
> According to the log, you booted the computer on March 10 and about 12 
> minutes later started getting those -110 errors on the LCD device.  

Uh, it looks like I just didn't noticed that.

> Then you suspended the computer with no apparent problem.
> 
> Two days later you suspended three more times, and the the LCD monitor
> was disconnected during the third suspend.  When it came back, you

What log message do you refer to here?

> started getting the errors again.
> 
> Next you unplugged and replugged the hub into which the LCD was 
> connected.  Again there was another -110 error.  Finally you suspended 
> and resumed.
> 
> To me that makes it look like the LCD's problems have no connection at
> all with suspend/resume.

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?

Regards,
Tino

  reply	other threads:[~2008-03-13 15: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 [this message]
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
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=20080313151403.GA5667@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®