| 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
| ||
|
Date: Sun, 16 Dec 2007 12:34:33 -0500 (EST) From: Parag Warudkar <parag.warudkar@...il.com> To: devzero@....de cc: linux-kernel@...r.kernel.org, Matt.Domsch@...l.com, hpa@...or.com Subject: Re: [PATCH] [RFC] be more verbose when probing EDD On Sun, 16 Dec 2007, devzero@....de wrote: > > - it seems there are buggy Bios implementations out there which have problems with EDD > - your favourite distro may have set CONFIG_EDD=y|m , so EDD probe is on by default quite often nowadays. > - setting "edd=off" when you get that hang on boot is _not_ obvious. It does not look like this issue is common - googling for "Linux EDD Boot hang" does not bring up relevant and recent results - in fact this post of yours comes on top. Further more there does not seem to be problems with newer BIOSes so we would be irritating lot many users needlessly. Adding 3 printks for each such obscure problem would make it even more complex to parse and make sense of the boot log - I, for example, already dislike the mostly-useless-to-end-user stuff it spews on a normal boot. If there are known chipsets / BIOSes that have this problem - applying quirks - something like this quirk for pmtmr [1]- (if they work this early) or even special casing them with forced edd=off may be the right and more useful thing to do. [1] http://www.webservertalk.com/archive242-2006-3-1447442.html Parag -- 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