linux-kernel - Re: broken access to a USB HID device after suspend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 13 Mar 2008 16:14:03 +0100
From:	Tino Keitel <tino.keitel@....de>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Jiri Kosina <jkosina@...e.cz>, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org
Subject: Re: broken access to a USB HID device after suspend

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/