From: Oliver Neukum <oliver@neukum.org>
To: linux-usb-devel@lists.sourceforge.net, Greg KH <gregkh@suse.de>
Cc: Florin Iucha <florin@iucha.net>, Jiri Kosina <jikos@jikos.cz>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] USB-related oops in sysfs with linux v2.6.23-rc3-50-g28e8351
Date: Tue, 21 Aug 2007 14:06:31 +0200 [thread overview]
Message-ID: <200708211406.31726.oliver@neukum.org> (raw)
In-Reply-To: <20070821115115.GD10422@iucha.net>
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
next prev parent reply other threads:[~2007-08-21 12:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 13:31 Florin Iucha
2007-08-15 14:38 ` [linux-usb-devel] " Alan Stern
2007-08-15 14:50 ` Florin Iucha
2007-08-15 15:24 ` Alan Stern
2007-08-15 14:54 ` Tejun Heo
2007-08-15 15:21 ` Cornelia Huck
2007-08-15 15:30 ` Tejun Heo
2007-08-15 15:33 ` Alan Stern
2007-08-15 14:49 ` Jiri Kosina
2007-08-15 14:53 ` Florin Iucha
2007-08-15 14:58 ` Jiri Kosina
2007-08-21 11:51 ` Florin Iucha
2007-08-21 12:04 ` Jiri Kosina
2007-08-21 12:28 ` Florin Iucha
2007-08-21 14:51 ` Alan Stern
2007-08-21 12:06 ` Oliver Neukum [this message]
2007-08-21 12:09 ` Jiri Kosina
2007-08-21 12:19 ` Oliver Neukum
2007-08-21 12:57 ` Florin Iucha
2007-08-21 13:05 ` Jiri Kosina
2007-08-21 13:17 ` Florin Iucha
2007-08-21 13:27 ` Florin Iucha
2007-08-21 13:42 ` Jiri Kosina
2007-08-22 13:22 ` Florin Iucha
2007-08-23 12:52 ` NFS woes again Was: " Florin Iucha
2007-08-23 17:14 ` Bret Towe
2007-08-23 17:36 ` Florin Iucha
2007-08-27 13:17 ` Trond Myklebust
2007-08-28 1:19 ` Bret Towe
2007-08-28 1:35 ` NFS woes again Florin Iucha
2007-08-28 13:28 ` Trond Myklebust
2007-08-29 3:27 ` Florin Iucha
2007-08-29 5:52 ` Bret Towe
2007-08-30 22:18 ` Bret Towe
2007-08-30 23:14 ` Florin Iucha
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=200708211406.31726.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=florin@iucha.net \
--cc=gregkh@suse.de \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=michal.k.k.piotrowski@gmail.com \
/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®