| To: | Peter Buckingham <peter@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Mystery packet killing tg3 |
| From: | Andi Kleen <ak@xxxxxx> |
| Date: | 5 May 2005 13:43:27 +0200 |
| Date: | Thu, 5 May 2005 13:43:27 +0200 |
| Cc: | "David S. Miller" <davem@xxxxxxxxxxxxx>, jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <42791825.2080204@xxxxxxxxxxxx> |
| References: | <20050502162405.65dfb4a9@xxxxxxxxxxxxxxxxxxxxx> <20050502200251.38271b61.davem@xxxxxxxxxxxxx> <m14qdiyhcn.fsf@xxxxxx> <42791825.2080204@xxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.1i |
> >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. -Andi |
| Previous by Date: | Re: oops in ip_rcv, Herbert Xu |
|---|---|
| Next by Date: | Re: [PATCH 2/3] add open iscsi netlink interface to iscsi transport class, YOSHIFUJI Hideaki / 吉藤英明 |
| Previous by Thread: | Re: Mystery packet killing tg3, Peter Buckingham |
| Next by Thread: | Re: Mystery packet killing tg3, Stephen Hemminger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |