public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Andreas Mohr <andi@lisas.de>, LKML <linux-kernel@vger.kernel.org>,
	john stultz <johnstul@us.ibm.com>,
	OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-acpi@vger.kernel.org
Subject: Re: ACPI PM-Timer on K6-3 SiS5591: Houston...
Date: Sun, 10 Aug 2008 09:40:38 -0700	[thread overview]
Message-ID: <20080810094038.141480b4@infradead.org> (raw)
In-Reply-To: <20080810162920.GA9860@comet.dominikbrodowski.net>

On Sun, 10 Aug 2008 18:29:20 +0200
Dominik Brodowski <linux@dominikbrodowski.net> wrote:

> Hi Andreas,
> 
> On Sun, Aug 10, 2008 at 12:17:30PM +0200, Andreas Mohr wrote:
> > Result: catastrophic timer behaviour (a large backwards skip is
> > possible), even in case we do a triple-read workaround, due to a
> > floating bit at 0x0400 (possibly caused by underclocking from 400
> > to 150, but whatever...).
> 
> this isn't the bug which is handled by the
> read-three-times-workaround. Instead, that handels the following
> PIIX4 errata:
> 
>  * PIIX4 Errata:
>  *
>  * The power management timer may return improper results when read.
>  * Although the timer value settles properly after incrementing,
>  * while incrementing there is a 3 ns window every 69.8 ns where the
>  * timer value is indeterminate (a 4.2% chance that the data will be
>  * incorrect when read). As a result, the ACPI free running count up
>  * timer specification is violated due to erroneous reads.
> 
> > And my system does pass the bootup PM-Timer check quite often
> > despite this severe defect (2 in 4 bootups _did_ register my
> > defective acpi_pm clocksource).
> 
> No surprise there -- it is the first time I see such an error; and it
> might actually be a bug specific to your computer's motherboard. 
> 

if it's really only one board that's faulty... a dmi blacklist might be
appropriate.


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-08-10 16:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-10 10:17 ACPI PM-Timer on K6-3 SiS5591: Houston Andreas Mohr
2008-08-10 16:29 ` Dominik Brodowski
2008-08-10 16:40   ` Arjan van de Ven [this message]
2008-08-10 19:08   ` Andreas Mohr
2008-08-10 20:02     ` Dominik Brodowski
2008-08-18 19:03     ` [git pull?] clocksource: ACPI pmtmr bugfixes [Was: Re: ACPI PM-Timer on K6-3 SiS5591: Houston...] Dominik Brodowski
2008-08-18 19:05       ` [PATCH 1/2] acpi_pm.c: use proper read function also in errata mode Dominik Brodowski
2008-08-18 19:05       ` [PATCH 2/2] acpi_pm.c: check for monotonicity Dominik Brodowski
2008-08-18 19:19       ` [git pull?] clocksource: ACPI pmtmr bugfixes [Was: Re: ACPI PM-Timer on K6-3 SiS5591: Houston...] Andrew Morton
2008-08-18 19:35         ` Dominik Brodowski
2008-08-18 19:47           ` Andrew Morton
2008-08-18 20:09             ` Dominik Brodowski
2008-08-18 20:10               ` [PATCH 1/2] acpi_pm.c: use proper read function also in errata mode Dominik Brodowski
2008-08-19  9:43                 ` Andrew Morton
2008-08-19  9:49                   ` Dominik Brodowski
2008-08-19  9:59                     ` Andrew Morton
2008-08-22 22:22                       ` [PATCH v2 " Dominik Brodowski
2008-08-22 22:26                       ` [PATCH v2 2/2] acpi_pm.c: check for monotonicity Dominik Brodowski
2008-08-23  8:48                         ` Jochen Voß
2008-08-18 20:11               ` [PATCH " Dominik Brodowski
2008-08-18 20:18                 ` Andreas Mohr
2008-08-18 20:28                   ` Andrew Morton
2008-08-18 20:42                     ` Dominik Brodowski
2008-08-18 20:25               ` [git pull?] clocksource: ACPI pmtmr bugfixes [Was: Re: ACPI PM-Timer on K6-3 SiS5591: Houston...] Andrew Morton
2008-08-18 20:29                 ` Dominik Brodowski
2008-08-18 20:00           ` Andreas Mohr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080810094038.141480b4@infradead.org \
    --to=arjan@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andi@lisas.de \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=johnstul@us.ibm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox