linux-kernel - Re: [linux-usb-devel] 2.6.19-rc5: possible regression - OHCI dead after several STD/resume cycles

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] [day] [month] [year] [list]

Date:	Tue, 21 Nov 2006 15:59:25 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Andrey Borzenkov <arvidjaar@...l.ru>
cc:	linux-usb-devel@...ts.sourceforge.net,
	<linux-kernel@...r.kernel.org>
Subject: Re: [linux-usb-devel] 2.6.19-rc5: possible regression - OHCI dead
 after several STD/resume cycles

On Tue, 21 Nov 2006, Andrey Borzenkov wrote:

> Using 2.6.9-rc5 + Alan Stern fix for "can't disable OHCI wakeup via sysfs". I 
> started noticing strange messages after resume:
> 
> ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LNKH] -> GSI 11 (level, low) -> 
> IRQ 11
> ACPI: PCI interrupt for device 0000:00:06.0 disabled
> ACPI: PCI interrupt for device 0000:00:0a.0 disabled
> pccard: card ejected from slot 0
> Stopping tasks... 
> ===========================================================================================done.
> Shrinking memory... done (27344 pages freed)
> Suspending console(s)
>  usbdev1.1_ep81: PM: suspend 0->1, parent 1-0:1.0 already 1
> hub 1-0:1.0: PM: suspend 1->1, parent usb1 already 1
>  usbdev1.1_ep00: PM: suspend 0->1, parent usb1 already 1
> usb usb1: PM: suspend 1->1, parent 0000:00:02.0 already 2
...
>  usbdev1.1_ep00: PM: resume from 0, parent usb1 still 1
>  usbdev1.1_ep81: PM: resume from 0, parent 1-0:1.0 still 1
> Restarting tasks... done.
> 
> those strange are usbdev1.1_ep00/81.

Those aren't real devices at all; they are merely entries in sysfs which
represent logical communication endpoints in the OHCI controller.  It's  
not meaningful to speak of suspending or resuming them, but the PM core 
tries to do anyway.  You can ignore those messages; they are harmless.

> Now I needed to read from USB stick - it was not detected. Actually even HUB 
> itself has not been shown in lsusb output. Reloading ohci did fix it.
> 
> This never happend to me in all previous versions (since 2.6.15 I guess). Also 
> it did not start immediately after Alan's patch so I do not believe it is 
> related.
> 
> Please tell me what can I sensibly test and which input info should I collect. 
> Thank you. Configuration, dmesg etc available on request. lspci:

Turn on CONFIG_USB_DEBUG and then post the dmesg log showing what happens
when you plug in your USB stick.

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/