Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261235AbTEHJSM (ORCPT ); Thu, 8 May 2003 05:18:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261239AbTEHJSL (ORCPT ); Thu, 8 May 2003 05:18:11 -0400 Received: from [212.50.18.217] ([212.50.18.217]:2056 "EHLO gw.zaxl.net") by vger.kernel.org with ESMTP id S261235AbTEHJSK (ORCPT ); Thu, 8 May 2003 05:18:10 -0400 Date: Thu, 8 May 2003 12:31:34 +0300 (EEST) From: Alexander Atanasov To: linux-kernel@vger.kernel.org, Alan Cox , Bartlomiej Zolnierkiewicz Subject: Re: 2.5.69, IDE problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1670 Lines: 47 On Thu, 8 May 2003, Alexander Atanasov wrote: > Hello, > > On Thu, 8 May 2003, David Ford wrote: > > > hda: dma_timer_expiry: dma status == 0x24 > > drivers/ide/ide-io.c:108: spin_lock(drivers/ide/ide.c:c04fb648) already > > locked by drivers/ide/ide-io.c/948 > > drivers/ide/ide-io.c:990: spin_unlock(drivers/ide/ide.c:c04fb648) not locked > > hda: lost interrupt > > hda: dma_intr: bad DMA status (dma_stat=30) > > hda: dma_intr: status=0x50 { DriveReady SeekComplete } > > > > hda: dma_timer_expiry: dma status == 0x24 > > drivers/ide/ide-io.c:108: spin_lock(drivers/ide/ide.c:c04fb648) already > > locked by drivers/ide/ide-io.c/948 > > drivers/ide/ide-io.c:990: spin_unlock(drivers/ide/ide.c:c04fb648) not locked > > hda: lost interrupt > > hda: dma_intr: bad DMA status (dma_stat=30) > > hda: dma_intr: status=0x50 { DriveReady SeekComplete } > > known problem, patch sent to alan some time ago(may be i should > resync/resend?) for this dma_timer_expiry have several problems: > calls DRIVER(drive)->error - the one above, it's called with lock from > ide_timer_expiry > calls ide_dma_end - the reason for called while not waiting messages, > it's called again in ide_timer_expiry +++ calls handler under the lock, thats fixed in -ac, and thats above, not error. > > there is one more locking problem known to me - HDIO_DRIVE_RESET, > but can not find out how to fix it properly. > > -- have fun, alex - 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/