Incorrect mdelay() results on Power Managed Machines x86
Quoted 5 lines
Boot with the 'notsc' option is one approach. We certainly could recalibrate the clock if we could get events out of ACPI, APM or some other source. Maybe someone at IBM knows something on the thinkpad front here. If there is for example an additional apm event or irq we can enable for the thinkpads to see the speed change we can make it work
On the ThinkPad 600E (at least), we get a Power Status Change APM event.
Cheers,
Stephen Rothwell
P.S. We actually get two of these events each time we remove or insert the power cord ...
Quoted 1 line
On the ThinkPad 600E (at least), we get a Power Status Change APM event.
Any reason we couldn't recalibrate the bogomips on a power status change, at least for laptops we know appear to need it (I can make the DMI code look for matches there..)
Hi!
Quoted 5 lines
Quoted 1 line
On the ThinkPad 600E (at least), we get a Power Status Change APM event.
Any reason we couldn't recalibrate the bogomips on a power status change, at least for laptops we know appear to need it (I can make the DMI code look for matches there..)
Notice that this is not 100% solution. APM is async, and you might already did few wrong delays by the time apm event is delivered to you.
Also notice that at least my toshiba goes low speed (150MHz) on *) batteries going low
*) overheat
It goes back to 300MHz at ac power. Another crazy thing: it goes down to 35MHz on extreme overheat -- that's factor of 10 change.
Signature · 2 lines
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.