diff options
author | 2008-09-05 14:05:33 -0700 | |
---|---|---|
committer | 2008-09-06 15:33:31 +0200 | |
commit | dfdf748a61a21b7397b9f57c83de722de71dc56a (patch) | |
tree | 78fce25782a3a313a4d8db4464a849e66cc77fa8 /fs/jbd2/commit.c | |
parent | ntp: fix calculation of the next jiffie to trigger RTC sync (diff) | |
download | linux-dev-dfdf748a61a21b7397b9f57c83de722de71dc56a.tar.xz linux-dev-dfdf748a61a21b7397b9f57c83de722de71dc56a.zip |
clocksource, acpi_pm.c: use proper read function also in errata mode
On all hardware (some Intel ICH4, PIIX4 and PIIX4E chipsets) affected by a
hardware errata there's about a 4.2% chance that initialization of the
ACPI PMTMR fails. On those chipsets, we need to read out the timer value
at least three times to get a correct result, for every once in a while
(i.e. within a 3 ns window every 69.8 ns) the read returns a bogus
result. During normal operation we work around this issue, but during
initialization reading a bogus value may lead to -EINVAL even though the
hardware is usable.
Thanks to Andreas Mohr for spotting this issue.
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions