On Thu, Jun 11, 2009 at 12:05:08PM +0100, Alan Cox wrote:
> > ata1.00: status: { DRDY }
> >
> > which seems to suggest that it's sitting there waiting for the data to
> > be transferred... but for some reason it's just not happening.
>
> Yes - it indicates the two ends have probably fallen out over the
> transfer length. It could also however be the drive took so long to
> respond we got bored of waiting for DF to appear.
Hmm, is there a way to get a dump of the host side registers when a
timeout occurs?
> > The IDE interface on this is:
>
> Utterly generic aging PIIX4. Thinkpad 600 kind of era, no known bugs.
Indeed, it's my old 380XD "brick".
> Two things to check
>
> - disable the SMART stuff
> - turn off drive side power saving (hdparm)
>
> see if that makes any difference.
I don't have any smart process running, and although I do have hdparm
installed, I don't have any reference to it in any script in /etc/rc.d.
As far as the drive power saving goes, that seems to be managed (somewhat
randomly) by the BIOS - while I can use hdparm to change the settings,
the BIOS at some random point will change them back to what it wants.
It's something this laptop has always done, even back in the days of
2.4 kernels. To give an example, I used 'hdparm -S0 /dev/sda' before
typing the following paragraph, but by the end of it, the disk has been
spun back down.
| What I would say is that turning off the drive side power management
| (-S0) will prevent the problem occuring - it only appears to occur when
| the drive has already been spun down.
which I would now delete because I can't keep it in -S0 mode! ;(
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
