From: Florin Iucha <florin@iucha.net>
To: Jiri Kosina <jikos@jikos.cz>
Cc: linux-usb-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@suse.de>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Subject: Re: [linux-usb-devel] USB-related oops in sysfs with linux v2.6.23-rc3-50-g28e8351
Date: Wed, 15 Aug 2007 09:53:14 -0500 [thread overview]
Message-ID: <20070815145313.GC7124@iucha.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0708151647540.2460@twin.jikos.cz>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
On Wed, Aug 15, 2007 at 04:49:02PM +0200, Jiri Kosina wrote:
> On Wed, 15 Aug 2007, Florin Iucha wrote:
>
> > Today my USB keyboard stopped working in the middle of composing and
> > e-mail. I unplugged it and plugged it back, with no success. I
> > logged in remotely and found this lovely message:
>
> The error message seems unrelated to your keyboard becoming dead.
Yes, it was related to me unplugging it in the hopes that a re-plug
will make it work again ;)
> > I am testing each rcX kernel, and I did not see this problem so far.
> > Smells like a new regression.
>
> Is that reproducible, or did it happen just once? Any error message
> present in log prior to that sysfs dump please?
[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.
Regards,
florin
--
Bruce Schneier expects the Spanish Inquisition.
http://geekz.co.uk/schneierfacts/fact/163
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-08-15 14:53 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 13:31 USB-related oops in sysfs with linux v2.6.23-rc3-50-g28e8351 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 [this message]
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
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=20070815145313.GC7124@iucha.net \
--to=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