mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Chris Rankin <rankincj@yahoo.com>
Cc: Con Kolivas <kernel@kolivas.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.17: PM-Timer bug warning?
Date: Tue, 20 Jun 2006 10:41:45 +0200	[thread overview]
Message-ID: <20060620084145.GA29378@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <20060620075947.33014.qmail@web52914.mail.yahoo.com>

Hi,

On Tue, Jun 20, 2006 at 08:59:47AM +0100, Chris Rankin wrote:
> --- Con Kolivas <kernel@kolivas.org> wrote:
> > We don't have such a list that tells us which hardware is prone otherwise we 
> > could have put the workaround for broken chipsets only.
> 
> True, but if there were no way to test for this bug then arguably the bug could not be said to
> exist in the first place. So how would I determine whether my chipset really is prone or not?

OGAWA Hirofumi initially posted a test app:

http://marc.theaimsgroup.com/?l=linux-kernel&m=114297656924494&w=2

and there were lots of PM-Timer abandon triple-read optimization
LKML discussions quite recently where one can read on that topic...

Thanks for your testing help, it's very important!

Andreas Mohr

  reply	other threads:[~2006-06-20  8:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20  0:15 Chris Rankin
2006-06-20  1:23 ` Con Kolivas
2006-06-20  7:59   ` Chris Rankin
2006-06-20  8:41     ` Andreas Mohr [this message]
2006-06-20 19:53       ` Chris Rankin
     [not found] <20060620100800.GB5040@disjunkt.com>
2006-06-20 10:19 ` Andreas Mohr
2006-06-20 13:03   ` Jean-Daniel Pauget
2006-06-20 14:58   ` OGAWA Hirofumi
2006-06-20 15:16     ` Andreas Mohr
2006-06-25 21:55 Albert Cahalan

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=20060620084145.GA29378@rhlx01.fht-esslingen.de \
    --to=andi@rhlx01.fht-esslingen.de \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rankincj@yahoo.com \
    /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
all inboxes | Powered by JetHome®