Bug 25338
| Summary: | HARD READ ERROR on IBM Hard Disks connected through Promise Ultra 66 Card | ||
|---|---|---|---|
| Product: | Base System | Reporter: | chenggl <chenggl> |
| Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
It seems chenggl@yahoo.com wrote: > Feb 1 19:19:59 sr20 /kernel: ad6: HARD READ ERROR blk# 63793760ata3-master: WARNING: WAIT_READY active=ATA_ACT > IVE_ATA > Feb 1 19:19:59 sr20 /kernel: ad6: DMA problem fallback to PIO mode > Feb 1 19:19:59 sr20 last message repeated 5 times > Feb 1 19:20:05 sr20 /kernel: ad6: HARD READ ERROR blk# 63793856 status=59 error=40 > Feb 1 19:20:05 sr20 /kernel: ad6: DMA problem fallback to PIO mode > Feb 1 19:20:05 sr20 /kernel: ccd0: error 5 on component 6 block 63793744 (ccd block 701731392) > > >How-To-Repeat: > 100% repeatable, every time I access a normal file on the ccd, the ad6 disk fails, DMA falls back to PIO, which leads to ccd fail. Have you tried swapping disks and controllers ? ie have you outruled that ad6 isn't broken, or that the controller is for that matter. Also some motherboards doesn't allow for busmastering in all pci slots etc etc ... > >Fix: > Don't know how to fix it. > > But I afraid that problem may be related with timing setting of Promise Ultra66 cards? Nope, I know from several semilar configs that it actually works. -Søren State Changed From-To: open->closed There are no outstanding problems with the promise controllers, but I would suggest you check your power, the DTLA's are picky about get that smoothly.. |
Every time when I try to read a file on my ccd stripped disk, it prompts: Feb 1 19:19:59 sr20 /kernel: ad6: HARD READ ERROR blk# 63793760ata3-master: WARNING: WAIT_READY active=ATA_ACT IVE_ATA Feb 1 19:19:59 sr20 /kernel: ad6: DMA problem fallback to PIO mode Feb 1 19:19:59 sr20 last message repeated 5 times Feb 1 19:20:05 sr20 /kernel: ad6: HARD READ ERROR blk# 63793856 status=59 error=40 Feb 1 19:20:05 sr20 /kernel: ad6: DMA problem fallback to PIO mode Feb 1 19:20:05 sr20 /kernel: ccd0: error 5 on component 6 block 63793744 (ccd block 701731392) Feb 1 19:20:10 sr20 /kernel: ad6: HARD READ ERROR blk# 63793856 status=59 error=40 Feb 1 19:20:10 sr20 /kernel: ccd0: error 5 on component 6 block 63793760 (ccd block 701731408) Feb 1 19:20:15 sr20 /kernel: ad6: HARD READ ERROR blk# 63793856 status=59 error=40 Feb 1 19:20:15 sr20 /kernel: ccd0: error 5 on component 6 block 63793776 (ccd block 701731424) Feb 1 19:20:21 sr20 /kernel: ad6: HARD READ ERROR blk# 63793856 status=59 error=40 Feb 1 19:20:21 sr20 /kernel: ccd0: error 5 on component 6 block 63793792 (ccd block 701731440) Feb 1 19:20:26 sr20 /kernel: ad6: HARD READ ERROR blk# 63793856 status=59 error=40 Feb 1 19:20:26 sr20 /kernel: ccd0: error 5 on component 6 block 63793808 (ccd block 701731456) Feb 1 19:20:32 sr20 /kernel: ad6: HARD READ ERROR blk# 63793856 status=59 error=40 Feb 1 19:20:32 sr20 /kernel: ccd0: error 5 on component 6 block 63793824 (ccd block 701731472) Feb 1 19:20:37 sr20 /kernel: ad6: HARD READ ERROR blk# 63793856 status=59 error=40 Feb 1 19:20:37 sr20 /kernel: ccd0: error 5 on component 6 block 63793840 (ccd block 701731488) Feb 1 19:20:42 sr20 /kernel: ad6: HARD READ ERROR blk# 63793856 status=59 error=40 Feb 1 19:20:42 sr20 /kernel: ccd0: error 5 on component 6 block 63793840 (ccd block 701731488) Fix: Don't know how to fix it. But I afraid that problem may be related with timing setting of Promise Ultra66 cards? How-To-Repeat: 100% repeatable, every time I access a normal file on the ccd, the ad6 disk fails, DMA falls back to PIO, which leads to ccd fail.