> > 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 [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Reproducable hard locks in 2.2.17. IDE related Igmar Palsenberg
- Re: Reproducable hard locks in 2.2.17. IDE related Carsten Lang
- Re: Reproducable hard locks in 2.2.17. IDE relat... Andre Hedrick
- Re: Reproducable hard locks in 2.2.17. IDE r... Igmar Palsenberg
- Re: Reproducable hard locks in 2.2.17. IDE relat... Alan Cox
- Re: Reproducable hard locks in 2.2.17. IDE r... Igmar Palsenberg
- Re: Reproducable hard locks in 2.2.17. I... Igmar Palsenberg
- Re: Reproducable hard locks in 2.2.17. IDE relat... Igmar Palsenberg
- Re: Reproducable hard locks in 2.2.17. IDE relat... Pavel Machek
- Re: Reproducable hard locks in 2.2.17. IDE r... Igmar Palsenberg
- Re: Reproducable hard locks in 2.2.17. IDE related Igmar Palsenberg
- Re: Reproducable hard locks in 2.2.17. IDE relat... Andries Brouwer
- Re: Reproducable hard locks in 2.2.17. IDE r... Igmar Palsenberg
- Re: Reproducable hard locks in 2.2.17. IDE r... Andre Hedrick
- Re: Reproducable hard locks in 2.2.17. I... Igmar Palsenberg