public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Linux-usb <linux-usb@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: root hub lost power or was reset
Date: Wed, 02 Dec 2009 16:58:46 -0800	[thread overview]
Message-ID: <4B170D46.9030701@gmail.com> (raw)
In-Reply-To: <4B1701EC.9030504@gmail.com>

On 12/02/09 16:10, Robert Hancock wrote:
> On 12/02/2009 04:34 PM, Justin Mattock wrote:
>> I've been getting a 45 sec
>> pause when waking my machine up
>> on the first cycle using s2ram.
>> At first thought it was udev, but later
>> am not sure it is. With further looking
>> if I remove the isight_firmware module from the kernel
>> suspend wakes up the first cycle as it should.(I don't have
>> isight-firmware-tools installed, leading me to believe this might
>> be the issue with isight-firmware.ko.)
>>
>> 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.

s2ram is working.. at first thought this was the cause,
but ended up not having anything todo with the real cause
of s2ram pausing.

Justin P. Mattock

  reply	other threads:[~2009-12-03  1:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 22:34 root hub lost power or was reset Justin Mattock
2009-12-02 23:19 ` Oliver Neukum
2009-12-02 23:37   ` Justin Mattock
2009-12-03  0:10 ` Robert Hancock
2009-12-03  0:58   ` Justin P. Mattock [this message]
2009-12-03  8:33     ` Oliver Neukum
2009-12-03 15:16       ` Alan Stern
2009-12-03 16:21         ` Justin P. Mattock
2009-12-03 16:45         ` Oliver Neukum
2009-12-04 18:22           ` Justin P. Mattock

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=4B170D46.9030701@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=hancockrwd@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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