RE: clock drift with two Promise Ultra133 TX2 (PDC 20269) cards

RE: clock drift with two Promise Ultra133 TX2 (PDC 20269) cards

[Drew Winstel]

> Thanks, now it loads correctly. Unfortunately the clock drift still occurs
> with pata_pdc2027x. I'm guessing here, but can clock drift have anything
> to do with IRQs? Also, is it normal to see errors in /proc/interrupt?

I've never noticed any errors before, but that could just be a result of me 
never actually bothering to look.

> # cat /proc/interrupts 

<snip>
> ERR:      23672

Hmmm....

I'm grasping at straws here.

Let's do some poking into your kernel config.  What do you have set under 
"Processor type and features"?  

I experienced a similar situation once in the past, but that was a result of 
drives losing DMA and doing simultaneous activity on eight drives and four 
controllers.  Moving to the pata_pdc2027x driver seems to have cleared it 
right up.

Sorry I can't provide a quick cure-all!

Drew

Re: clock drift with two Promise Ultra133 TX2 (PDC 20269) cards

[Oskar Liljeblad]

On Tuesday, May 03, 2005 at 13:45, Drew Winstel wrote:
> > Thanks, now it loads correctly. Unfortunately the clock drift still occurs
> > with pata_pdc2027x. I'm guessing here, but can clock drift have anything
> > to do with IRQs? Also, is it normal to see errors in /proc/interrupt?
> 
> I've never noticed any errors before, but that could just be a result of me 
> never actually bothering to look.

Are interrupts errors serious? Can anyone tell? The error count was higher
when I had a fifth PCI card in the computer (natsemi ethernet NIC).
Could there be some kind of PCI card conflict? Maybe I should try to
remove a few of them...

[..]
> Let's do some poking into your kernel config.  What do you have set under 
> "Processor type and features"?

CONFIG_X86_PC=y
CONFIG_MK7=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
CONFIG_HPET_TIMER=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y

In other words, Athlon/Duron/K7 + HPET + Local APIC + IO-Apic
(though I have tried with both XT-PIC and Local APIC, with same
drift).

And no, the clock drift occurs no matter if ntpd is running or not.
It's having a very hard time to syncronize with the remote servers,
because the clock drift is too high. (It also says somewhere in the
NTP documentation that it doesn't handle too high clock drift.)

Regards,

Oskar Liljeblad (oskar@osk.mine.nu)

RE: clock drift with two Promise Ultra133 TX2 (PDC 20269) cards

[Drew Winstel]

> Are interrupts errors serious? Can anyone tell? The error count was higher
> when I had a fifth PCI card in the computer (natsemi ethernet NIC).
> Could there be some kind of PCI card conflict? Maybe I should try to
> remove a few of them...

It's worth a shot. Just for the record, I haven't had any such errors on my
machine.
root@linux /proc # cat interrupts 
           CPU0       
  0:   46494411          XT-PIC  timer
  1:      13644          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  5:    1210194          XT-PIC  ohci_hcd, SiS SI7012
  7:         19          XT-PIC  parport0
  9:    3492898          XT-PIC  acpi, ohci_hcd, nvidia
 10:          0          XT-PIC  ohci_hcd
 11:      29194          XT-PIC  ehci_hcd, eth0
 12:     295381          XT-PIC  i8042
 14:     567754          XT-PIC  ide0
 15:         48          XT-PIC  ide1
NMI:          0 
ERR:          0
root@linux /proc # uptime
 09:38:16 up 12:54,  5 users,  load average: 0.08, 0.03, 0.03

> In other words, Athlon/Duron/K7 + HPET + Local APIC + IO-Apic
> (though I have tried with both XT-PIC and Local APIC, with same
> drift).

So much for that thought.  The kernel config is solid (as expected).

> And no, the clock drift occurs no matter if ntpd is running or not.
> It's having a very hard time to syncronize with the remote servers,
> because the clock drift is too high. (It also says somewhere in the
> NTP documentation that it doesn't handle too high clock drift.)

I just had an idea.  Using the old PDC20269 IDE driver, try repeating
your test to trigger clock drift.  While the test is in progress, run
hdparm (no need for -i) on both drives.  I wonder if it's dropping out
of DMA mode temporarily for no apparent reason.

Thanks,
Drew

RE: clock drift with two Promise Ultra133 TX2 (PDC 20269) cards

[Drew Winstel]

>Hm, I patched the kernel with 2.6.11-libata-dev1, compiled it with

># CONFIG_BLK_DEV_PDC202XX_NEW is not set
>CONFIG_BLK_DEV_VIA82CXXX=y   (for the motherboard IDE)
>CONFIG_SCSI=y
>CONFIG_SCSI_SATA=y
>CONFIG_SCSI_PATA_PDC2027X=y

>and rebooted. SCSI is initialized and the pata_pdc2027x driver is
>loaded, but it doesn't seem to find any devices. Or maybe it doesn't
>look for devices at all. I can tell that it's loaded by the existence
>of /sys/bus/pci/drivers/pata_pdc2027x (a directory which is empty).

>/proc/scsi/scsi is also empty besides the "Attached devices:" line.
>During startup the kernel does say "Probing IDE interface ide0"
>through "ide5" (finding only devices on ide0). I also tried compiling
>pata_pdc2027x as a module, with same result.

>What's wrong here?

I think I know what the problem is.

In include/linux/libata.h, make sure the preprocessor declarations are as 
follows.  I think the defaults have ATA_ENABLE_PATA undefined.

#define ATA_ENABLE_ATAPI        /* undefine to disable ATAPI support */
#define ATA_ENABLE_PATA          /* define to enable PATA support in some
                                 * low-level drivers */

Sorry I forgot to mention this earlier.  

Drew

Re: clock drift with two Promise Ultra133 TX2 (PDC 20269) cards

[Oskar Liljeblad]

On Tuesday, May 03, 2005 at 11:53, Drew Winstel wrote:
> I think I know what the problem is.
> 
> In include/linux/libata.h, make sure the preprocessor declarations are as 
> follows.  I think the defaults have ATA_ENABLE_PATA undefined.
> 
> #define ATA_ENABLE_ATAPI        /* undefine to disable ATAPI support */
> #define ATA_ENABLE_PATA          /* define to enable PATA support in some
>                                  * low-level drivers */

Thanks, now it loads correctly. Unfortunately the clock drift still occurs
with pata_pdc2027x. I'm guessing here, but can clock drift have anything
to do with IRQs? Also, is it normal to see errors in /proc/interrupt?

# cat /proc/interrupts 
           CPU0       
  0:     954189          XT-PIC  timer
  2:          0          XT-PIC  cascade
  8:         16          XT-PIC  rtc
  9:          0          XT-PIC  acpi
 10:       1630          XT-PIC  eth1
 11:     103147          XT-PIC  libata
 12:       9990          XT-PIC  eth0
 14:       5993          XT-PIC  ide0
 15:     145866          XT-PIC  libata
NMI:          0 
LOC:          0 
ERR:      23672
MIS:          0

Regards,

Oskar Liljeblad (oskar@osk.mine.nu)

Re: clock drift with two Promise Ultra133 TX2 (PDC 20269) cards

[Bill Davidsen]

Oskar Liljeblad wrote:
> On Tuesday, May 03, 2005 at 11:53, Drew Winstel wrote:
> 
>>I think I know what the problem is.
>>
>>In include/linux/libata.h, make sure the preprocessor declarations are as 
>>follows.  I think the defaults have ATA_ENABLE_PATA undefined.
>>
>>#define ATA_ENABLE_ATAPI        /* undefine to disable ATAPI support */
>>#define ATA_ENABLE_PATA          /* define to enable PATA support in some
>>                                 * low-level drivers */
> 
> 
> Thanks, now it loads correctly. Unfortunately the clock drift still occurs
> with pata_pdc2027x. I'm guessing here, but can clock drift have anything
> to do with IRQs? Also, is it normal to see errors in /proc/interrupt?

Are you by chance running ntpd? And have you checked to see if it dies 
as soon as it starts? There's a bug in the ntp M/L wrt execstack.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

RE: clock drift with two Promise Ultra133 TX2 (PDC 20269) cards

[Drew Winstel]

> geometry     = 30515/255/63, sectors = 490234752, start = 0

>/dev/hde:

> Model=Maxtor 6B250R0, FwRev=BAH41BM0, SerialNo=<...>
> Config={ Fixed }
> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
> BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=off
> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
> IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
> PIO modes:  pio0 pio1 pio2 pio3 pio4 
> DMA modes:  mdma0 mdma1 mdma2 
> UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
> AdvancedPM=yes: disabled (255) WriteCache=enabled
> Drive conforms to: (null): 

> * signifies the current active mode

Hmm... that puzzles me, although for no other reason than I'm not familiar 
with how Maxtor drives report themselves.  Having the BIOS-reported LBA 
sectors not equal to the OS-reported geometry may not be a problem, but 
I must defer to the experts on that one.  

As an FYI just in case, the new libata-based driver will treat your drives 
as SCSI drives, so you'll see the drives as sda, sdb, and so forth instead of
hd?.  

Good luck!

Drew

Re: clock drift with two Promise Ultra133 TX2 (PDC 20269) cards

[Oskar Liljeblad]

On Tuesday, May 03, 2005 at 10:17, Drew Winstel wrote:
> 
> Hmm... that puzzles me, although for no other reason than I'm not familiar 
> with how Maxtor drives report themselves.  Having the BIOS-reported LBA 
> sectors not equal to the OS-reported geometry may not be a problem, but 
> I must defer to the experts on that one.  
> 
> As an FYI just in case, the new libata-based driver will treat your drives 
> as SCSI drives, so you'll see the drives as sda, sdb, and so forth instead of
> hd?.  

Hm, I patched the kernel with 2.6.11-libata-dev1, compiled it with

# CONFIG_BLK_DEV_PDC202XX_NEW is not set
CONFIG_BLK_DEV_VIA82CXXX=y   (for the motherboard IDE)
CONFIG_SCSI=y
CONFIG_SCSI_SATA=y
CONFIG_SCSI_PATA_PDC2027X=y

and rebooted. SCSI is initialized and the pata_pdc2027x driver is
loaded, but it doesn't seem to find any devices. Or maybe it doesn't
look for devices at all. I can tell that it's loaded by the existence
of /sys/bus/pci/drivers/pata_pdc2027x (a directory which is empty).

/proc/scsi/scsi is also empty besides the "Attached devices:" line.
During startup the kernel does say "Probing IDE interface ide0"
through "ide5" (finding only devices on ide0). I also tried compiling
pata_pdc2027x as a module, with same result.

What's wrong here?

Regards,

Oskar Liljeblad (oskar@osk.mine.nu)

RE: clock drift with two Promise Ultra133 TX2 (PDC 20269) cards

[Drew Winstel]

Hello,


>I'm running 2.6.11.8 on an server with two Promise Ultra133 TX2 (PDC20269)
>PCI cards, same hardware revision (judging from stickers on the cards).
>I'm using the CONFIG_BLK_DEV_PDC202XX_NEW driver.
>Each card has two connected hard drives. Whenever I read from a disk
>on one of the cards (e.g. using 'dd if=/dev/hdX of=/dev/null bs=1M'), and
>at the same time read from a disk on the other card, there is heavy
>software clock drift. It drifts about 2-5 seconds per minute.

>This does not happen if I read from two drives connected on the same
>card, or if I read from a drive connected to the motherboard IDE
>(VIA vt8233a) and a drive on either of the Promise cards.

>Oskar Liljeblad (oskar@osk.mine.nu)

Just to verify your setup:

You have a total of four hard drives connected to your PDC20269, hde, hdg, 
hdi, and hdk, correct?

Are all four drives running in DMA mode?

Please post the output of lspci -vv and hdparm run on each of the four hard 
drives.

Also, you may want to try downloading and using Albert Lee's pata_pdc2027x 
driver (part of libata-dev-2.6 tree).  See info at my thread from earlier:
http://marc.theaimsgroup.com/?l=linux-ide&m=110902518625384&w=2

Download the latest libata-dev patch set at 
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/

Hope this gets you started.

Drew

Re: clock drift with two Promise Ultra133 TX2 (PDC 20269) cards

[Oskar Liljeblad]

[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]

On Tuesday, May 03, 2005 at 09:58, Drew Winstel wrote:

Hi & Thanks for your quick reply!

> Just to verify your setup:
> 
> You have a total of four hard drives connected to your PDC20269, hde, hdg, 
> hdi, and hdk, correct?

Yes, two drives per physical PDC20269 card. 

> Are all four drives running in DMA mode?

Yes, all are running udma6. Here's what hdparm tells me for all drives
(only difference is serial number):

# hdparm /dev/hde

/dev/hde:
 multcount    =  0 (off)
 IO_support   =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 30515/255/63, sectors = 490234752, start = 0
# hdparm -i /dev/hde

/dev/hde:

 Model=Maxtor 6B250R0, FwRev=BAH41BM0, SerialNo=<...>
 Config={ Fixed }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
 BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=off
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
 AdvancedPM=yes: disabled (255) WriteCache=enabled
 Drive conforms to: (null): 

 * signifies the current active mode

#

> Please post the output of lspci -vv and hdparm run on each of the four hard 
> drives.

See attached file for lspci output.

> Also, you may want to try downloading and using Albert Lee's pata_pdc2027x 
> driver (part of libata-dev-2.6 tree).  See info at my thread from earlier:
> http://marc.theaimsgroup.com/?l=linux-ide&m=110902518625384&w=2

Interesting, I will try them out ASAP and return to you!
 
> Download the latest libata-dev patch set at 
> http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/
> 
> Hope this gets you started.

Thanks again!

Regards,

Oskar Liljeblad (oskar@osk.mine.nu)

[-- Attachment #2: lspci.out --]
[-- Type: text/plain, Size: 8312 bytes --]

0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
	Subsystem: Asustek Computer, Inc. A7V266-E Mainboard
	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 0: Memory at fc000000 (32-bit, prefetchable) [size=32M]
	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>
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] (prog-if 00 [Normal decode])
	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
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: fa000000-fadfffff
	Prefetchable memory behind bridge: faf00000-fbffffff
	BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:0c.0 Unknown mass storage controller: Promise Technology, Inc. 20269 (rev 02) (prog-if 85)
	Subsystem: Promise Technology, Inc. Ultra133TX2
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (1000ns min, 4500ns max), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 15
	Region 0: I/O ports at b800 [size=8]
	Region 1: I/O ports at b400 [size=4]
	Region 2: I/O ports at b000 [size=8]
	Region 3: I/O ports at a800 [size=4]
	Region 4: I/O ports at a400 [size=16]
	Region 5: Memory at f9800000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [60] Power Management version 1
		Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:0d.0 Unknown mass storage controller: Promise Technology, Inc. 20269 (rev 02) (prog-if 85)
	Subsystem: Promise Technology, Inc. Ultra133TX2
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (1000ns min, 4500ns max), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at a000 [size=8]
	Region 1: I/O ports at 9800 [size=4]
	Region 2: I/O ports at 9400 [size=8]
	Region 3: I/O ports at 9000 [size=4]
	Region 4: I/O ports at 8800 [size=16]
	Region 5: Memory at f9000000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [60] Power Management version 1
		Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:0e.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02)
	Subsystem: Intel Corp. PRO/1000 MT Desktop Adapter
	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 (63750ns min), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 10
	Region 0: Memory at f8800000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at f8000000 (32-bit, non-prefetchable) [size=128K]
	Region 2: I/O ports at 8400 [size=64]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [e4] PCI-X non-bridge device.
		Command: DPERE- ERO+ RBC=0 OST=0
		Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=2, DMOST=0, DMCRS=1, RSCEM-
	Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000

0000:00:0f.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller
	Subsystem: Netgear FA311 / FA312 (FA311 with WoL HW)
	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 (2750ns min, 13000ns max)
	Interrupt: pin A routed to IRQ 12
	Region 0: I/O ports at 8000 [size=256]
	Region 1: Memory at f7800000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [40] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=320mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME+

0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge
	Subsystem: Asustek Computer, Inc.: Unknown device 8052
	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
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
	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
	Interrupt: pin A routed to IRQ 11
	Region 4: I/O ports at 7800 [size=16]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23) (prog-if 00 [UHCI])
	Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
	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, Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin D routed to IRQ 15
	Region 4: I/O ports at 7400 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23) (prog-if 00 [UHCI])
	Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
	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, Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin D routed to IRQ 15
	Region 4: I/O ports at 7000 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP 1X/2X (rev 5c) (prog-if 00 [VGA])
	Subsystem: ATI Technologies Inc Rage Pro Turbo AGP 2X
	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 (2000ns min), Cache Line Size: 0x08 (32 bytes)
	Region 0: Memory at fb000000 (32-bit, prefetchable) [size=16M]
	Region 1: I/O ports at d800 [size=256]
	Region 2: Memory at fa000000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at fafe0000 [disabled] [size=128K]
	Capabilities: [50] AGP version 1.0
		Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2
		Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>

clock drift with two Promise Ultra133 TX2 (PDC 20269) cards

[Oskar Liljeblad]

I'm running 2.6.11.8 on an server with two Promise Ultra133 TX2 (PDC20269)
PCI cards, same hardware revision (judging from stickers on the cards).
I'm using the CONFIG_BLK_DEV_PDC202XX_NEW driver.
Each card has two connected hard drives. Whenever I read from a disk
on one of the cards (e.g. using 'dd if=/dev/hdX of=/dev/null bs=1M'), and
at the same time read from a disk on the other card, there is heavy
software clock drift. It drifts about 2-5 seconds per minute.

This does not happen if I read from two drives connected on the same
card, or if I read from a drive connected to the motherboard IDE
(VIA vt8233a) and a drive on either of the Promise cards.

Oskar Liljeblad (oskar@osk.mine.nu)