linux-kernel - Re: quirk_usb_disable_ehci takes 2x 1.5s on boot

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, 24 Feb 2009 14:32:03 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	Robert Hancock <hancockr@...w.ca>
CC:	David Brownell <david-b@...bell.net>,
	USB list <linux-usb@...r.kernel.org>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Alan Stern <stern@...land.harvard.edu>
Subject: Re: quirk_usb_disable_ehci takes 2x 1.5s on boot

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 :).
--
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/