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>] [day] [month] [year] [list]
Message-ID: <0FF8E27EC45B4FDB903F8B368059568E@cyberweb>
Date:	Tue, 2 Dec 2008 16:57:53 +0100
From:	"Sirius" <sirius@...nenkinder.org>
To:	<linux-kernel@...r.kernel.org>
Subject: Concerning EHCI BIOS handoff timeout

Hello everyone!

My BIOS seems to be buggy when it comes to the EHCI BIOS handoff process (at 
least that's what syslog is telling me). That's why I need to wait for the 
timeout (five seconds) to happen EVERY boot. So I know in advance that 
something won't happen but still I need to wait for it - not to happen.

Of course I could just change the timeout to 0 in 
/drivers/usb/host/pci-quirks.c but then all the benefits from running my 
distribution's kernel would be gone.

I think there should be a way (maybe via a kernel boot parameter?) to tell 
the kernel that there is no need to wait.

Thanks for your input,
Sirius 

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