public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: linas@austin.ibm.com (Linas Vepstas)
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Stuart_Hayes@Dell.com, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] ide dma_timer_expiry, then hard lockup
Date: Tue, 19 Jun 2007 11:48:54 -0500	[thread overview]
Message-ID: <20070619164854.GR5836@austin.ibm.com> (raw)
In-Reply-To: <4677FFF1.2010308@ru.mvista.com>

On Tue, Jun 19, 2007 at 08:10:25PM +0400, Sergei Shtylyov wrote:
> 
> >I'm thinking that trying to debug libata is a better idea, rather than
> >investing time in ide, right?  Although at the moment, libata works even 
> >less; see other email.
> 
>    Which makes me think this really is some *hardware* issue.

There are two distinct issues.
-- libata locks up in partition table read on an hpt366+old maxtor disk
   that has ben working fine for many years with old ide driver. (It
   still works fine when I boot to the alternate ide-based kernel).

-- ide driver locks up on hpt366+new maxtor disk under heavy 
   i/o load. I was able to copy 60GB from old to new disk without a
   problem; however, raid reconstruction locks it up, maybe after 5-15
   seconds.

   This probably is "hardware related"; its something that the new 
   hard drive does. Given that its being sold at a big discount, it
   may even be that the sellers know that this is a crappy disk. :-)

   All I want is some way of resetting the disk, and continuing on.

I'm stalled in debugging; I'm not sue what I'm looking for.

--linas



  reply	other threads:[~2007-06-19 16:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 17:57 [BUG] ide dma_timer_expiry, then hard lockup Linas Vepstas
2007-06-18 18:11 ` Stuart_Hayes
2007-06-19 14:07   ` Sergei Shtylyov
2007-06-19 15:05     ` Linas Vepstas
2007-06-19 16:10       ` Sergei Shtylyov
2007-06-19 16:48         ` Linas Vepstas [this message]
2007-06-19 18:43           ` Bartlomiej Zolnierkiewicz
2007-06-19 20:07             ` Sergei Shtylyov
2007-06-20 16:28               ` Linas Vepstas
2007-06-20 17:01                 ` Alan Cox
2007-06-21 17:58                   ` Sergei Shtylyov
2007-06-21 21:41                     ` Alan Cox
2007-06-21 19:47                   ` Linas Vepstas
2007-06-21 22:04                     ` Alan Cox
2007-06-18 20:27 ` Alan Cox
2007-06-18 20:46   ` Linas Vepstas
2007-06-18 21:04     ` Alan Cox
2007-06-18 21:22       ` Linas Vepstas
2007-06-19 14:56         ` bug in libata [was " Linas Vepstas
2007-06-19 14:10       ` Sergei Shtylyov
2007-06-19 14:19         ` Alan Cox
2007-06-19 14:24           ` Sergei Shtylyov
2007-06-19 15:38             ` Mark Lord
2007-06-19 15:51               ` Sergei Shtylyov
2007-06-19 16:17               ` Alan Cox
2007-06-19 16:32                 ` Sergei Shtylyov
2007-06-22 15:39 ` Sergei Shtylyov
2007-06-29 18:52   ` Sergei Shtylyov

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=20070619164854.GR5836@austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=Stuart_Hayes@Dell.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.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