mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Jean-Daniel Pauget <jd@disjunkt.com>,
	Chris Rankin <rankincj@yahoo.com>,
	linux-kernel@vger.kernel.org, john stultz <johnstul@us.ibm.com>,
	bert hubert <bert.hubert@netherlabs.nl>,
	george@mvista.com
Subject: [PATCH -mm] clocksource: add PM Timer bug hunting notes
Date: Fri, 23 Jun 2006 20:22:37 +0200	[thread overview]
Message-ID: <20060623182237.GA19853@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <20060620151658.GA5230@rhlx01.fht-esslingen.de>

On Tue, Jun 20, 2006 at 05:16:58PM +0200, Andreas Mohr wrote:
> Hi,
> 
> On Tue, Jun 20, 2006 at 11:58:01PM +0900, OGAWA Hirofumi wrote:
> > Almost ICH4 should be sane.  Since there seems both reports of good
> > and bad, probably the bug of ICH4 seems to be depending on a specific
> > motherboard.
> > 
> > FWIW, If you want to reduce gray-list, probably it should be
> > motherboard list.
> 
> OK, so if I get a nice description of which dual P4 Xeon motherboard that
> was (Dell something?), then I'll make a patch adding
> this chipset's revision + motherboard + LKML link of bug test app
> to the file, and asking for more testers there, too.

Done, hope that's ok (fixed a typo in the process).

Jean-Daniel, Chris: please complain loudly if you don't want to have your name
in that file...

Compile-tested on 2.6.17-mm1.

Signed-off-by: Andreas Mohr <andi@lisas.de>


--- linux-2.6.17-mm1.orig/drivers/clocksource/acpi_pm.c	2006-06-21 14:28:16.000000000 +0200
+++ linux-2.6.17-mm1/drivers/clocksource/acpi_pm.c	2006-06-23 20:11:32.000000000 +0200
@@ -70,7 +70,7 @@
 	.rating		= 200,
 	.read		= acpi_pm_read,
 	.mask		= (cycle_t)ACPI_PM_MASK,
-	.mult		= 0, /*to be caluclated*/
+	.mult		= 0, /* to be calculated */
 	.shift		= 22,
 	.is_continuous	= 1,
 };
@@ -92,7 +92,8 @@
 }
 
 /*
- * PIIX4 Errata:
+ * PIIX4 Errata #20, Intel PDF 29773817:
+ * (affects PIIX4 A0/A1/B0 and PIIX4E A0, *fixed* in PIIX4M A0)
  *
  * The power management timer may return improper results when read.
  * Although the timer value settles properly after incrementing,
@@ -135,6 +136,20 @@
 	       " workaround\n");
 
 	acpi_pm_need_workaround();
+
+	/* If you happen to have such a chipset and want to help improve things,
+	   then please run OGAWA Hirofumi's test app at
+	   http://marc.theaimsgroup.com/?l=linux-kernel&m=114297656924494&w=2
+	   (run for a somewhat longer time to be sure)
+	   and report bug status of your chipset revision/motherboard.
+
+	   Devices that seem to work fine (run "lspci -n"):
+	   - Chris Rankin: 8086:24c0 (rev 01), Dell Precision 650 (dual P4 Xeon)
+	   - Jean-Daniel Pauget: 8086:24c0 (rev 02), ASUS P4PE (non-SMP)
+
+	   Possibly the 8086:24c0 device is completely fine with all revisions
+	   after all... (but not sure yet, which is why we need your input)
+	*/
 }
 DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82801DB_0,
 			acpi_pm_check_graylist);

-- 
No programming skills!? Why not help translate many Linux applications! 
https://launchpad.ubuntu.com/rosetta
(or alternatively buy nicely packaged Linux distros/OSS software to help
support Linux developers creating shiny new things for you?)

  reply	other threads:[~2006-06-23 18:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060620100800.GB5040@disjunkt.com>
2006-06-20 10:19 ` Linux 2.6.17: PM-Timer bug warning? 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-23 18:22       ` Andreas Mohr [this message]
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

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=20060623182237.GA19853@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 \
    --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®