public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Simon Arlott <simon@fire.lp0.eu>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, dwalker@mvista.com
Subject: Re: [patch 0/3] fastboot patches series 1
Date: Fri, 18 Jul 2008 22:16:30 -0700	[thread overview]
Message-ID: <20080718221630.2809abbd@infradead.org> (raw)
In-Reply-To: <488172E0.6050502@simon.arlott.org.uk>

On Sat, 19 Jul 2008 05:51:44 +0100
Simon Arlott <simon@fire.lp0.eu> wrote:

> 
> This is a great idea... I was thinking about trying to run usb 
> initialisation in parallel because it takes so long. It would be more 
> useful to run usb init in parallel with ide/sata on my system, since
> they both take a while to run (I realise /dev/sd* will be in a
> unstable order).
> 
> Unfortunately this patch set has the opposite effect on my system...
> something appears to be going badly wrong (logs attached). The mouse 
> pointer was really erratic so I reconnected it (by turning the hub in 
> my display off/on)... that took a while:

is this repeatable? and was it repeatedly stable before?


> 
> Strangely, when this output appeared:
> [    1.370693] ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00,
> driver 10 Dec 2004
> 
> I didn't see anything else until the next screenful of output, but
> the log shows this output before that:
> [    4.683674] usb usb1: default language 0x0409
> [    7.548621] usb usb1: uevent
> 
> There was another long pause with no output but I can't see where
> from reading back the log. The timestamps are a bit confused too,
> jumping +/-10s.

looks like you have a timing problem.. can you try booting with "notsc"
and see if that fixes it?


One possible theory is that we now run on both cpus and if they're out
of sync timewise, things like delays suddenly are shorter than expected
if time jumps around....

can you also post a dmesg of a successful boot?

(and I'm supposed to give you a hard time for using a proprietary
module, but something is clearly going wrong before it's even loaded so
for now I'll just ignore that ;-)

  reply	other threads:[~2008-07-19  5:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 22:15 [patch 0/3] fastboot patches series 1 Arjan van de Ven
2008-07-18 22:16 ` [patch 1/3] fastboot: Create a "asynchronous" initlevel Arjan van de Ven
2008-07-19  1:22   ` Daniel Walker
2008-07-19  3:44     ` Arjan van de Ven
2008-07-19  4:11       ` Daniel Walker
2008-07-19  4:58         ` Arjan van de Ven
2008-07-19  5:20         ` Arjan van de Ven
2008-07-19 15:24           ` Daniel Walker
2008-07-19 15:35             ` Arjan van de Ven
2008-07-19 16:08               ` Daniel Walker
2008-07-19 16:14                 ` Arjan van de Ven
2008-07-19  4:28       ` Daniel Walker
2008-07-19  7:53   ` Rene Herman
2008-07-19  8:10     ` Rene Herman
2008-07-19 15:44       ` Arjan van de Ven
2008-07-20  7:23         ` Rene Herman
2008-07-20 11:10           ` Arjan van de Ven
2008-07-20 14:20             ` Rene Herman
2008-07-20 15:35               ` Arjan van de Ven
2008-07-18 22:16 ` [patch 2/3] fastboot: turn the USB hostcontroller initcalls into async initcalls Arjan van de Ven
2008-07-18 22:17 ` [patch 3/3] fastboot: convert a few non-critical ACPI drivers to " Arjan van de Ven
2008-07-19  4:51 ` [patch 0/3] fastboot patches series 1 Simon Arlott
2008-07-19  5:16   ` Arjan van de Ven [this message]
2008-07-19  5:47     ` Simon Arlott
2008-07-19 10:22     ` Andi Kleen
2008-07-20  8:31 ` Ingo Molnar

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=20080718221630.2809abbd@infradead.org \
    --to=arjan@infradead.org \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=simon@fire.lp0.eu \
    /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