Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964828AbWACVJf (ORCPT ); Tue, 3 Jan 2006 16:09:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964841AbWACVJd (ORCPT ); Tue, 3 Jan 2006 16:09:33 -0500 Received: from vvv.conterra.de ([212.124.44.162]:61119 "EHLO conterra.de") by vger.kernel.org with ESMTP id S964830AbWACVJD (ORCPT ); Tue, 3 Jan 2006 16:09:03 -0500 Message-ID: <43BAE7E3.6070504@conterra.de> Date: Tue, 03 Jan 2006 22:08:51 +0100 From: =?ISO-8859-1?Q?Dieter_St=FCken?= MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: Re: X86_64 + VIA + 4g problems References: <43B90A04.2090403@conterra.de> <43BA4C3D.4060206@conterra.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1060 Lines: 27 OK, here are my last results for today: using "iommu=allowed" did not work. System freezes during initialization of the PDC20318, which is on the external PCI bus. But swiotlb=force works well! Using the patch for pci-gart.c currently works while reading data on all 8 disks in parallel, reading data via NFS and writing this mail. The pci-gart.c patch seems to disable dma. Is this the DMA my PCI devices perform them self? As I learned, they may perform DMA even above 4g if all works well. Thus I may be happy without any IOMMU. As I saw my system working even without this patch, I will turn back to the original 2.6.15-rc7 an continue running this torture test during this night. Dieter. -- Dieter St?ken, con terra GmbH, M?nster stueken@conterra.de http://www.conterra.de/ (0)251-7474-501 - 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/