Re: Random IDE Lock ups with via IDE

[Ross Biro <ross.biro@gmail.com>]

Since you say the problem started with 2.6.8, perhaps the easiest
thing to do is look at the
kernel you say worked and its config and then just diff it vs 2.6.8.

I took a second look at your original message, and since it's an irq
timeout, it could just be that your drive is slow to answer a command
and then is confused by the error recovery code.  Having two identical
laptops makes this easy.  If your other laptop has the same problem,
then it's software (or buggy hardware that the software hasn't figured
out how to work around) if it doesn't, then it's hardware and there
are a couple of things that can be tweaked to see if it fixes things.

    Ross

On 5/25/05, Jim Gifford <maillist@jg555.com> wrote:
> Ross,
>     I thought of that to, I just have 2 laptops that are identical here
> now. I have placed a different drive in the other one. So we can test
> it, but looking through all my logs that I backed up, this problem
> started when I put 2.6.8 on the laptop. I'm wondering if it could be an
> ACPI issue or IDE issue, but have no idea on what to really look for.
> 
> May 24 16:22:31 laptop kernel: mtrr: 0x40000000,0x800000 overlaps
> existing 0x40000000,0x400000
> May 24 18:25:11 laptop kernel: hda: status timeout: status=0xd0 { Busy }
> May 24 18:25:11 laptop kernel:
> May 24 18:25:11 laptop kernel: ide: failed opcode was: unknown
> May 24 18:25:11 laptop kernel: hda: no DRQ after issuing MULTWRITE
> May 24 18:25:12 laptop kernel: ide0: reset: success
> 
> May 24 12:21:15 laptop2 kernel: mtrr: 0x40000000,0x800000 overlaps
> existing 0x40000000,0x400000
> May 24 16:55:53 laptop2 kernel: hda: status timeout: status=0xd0 { Busy }
> May 24 16:55:53 laptop2 kernel:
> May 24 16:55:54 laptop2 kernel: ide: failed opcode was: unknown
> May 24 16:55:54 laptop2 kernel: hda: no DRQ after issuing MULTWRITE
> May 24 16:55:54 laptop2 kernel: ide0: reset: success
> 
> Here is a link to my .config file
> http://ftp.jg555.com/configs/laptop.config
>
-
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/