Zdrastwujtie.
> I have a flaky IDE subsystem in one box. Reads work fine,
> writes sometimes don't work and hang either IDE/block device
> sybsystem or entire box. For example, I dumped ~40 MB file to
> the disk and now I have additional power led (i.e. hdd activity
> led is constantly on) and a bunch of "D" state processes
> (kupdated, mount, umount).
>
> This is happening since I decided to try 2.5.7.
> 2.4.18 reported DMA failures and reverted to PIO.
>
> I did send a detailed report of similar event with
> ksymoopsed stack traces of hung prosesses to lkml.
>
> Since you are working on IDE subsystem, I will be glad to
> *retain* my flaky IDE setup and test future kernels
> for correct operation in this failure mode.
>
> Please inform me whenever you want me to test your patches.
Guessing from the symptoms I would rather suggest that:
1. Are you sure you have the support for your chipset properly
enabled? It's allmost a must for DMA.
2. Could you please report about the hardware you have. There are
chipsets around there which are using theyr own transport layer
implementations. host chip (aka south bridge) disk types and so on.
3. Some timeout values got increased to more generally used values (in esp.
IBM microdrives advice about timeout values. Could you see whatever
the data doesn't eventually go to the disk after georgeous
amounts of time.
4. Could you try to set the DMA mode lower then it's set up
per default by using hdparm and try whatever it helps?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/