linux-kernel - Re: [linux-usb-devel] USB-related oops in sysfs with linux v2.6.23-rc3-50-g28e8351

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <200708211406.31726.oliver@neukum.org>
Date:	Tue, 21 Aug 2007 14:06:31 +0200
From:	Oliver Neukum <oliver@...kum.org>
To:	linux-usb-devel@...ts.sourceforge.net, Greg KH <gregkh@...e.de>
Cc:	Florin Iucha <florin@...ha.net>, Jiri Kosina <jikos@...os.cz>,
	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [linux-usb-devel] USB-related oops in sysfs with linux	v2.6.23-rc3-50-g28e8351

Am Dienstag 21 August 2007 schrieb Florin Iucha:
> On Wed, Aug 15, 2007 at 04:58:33PM +0200, Jiri Kosina wrote:
> > On Wed, 15 Aug 2007, Florin Iucha wrote:
> > 
> > > [See my message to Alan]: It happened twice, within 15 minutes of 
> > > boot+login, with 2.6.23-rc3-$whatever .  I does not happen with 
> > > 2.6.2[123](-rc*)?  After the two incidents, I rebooted in 2.6.23-rc2 and 
> > > it is working for an hour now.
> > 
> > It is not immediately clear what might be causing this, 2.6.23-rc3 didn't 
> > get any USB nor HID updates at all compared to 2.6.23-rc2.
> > 
> > Could you please enable USB and HID debugging to see whether we can see 
> > anything spurious in the logs at the time the keyboard gets stuck?
> 
> Jiri,
> 
> I have enabled USB debugging and I see a bunch (=46) of these messages:
> 
>    [  $timestamp] usb 1-9: usb auto-suspend
>    [  $timestamp] usb 1-9: usb auto-resume
>    [  $timestamp] ehci_hcd 0000:00:02.1: GetStatus port 9 status 001005 POWER sig=se0 PE CONNECT
>    [  $timestamp] usb 1-9: finish resume
> 
> The messages continued to be logged, even after the keyboard has
> become unresponsive.

[   60.756730] usb 1-9: usb auto-resume
Did you hit a key at that time?


It looks like your keyboard gets autosuspended. But how can that happen?
Keyboards should never autosuspend, as they are always open.
The patch for minimum autosuspend support in HID did get in earlier,
didn't it?

	Regards
		Oliver


-
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/