Re: Linux 2.6.17: PM-Timer bug warning?

Re: Linux 2.6.17: PM-Timer bug warning?

[Andreas Mohr]

[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

Re: Linux 2.6.17: PM-Timer bug warning?

[Jean-Daniel Pauget]

On Tue, Jun 20, 2006 at 12:19:46PM +0200, Andreas Mohr wrote:
> On Tue, Jun 20, 2006 at 12:08:00PM +0200, Jean-Daniel Pauget wrote:
> >     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:
>  (.../...)

    oups sorry, I think my post interfered with Chris Rankin's post.

    my board is single cpu-ed (asus p4pe), gray-listed but OGAWA's test 
    doesn't trigger the bug :

myboard@asus-p4pe# lspci -v -v

0000:00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 02)
	Subsystem: Asustek Computer, Inc.: Unknown device 80b2
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 0
	Region 0: Memory at e0000000 (32-bit, prefetchable) [size=256M]
	Capabilities: <available only to root>

0000:00:01.0 PCI bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE Host-to-AGP Bridge (rev 02) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	Memory behind bridge: c6000000-c76fffff
	Prefetchable memory behind bridge: d7700000-dfffffff
	BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-

0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Asustek Computer, Inc.: Unknown device 8089
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 19
	Region 4: I/O ports at d800 [size=32]

0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Asustek Computer, Inc.: Unknown device 8089
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 20
	Region 4: I/O ports at d400 [size=32]

0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Asustek Computer, Inc.: Unknown device 8089
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin C routed to IRQ 17
	Region 4: I/O ports at d000 [size=32]

0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 02) (prog-if 20 [EHCI])
	Subsystem: Asustek Computer, Inc.: Unknown device 8089
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin D routed to IRQ 18
	Region 0: Memory at c5800000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <available only to root>

0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 82) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR+
	Latency: 0
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
	I/O behind bridge: 0000b000-0000bfff
	Memory behind bridge: c3000000-c57fffff
	Prefetchable memory behind bridge: c7700000-d76fffff
	BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-

0000:00:1f.0 ISA bridge: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) LPC Bridge (rev 02)
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0

0000:00:1f.1 IDE interface: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) UltraATA-100 IDE Controller (rev 02) (prog-if 8a [Master SecP PriP])
	Subsystem: Asustek Computer, Inc.: Unknown device 8089
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 17
	Region 0: I/O ports at <unassigned>
	Region 1: I/O ports at <unassigned>
	Region 2: I/O ports at <unassigned>
	Region 3: I/O ports at <unassigned>
	Region 4: I/O ports at f000 [size=16]
	Region 5: Memory at 50000000 (32-bit, non-prefetchable) [size=1K]

0000:00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 02)
	Subsystem: Asustek Computer, Inc.: Unknown device 8089
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin B routed to IRQ 0
	Region 4: I/O ports at e800 [size=32]

0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02)
	Subsystem: Asustek Computer, Inc.: Unknown device 80b0
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 21
	Region 0: I/O ports at a800 [size=256]
	Region 1: I/O ports at a400 [size=64]
	Region 2: Memory at c2800000 (32-bit, non-prefetchable) [size=512]
	Region 3: Memory at c2000000 (32-bit, non-prefetchable) [size=256]
	Capabilities: <available only to root>

0000:01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4200] (rev a3) (prog-if 00 [VGA])
	Subsystem: Asustek Computer, Inc.: Unknown device 8043
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 248 (1250ns min, 250ns max)
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at c6000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at d8000000 (32-bit, prefetchable) [size=128M]
	Region 2: Memory at d7800000 (32-bit, prefetchable) [size=512K]
	Expansion ROM at d77e0000 [disabled] [size=128K]
	Capabilities: <available only to root>

0000:02:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) (prog-if 10 [OHCI])
	Subsystem: Asustek Computer, Inc.: Unknown device 808a
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping+ SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (8000ns max), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 22
	Region 0: Memory at c5000000 (32-bit, non-prefetchable) [size=2K]
	Region 1: I/O ports at b800 [size=128]
	Capabilities: <available only to root>

0000:02:05.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702X Gigabit Ethernet (rev 02)
	Subsystem: Asustek Computer, Inc.: Unknown device 80a9
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64 (16000ns min), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at c4800000 (64-bit, non-prefetchable) [size=64K]
	Expansion ROM at d76f0000 [disabled] [size=64K]
	Capabilities: <available only to root>

0000:02:0a.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 440] (rev a3) (prog-if 00 [VGA])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 248 (1250ns min, 250ns max)
	Interrupt: pin A routed to IRQ 22
	Region 0: Memory at c3000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at c8000000 (32-bit, prefetchable) [size=128M]
	Region 2: Memory at c7800000 (32-bit, prefetchable) [size=512K]
	Expansion ROM at c77e0000 [disabled] [size=128K]
	Capabilities: <available only to root>

----------------------------------------------

--
    Jean-Daniel Pauget  -  http://disjunkt.com  -  http://nekodune.com
    Tél: +33 (0)2 33 17 20 16
    2, rue André PELCA
    50580 Denneville-Plage
    France

Re: Linux 2.6.17: PM-Timer bug warning?

[OGAWA Hirofumi]

Andreas Mohr <andi@rhlx01.fht-esslingen.de> writes:

>>     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).

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.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

Re: Linux 2.6.17: PM-Timer bug warning?

[Andreas Mohr]

Hi,

On Tue, Jun 20, 2006 at 11:58:01PM +0900, OGAWA Hirofumi wrote:
> Andreas Mohr <andi@rhlx01.fht-esslingen.de> writes:
> 
> >>     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).
> 
> 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.

Andreas Mohr

-- 
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?)

[PATCH -mm] clocksource: add PM Timer bug hunting notes

[Andreas Mohr]

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?)

Linux-2.6.17: PMTimer results for another PCI chipset

[Chris Rankin]

Hi,

This motherboard / chipset runs the pmtimer_test application correctly as well. (PIII / UP).

Linux version 2.6.17 (chris@twopit) (gcc version 4.1.1) #1 SMP Sun Jun 25 20:29:46 BST 2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001ffeb000 (usable)
 BIOS-e820: 000000001ffeb000 - 000000001ffef000 (ACPI data)
 BIOS-e820: 000000001ffef000 - 000000001ffff000 (reserved)
 BIOS-e820: 000000001ffff000 - 0000000020000000 (ACPI NVS)
 BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
511MB LOWMEM available.
On node 0 totalpages: 131051
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 126955 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v000 ASUS                                  ) @ 0x000f7b40
ACPI: RSDT (v001 ASUS   TUSL2-C  0x30303031 MSFT 0x31313031) @ 0x1ffeb000
ACPI: FADT (v001 ASUS   TUSL2-C  0x30303031 MSFT 0x31313031) @ 0x1ffeb100
ACPI: BOOT (v001 ASUS   TUSL2-C  0x30303031 MSFT 0x31313031) @ 0x1ffeb040
ACPI: MADT (v001 ASUS   TUSL2-C  0x30303031 MSFT 0x31313031) @ 0x1ffeb080
ACPI: DSDT (v001   ASUS TUSL2-C  0x00001000 MSFT 0x0100000b) @ 0x00000000
ACPI: PM-Timer IO Port: 0xe408

PCI summary:

00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 04)
00:01.0 PCI bridge: Intel Corp. 82815 815 Chipset AGP Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 05)
00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 05)
00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 05)
00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 05)
00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 05)
00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 05)

Full PCI output:

00:00.0 Class 0600: 8086:1130 (rev 04)
	Subsystem: 1043:8027
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 0
	Region 0: Memory at fc000000 (32-bit, prefetchable) [size=32M]
	Capabilities: [88] #09 [e104]
	Capabilities: [a0] AGP version 2.0
		Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
		Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>

00:01.0 Class 0604: 8086:1131 (rev 04)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: f8800000-f9cfffff
	Prefetchable memory behind bridge: f9f00000-fbffffff
	BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-

00:1e.0 Class 0604: 8086:244e (rev 05)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Bus: primary=00, secondary=02, subordinate=03, sec-latency=32
	I/O behind bridge: 0000b000-0000dfff
	Memory behind bridge: f5800000-f87fffff
	Prefetchable memory behind bridge: f9d00000-f9efffff
	BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-

00:1f.0 Class 0601: 8086:2440 (rev 05)
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0

00:1f.1 Class 0101: 8086:244b (rev 05) (prog-if 80 [Master])
	Subsystem: 1043:8027
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Region 4: I/O ports at a800 [size=16]

00:1f.2 Class 0c03: 8086:2442 (rev 05)
	Subsystem: 1043:8027
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin D routed to IRQ 17
	Region 4: I/O ports at a400 [size=32]

00:1f.3 Class 0c05: 8086:2443 (rev 05)
	Subsystem: 1043:8027
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin B routed to IRQ 10
	Region 4: I/O ports at e800 [size=16]

00:1f.4 Class 0c03: 8086:2444 (rev 05)
	Subsystem: 1043:8027
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin C routed to IRQ 18
	Region 4: I/O ports at a000 [size=32]



		
___________________________________________________________ 
Inbox full of spam? Get leading spam protection and 1GB storage with All New Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html

Re: Linux-2.6.17: PMTimer results for another PCI chipset

[Andreas Mohr]

Hi,

On Sun, Jun 25, 2006 at 09:42:12PM +0100, Chris Rankin wrote:
> Hi,
> 
> This motherboard / chipset runs the pmtimer_test application correctly as well. (PIII / UP).

Yeah, but this is no problem anyway, since it's neither in the blacklisted
nor in the graylisted area, IOW it's whitelisted and should work
without delays.
Or do you get the "The chipset may have PM-Timer Bug" message here??

> 00:1f.0 Class 0601: 8086:2440 (rev 05)

#define PCI_DEVICE_ID_INTEL_82801BA_0   0x2440

Thanks,

Andreas Mohr

Re: Linux-2.6.17: PMTimer results for another PCI chipset

[Chris Rankin]

--- Andreas Mohr <andi@rhlx01.fht-esslingen.de> wrote:
> Yeah, but this is no problem anyway, since it's neither in the blacklisted
> nor in the graylisted area, IOW it's whitelisted and should work
> without delays.
> Or do you get the "The chipset may have PM-Timer Bug" message here??
> 
> > 00:1f.0 Class 0601: 8086:2440 (rev 05)
> 
> #define PCI_DEVICE_ID_INTEL_82801BA_0   0x2440

Nope, it's all good. But since this chipset was released between the one which definitely has the
bug and one which might have the bug, I thought that it was worth testing it for real.

Cheers,
Chris



		
___________________________________________________________ 
Try the all-new Yahoo! Mail. "The New Version is radically easier to use" – The Wall Street Journal 
http://uk.docs.yahoo.com/nowyoucan.html

Re: Linux-2.6.17: PMTimer results for another PCI chipset

[Andreas Mohr]

Hi,

On Mon, Jun 26, 2006 at 06:44:12PM +0100, Chris Rankin wrote:
> --- Andreas Mohr <andi@rhlx01.fht-esslingen.de> wrote:
> > Yeah, but this is no problem anyway, since it's neither in the blacklisted
> > nor in the graylisted area, IOW it's whitelisted and should work
> > without delays.
> > Or do you get the "The chipset may have PM-Timer Bug" message here??
> > 
> > > 00:1f.0 Class 0601: 8086:2440 (rev 05)
> > 
> > #define PCI_DEVICE_ID_INTEL_82801BA_0   0x2440
> 
> Nope, it's all good. But since this chipset was released between the one which definitely has the
> bug and one which might have the bug, I thought that it was worth testing it for real.

Oh, then it's a very valid concern indeed!
Thanks for verifying that it doesn't seem to be a problem here.
(however, given the SMM/SMI BIOS fixups as pointed out by Albert Cahalan,
there might still be an issue with this chipset)

Andreas Mohr