From: Jiri Slaby <jirislaby@gmail.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: David Brownell <david-b@pacbell.net>,
USB list <linux-usb@vger.kernel.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: quirk_usb_disable_ehci takes 2x 1.5s on boot
Date: Tue, 24 Feb 2009 14:32:03 +0100 [thread overview]
Message-ID: <49A3F6D3.4030703@gmail.com> (raw)
In-Reply-To: <4962A792.9070706@shaw.ca>
On 6.1.2009 01:36, Robert Hancock wrote:
> Jiri Slaby wrote:
>> I don't know since which moment (maybe I changed something in bios,
>> but usb
>> legacy kbd was ever enabled), but quirk_usb_disable_ehci takes for
>> both of my
>> ehci controllers 1.5 s.
>>
>> More precisely, the time is spent in
>> pci_write_config_byte(pdev, offset + 3, 1);
>> by
>> outb((u8)value, 0xCFC + (reg & 3));
>> from pci_conf1_write deep in the callstack.
>>
>> Is there any workaround known or something. Turning legacy usb off is
>> not an
>> option, I want to control grub.
>
> Most likely the PCI config space write is causing some SMM trap and the
> BIOS is taking forever to do whatever it's doing. It doesn't report that
> the handoff failed, though?
Some time ago there was something like that:
http://kerneltrap.org/mailarchive/linux-kernel/2007/9/24/273262
I haven't seen it since that time.
> I'd look for a BIOS update..
I can't find any, bad luck. It's some kind of testing machine sample...
Nevermind, it obviously doesn't occur during kexeced kernel bootup, I
can live with that :).
prev parent reply other threads:[~2009-02-24 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 13:41 quirk_usb_disable_ehci takes 2x 1.5s on boot Jiri Slaby
2009-01-05 22:44 ` David Brownell
2009-01-06 0:36 ` Robert Hancock
2009-02-24 13:32 ` Jiri Slaby [this message]
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=49A3F6D3.4030703@gmail.com \
--to=jirislaby@gmail.com \
--cc=david-b@pacbell.net \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.