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

[Florin Iucha <florin@iucha.net>]

[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]

On Tue, Aug 21, 2007 at 06:51:15AM -0500, Florin Iucha wrote:
> 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.

[snip]

> Do you need me to build a -rc2 with USB debug enabled to compare and
> contrast?

With 2.6.23-rc2 and USB_DEBUG enabled, I see the same messages but no
keyboard "dissapearance".

I have rebuilt 2.6.23-rc3 with 'CONFIG_USB_EHCI_HCD=m' and
'CONFIG_USB_SUSPEND is not set' and will use it for a while, to see if 
the keyboard/usb behaves or not.

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