From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: Mystery packet killing tg3 Date: Thu, 05 May 2005 09:20:25 -0700 Message-ID: <427A47C9.6040302@osdl.org> References: <20050502162405.65dfb4a9@localhost.localdomain> <20050502200251.38271b61.davem@davemloft.net> <42791825.2080204@pantasys.com> <20050505114327.GA51761@muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Peter Buckingham , "David S. Miller" , jgarzik@pobox.com, netdev@oss.sgi.com Return-path: To: Andi Kleen In-Reply-To: <20050505114327.GA51761@muc.de> Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org Andi Kleen wrote: >>>IOMMU code on x86-64 should be never active unless Stephen >>>used IOMMU_DEBUG or iommu=force. THat is because the tg3 >>>is a 64bit capable device and should always use bypass. >>> >>> >>how is this detected? we have a board that is using a 32bit e1000 and we >>have to use iommu=force otherwise it doesn't do the right thing with > >>4GB of RAM. >> >> > >"32bit e1000"? How did you get such a beast? AFAIK all e1000s are 64bit >address capable. Please supply a full boot log without iommu=force >and describe what happens exactly. > > One of the osdl e1000's in the lab is an IBM rebranded card that although it uses a 64bit slot, is really only 32bit