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]

Date:	Wed, 15 Aug 2007 11:24:50 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Florin Iucha <florin@...ha.net>
cc:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Tejun Heo <htejun@...il.com>, Greg KH <gregkh@...e.de>,
	USB development list <linux-usb-devel@...ts.sourceforge.net>,
	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

On Wed, 15 Aug 2007, Florin Iucha wrote:

> On Wed, Aug 15, 2007 at 10:38:54AM -0400, Alan Stern wrote:
> > This patch will get rid of the annoying error messages.  It won't do 
> > anything about your keyboard's tendency to spontaneously stop working, 
> > alas.
> 
> My keyboard works fine for days, with kernels up to and including
> 2.6.23-rc2 . I have booted into 2.6.23-rc3-$whatever this morning, and
> after 10-15 minutes the keyboard stopped working.  The mice which were
> plugged in the keyboard's built-in hub were fine though.
> 
> The first time it happened, I removed the keyboard and got the oops
> that started this thread.

It wasn't an oops, just a warning.

>  The second time, I just logged-in remotely
> and rebooted, and the reboot process stopped at "KILLING all
> processes" step.  I simply reset the box and rebooted into 2.6.23-rc2
> and it is fine since (over an hour ago).

To track this down, you might try building 2.6.23-rc3 with 
CONFIG_USB_DEBUG enabled.  Then retrieve the dmesg log after the 
keyboard stops working and post it.  You probably ought to CC: the 
maintainer of the HID core layer as well (and you can trim the existing 
CC: list).

Alan Stern

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