Date: Thu, 28 Jun 2012 20:48:07 +0200 From: Herbert Poeckl <freebsdml@ist.tugraz.at> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-stable@FreeBSD.org Subject: Re: Need help with nfsv4 and krb5 access denied Message-ID: <4FECA6E7.1080303@ist.tugraz.at> In-Reply-To: <4FECA47A.6080003@ist.tugraz.at> References: <1914283839.2362353.1340897684902.JavaMail.root@erie.cs.uoguelph.ca> <4FECA47A.6080003@ist.tugraz.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/28/2012 08:37 PM, Herbert Poeckl wrote: > On 06/28/2012 05:34 PM, Rick Macklem wrote: >> The only other thought I had (I have no idea if this is even possible?) >> is that some sort of hardware offload in the network card is screwing >> things up. (I don't know the em hardware, but you might try disabling >> TSO etc, in case the packets are somehow getting corrupted?) >> >> Good luck with it. It would be nice to know why this is happening. >> Since the NIC is way below the NFS layer, I can't think of any reason >> why NFS would care which NIC is used. > > I did some more testing. > > What is the difference between the two cards is, that on of them (the > working one) says: > em0: Using an MSI interrupt > > The card where I get the access denied doesn't say anything like this. > > So I tried to disable msi with > hw.pci.enable_msi=0 > > .. in /boot/loader.conf and now I get access denied on both NICs. > > The card now says: > em0: No MSI/MSIX using a Legacy IRQ > > Hmm. Is there an idea of what to do next? Oh sorry! Please forget this posting. I did a crosscheck and it still is working (even with MSI disabled). Very sorry, Herbert (still searching to find a solution)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FECA6E7.1080303>