Re: Reproducable hard locks in 2.2.17. IDE related

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Fri Sep 22 2000 - 05:27:58 EDT

Next message: Rik van Riel: "Re: Linux-2.4.0-test9-pre2"

Previous message: James Lewis Nance: "Re: [patch *] VM deadlock fix"
In reply to: Carsten Lang: "Re: Reproducable hard locks in 2.2.17. IDE related"
Next in thread: Igmar Palsenberg: "Re: Reproducable hard locks in 2.2.17. IDE related"
Next in thread: Igmar Palsenberg: "Re: Reproducable hard locks in 2.2.17. IDE related"
Reply: Igmar Palsenberg: "Re: Reproducable hard locks in 2.2.17. IDE related"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> > Uncorrectable error is the drive.
>
> i don't think that we can blame the disks!

Uncorrectable error is the drive. Its not something the kernel can directly
get wrong nor is it timing. It is possible it occurred because the kernel asked
for something silly.

Do you have stuff logged about trying to access out of range blocks ?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Next message: Rik van Riel: "Re: Linux-2.4.0-test9-pre2"
Previous message: James Lewis Nance: "Re: [patch *] VM deadlock fix"
In reply to: Carsten Lang: "Re: Reproducable hard locks in 2.2.17. IDE related"
Next in thread: Igmar Palsenberg: "Re: Reproducable hard locks in 2.2.17. IDE related"
Next in thread: Igmar Palsenberg: "Re: Reproducable hard locks in 2.2.17. IDE related"
Reply: Igmar Palsenberg: "Re: Reproducable hard locks in 2.2.17. IDE related"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Sep 22 2000 - 05:31:19 EDT