Re: PDC sata timeouts.

William Fletcher <[email protected]>
Newsgroups gmane.os.netbsd.help
Message-ID <[email protected]>
Have eliminated the motherboard and controller too.

Since I have two identical machines running with 80s working fine.
And I tried two identical motherboards, and two identical controllers,
with these drives.

So, I'm pretty sure it must be either the driver or the drives.

I could try the SATA on the board, but, the DMA stuff doesn't work
and it'll be quite slow, I'll only be able to get back to you in a few
hours about how that goes.

I did run dd if=/dev/zero of=/dev/wd2d and of=/dev/wd3d, both the drives
on the PDCSATA controller, I got no problems, will look into PC doctor.

I only seem to encounter problems with a RAID reconstruction to the second
drive. So, it only seems to happen when I read data from one drive and write
it to another in quick succession.

But you guys are the experts. Thank you in advance.

Dmesg follows:
NetBSD 3.1 (GENERIC) #0: Tue Oct 31 04:27:07 UTC 2006
        [email protected]:/home/builds/ab/netbsd-3-1-RELEASE/i386/20061030205
3Z-obj/home/builds/ab/netbsd-3-1-RELEASE/src/sys/arch/i386/compile/GENERIC
total memory = 1023 MB
avail memory = 993 MB
BIOS32 rev. 0 found at 0xf0010
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: AMD Unknown K7 (Athlon) (686-class), 2199.91 MHz, id 0x40ff2
cpu0: features 78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
cpu0: features 78bfbff<PGE,MCA,CMOV,PAT,PSE36,MPC,MMX>
cpu0: features 78bfbff<FXSR,SSE,SSE2>
cpu0: features2 2001<SSE3>
cpu0: "AMD Athlon(tm) 64 Processor 3500+"
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0
pchb0: VIA Technologies product 0x0351 (rev. 0x00)
pchb1 at pci0 dev 0 function 1
pchb1: VIA Technologies product 0x1351 (rev. 0x00)
pchb2 at pci0 dev 0 function 2
pchb2: VIA Technologies product 0x2351 (rev. 0x00)
pchb3: VIA Technologies product 0x3351 (rev. 0x00)
pchb4 at pci0 dev 0 function 4
pchb4: VIA Technologies product 0x4351 (rev. 0x00)
VIA Technologies product 0x5351 (interrupt system, interface 0x20) at pci0 dev 0
 function 5 not configured
pchb5 at pci0 dev 0 function 6
pchb5: VIA Technologies product 0x6238 (rev. 0x00)
pchb6 at pci0 dev 0 function 7
pchb6: VIA Technologies product 0x7351 (rev. 0x00)
ppb0 at pci0 dev 1 function 0: VIA Technologies product 0xb999 (rev. 0x00)
pci1 at ppb0 bus 1
pci1: no spaces enabled!
ppb1 at pci0 dev 2 function 0: VIA Technologies product 0xa238 (rev. 0x00)
pci2 at ppb1 bus 2
pci2: i/o space, memory space enabled, rd/line, wr/inv ok
vga1 at pci2 dev 0 function 0: ATI Technologies Radeon X300 Series (rev. 0x00)
wsdisplay0 at vga1 kbdmux 1
wsmux1: connecting to wsdisplay0
ATI Technologies Radeon X300 Series Secondary (miscellaneous display) at pci2 de
v 0 function 1 not configured
ppb2 at pci0 dev 3 function 0: VIA Technologies product 0xc238 (rev. 0x00)
pci3 at ppb2 bus 6
ppb3 at pci0 dev 3 function 1: VIA Technologies product 0xd238 (rev. 0x00)
pci4 at ppb3 bus 5
pci4: memory space enabled, rd/line, wr/inv ok
ppb4 at pci0 dev 3 function 2: VIA Technologies product 0xe238 (rev. 0x00)
pci5 at ppb4 bus 4
pci5: memory space enabled, rd/line, wr/inv ok
unknown vendor 0x1969 product 0x1048 (ethernet network, revision 0xb0) at pci5 d
ev 0 function 0 not configured
ppb5 at pci0 dev 3 function 3: VIA Technologies product 0xf238 (rev. 0x00)
pci6 at ppb5 bus 3
pci6: memory space enabled, rd/line, wr/inv ok
pciide0 at pci0 dev 15 function 0
pciide0: VIA Technologies product 0x0591 (rev. 0x80)
pciide0: bus-master DMA support present, but unused (no driver support)
pciide0: primary channel configured to native-PCI mode
pciide0: using irq 10 for native-PCI interrupt
atabus0 at pciide0 channel 0
pciide0: secondary channel configured to native-PCI mode
atabus1 at pciide0 channel 1
viaide0 at pci0 dev 15 function 1
viaide0: VIA Technologies unknown VIA ATA controller
viaide0: bus-master DMA support present
viaide0: primary channel interrupting at irq 14
atabus2 at viaide0 channel 0
viaide0: secondary channel configured to compatibility mode
viaide0: secondary channel interrupting at irq 15
atabus3 at viaide0 channel 1
pcib0 at pci0 dev 17 function 0
pcib0: VIA Technologies product 0x3337 (rev. 0x00)
pchb7 at pci0 dev 17 function 7
pchb7: VIA Technologies product 0x287e (rev. 0x00)
ppb6 at pci0 dev 19 function 0: VIA Technologies product 0x337b (rev. 0x00)
pci7 at ppb6 bus 8
pci7: no spaces enabled!
ppb7 at pci0 dev 19 function 1: VIA Technologies product 0x337a (rev. 0x00)
pci8 at ppb7 bus 7
pci8: i/o space, memory space enabled
pdcsata0 at pci8 dev 6 function 0
pdcsata0: Promise PDC20775 SATA300 controller (rev. 0x02)
pdcsata0: interrupting at irq 5
pdcsata0: bus-master DMA support present
atabus4 at pdcsata0 channel 0
atabus5 at pdcsata0 channel 1
atabus6 at pdcsata0 channel 2
rtk0: interrupting at irq 10
rtk0: Ethernet address 00:30:4f:53:f9:9a
ukphy0 at rtk0 phy 7: Generic IEEE 802.3u media interface
ukphy0: OUI 0x000000, model 0x0000, rev. 0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Realtek Semiconductor product 0x8339 (ethernet network, revision 0x10) at pci8 d
ev 8 function 0 not configured
rtk1 at pci8 dev 9 function 0: Realtek 8139 10/100BaseTX
rtk1: interrupting at irq 7
rtk1: Ethernet address 00:30:4f:53:f9:94
ukphy1 at rtk1 phy 7: Generic IEEE 802.3u media interface
ukphy1: OUI 0x000000, model 0x0000, rev. 0
ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pchb8 at pci0 dev 24 function 0
pchb8: Advanced Micro Devices AMD64 HyperTransport configuration (rev. 0x00)
pchb9 at pci0 dev 24 function 1
pchb9: Advanced Micro Devices AMD64 Address Map configuration (rev. 0x00)
pchb10 at pci0 dev 24 function 2
pchb10: Advanced Micro Devices AMD64 DRAM configuration (rev. 0x00)
pchb11 at pci0 dev 24 function 3
pchb11: Advanced Micro Devices AMD64 Miscellaneous configuration (rev. 0x00)
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com0: console
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0 mux 1
wskbd0: connecting to wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff: using exception 16
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
isapnp0: no ISA Plug 'n Play devices found
Kernelized RAIDframe activated
wd0 at atabus0 drive 0: <HDS728080PLA380>
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 78533 MB, 159560 cyl, 16 head, 63 sec, 512 bytes/sect x 160836480 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd1 at atabus1 drive 0: <ST3320620AS>
wd1: drive supports 16-sector PIO transfers, LBA48 addressing
wd1: 298 GB, 620181 cyl, 16 head, 63 sec, 512 bytes/sect x 625142448 sectors
atapibus0 at atabus2: 2 targets
cd0 at atapibus0 drive 1: <SAMSUNG CD-R/RW SW-252B, , R701> cdrom removable
cd0: 32-bit data port
cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
cd0(viaide0:0:1): using PIO mode 4, DMA mode 2 (using DMA)
wd2 at atabus4 drive 0: <ST3160211AS>
wd2: drive supports 16-sector PIO transfers, LBA48 addressing
wd2: 149 GB, 310101 cyl, 16 head, 63 sec, 512 bytes/sect x 312581808 sectors
wd2: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd2(pdcsata0:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
wd3 at atabus5 drive 0: <ST3160211AS>
wd3: drive supports 16-sector PIO transfers, LBA48 addressing
wd3: 149 GB, 310101 cyl, 16 head, 63 sec, 512 bytes/sect x 312581808 sectors
wd3: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd3(pdcsata0:1:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
raid0: RAID Level 1
raid0: Components: /dev/wd2a component1[**FAILED**]
raid0: Total Sectors: 312581632 (152627 MB)
boot device: raid0
root on raid0a dumps on raid0b
root file system type: ffs
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 3 added (80x25, vt100 emulation)

On Tue, Mar 20, 2007 at 11:29:43PM -0400, Brian A. Seklecki wrote:
> If you've eliminated the cable, then that leaves the drives, the
> controller/MB, and driver.
> 
> Try running PC-Doctor and doing a low-level sector scan for grown
> defects?
> 
> Send us your full dmesg(8)?  Try an intel SATA controller? 
> 
> ~BAS
> 
> On Wed, 2007-03-21 at 02:30 +0200, William Fletcher wrote:
> > Hi list,
> > 
> > I've been trying to build a raid(frame) onto two 160G Hitachi hard drives,
> > but always end up with "lost interrupt" messages.
> > 
> > I'm using the pdcsata driver, with a "Promise PDC20775 SATA300 controller".
> > 
> > The following are some of the messages displayed in the dmesg:
> > pdcsata0:0:0: device timeout, c_bcount=65536, c_skip0
> > wd2a: device timeout reading fsbn 26698048 of 26698048-26698175 (wd2 bn 26698111; cn 26486 tn 3 sn 34), retrying
> > pdcsata0:0:0: lost interrupt
> >         type: ata tc_bcount: 65536 tc_skip: 0
> > 
> > The machine in question is running NetBSD 3.1, with a fresh installation.
> > 
> > I've tried two identical motherboards, and two identical PDC20775 controllers,
> > different memory and different CPUs, Different SATA cables and different drives (300G).
> > 
> > I'm pretty sure the hardware isn't the problem.
> > 
> > This problem doesn't seem to occur on machines with only 80 gig hard drives,
> > it appears to be tied in with the bigger 160 gigs, since I have two machines
> > in production with 80 gig Hitachi drives and identical PDC20775 controllers,
> > I reconstructed the RAID on one to check, and used its motherboard with the
> > 160Gs to see if I was perhaps losing my mind.
> > 
> > Please help, the voices in my head are growing louder, I don't know how long
> > I can contain them anymore.
> > 
> > Thank you all very much in advance.
> > 
> -- 
> Brian A. Seklecki <[email protected]>
> Collaborative Fusion, Inc.
> 
> 
> 
> 
> IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited.  Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
> 
> 

-- 
Omina Solutions  | http://omina.co.za | (012) Ph. 664-2480 F. 664-2474
signature.asc (application/pgp-signature, 186 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (NetBSD)

iD8DBQFGAQjC0o1hk/SHCkoRAgmvAKCGuervU5FoQwQccHDb+cnWTB4jcgCeJI75
zhQkAQDtW4a0nf0gzb4/8mo=
=W0kf
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.