From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932129AbWGLCzF (ORCPT ); Tue, 11 Jul 2006 22:55:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932355AbWGLCzE (ORCPT ); Tue, 11 Jul 2006 22:55:04 -0400 Received: from ns.suse.de ([195.135.220.2]:37603 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S932129AbWGLCzD (ORCPT ); Tue, 11 Jul 2006 22:55:03 -0400 Message-ID: <121226.1152672894714.SLOX.WebMail.wwwrun@imap-dhs.suse.de> Date: Wed, 12 Jul 2006 04:54:54 +0200 (CEST) From: Andreas Kleen To: Anthony DeRobertis Subject: Re: skge error; hangs w/ hardware memory hole Cc: Stephen Hemminger , Martin Michlmayr , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, kevin@sysexperts.com In-Reply-To: <44B46276.5030006@suespammers.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 (normal) X-Mailer: SuSE Linux Openexchange Server 4 - WebMail (Build 2.4160) X-Operating-System: Linux 2.4.21-309-smp i386 (JVM 1.3.1_18) Organization: SuSE Linux AG References: <20060703205238.GA10851@deprecation.cyrius.com> <20060707141843.73fc6188@dxpl.pdx.osdl.net> <200607072328.51282.ak@suse.de> <44B46276.5030006@suespammers.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Spamming bug robot dropped from cc list. Am Mi 12.07.2006 04:46 schrieb Anthony DeRobertis : > OK, here are the results with iommu=force. All of these are copied > down > by hand, so please forgive any transcription errors: You need to use iommu=soft swiotlb=force The standard IOMMU is also broken on VIA, but forced swiotlb should work. However it is a bit slow because it will force all IO through an additional copy. If it helps I can do a proper patch that only bounces IO > 4GB through the copy. > Honestly, should I chuck this board through the window of my nearest > ASUS and/or VIA office, and buy an NForce board? We can probably get it to work, but you're clearly outside validated territory (= you're running the hardware in a untested by the vendor configuration). Normally that's not a good idea. BTW there are NForce systems with similar problems, but they are rare. -Andi