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:	Thu, 03 Dec 2009 08:21:00 -0800
From:	"Justin P. Mattock" <justinmattock@...il.com>
To:	Alan Stern <stern@...land.harvard.edu>
CC:	Oliver Neukum <oliver@...kum.org>,
	Robert Hancock <hancockrwd@...il.com>,
	Linux-usb <linux-usb@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: root hub lost power or was reset

On 12/03/09 07:16, Alan Stern wrote:
> On Thu, 3 Dec 2009, Oliver Neukum wrote:
>
>> Am Donnerstag, 3. Dezember 2009 01:58:46 schrieb Justin P. Mattock:
>>>>> Now looking at dmesg I see:
>>>>>
>>>>> [ 413.551845] uhci_hcd 0000:00:1d.0: PCI INT A ->  GSI 23 (level, low)
>>>>> ->  IRQ 23
>>>>> [ 413.551855] uhci_hcd 0000:00:1d.0: setting latency timer to 64
>>>>> [ 413.551887] usb usb2: root hub lost power or was reset
>>>>
>>>> Is that unexpected? It seems reasonable to me..
>>>
>>> honestly I can't remember seeing this or not.
>>> if this is normal then I'll leave it as is.
>>
>> This happens if your system cuts power to USB during S2.
>
> It also happens if the system retains power but resets the controller
> while resuming (as indicated by the log message: "lost power or was
> reset".)  Again, it's a BIOS thing.
>
> And it seems to be very widespread.  I haven't seen more than a handful
> of systems which _don't_ cut power or reset their UHCI controllers
> during S3 sleep.
>
> Alan Stern
>
>


Thanks for all the info on this.
Well, s2ram works ended up being
isight_firmware for some reason
or another. As for the reset
it is a macbook, so if theres something wrong
with the bios, then this makes sense
(something with efi);

In any case everything else seems o.k.
Thanks again for the info.

Justin P. Mattock


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ