| To: | Andi Kleen <ak@xxxxxx> |
|---|---|
| Subject: | Re: Mystery packet killing tg3 |
| From: | Stephen Hemminger <shemminger@xxxxxxxx> |
| Date: | Thu, 05 May 2005 09:20:25 -0700 |
| Cc: | Peter Buckingham <peter@xxxxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>, jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20050505114327.GA51761@muc.de> |
| References: | <20050502162405.65dfb4a9@localhost.localdomain> <20050502200251.38271b61.davem@davemloft.net> <m14qdiyhcn.fsf@muc.de> <42791825.2080204@pantasys.com> <20050505114327.GA51761@muc.de> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 1.0.2 (X11/20050404) |
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 |
| Previous by Date: | Re: [RFC] textsearch infrastructure + skb_find_text(), Thomas Graf |
|---|---|
| Next by Date: | e1000 (?) jumbo frames performance issue, Michael Iatrou |
| Previous by Thread: | Re: Mystery packet killing tg3, Andi Kleen |
| Next by Thread: | Re: Mystery packet killing tg3, Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |