Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932245AbXFBVT6 (ORCPT ); Sat, 2 Jun 2007 17:19:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757269AbXFBVTf (ORCPT ); Sat, 2 Jun 2007 17:19:35 -0400 Received: from ug-out-1314.google.com ([66.249.92.172]:47864 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756960AbXFBVTd (ORCPT ); Sat, 2 Jun 2007 17:19:33 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-disposition:message-id:content-type:content-transfer-encoding; b=A4j+PMtmJvkH329mhdK8pWwiVM8OhuxMxijfmLAwNwnCboTsjt9rWhaxf8Kn4RbolioUrMdbuYQJzJJpcw6+YpvgMcZbyVh5V5vDQdBxGpACWf7ImkmEULHRa89ZnzhUUDWG70L5+XUIbACQkC1S52LSFliel3y4yX422IRRcyo= From: Bartlomiej Zolnierkiewicz To: Thomas Kuther Subject: Re: IT821x: no DMA since 2.6.21 Date: Sat, 2 Jun 2007 23:32:49 +0200 User-Agent: KMail/1.9.6 Cc: Alan Cox , linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org References: <20070515125308.3a9f6442@SiRiUS.home> <200705241146.24079.bzolnier@gmail.com> <20070531212335.77486121@SiRiUS.home> In-Reply-To: <20070531212335.77486121@SiRiUS.home> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200706022332.49229.bzolnier@gmail.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2521 Lines: 70 On Thursday 31 May 2007, Thomas Kuther wrote: > On Do, 24.05.07 11:46 Bartlomiej Zolnierkiewicz > wrote: > > > > > Hi, > > > > [...] > > > > Improved patch - this time the issue should be fixed for good (I was > > looking only at the RAID specific part of the fixups and I overlooked > > the fact that the original code was clearing too much of > > id->field_valid), there is now also an extra debugging printk to give > > us some more info. > > > > Please give it a try. > > > > [ recal_intr warning (which should be harmless) is not fixed by this > > patch because it is a different problem and requires some more > > work. ] > > > > Hi, > > Sorry again for late response. > > This patch works. At least it restores the behaviour before .21 :) > ---------------------------- > IT8212: IDE controller at PCI slot 0000:00:09.0 > ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 17 (level, low) -> IRQ 18 > IT8212: chipset revision 17 > it821x: controller in smart mode. > IT8212: 100% native mode on irq 18 > ide2: BM-DMA at 0xdc00-0xdc07, BIOS settings: hde:pio, hdf:pio > ide3: BM-DMA at 0xdc08-0xdc0f, BIOS settings: hdg:pio, hdh:pio > Probing IDE interface ide2... > hde: SAMSUNG SP2514N, ATA DISK drive > hdf: Maxtor 6Y120L0, ATA DISK drive > hde: field_valid=0007 capability=2f dma_mword=0007 dma_status=04 > hde: Performing identify fixups. > hdf: field_valid=0007 capability=2f dma_mword=0007 dma_status=04 > hdf: Performing identify fixups. > hde: selected mode 0x22 > hdf: selected mode 0x22 > ide2 at 0xec00-0xec07,0xe802 on irq 18 > hde: max request size: 128KiB > hde: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, > DMA hde:hde: recal_intr: status=0x51 { DriveReady SeekComplete Error } > hde: recal_intr: error=0x04 { DriveStatusError } > ide: failed opcode was: unknown > hde1 > hdf: max request size: 128KiB > hdf: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=65535/16/63, DMA > hdf:hdf: recal_intr: status=0x51 { DriveReady SeekComplete Error } > hdf: recal_intr: error=0x04 { DriveStatusError } > ide: failed opcode was: unknown > hdf1 > ---------------------------------------- > > hdparm does not complain, and disk IO speed is OK. I'm glad that the issue is finally fixed. :) Thanks, Bart - 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/