* libata and md issues with 2.9.1-rc1
@ 2004-08-24 17:24 Brad Campbell
2004-08-24 17:40 ` Jeff Garzik
2004-08-24 22:31 ` libata and md issues with 2.9.1-rc1 J. Ryan Earl
0 siblings, 2 replies; 8+ messages in thread
From: Brad Campbell @ 2004-08-24 17:24 UTC (permalink / raw)
To: linux-ide; +Cc: RAID Linux
Just a heads up. I'm experiencing "issues" with 2.6.9-rc1 that don't occur with 2.6.5.
I run a 10 disk raid-5 on 3xPromise SATA150 cards and a 2 disk raid-0 on the on-board VIA chipset.
The 10 disks are Maxtor Maxline-II SATA drives and the raid-0 is a pair of WD2000JB drives with
Addonics SATA->PATA converters.
I am not seeing any issues with the Promise/Maxtor combo at this stage, but I'm getting random
read/write errors with the VIA/WD combo that don't appear under 2.6.5 or DOS (I also use Spinrite to
check the disks when I get issues).
This only appears when the 2 drives are run in the raid-0.
Under 2.6.5 I ran a complete badlocks -n on both drives simultaneously, and repeated the same under
2.6.9-rc1 with no problems (7 hours for a complete run). I even ran 5 simultaneous badblocks runs on
host 1, 6, 9, 12 & 13 for about 30 minutes with no problems (except PCI bus saturation!)
After starting the raid I ran a complete badblocks -n on /dev/md1 under 2.6.5 with no problems.
Under 2.6.9-rc1 I get timeouts immediately I start badblocks -n (the -n is the key as I have to
write something to cause the problem)
Aug 24 18:55:03 srv kernel: raid0: looking at sdk1
Aug 24 18:55:03 srv kernel: raid0: comparing sdk1(195310080) with sdk1(195310080)
Aug 24 18:55:03 srv kernel: raid0: END
Aug 24 18:55:03 srv kernel: raid0: ==> UNIQUE
Aug 24 18:55:03 srv kernel: raid0: 1 zones
Aug 24 18:55:03 srv kernel: raid0: looking at sdl1
Aug 24 18:55:03 srv kernel: raid0: comparing sdl1(195358336) with sdk1(195310080)
Aug 24 18:55:03 srv kernel: raid0: NOT EQUAL
Aug 24 18:55:03 srv kernel: raid0: comparing sdl1(195358336) with sdl1(195358336)
Aug 24 18:55:03 srv kernel: raid0: END
Aug 24 18:55:03 srv kernel: raid0: ==> UNIQUE
Aug 24 18:55:03 srv kernel: raid0: 2 zones
Aug 24 18:55:03 srv kernel: raid0: FINAL 2 zones
Aug 24 18:55:03 srv kernel: raid0: zone 1
Aug 24 18:55:03 srv kernel: raid0: checking sdk1 ... nope.
Aug 24 18:55:03 srv kernel: raid0: checking sdl1 ... contained as device 0
Aug 24 18:55:03 srv kernel: (195358336) is smallest!.
Aug 24 18:55:03 srv kernel: raid0: zone->nb_dev: 1, size: 48256
Aug 24 18:55:03 srv kernel: raid0: current zone offset: 195358336
Aug 24 18:55:03 srv kernel: raid0: done.
Aug 24 18:55:03 srv kernel: raid0 : md_size is 390668416 blocks.
Aug 24 18:55:03 srv kernel: raid0 : conf->hash_spacing is 390620160 blocks.
Aug 24 18:55:03 srv kernel: raid0 : nb_zone is 2.
Aug 24 18:55:03 srv kernel: raid0 : Allocating 8 bytes for hash.
Aug 24 19:01:37 srv kernel: ata13: command 0x35 timeout, stat 0xd0 host_stat 0x0
Aug 24 19:01:37 srv kernel: ata13: status=0xd0 { Busy }
Aug 24 19:01:37 srv kernel: SCSI error : <12 0 0 0> return code = 0x8000002
Aug 24 19:01:37 srv kernel: FMK EOM ILI Current sdk: sense = 70 ef
Aug 24 19:01:37 srv kernel: ASC=28 ASCQ=c0
Aug 24 19:01:37 srv kernel: end_request: I/O error, dev sdk, sector 63
Aug 24 19:01:37 srv kernel: ATA: abnormal status 0xD0 on port 0x8807
Aug 24 19:01:37 srv last message repeated 2 times
Aug 24 19:02:07 srv kernel: ata13: command 0x35 timeout, stat 0xd0 host_stat 0x1
Aug 24 19:02:07 srv kernel: ata13: status=0xd0 { Busy }
Aug 24 19:02:07 srv kernel: SCSI error : <12 0 0 0> return code = 0x8000002
Aug 24 19:02:07 srv kernel: FMK EOM ILI Current sdk: sense = 70 ef
Aug 24 19:02:07 srv kernel: ASC=28 ASCQ=c0
Aug 24 19:02:07 srv kernel: end_request: I/O error, dev sdk, sector 71
Aug 24 19:02:07 srv kernel: ATA: abnormal status 0xD0 on port 0x8807
Aug 24 19:02:07 srv last message repeated 2 times
I'm not really even sure where to start here as it only occurs when the 2 drives are in a Raid-0 and
depending on what is going on with the system it can take a while to manifest. (Never more than a
hundred megs or so of data though)
Relevant boot log from 2.6.9-rc1 attached
Regards,
Brad (Certified libata torturer)
Aug 24 19:03:55 srv kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Aug 24 19:03:55 srv kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Aug 24 19:03:55 srv kernel: VP_IDE: IDE controller at PCI slot 0000:00:0f.1
Aug 24 19:03:55 srv kernel: VP_IDE: chipset revision 6
Aug 24 19:03:55 srv kernel: VP_IDE: not 100%% native mode: will probe irqs later
Aug 24 19:03:55 srv kernel: VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
Aug 24 19:03:55 srv kernel: ide0: BM-DMA at 0x6800-0x6807, BIOS settings: hda:DMA, hdb:pio
Aug 24 19:03:55 srv kernel: ide1: BM-DMA at 0x6808-0x680f, BIOS settings: hdc:pio, hdd:pio
Aug 24 19:03:55 srv kernel: hda: WDC WD400EB-00CPF0, ATA DISK drive
Aug 24 19:03:55 srv kernel: Using anticipatory io scheduler
Aug 24 19:03:55 srv kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Aug 24 19:03:55 srv kernel: hda: max request size: 128KiB
Aug 24 19:03:55 srv kernel: hda: Host Protected Area detected.
Aug 24 19:03:55 srv kernel: ^Icurrent capacity is 78159151 sectors (40017 MB)
Aug 24 19:03:55 srv kernel: ^Inative capacity is 78165360 sectors (40020 MB)
Aug 24 19:03:55 srv kernel: hda: 78159151 sectors (40017 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
Aug 24 19:03:55 srv kernel: /dev/ide/host0/bus0/target0/lun0: p1 p2 p3
Aug 24 19:03:55 srv kernel: libata version 1.02 loaded.
Aug 24 19:03:55 srv kernel: sata_promise version 0.91
Aug 24 19:03:55 srv kernel: ata1: SATA max UDMA/133 cmd 0xE080B200 ctl 0xE080B238 bmdma 0x0 irq 19
Aug 24 19:03:55 srv kernel: ata2: SATA max UDMA/133 cmd 0xE080B280 ctl 0xE080B2B8 bmdma 0x0 irq 19
Aug 24 19:03:55 srv kernel: ata3: SATA max UDMA/133 cmd 0xE080B300 ctl 0xE080B338 bmdma 0x0 irq 19
Aug 24 19:03:55 srv kernel: ata4: SATA max UDMA/133 cmd 0xE080B380 ctl 0xE080B3B8 bmdma 0x0 irq 19
Aug 24 19:03:55 srv kernel: ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003
88:407f
Aug 24 19:03:55 srv kernel: ata1: dev 0 ATA, max UDMA/133, 490234752 sectors (lba48)
Aug 24 19:03:55 srv kernel: ata1: dev 0 configured for UDMA/133
Aug 24 19:03:55 srv kernel: scsi0 : sata_promise
Aug 24 19:03:55 srv kernel: ata2: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003
88:407f
Aug 24 19:03:55 srv kernel: ata2: dev 0 ATA, max UDMA/133, 490234752 sectors (lba48)
Aug 24 19:03:55 srv kernel: ata2: dev 0 configured for UDMA/133
Aug 24 19:03:55 srv kernel: scsi1 : sata_promise
Aug 24 19:03:55 srv kernel: ata3: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003
88:407f
Aug 24 19:03:55 srv kernel: ata3: dev 0 ATA, max UDMA/133, 490234752 sectors (lba48)
Aug 24 19:03:55 srv kernel: ata3: dev 0 configured for UDMA/133
Aug 24 19:03:55 srv kernel: scsi2 : sata_promise
Aug 24 19:03:55 srv kernel: ata4: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003
88:407f
Aug 24 19:03:55 srv kernel: ata4: dev 0 ATA, max UDMA/133, 490234752 sectors (lba48)
Aug 24 19:03:55 srv kernel: ata4: dev 0 configured for UDMA/133
Aug 24 19:03:55 srv kernel: scsi3 : sata_promise
Aug 24 19:03:55 srv kernel: Vendor: ATA Model: Maxtor 7Y250M0 Rev: 1.02
Aug 24 19:03:55 srv kernel: Type: Direct-Access ANSI SCSI revision: 05
Aug 24 19:03:55 srv kernel: Vendor: ATA Model: Maxtor 7Y250M0 Rev: 1.02
Aug 24 19:03:55 srv kernel: Type: Direct-Access ANSI SCSI revision: 05
Aug 24 19:03:55 srv kernel: Vendor: ATA Model: Maxtor 7Y250M0 Rev: 1.02
Aug 24 19:03:55 srv kernel: Type: Direct-Access ANSI SCSI revision: 05
Aug 24 19:03:55 srv kernel: Vendor: ATA Model: Maxtor 7Y250M0 Rev: 1.02
Aug 24 19:03:55 srv kernel: Type: Direct-Access ANSI SCSI revision: 05
Aug 24 19:03:55 srv kernel: ata5: SATA max UDMA/133 cmd 0xE080D200 ctl 0xE080D238 bmdma 0x0 irq 17
Aug 24 19:03:55 srv kernel: ata6: SATA max UDMA/133 cmd 0xE080D280 ctl 0xE080D2B8 bmdma 0x0 irq 17
Aug 24 19:03:55 srv kernel: ata7: SATA max UDMA/133 cmd 0xE080D300 ctl 0xE080D338 bmdma 0x0 irq 17
Aug 24 19:03:55 srv kernel: ata8: SATA max UDMA/133 cmd 0xE080D380 ctl 0xE080D3B8 bmdma 0x0 irq 17
Aug 24 19:03:55 srv kernel: ata5: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003
88:407fAug 24 19:03:55 srv kernel: ata5: dev 0 ATA, max UDMA/133, 490234752 sectors (lba48)
Aug 24 19:03:55 srv kernel: ata5: dev 0 configured for UDMA/133
Aug 24 19:03:55 srv kernel: scsi4 : sata_promise
Aug 24 19:03:55 srv kernel: ata6: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003
88:407f
Aug 24 19:03:55 srv kernel: ata6: dev 0 ATA, max UDMA/133, 490234752 sectors (lba48)
Aug 24 19:03:55 srv kernel: ata6: dev 0 configured for UDMA/133
Aug 24 19:03:55 srv kernel: scsi5 : sata_promise
Aug 24 19:03:55 srv kernel: ata7: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003
88:407f
Aug 24 19:03:55 srv kernel: ata7: dev 0 ATA, max UDMA/133, 490234752 sectors (lba48)
Aug 24 19:03:55 srv kernel: ata7: dev 0 configured for UDMA/133
Aug 24 19:03:55 srv kernel: scsi6 : sata_promise
Aug 24 19:03:55 srv kernel: ata8: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003
88:407f
Aug 24 19:03:55 srv kernel: ata8: dev 0 ATA, max UDMA/133, 490234752 sectors (lba48)
Aug 24 19:03:55 srv kernel: ata8: dev 0 configured for UDMA/133
Aug 24 19:03:55 srv kernel: scsi7 : sata_promise
Aug 24 19:03:55 srv kernel: Vendor: ATA Model: Maxtor 7Y250M0 Rev: 1.02
Aug 24 19:03:55 srv kernel: Type: Direct-Access ANSI SCSI revision: 05
Aug 24 19:03:55 srv kernel: Vendor: ATA Model: Maxtor 7Y250M0 Rev: 1.02
Aug 24 19:03:55 srv kernel: Type: Direct-Access ANSI SCSI revision: 05
Aug 24 19:03:55 srv kernel: Vendor: ATA Model: Maxtor 7Y250M0 Rev: 1.02
Aug 24 19:03:55 srv kernel: Type: Direct-Access ANSI SCSI revision: 05
Aug 24 19:03:55 srv kernel: Vendor: ATA Model: Maxtor 7Y250M0 Rev: 1.02
Aug 24 19:03:55 srv kernel: Type: Direct-Access ANSI SCSI revision: 05
Aug 24 19:03:55 srv kernel: ata9: SATA max UDMA/133 cmd 0xE080F200 ctl 0xE080F238 bmdma 0x0 irq 18
Aug 24 19:03:55 srv kernel: ata10: SATA max UDMA/133 cmd 0xE080F280 ctl 0xE080F2B8 bmdma 0x0 irq 18
Aug 24 19:03:55 srv kernel: ata11: SATA max UDMA/133 cmd 0xE080F300 ctl 0xE080F338 bmdma 0x0 irq 18
Aug 24 19:03:55 srv kernel: ata12: SATA max UDMA/133 cmd 0xE080F380 ctl 0xE080F3B8 bmdma 0x0 irq 18
Aug 24 19:03:55 srv kernel: ata9: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003
88:407f
Aug 24 19:03:55 srv kernel: ata9: dev 0 ATA, max UDMA/133, 490234752 sectors (lba48)
Aug 24 19:03:55 srv kernel: ata9: dev 0 configured for UDMA/133
Aug 24 19:03:55 srv kernel: scsi8 : sata_promise
Aug 24 19:03:55 srv kernel: ata10: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003
88:407f
Aug 24 19:03:55 srv kernel: ata10: dev 0 ATA, max UDMA/133, 490234752 sectors (lba48)
Aug 24 19:03:55 srv kernel: ata10: dev 0 configured for UDMA/133
Aug 24 19:03:55 srv kernel: scsi9 : sata_promise
Aug 24 19:03:55 srv kernel: ata11: no device found (phy stat 00000000)
Aug 24 19:03:55 srv kernel: ata11: thread exiting
Aug 24 19:03:55 srv kernel: scsi10 : sata_promise
Aug 24 19:03:55 srv kernel: ata12: no device found (phy stat 00000000)
Aug 24 19:03:55 srv kernel: ata12: thread exiting
Aug 24 19:03:55 srv kernel: scsi11 : sata_promise
Aug 24 19:03:55 srv kernel: Vendor: ATA Model: Maxtor 7Y250M0 Rev: 1.02
Aug 24 19:03:55 srv kernel: Type: Direct-Access ANSI SCSI revision: 05
Aug 24 19:03:55 srv kernel: Vendor: ATA Model: Maxtor 7Y250M0 Rev: 1.02
Aug 24 19:03:55 srv kernel: Type: Direct-Access ANSI SCSI revision: 05
Aug 24 19:03:55 srv kernel: sata_via version 0.20
Aug 24 19:03:55 srv kernel: sata_via(0000:00:0f.0): routed to hard irq line 6
Aug 24 19:03:55 srv kernel: ata13: SATA max UDMA/133 cmd 0x8800 ctl 0x8402 bmdma 0x7400 irq 20
Aug 24 19:03:55 srv kernel: ata14: SATA max UDMA/133 cmd 0x8000 ctl 0x7802 bmdma 0x7408 irq 20
Aug 24 19:03:55 srv kernel: ata13: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3469 86:3c01 87:4003
88:203f
Aug 24 19:03:55 srv kernel: ata13: dev 0 ATA, max UDMA/100, 390622887 sectors (lba48)
Aug 24 19:03:55 srv kernel: ata13: dev 0 configured for UDMA/100
Aug 24 19:03:55 srv kernel: scsi12 : sata_via
Aug 24 19:03:55 srv kernel: ata14: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3469 86:3c01 87:4003
88:203f
Aug 24 19:03:55 srv kernel: ata14: dev 0 ATA, max UDMA/100, 390719855 sectors (lba48)
Aug 24 19:03:55 srv kernel: ata14: dev 0 configured for UDMA/100
Aug 24 19:03:55 srv kernel: scsi13 : sata_via
Aug 24 19:03:55 srv kernel: Vendor: ATA Model: WDC WD2000JB-00D Rev: 1.02
Aug 24 19:03:55 srv kernel: Type: Direct-Access ANSI SCSI revision: 05
Aug 24 19:03:55 srv kernel: Vendor: ATA Model: WDC WD2000JB-00F Rev: 1.02
Aug 24 19:03:55 srv kernel: Type: Direct-Access ANSI SCSI revision: 05
Aug 24 19:03:55 srv kernel: SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
Aug 24 19:03:55 srv kernel: SCSI device sda: drive cache: write through
Aug 24 19:03:55 srv kernel: /dev/scsi/host0/bus0/target0/lun0: p1
Aug 24 19:03:55 srv kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Aug 24 19:03:55 srv kernel: SCSI device sdb: 490234752 512-byte hdwr sectors (251000 MB)
Aug 24 19:03:55 srv kernel: SCSI device sdb: drive cache: write through
Aug 24 19:03:55 srv kernel: /dev/scsi/host1/bus0/target0/lun0: p1
Aug 24 19:03:55 srv kernel: Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Aug 24 19:03:55 srv kernel: SCSI device sdc: 490234752 512-byte hdwr sectors (251000 MB)
Aug 24 19:03:55 srv kernel: SCSI device sdc: drive cache: write through
Aug 24 19:03:55 srv kernel: /dev/scsi/host2/bus0/target0/lun0: p1
Aug 24 19:03:55 srv kernel: Attached scsi disk sdc at scsi2, channel 0, id 0, lun 0
Aug 24 19:03:55 srv kernel: SCSI device sdd: 490234752 512-byte hdwr sectors (251000 MB)
Aug 24 19:03:55 srv kernel: SCSI device sdd: drive cache: write through
Aug 24 19:03:55 srv kernel: /dev/scsi/host3/bus0/target0/lun0: p1
Aug 24 19:03:55 srv kernel: Attached scsi disk sdd at scsi3, channel 0, id 0, lun 0
Aug 24 19:03:55 srv kernel: SCSI device sde: 490234752 512-byte hdwr sectors (251000 MB)
Aug 24 19:03:55 srv kernel: SCSI device sde: drive cache: write through
Aug 24 19:03:55 srv kernel: /dev/scsi/host4/bus0/target0/lun0: p1
Aug 24 19:03:55 srv kernel: Attached scsi disk sde at scsi4, channel 0, id 0, lun 0
Aug 24 19:03:55 srv kernel: SCSI device sdf: 490234752 512-byte hdwr sectors (251000 MB)
Aug 24 19:03:55 srv kernel: SCSI device sdf: drive cache: write through
Aug 24 19:03:55 srv kernel: /dev/scsi/host5/bus0/target0/lun0: p1
Aug 24 19:03:55 srv kernel: Attached scsi disk sdf at scsi5, channel 0, id 0, lun 0
Aug 24 19:03:55 srv kernel: SCSI device sdg: 490234752 512-byte hdwr sectors (251000 MB)
Aug 24 19:03:55 srv kernel: SCSI device sdg: drive cache: write through
Aug 24 19:03:55 srv kernel: /dev/scsi/host6/bus0/target0/lun0: p1
Aug 24 19:03:55 srv kernel: Attached scsi disk sdg at scsi6, channel 0, id 0, lun 0
Aug 24 19:03:55 srv kernel: SCSI device sdh: 490234752 512-byte hdwr sectors (251000 MB)
Aug 24 19:03:55 srv kernel: SCSI device sdh: drive cache: write through
Aug 24 19:03:55 srv kernel: /dev/scsi/host7/bus0/target0/lun0: p1
Aug 24 19:03:55 srv kernel: Attached scsi disk sdh at scsi7, channel 0, id 0, lun 0
Aug 24 19:03:55 srv kernel: SCSI device sdi: 490234752 512-byte hdwr sectors (251000 MB)
Aug 24 19:03:55 srv kernel: SCSI device sdi: drive cache: write through
Aug 24 19:03:55 srv kernel: /dev/scsi/host8/bus0/target0/lun0: p1
Aug 24 19:03:55 srv kernel: Attached scsi disk sdi at scsi8, channel 0, id 0, lun 0
Aug 24 19:03:55 srv kernel: SCSI device sdj: 490234752 512-byte hdwr sectors (251000 MB)
Aug 24 19:03:55 srv kernel: SCSI device sdj: drive cache: write through
Aug 24 19:03:55 srv kernel: /dev/scsi/host9/bus0/target0/lun0: p1
Aug 24 19:03:55 srv kernel: Attached scsi disk sdj at scsi9, channel 0, id 0, lun 0
Aug 24 19:03:55 srv kernel: SCSI device sdk: 390622887 512-byte hdwr sectors (199999 MB)
Aug 24 19:03:55 srv kernel: SCSI device sdk: drive cache: write through
Aug 24 19:03:55 srv kernel: /dev/scsi/host12/bus0/target0/lun0: p1
Aug 24 19:03:55 srv kernel: Attached scsi disk sdk at scsi12, channel 0, id 0, lun 0
Aug 24 19:03:55 srv kernel: SCSI device sdl: 390719855 512-byte hdwr sectors (200049 MB)
Aug 24 19:03:55 srv kernel: SCSI device sdl: drive cache: write through
Aug 24 19:03:55 srv kernel: /dev/scsi/host13/bus0/target0/lun0: p1
Aug 24 19:03:55 srv kernel: Attached scsi disk sdl at scsi13, channel 0, id 0, lun 0
Aug 24 19:03:55 srv kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Aug 24 19:03:55 srv kernel: Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 0
Aug 24 19:03:55 srv kernel: Attached scsi generic sg2 at scsi2, channel 0, id 0, lun 0, type 0
Aug 24 19:03:55 srv kernel: Attached scsi generic sg3 at scsi3, channel 0, id 0, lun 0, type 0
Aug 24 19:03:55 srv kernel: Attached scsi generic sg4 at scsi4, channel 0, id 0, lun 0, type 0
Aug 24 19:03:55 srv kernel: Attached scsi generic sg5 at scsi5, channel 0, id 0, lun 0, type 0
Aug 24 19:03:55 srv kernel: Attached scsi generic sg6 at scsi6, channel 0, id 0, lun 0, type 0
Aug 24 19:03:55 srv kernel: Attached scsi generic sg7 at scsi7, channel 0, id 0, lun 0, type 0
Aug 24 19:03:55 srv kernel: Attached scsi generic sg8 at scsi8, channel 0, id 0, lun 0, type 0
Aug 24 19:03:55 srv kernel: Attached scsi generic sg9 at scsi9, channel 0, id 0, lun 0, type 0
Aug 24 19:03:55 srv kernel: Attached scsi generic sg10 at scsi12, channel 0, id 0, lun 0, type 0
Aug 24 19:03:55 srv kernel: Attached scsi generic sg11 at scsi13, channel 0, id 0, lun 0, type 0
Aug 24 19:03:55 srv kernel: mice: PS/2 mouse device common for all mice
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: libata and md issues with 2.9.1-rc1
2004-08-24 17:24 libata and md issues with 2.9.1-rc1 Brad Campbell
@ 2004-08-24 17:40 ` Jeff Garzik
2004-08-24 17:50 ` Brad Campbell
2004-08-24 18:41 ` libata and md issues with 2.6.9-rc1 Brad Campbell
2004-08-24 22:31 ` libata and md issues with 2.9.1-rc1 J. Ryan Earl
1 sibling, 2 replies; 8+ messages in thread
From: Jeff Garzik @ 2004-08-24 17:40 UTC (permalink / raw)
To: Brad Campbell; +Cc: linux-ide, RAID Linux
Is there a difference between 2.6.8.1 and 2.6.9-rc1?
Any chance we could narrow it down to a specific change?
Jeff
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: libata and md issues with 2.9.1-rc1
2004-08-24 17:40 ` Jeff Garzik
@ 2004-08-24 17:50 ` Brad Campbell
2004-08-24 18:41 ` libata and md issues with 2.6.9-rc1 Brad Campbell
1 sibling, 0 replies; 8+ messages in thread
From: Brad Campbell @ 2004-08-24 17:50 UTC (permalink / raw)
To: Jeff Garzik; +Cc: linux-ide, RAID Linux
Jeff Garzik wrote:
> Is there a difference between 2.6.8.1 and 2.6.9-rc1?
Oooh good point. I was using 2.6.8.1 but with yesterdays BK cset applied. I'll try a raw 2.6.8.1 now.
> Any chance we could narrow it down to a specific change?
I'm thinking about a binary search between 2.6.5 and 2.6.9-rc1. I'm just rebuilding the array at the
moment and restoring the backups I took this afternoon (Talk about timing!).
Then I'll slot another couple of disks in and try some regression testing.
At least it's easily reproducible.
It has given the error recovery patch a good workout though! :p)
I mainly posted it just as a warning to be careful when upgrading until I figure out what is causing
the issue.
I'll keep you posted.
Regards,
Brad
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: libata and md issues with 2.6.9-rc1
2004-08-24 17:40 ` Jeff Garzik
2004-08-24 17:50 ` Brad Campbell
@ 2004-08-24 18:41 ` Brad Campbell
1 sibling, 0 replies; 8+ messages in thread
From: Brad Campbell @ 2004-08-24 18:41 UTC (permalink / raw)
To: Jeff Garzik; +Cc: linux-ide, RAID Linux
Jeff Garzik wrote:
> Is there a difference between 2.6.8.1 and 2.6.9-rc1?
>
> Any chance we could narrow it down to a specific change?
2.6.6 -> 2.6.7-rc1 is the problem.
Going in search of finer grained change sets now.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: libata and md issues with 2.9.1-rc1
2004-08-24 17:24 libata and md issues with 2.9.1-rc1 Brad Campbell
2004-08-24 17:40 ` Jeff Garzik
@ 2004-08-24 22:31 ` J. Ryan Earl
2004-08-25 4:53 ` Brad Campbell
1 sibling, 1 reply; 8+ messages in thread
From: J. Ryan Earl @ 2004-08-24 22:31 UTC (permalink / raw)
To: Brad Campbell; +Cc: linux-ide, RAID Linux
Brad Campbell wrote:
> Just a heads up. I'm experiencing "issues" with 2.6.9-rc1 that don't
> occur with 2.6.5.
>
> I run a 10 disk raid-5 on 3xPromise SATA150 cards and a 2 disk raid-0
> on the on-board VIA chipset.
> The 10 disks are Maxtor Maxline-II SATA drives and the raid-0 is a
> pair of WD2000JB drives with
> Addonics SATA->PATA converters.
Did you try RAID-0 with the pair of Western Digital drives on the two
free Promise slots? If that fails similarly, it might not be a libata
issue.
-ryan
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: libata and md issues with 2.9.1-rc1
2004-08-24 22:31 ` libata and md issues with 2.9.1-rc1 J. Ryan Earl
@ 2004-08-25 4:53 ` Brad Campbell
2004-08-26 10:30 ` Brad Campbell
0 siblings, 1 reply; 8+ messages in thread
From: Brad Campbell @ 2004-08-25 4:53 UTC (permalink / raw)
To: J. Ryan Earl; +Cc: linux-ide, RAID Linux
J. Ryan Earl wrote:
> Brad Campbell wrote:
>
>> Just a heads up. I'm experiencing "issues" with 2.6.9-rc1 that don't
>> occur with 2.6.5.
>>
>> I run a 10 disk raid-5 on 3xPromise SATA150 cards and a 2 disk raid-0
>> on the on-board VIA chipset.
>> The 10 disks are Maxtor Maxline-II SATA drives and the raid-0 is a
>> pair of WD2000JB drives with
>> Addonics SATA->PATA converters.
>
>
> Did you try RAID-0 with the pair of Western Digital drives on the two
> free Promise slots? If that fails similarly, it might not be a libata
> issue.
I thought about it. Given the drives are giving write errors when I write to /dev/md1 and not giving
write errors when the raid is stopped and I write to the individual disks then it *must* be some
issue with the hardware drivers.
If the block layer can submit a block to the driver that causes the drive to error out, then it's
really a fault of the driver for trying to do something illegal.
Anyway, I have done a clone of the libata-2.6 bk tree and I'm trying to figure out how to extract
all the individual csets between 2.6.6 and 2.6.7-rc1 so I can back them out 1 by 1 and see what
caused the problem.
My other tack is to enable full SCSI debugging and compare the trace from 2.6.5 and 2.6.7-rc1 to see
what is different.
I will give your suggestion a try when I get home tonight and fire it up on the extra promise channels.
Can anyone point me to a dummys guide to regression testing with BK? I read a great one by the WINE
guys years ago on regression testing by date with CVS and it has proved immensely helpful over the
years.
Regards,
Brad
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: libata and md issues with 2.9.1-rc1
2004-08-25 4:53 ` Brad Campbell
@ 2004-08-26 10:30 ` Brad Campbell
2004-08-26 12:21 ` libata and md issues with 2.9.1-rc1 - id10t error Brad Campbell
0 siblings, 1 reply; 8+ messages in thread
From: Brad Campbell @ 2004-08-26 10:30 UTC (permalink / raw)
To: linux-ide; +Cc: J. Ryan Earl, Jeff Garzik
Brad Campbell wrote:
> J. Ryan Earl wrote:
>
>> Brad Campbell wrote:
>>
>>> Just a heads up. I'm experiencing "issues" with 2.6.9-rc1 that don't
>>> occur with 2.6.5.
>>>
>>> I run a 10 disk raid-5 on 3xPromise SATA150 cards and a 2 disk raid-0
>>> on the on-board VIA chipset.
>>> The 10 disks are Maxtor Maxline-II SATA drives and the raid-0 is a
>>> pair of WD2000JB drives with
>>> Addonics SATA->PATA converters.
>>
>>
>>
>> Did you try RAID-0 with the pair of Western Digital drives on the two
>> free Promise slots? If that fails similarly, it might not be a libata
>> issue.
>
Worse. It won't even boot!
Jeff, it looks like the same issue I was facing with 2.6.6-pre1 with regards to the taskfile
submission. It just hangs when the kernel tries to access the drive.
On the via interface it does not hang until I try and write to the drive but only in an md
configuration, reads are ok. On the promise interface it hangs here during the boot sequence.
I'm going to try and get into the code somewhat deeper, but any insight you could provide on where
to poke would be much appreciated.
This is obviously not happening with my native SATA drives, but only with the WD drives via the
PATA->SATA converter. SIL3611CT80 chipset.
I'm removing linux-raid from the cc: as it's most certainly not a raid issue.
VP_IDE: IDE controller at PCI slot 0000:00:0f.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
ide0: BM-DMA at 0x6800-0x6807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x6808-0x680f, BIOS settings: hdc:pio, hdd:pio
hda: WDC WD400EB-00CPF0, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: Host Protected Area detected.
current capacity is 78159151 sectors (40017 MB)
native capacity is 78165360 sectors (40020 MB)
hda: 78159151 sectors (40017 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
/dev/ide/host0/bus0/target0/lun0: p1 p2 p3
ata1: SATA max UDMA/133 cmd 0xE080B200 ctl 0xE080B238 bmdma 0x0 irq 19
ata2: SATA max UDMA/133 cmd 0xE080B280 ctl 0xE080B2B8 bmdma 0x0 irq 19
ata3: SATA max UDMA/133 cmd 0xE080B300 ctl 0xE080B338 bmdma 0x0 irq 19
ata4: SATA max UDMA/133 cmd 0xE080B380 ctl 0xE080B3B8 bmdma 0x0 irq 19
ata1: no device found (phy stat 00000000)
scsi0 : sata_promise
ata2: no device found (phy stat 00000000)
scsi1 : sata_promise
ata3: no device found (phy stat 00000000)
scsi2 : sata_promise
ata4: no device found (phy stat 00000000)
scsi3 : sata_promise
ata5: SATA max UDMA/133 cmd 0xE080D200 ctl 0xE080D238 bmdma 0x0 irq 17
ata6: SATA max UDMA/133 cmd 0xE080D280 ctl 0xE080D2B8 bmdma 0x0 irq 17
ata7: SATA max UDMA/133 cmd 0xE080D300 ctl 0xE080D338 bmdma 0x0 irq 17
ata8: SATA max UDMA/133 cmd 0xE080D380 ctl 0xE080D3B8 bmdma 0x0 irq 17
ata5: no device found (phy stat 00000000)
scsi4 : sata_promise
ata6: no device found (phy stat 00000000)
scsi5 : sata_promise
ata7: no device found (phy stat 00000000)
scsi6 : sata_promise
ata8: no device found (phy stat 00000000)
scsi7 : sata_promise
ata9: SATA max UDMA/133 cmd 0xE080F200 ctl 0xE080F238 bmdma 0x0 irq 18
ata10: SATA max UDMA/133 cmd 0xE080F280 ctl 0xE080F2B8 bmdma 0x0 irq 18
ata11: SATA max UDMA/133 cmd 0xE080F300 ctl 0xE080F338 bmdma 0x0 irq 18
ata12: SATA max UDMA/133 cmd 0xE080F380 ctl 0xE080F3B8 bmdma 0x0 irq 18
ata9: no device found (phy stat 00000000)
scsi8 : sata_promise
ata10: no device found (phy stat 00000000)
scsi9 : sata_promise
ata11: dev 0 ATA, max UDMA/100, 390622887 sectors: lba48
ata11: dev 0 configured for UDMA/100
scsi10 : sata_promise
ata12: dev 0 ATA, max UDMA/100, 390719855 sectors: lba48
ata12: dev 0 configured for UDMA/100
scsi11 : sata_promise
Vendor: ATA Model: WDC WD2000JB-00D Rev: 02.1
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: WDC WD2000JB-00F Rev: 15.0
Type: Direct-Access ANSI SCSI revision: 05
sata_via(0000:00:0f.0): routed to hard irq line 6
ata13: SATA max UDMA/133 cmd 0x8800 ctl 0x8402 bmdma 0x7400 irq 20
ata14: SATA max UDMA/133 cmd 0x8000 ctl 0x7802 bmdma 0x7408 irq 20
ata13: no device found (phy stat 00000000)
scsi12 : sata_via
ata14: no device found (phy stat 00000000)
scsi13 : sata_via
SCSI device sda: 390622887 512-byte hdwr sectors (199999 MB)
SCSI device sda: drive cache: write back
/dev/scsi/host10/bus0/target0/lun0:<3>ata11: DMA timeout
If I remove the 1st 2 promise cards then it boots fine and I can write to /dev/md1 to my hearts
content if the drives are on the promise controller.
If I remove all the promise controllers from the machine, I can still reproduce the fault on the via
controller by itself so I do have an issue there.
I'm going out now to buy 2 new Maxtor-Maxline-II SATA drives to experiment with.
ARGH!
Here is the serial log
I logged in on the local console and ran
mdadm --assemble /dev/md1 /dev/sda /dev/sdb
dd if=/dev/zero | pipebench | dd of=/dev/md1
At about 50MB (Where it starts to try and flush to the disk) it does this
srv login: md: md1 stopped.
md: bind<sdb>
md: bind<sda>
md1: setting max_sectors to 8192, segment boundary to 2097151
raid0: looking at sda
raid0: comparing sda(195309568) with sda(195309568)
raid0: END
raid0: ==> UNIQUE
raid0: 1 zones
raid0: looking at sdb
raid0: comparing sdb(195358720) with sda(195309568)
raid0: NOT EQUAL
raid0: comparing sdb(195358720) with sdb(195358720)
raid0: END
raid0: ==> UNIQUE
raid0: 2 zones
raid0: FINAL 2 zones
raid0: zone 1
raid0: checking sda ... nope.
raid0: checking sdb ... contained as device 0
(195358720) is smallest!.
raid0: zone->nb_dev: 1, size: 49152
raid0: current zone offset: 195358720
raid0: done.
raid0 : md_size is 390668288 blocks.
raid0 : conf->hash_spacing is 390619136 blocks.
raid0 : nb_zone is 2.
raid0 : Allocating 8 bytes for hash.
ata1: DMA timeout, stat 0x0
ATA: abnormal status 0xD0 on port 0xA807
scsi0: ERROR on channel 0, id 0, lun 0, CDB: Write (10) 00 00 00 00 00 00 04 00 00
Current sda: sense key Medium Error
Additional sense: Write error - auto reallocation failed
end_request: I/O error, dev sda, sector 0
ATA: abnormal status 0xD0 on port 0xA807
ATA: abnormal status 0xD0 on port 0xA807
ATA: abnormal status 0xD0 on port 0xA807
Here is the relevant part of this boot log. System has been stripped of all promise controllers
VP_IDE: IDE controller at PCI slot 0000:00:0f.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
ide0: BM-DMA at 0x8800-0x8807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x8808-0x880f, BIOS settings: hdc:pio, hdd:pio
hda: WDC WD400EB-00CPF0, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: Host Protected Area detected.
current capacity is 78159151 sectors (40017 MB)
native capacity is 78165360 sectors (40020 MB)
hda: 78159151 sectors (40017 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
/dev/ide/host0/bus0/target0/lun0: p1 p2 p3
sata_via(0000:00:0f.0): routed to hard irq line 5
ata1: SATA max UDMA/133 cmd 0xA800 ctl 0xA402 bmdma 0x9400 irq 20
ata2: SATA max UDMA/133 cmd 0xA000 ctl 0x9802 bmdma 0x9408 irq 20
ata1: dev 0 ATA, max UDMA/100, 390622887 sectors: lba48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_via
ata2: dev 0 ATA, max UDMA/100, 390719855 sectors: lba48
ata2: dev 0 configured for UDMA/100
scsi1 : sata_via
Vendor: ATA Model: WDC WD2000JB-00D Rev: 02.1
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: WDC WD2000JB-00F Rev: 15.0
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 390622887 512-byte hdwr sectors (199999 MB)
SCSI device sda: drive cache: write back
/dev/scsi/host0/bus0/target0/lun0: unknown partition table
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 390719855 512-byte hdwr sectors (200049 MB)
SCSI device sdb: drive cache: write back
/dev/scsi/host1/bus0/target0/lun0: unknown partition table
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 0
mice: PS/2 mouse device common for all mice
Of course, on anything earlier than 2.6.7-rc1 none of this happens and it all works swimmingly!
Regards,
Brad
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: libata and md issues with 2.9.1-rc1 - id10t error
2004-08-26 10:30 ` Brad Campbell
@ 2004-08-26 12:21 ` Brad Campbell
0 siblings, 0 replies; 8+ messages in thread
From: Brad Campbell @ 2004-08-26 12:21 UTC (permalink / raw)
To: linux-ide; +Cc: J. Ryan Earl, Jeff Garzik
Brad Campbell wrote:
> Brad Campbell wrote:
>
>> J. Ryan Earl wrote:
>>
>>> Brad Campbell wrote:
>>>
>>>> Just a heads up. I'm experiencing "issues" with 2.6.9-rc1 that don't
>>>> occur with 2.6.5.
>>>>
>>>> I run a 10 disk raid-5 on 3xPromise SATA150 cards and a 2 disk
>>>> raid-0 on the on-board VIA chipset.
>>>> The 10 disks are Maxtor Maxline-II SATA drives and the raid-0 is a
>>>> pair of WD2000JB drives with
>>>> Addonics SATA->PATA converters.
>>>
>>>
>>>
>>>
>>> Did you try RAID-0 with the pair of Western Digital drives on the two
>>> free Promise slots? If that fails similarly, it might not be a
>>> libata issue.
>>
>>
>
> Worse. It won't even boot!
>
> Of course, on anything earlier than 2.6.7-rc1 none of this happens and
> it all works swimmingly!
Ignore the retard people.. move along.. nothing to see here..
I was tesing with 2.6.7-rc1 <ack>
Now repeat after me, I will check my uname -a before I e-mail, I will check my uname -a before I email!
With 2.6.9-rc1 there are no issues with the promise driver, there are issues still with the sata_via
driver.
I'll keep poking at the via driver.
Here is a full debug log of the error occuring (on the via interface, on a 2.6.9-rc1 kernel with a
WD ATA drive via the PATA->SATA bridge)
pdc_interrupt: ENTER
pdc_interrupt: QUICK EXIT 3
pdc_interrupt: ENTER
pdc_interrupt: QUICK EXIT 3
ata_scsi_dump_cdb: CDB (13:0,0,0) 2a 00 00 00 05 40 00 04 00
ata_scsi_translate: ENTER
ata_scsi_rw_xlat: ten-byte command
ata_sg_setup: ENTER, ata13
ata_sg_setup: 128 sg elements mapped
ata_fill_sg: PRD[0] = (0x1CA09000, 0x1000)
ata_fill_sg: PRD[1] = (0x1CA0C000, 0x1000)
ata_fill_sg: PRD[2] = (0x1CA0B000, 0x1000)
ata_fill_sg: PRD[3] = (0x1CA0D000, 0x1000)
ata_fill_sg: PRD[4] = (0x1C9E6000, 0x1000)
ata_fill_sg: PRD[5] = (0x1CA13000, 0x1000)
ata_fill_sg: PRD[6] = (0x1CA14000, 0x1000)
ata_fill_sg: PRD[7] = (0x1CA15000, 0x1000)
ata_fill_sg: PRD[8] = (0x1CA19000, 0x1000)
ata_fill_sg: PRD[9] = (0x1CA1A000, 0x1000)
ata_fill_sg: PRD[10] = (0x1CA27000, 0x1000)
ata_fill_sg: PRD[11] = (0x1CA28000, 0x1000)
ata_fill_sg: PRD[12] = (0x1CA29000, 0x1000)
ata_fill_sg: PRD[13] = (0x1CA2A000, 0x1000)
ata_fill_sg: PRD[14] = (0x1CA2B000, 0x1000)
ata_fill_sg: PRD[15] = (0x1CA2E000, 0x1000)
ata_fill_sg: PRD[16] = (0x1CA2F000, 0x1000)
ata_fill_sg: PRD[17] = (0x1CA30000, 0x1000)
ata_fill_sg: PRD[18] = (0x1CA33000, 0x1000)
ata_fill_sg: PRD[19] = (0x1CA34000, 0x1000)
ata_fill_sg: PRD[20] = (0x1CA38000, 0x1000)
ata_fill_sg: PRD[21] = (0x1CA39000, 0x1000)
ata_fill_sg: PRD[22] = (0x1CA3B000, 0x1000)
ata_fill_sg: PRD[23] = (0x1CA3D000, 0x1000)
ata_fill_sg: PRD[24] = (0x1CA3E000, 0x1000)
ata_fill_sg: PRD[25] = (0x1CA3F000, 0x1000)
ata_fill_sg: PRD[26] = (0x1CA42000, 0x1000)
ata_fill_sg: PRD[27] = (0x1CA43000, 0x1000)
ata_fill_sg: PRD[28] = (0x1CA44000, 0x1000)
ata_fill_sg: PRD[29] = (0x1CA45000, 0x1000)
ata_fill_sg: PRD[30] = (0x1CA48000, 0x1000)
ata_fill_sg: PRD[31] = (0x1CA4F000, 0x1000)
ata_fill_sg: PRD[32] = (0x1CA50000, 0x1000)
ata_fill_sg: PRD[33] = (0x1C9D9000, 0x1000)
ata_fill_sg: PRD[34] = (0x1C9DD000, 0x1000)
ata_fill_sg: PRD[35] = (0x1C952000, 0x1000)
ata_fill_sg: PRD[36] = (0x1CA12000, 0x1000)
ata_fill_sg: PRD[37] = (0x1CA11000, 0x1000)
ata_fill_sg: PRD[38] = (0x1CA0E000, 0x1000)
ata_fill_sg: PRD[39] = (0x1CA0F000, 0x1000)
ata_fill_sg: PRD[40] = (0x1CA52000, 0x1000)
ata_fill_sg: PRD[41] = (0x1CA55000, 0x1000)
ata_fill_sg: PRD[42] = (0x1CA56000, 0x1000)
ata_fill_sg: PRD[43] = (0x1CA58000, 0x1000)
ata_fill_sg: PRD[44] = (0x1CA5A000, 0x1000)
ata_fill_sg: PRD[45] = (0x1CA5F000, 0x1000)
ata_fill_sg: PRD[46] = (0x1CA60000, 0x1000)
ata_fill_sg: PRD[47] = (0x1CA61000, 0x1000)
ata_fill_sg: PRD[48] = (0x1CA63000, 0x1000)
ata_fill_sg: PRD[49] = (0x1CA65000, 0x1000)
ata_fill_sg: PRD[50] = (0x1CA66000, 0x1000)
ata_fill_sg: PRD[51] = (0x1CA67000, 0x1000)
ata_fill_sg: PRD[52] = (0x1CA6A000, 0x1000)
ata_fill_sg: PRD[53] = (0x1CA6B000, 0x1000)
ata_fill_sg: PRD[54] = (0x1CA6C000, 0x1000)
ata_fill_sg: PRD[55] = (0x1E881000, 0x1000)
ata_fill_sg: PRD[56] = (0x1CA6E000, 0x1000)
ata_fill_sg: PRD[57] = (0x1CA6F000, 0x1000)
ata_fill_sg: PRD[58] = (0x1CA70000, 0x1000)
ata_fill_sg: PRD[59] = (0x1CA72000, 0x1000)
ata_fill_sg: PRD[60] = (0x1CA74000, 0x1000)
ata_fill_sg: PRD[61] = (0x1CA75000, 0x1000)
ata_fill_sg: PRD[62] = (0x1CA77000, 0x1000)
ata_fill_sg: PRD[63] = (0x1CA79000, 0x1000)
ata_fill_sg: PRD[64] = (0x1CACA000, 0x1000)
ata_fill_sg: PRD[65] = (0x1CAE6000, 0x1000)
ata_fill_sg: PRD[66] = (0x1CAA9000, 0x1000)
ata_fill_sg: PRD[67] = (0x1CAA8000, 0x1000)
ata_fill_sg: PRD[68] = (0x1CAF7000, 0x1000)
ata_fill_sg: PRD[69] = (0x1CAF8000, 0x1000)
ata_fill_sg: PRD[70] = (0x1CAF9000, 0x1000)
ata_fill_sg: PRD[71] = (0x1CB68000, 0x1000)
ata_fill_sg: PRD[72] = (0x1CB6B000, 0x1000)
ata_fill_sg: PRD[73] = (0x1CB6C000, 0x1000)
ata_fill_sg: PRD[74] = (0x1CB6D000, 0x1000)
ata_fill_sg: PRD[75] = (0x1FB1B000, 0x1000)
ata_fill_sg: PRD[76] = (0x1CB6E000, 0x1000)
ata_fill_sg: PRD[77] = (0x1CB79000, 0x1000)
ata_fill_sg: PRD[78] = (0x1CB7A000, 0x1000)
ata_fill_sg: PRD[79] = (0x1CB7B000, 0x1000)
ata_fill_sg: PRD[80] = (0x1CB7D000, 0x1000)
ata_fill_sg: PRD[81] = (0x1CB7F000, 0x1000)
ata_fill_sg: PRD[82] = (0x1CB80000, 0x1000)
ata_fill_sg: PRD[83] = (0x1CB81000, 0x1000)
ata_fill_sg: PRD[84] = (0x1CB84000, 0x1000)
ata_fill_sg: PRD[85] = (0x1CB85000, 0x1000)
ata_fill_sg: PRD[86] = (0x1F91F000, 0x1000)
ata_fill_sg: PRD[87] = (0x1CB86000, 0x1000)
ata_fill_sg: PRD[88] = (0x1CB89000, 0x1000)
ata_fill_sg: PRD[89] = (0x1CB8A000, 0x1000)
ata_fill_sg: PRD[90] = (0x1CB8B000, 0x1000)
ata_fill_sg: PRD[91] = (0x1CB8D000, 0x1000)
ata_fill_sg: PRD[92] = (0x1CB8F000, 0x1000)
ata_fill_sg: PRD[93] = (0x1CB90000, 0x1000)
ata_fill_sg: PRD[94] = (0x1CB91000, 0x1000)
ata_fill_sg: PRD[95] = (0x1CB93000, 0x1000)
ata_fill_sg: PRD[96] = (0x1CB95000, 0x1000)
ata_fill_sg: PRD[97] = (0x1CB51000, 0x1000)
ata_fill_sg: PRD[98] = (0x1CB96000, 0x1000)
ata_fill_sg: PRD[99] = (0x1CB99000, 0x1000)
ata_fill_sg: PRD[100] = (0x1CB9A000, 0x1000)
ata_fill_sg: PRD[101] = (0x1CB9B000, 0x1000)
ata_fill_sg: PRD[102] = (0x1CB9C000, 0x1000)
ata_fill_sg: PRD[103] = (0x1CB9F000, 0x1000)
ata_fill_sg: PRD[104] = (0x1CBA2000, 0x1000)
ata_fill_sg: PRD[105] = (0x1CBA5000, 0x1000)
ata_fill_sg: PRD[106] = (0x1CBA7000, 0x1000)
ata_fill_sg: PRD[107] = (0x1CBA9000, 0x1000)
ata_fill_sg: PRD[108] = (0x1CBAA000, 0x1000)
ata_fill_sg: PRD[109] = (0x1CBAB000, 0x1000)
ata_fill_sg: PRD[110] = (0x1CBAD000, 0x1000)
ata_fill_sg: PRD[111] = (0x1CBAF000, 0x1000)
ata_fill_sg: PRD[112] = (0x1CBB0000, 0x1000)
ata_fill_sg: PRD[113] = (0x1CBB1000, 0x1000)
ata_fill_sg: PRD[114] = (0x1CBB5000, 0x1000)
ata_fill_sg: PRD[115] = (0x1CBB6000, 0x1000)
ata_fill_sg: PRD[116] = (0x1CBB7000, 0x1000)
ata_fill_sg: PRD[117] = (0x1CBB8000, 0x1000)
ata_fill_sg: PRD[118] = (0x1CBBB000, 0x1000)
ata_fill_sg: PRD[119] = (0x1CBBC000, 0x1000)
ata_fill_sg: PRD[120] = (0x1CBBD000, 0x1000)
ata_fill_sg: PRD[121] = (0x1CBBF000, 0x1000)
ata_fill_sg: PRD[122] = (0x1CBC1000, 0x1000)
ata_fill_sg: PRD[123] = (0x1CB41000, 0x1000)
ata_fill_sg: PRD[124] = (0x1CB43000, 0x1000)
ata_fill_sg: PRD[125] = (0x1CB42000, 0x1000)
ata_fill_sg: PRD[126] = (0x1CB4E000, 0x1000)
ata_fill_sg: PRD[127] = (0x1CB46000, 0x1000)
ata_dev_select: ENTER, ata13: device 0, wait 1
ata_tf_load_pio: hob: feat 0x0 nsect 0x4, lba 0x0 0x0 0x0
ata_tf_load_pio: feat 0x0 nsect 0x0 lba 0x40 0x5 0x0
ata_tf_load_pio: device 0xE0
ata_exec_command_pio: ata13: cmd 0x35
ata_scsi_translate: EXIT
pdc_interrupt: ENTER
pdc_interrupt: QUICK EXIT 3
pdc_interrupt: ENTER
pdc_interrupt: QUICK EXIT 3
pdc_interrupt: ENTER
pdc_interrupt: QUICK EXIT 3
<30 seconds of these snipped>
pdc_interrupt: ENTER
pdc_interrupt: QUICK EXIT 3
ata_scsi_error: ENTER
ata_eng_timeout: ENTER
ata_qc_timeout: ENTER
ata13: command 0x35 timeout, stat 0xd0 host_stat 0x0
ata_sg_clean: unmapping 128 sg elements
ata13: status=0xd0 { Busy }
SCSI error : <12 0 0 0> return code = 0x8000002
FMK EOM ILI Current sda: sense = 70 f7
ASC=28 ASCQ=c0
end_request: I/O error, dev sda, sector 1344
Buffer I/O error on device md1, logical block 168
lost page write due to I/O error on md1
ata_qc_complete: EXIT
ata_qc_timeout: EXIT
ata_eng_timeout: EXIT
ata_scsi_error: EXIT
ata_scsi_dump_cdb: CDB (13:0,0,0) 2a 00 00 00 05 48 00 03 f8
ata_scsi_translate: ENTER
ata_scsi_rw_xlat: ten-byte command
ata_sg_setup: ENTER, ata13
ata_sg_setup: 127 sg elements mapped
So, in summary. There is an issue with these WD drives using PATA->SATA bridges on the on-board VIA
controller. It does not exhibit this behaviour with Genuine Maxtor SATA drives and it does not
exhibit this behaviour on 2.6.5. It also makes no difference as to debugging being turned on or off
(console messages slowing things down a lot)
0000:00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
Off to do some more poking.
Regards,
Brad
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2004-08-26 12:21 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-08-24 17:24 libata and md issues with 2.9.1-rc1 Brad Campbell
2004-08-24 17:40 ` Jeff Garzik
2004-08-24 17:50 ` Brad Campbell
2004-08-24 18:41 ` libata and md issues with 2.6.9-rc1 Brad Campbell
2004-08-24 22:31 ` libata and md issues with 2.9.1-rc1 J. Ryan Earl
2004-08-25 4:53 ` Brad Campbell
2004-08-26 10:30 ` Brad Campbell
2004-08-26 12:21 ` libata and md issues with 2.9.1-rc1 - id10t error Brad Campbell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).