public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ross Biro <ross.biro@gmail.com>
To: Jim Gifford <maillist@jg555.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Random IDE Lock ups with via IDE
Date: Wed, 25 May 2005 19:57:23 -0400	[thread overview]
Message-ID: <8783be6605052516577daeebdf@mail.gmail.com> (raw)
In-Reply-To: <4294E409.9020907@jg555.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
>

  reply	other threads:[~2005-05-25 23:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24 23:27 Random IDE Lock ups with via IDE Jim Gifford
2005-05-25 17:50 ` Jim Gifford
2005-05-25 20:34   ` Ross Biro
2005-05-25 20:46     ` Jim Gifford
2005-05-25 23:57       ` Ross Biro [this message]
2005-05-26 18:28         ` Jim Gifford
2005-05-26 19:35           ` Ross Biro
2005-05-26 19:50             ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8783be6605052516577daeebdf@mail.gmail.com \
    --to=ross.biro@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maillist@jg555.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox