mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Jean-Daniel Pauget <jd@disjunkt.com>
Cc: linux-kernel@vger.kernel.org, john stultz <johnstul@us.ibm.com>,
	OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	bert hubert <bert.hubert@netherlabs.nl>,
	george@mvista.com
Subject: Re: Linux 2.6.17: PM-Timer bug warning?
Date: Tue, 20 Jun 2006 12:19:46 +0200	[thread overview]
Message-ID: <20060620101946.GA32658@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <20060620100800.GB5040@disjunkt.com>

[CC'ing further interested parties - sorry, a bit late in the discussion]

Hi,

On Tue, Jun 20, 2006 at 12:08:00PM +0200, Jean-Daniel Pauget wrote:
>     On Tue Jun 20, 2006 at 08:41:45 Andreas Mohr wrote :
> 
> >    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!
> 
>     fine !
>     though my hardware is in the gray list, it didn't trigger the bug with 
>     OGAWA's test.

[dual P4 Xeon board]

Interesting, so it likely isn't buggy.

Could you give lspci -v -v or so (to let us see chipset and revisions)?

Oh wait, you already did:

| 00:00.0 Host bridge: Intel Corporation E7505 Memory Controller Hub (rev 03)
| 00:01.0 PCI bridge: Intel Corporation E7505/E7205 PCI-to-AGP Bridge (rev 03)
| 00:02.0 PCI bridge: Intel Corporation E7505 Hub Interface B PCI-to-PCI Bridge
| +(rev 03)
| 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
| +USB UHCI Controller
| #1 (rev 01)
| 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
| +USB UHCI Controller
| #2 (rev 01)
| 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
| +USB UHCI Controller
| #3 (rev 01)
| 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI
| +Controller (rev 01)
| 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 81)
| 00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface
| +Bridge (rev 01)
| 00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 01)
| 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus
| +Controller (rev 01)
| 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM
| +(ICH4/ICH4-L/ICH4-M) AC'97
| Audio Controller (rev 01)


>     but now, how and to whom should I report ?

We need to enhance current kernel to whitelist this chipset revision
somehow. Or at least put a note there that this revision is ok, too
(to wait some more time for further evidence/revisions to appear).

>     about using other clocksource(s), where should we dig for ?

You mean e.g. the clock=tsc boot parameter?

Andreas Mohr

       reply	other threads:[~2006-06-20 10:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060620100800.GB5040@disjunkt.com>
2006-06-20 10:19 ` Andreas Mohr [this message]
2006-06-20 13:03   ` Jean-Daniel Pauget
2006-06-20 14:58   ` OGAWA Hirofumi
2006-06-20 15:16     ` Andreas Mohr
2006-06-23 18:22       ` [PATCH -mm] clocksource: add PM Timer bug hunting notes Andreas Mohr
2006-06-25 20:42         ` Linux-2.6.17: PMTimer results for another PCI chipset Chris Rankin
2006-06-26 12:08           ` Andreas Mohr
2006-06-26 17:44             ` Chris Rankin
2006-06-26 18:02               ` Andreas Mohr
2006-06-25 21:55 Linux 2.6.17: PM-Timer bug warning? Albert Cahalan
  -- strict thread matches above, loose matches on Subject: below --
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
2006-06-20 19:53       ` Chris Rankin

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=20060620101946.GA32658@rhlx01.fht-esslingen.de \
    --to=andi@rhlx01.fht-esslingen.de \
    --cc=bert.hubert@netherlabs.nl \
    --cc=george@mvista.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=jd@disjunkt.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®