From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bartlomiej Zolnierkiewicz Subject: Re: [BUG] ide dma_timer_expiry, then hard lockup Date: Tue, 19 Jun 2007 20:43:40 +0200 Message-ID: <200706192043.40298.bzolnier@gmail.com> References: <20070618175713.GD5836@austin.ibm.com> <4677FFF1.2010308@ru.mvista.com> <20070619164854.GR5836@austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from ug-out-1314.google.com ([66.249.92.168]:20728 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754091AbXFSS2x (ORCPT ); Tue, 19 Jun 2007 14:28:53 -0400 Received: by ug-out-1314.google.com with SMTP id j3so172335ugf for ; Tue, 19 Jun 2007 11:28:52 -0700 (PDT) In-Reply-To: <20070619164854.GR5836@austin.ibm.com> Content-Disposition: inline Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Linas Vepstas Cc: Sergei Shtylyov , Stuart_Hayes@dell.com, linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org Hi, On Tuesday 19 June 2007, Linas Vepstas wrote: > 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. Linas, have you checked that there are no firmware updates available for this drive? > 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. It would be useful to see hdparm --Istdout output for *both* disks. > I'm stalled in debugging; I'm not sue what I'm looking for. Sergei, do you think that testing the drive with DMA disabled may tell us something new? Thanks, Bart