be more verbose when probing EDD
Quoted 3 lines
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.
i dont wonder here - how should one know that its an edd problem if all he sees is a blank screen with a blinking cursor in the upper left ? so i assume, "Linux EDD Boot hang" isn`t the best term for searching here.
i think, there is no universal search phrase - i found some references with different words (linux install, blank screen, blinking cursor....)
some of them
http://forums.suselinuxsupport.de/lofiversion/index.php/t61581.html
http://suseforums.net/index.php?showtopic=1302
http://forums.suselinuxsupport.de/lofiversion/index.php/t3157.html
http://www.linuxforums.org/forum/installation/73984-cant-boot-past-loading-kernel-fedora-4-a.html
http://ubuntuforums.org/archive/index.php/t-146180.html
http://ubuntuforums.org/showthread.php?t=450630
http://www.linuxquestions.org/questions/linux-software-2/grub-freezes-before-uncompressing-kernel-464619/
not sure if really all of them are the edd problem i have, but i`m quite sure for some of those. can provide more links if somebody likes.
Quoted 1 line
Adding 3 printks for each such obscure problem would make it even more
i wouldn`t call that problem obscure.
i have seen this problem more than 5 times since that code is in linux. so its at least enough to discuss about even if no other person thinks its necessary :) just the fact that its not been discussed often (here or elsewhere) doesnt mean, that it exist or that users come across that. its more that type of "mhh, lets try linux instead of windows. oh, doesnt boot. ok, lets stay with windows then...". you don`t expect people like those posting the right question to the right forum, do you?
Quoted 3 lines
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.
mhh. im unsure. ok, im no kernel-hacker but there are so many variants of bios/hardware out there so blacklisting certain bios versions may be never more than half of a solution.
roland
Quoted 24 lines
-----Ursprüngliche Nachricht-----
Von: "Parag Warudkar" <[email protected]>
Gesendet: 16.12.07 18:34:48
An: [email protected]
CC: [email protected], [email protected], [email protected]
Betreff: Re: [PATCH] [RFC] be more verbose when probing EDDQuoted 4 lines · On Sun, 16 Dec 2007, [email protected] wrote:
- it seems there are buggy Bios implementations out there which have problems with EDD
- your favourite distro may have setCONFIG_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.
Quoted 8 lines
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
_______________________________________________________________________
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220
Quoted 11 lines · On Dec 16, 2007 2:11 PM, <[email protected]> wrote:
some of them
http://forums.suselinuxsupport.de/lofiversion/index.php/t61581.html
http://suseforums.net/index.php?showtopic=1302
http://forums.suselinuxsupport.de/lofiversion/index.php/t3157.html
http://www.linuxforums.org/forum/installation/73984-cant-boot-past-loading-kernel-fedora-4-a.html
http://ubuntuforums.org/archive/index.php/t-146180.html
http://ubuntuforums.org/showthread.php?t=450630
http://www.linuxquestions.org/questions/linux-software-2/grub-freezes-before-uncompressing-kernel-464619/not sure if really all of them are the edd problem i have, but i`m quite sure for some of those. can provide more links if somebody likes.
None of them seemed like they were determined as EDD problems - some even did not work with edd=skipmbr.
But that is not the point. Problem is not widely known, likely happens with very old BIOSes and people who use those systems should be knowing more than simply booting back to Win98.
And if those people are smart enough to figure out the right place to ask - they will likely get suggestions to do edd=off like some of the above links that you posted prove - without the message.
Why tax other people with a warning/hang etc. in printk when the problem is very unlikely on their systems?
Quoted 4 lines
Quoted 2 lines
Adding 3 printks for each such obscure problem would make it even more
i wouldn`t call that problem obscure.
i have seen this problem more than 5 times since that code is in linux. so its at least enough to discuss about even if no other person thinks its necessary :) just the fact that its not been discussed often (here or elsewhere) doesnt mean, that it exist or that users come across that. its more that type of "mhh, lets try linux instead of windows. oh, doesnt boot. ok, lets stay with windows then...". you don`t expect people like those posting the right question to the right forum, do you?
So you think those people with such low tech knowledge will figure out the right mailing list, make sense of the output of EDD message and then post the question? Or that they will figure out how to specify the edd=off to kernel command line? In that use case - not doing EDD on their boxes like I said would be the most useful thing to do. A message or 3 is useless in this case.
Quoted 5 lines
Quoted 4 lines
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.mhh. i
m unsure. ok, im no kernel-hacker but there are so many variants of bios/hardware out there so blacklisting certain bios versions may be never more than half of a solution.
We have no data though to say this is a widespread problem. And the type of people you are caterign to in your patch need further hand holding to keep their system running Linux anyway.
(Hey my modem won't work, the resolution is too low etc. let's go back to Windows.)
But yeah whatever - if you cut it down to one printk line and remove the hang word that would at least be bearable :)
Parag
Quoted 2 lines
Why tax other people with a warning/hang etc. in printk when the problem is very unlikely on their systems?
I think there is sense in it if you do it subtly differently.
printk(".. if this hangs do ... \r");
edd_stuff();
printk(" \r");So that we display it, do the EDD call, then write over it with whatever is next that matters.
That way you'd only see it when it hung - and that might be worth a patch and test from someone.
Quoted 6 lines · Alan Cox
Quoted 3 lines
Why tax other people with a warning/hang etc. in printk when the problem is very unlikely on their systems?
I think there is sense in it if you do it subtly differently.
Quoted 7 lines
printk(".. if this hangs do ... \r"); edd_stuff(); printk(" \r");So that we display it, do the EDD call, then write over it with whatever is next that matters.
Does printk support escape sequences? The last time I tried printk("\e[1;35m omg ponies \e[0m"); that did not went too successful.
Quoted 2 lines
That way you'd only see it when it hung - and that might be worth a patch and test from someone.
Quoted 10 lines · Jan Engelhardt
Quoted 9 lines · Alan Cox
Quoted 2 lines
Why tax other people with a warning/hang etc. in printk when the problem is very unlikely on their systems?
I think there is sense in it if you do it subtly differently.
printk(".. if this hangs do ... \r"); edd_stuff(); printk(" \r");
Quoted 6 lines
Quoted 2 lines
So that we display it, do the EDD call, then write over it with whatever is next that matters.
Does printk support escape sequences? The last time I tried
printk("\e[1;35m omg ponies \e[0m"); that did not went too successful.
Uh, no. Do that and anyone trying to interpret logs will beat you to death with a pickled herring.
-hpa
Quoted 2 lines
Does printk support escape sequences? The last time I tried
printk("\e[1;35m omg ponies \e[0m"); that did not went too successful.
It should handle \r correctly. If not that is easy to fix.
Escape codes are bad and should not be used - you may have a serial console and not be on a Linux console
Quoted 7 lines · Alan Cox
Quoted 2 lines
Does printk support escape sequences? The last time I tried
printk("\e[1;35m omg ponies \e[0m"); that did not went too successful.It should handle \r correctly. If not that is easy to fix.
Escape codes are bad and should not be used - you may have a serial console and not be on a Linux console
It's not printk(), or the console, that's the issue... Consider logging to a file, which is quite common.
Dumping formatting characters in there is a bit evil.
Instead of using \r and overwrite, something like
Testing foo... ok
printk(KERN_INFO "Testing foo... ");foo();printk("ok\n");
... really is a lot better. We used to do that a lot more.
-hpa