Re: limiting to UDMA/33 instead of UDMA/100 - pata_pdc202xx_old (also XFS error)?

On Fri, 07 Sep 2007 19:47:02 -0400
Jeff Garzik <[email protected]> wrote:

> >>         res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
> >>         res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
> >>         res 51/84:00:21:9d:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
> 
> 
> ATA bus error == straight-from-hardware reported error
> 
> Cable or connector is dying maybe?  Bad power supplies also sometimes 
> manifest this way.

With PATA some kind of misclocking can occassionally produce similar
results so its worth a bit of driver debug as well - especially if
forcing the speed down a little helps.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • limiting to UDMA/33 instead of UDMA/100 - pata_pdc202xx_old (also XFS error)?
    • From: "n" <[email protected]>
  • Re: limiting to UDMA/33 instead of UDMA/100 - pata_pdc202xx_old (also XFS error)?
    • From: David Chinner <[email protected]>
  • Re: limiting to UDMA/33 instead of UDMA/100 - pata_pdc202xx_old (also XFS error)?
    • From: Jeff Garzik <[email protected]>

• Prev by Date: Re: sata & scsi suggestion for make menuconfig
• Next by Date: Re: sysfs change of input/event devices in 2.6.23rc breaks udev
• Previous by thread: Re: limiting to UDMA/33 instead of UDMA/100 - pata_pdc202xx_old (also XFS error)?
• Next by thread: ethernet driver: hard_start_xmit
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]