> The BIOS in your machine doesn't support SR-IOV. You'll need to ask the
> manufacturer for a BIOS upgrade, if in fact one is available. Sometimes
> they're not.
very thanks Greg,my server Dell R710 with latest BIOS version and
option for SR-IOV(SR-IOV Global Enable->Enabled) opened,I'm conf
I tried removing the battery, the behavior was the same as with the
battery. I added the logging to the driver but nothing additional came up
in the logs. I have to conclude that the issue is solely a HW bug.
Thanks for your help.
On Thu, Nov 8, 2012 at 3:02 PM, Mark Bidewell wrote:
> Thanks
On 11/09/12 04:35, Dave, Tushar N wrote:
> Are you sure this is not similar issue as before that you reported.
> i.e.
Tushar,
Thanks for your quick response, I'll check with customer if they can modify the
Max
payload size from BIOS, this time issue hit on HP's server.
Thanks again,
Joe
> On
Hi Robert,
Yes that is correct about RSC vs. LRO. Have you tried turning of RSC on 82599?
ethtool -K lro off ethX
Also how about if you disable DCB? Does that have impact on latency?
Also could you please send us following after loading the driver:
Output from:
dmesg
lspci -vvv
Thanks,
Step
Getting two distinctive behaviors from two RHEL 5 servers. Seems the host with
the 82599 NICs reports significant latency when read requests surpass 32KB. The
host with the 82598 NICs does not demonstrate this behavior. It's our
understanding that the two NIC adapters perform different offload c
> -Original Message-
> From: Chris Friesen [mailto:chris.frie...@genband.com]
> Sent: Thursday, November 08, 2012 1:43 PM
> To: Levy, Lior
> Cc: e1000-devel@lists.sourceforge.net; Kirsher, Jeffrey T; Brandeburg, Jesse;
> Allan, Bruce W; Wyborny, Carolyn; Skidmore, Donald C; Rose, Gregory V;
On 11/08/2012 02:58 PM, Chris Friesen wrote:
> I tried
> using "ethtool -K ethX rxvlan off" but for some reason that option
> always showed as off even when CTRL.VME was actually set.
This is not my main problem, but somewhat related. I think I found a
flaw in the driver.
If you have a kernel w
On 11/06/2012 02:27 PM, Chris Friesen wrote:
> On 11/06/2012 02:10 PM, Chris Friesen wrote:
>
>> I'm doing a test to see if not stripping the vlan tag will make any
>> difference.
>
> So I applied this patch (basically just disabling vlan stripping for VFs)
> and vlan-on-vf to vlan-on-vf communicat
>-Original Message-
>From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org]
>On Behalf Of Joe Jin
>Sent: Wednesday, November 07, 2012 10:25 PM
>To: e1000-de...@lists.sf.net
>Cc: net...@vger.kernel.org; linux-ker...@vger.kernel.org; Mary Mcgrath
>Subject: 82571EB: Detected
Thanks, I will try the the battery trick. I have tried editing BIOS
settings and they seem to be preserved. The PSU in the box did go bad and
maybe that damaged something. I assume you mean the NIC NVM, is there
anything specific I should look for in the NVM?
On Thu, Nov 8, 2012 at 2:38 PM, Br
I had a look over the ubuntu bug discussion at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1072722?comments=all
There is an NVM utility called flashrom that might be able to see your NVM
data. You will likely have to boot with iomem=relaxed boot parameter.
Your hardware is acting flak
Thanks, I will try your driver change as soon as I can.
On Thu, Nov 8, 2012 at 2:30 PM, Alexander Duyck wrote:
> That is kind of what I figured. I am assuming that there is an error
> returned during e1000_probe that is causing the device to not show up as
> a network device.
>
> Thanks,
>
> A
That is kind of what I figured. I am assuming that there is an error
returned during e1000_probe that is causing the device to not show up as
a network device.
Thanks,
Alex
On 11/08/2012 11:25 AM, Mark Bidewell wrote:
> Thanks I will give that a try. I forgot to mention that e1000e does
> not
Thanks I will give that a try. I forgot to mention that e1000e does not
appear to fail to load. In the failure case, e1000e is still listed in
lsmod as a loaded module.
On Thu, Nov 8, 2012 at 2:17 PM, Alexander Duyck wrote:
> Looking over the code it looks like there is only one spot where th
Looking over the code it looks like there is only one spot where the
driver could be failing without displaying some sort of error message.
That would be at the register_netdev call.
If you look in the netdev.c file you should be able to find a tag named
"err_register:". It would greatly help wi
Yes, In the working case the log looks like:
Nov 3 12:26:00 cbidewell-desktop kernel: [1.400831] e1000e
:00:19.0: >irq 46 for MSI/MSI-X
Nov 3 12:26:00 cbidewell-desktop kernel: [1.705990] e1000e
:00:19.0: >eth0: (PCI Express:2.5GT/s:Width x1) 00:1c:c0:60:ee:1e
Nov 3 12:26:00 cb
Are you sure this is the failure case? I ask since it seems like the
e1000e is claiming the device and assigning it irq 47 for use with MSI
based on the snippet from the log below. I would have expected to see
an error stating that it failed to load the driver on the interface.
Thanks,
Alex
On
Thanks. Here is the logging in the failure case:
[1.139788] e1000e: Intel(R) PRO/1000 Network Driver - 2.0.0-k
[1.139791] e1000e: Copyright(c) 1999 - 2012 Intel Corporation.
[1.139828] e1000e :00:19.0: >setting latency timer to 64
[1.139899] e1000e :00:19.0: >Interrupt Thr
Mark,
I could recommend checking the dmesg log after you have
unloaded/reloaded the e1000e driver. There is likely an error that is
being reported that is preventing the driver from loading and knowing
what the error is that is being reported would go a long way toward
telling us what the issue i
> -Original Message-
> From: Jeff Kirsher [mailto:tar...@gmail.com]
> Sent: Thursday, November 08, 2012 3:23 AM
> To: pkill.2012
> Cc: linux-kernel; netdev; kvm; e1000-devel@lists.sourceforge.net; Rose,
> Gregory V
> Subject: Re: SR-IOV problem with Intel 82599EB (not enough MMIO resources
If there is no MSI it should be using legacy interrupts and interrupt 46 is not
a legacy interrupt. Can you try to boot the OS with MSI disabled?The boot
option is "nomsi". Maybe it will force the correct interrupt option for the
kernel to use.
Cheers,
John
From: Mark Bidewell [mailto:m
Thank you, that is what I suspect but since it worked up until recently, I
thought it would be good to check. I tried to recovery reflash the BIOS
after replacing the battery (I am already at the latest - so no update) no
way to know if it actually did the reflash. Should the e1000e be able to
s
Hi Mark,
Sorry to hear about your problem. This does however sound like something with
your system. The device has been supported for a long time now in the e1000e
driver. I think you still have something going on with your BIOS that isn't
setting things up correctly regarding the LAN device
My apologies if this is the wrong mailing list for this question, but
recently the 82566DC-2 NIC on my Intel DP35DP mainboard stopped being
recognized by linux (Ubuntu 12.04/12.10) although the card is still visible
in lspci. e1000e tries to load but does not bring up the card The issue
was at l
On 11/08/2012 03:15 AM, pkill.2012 wrote:
> Hello,
>
> I installed kvm and tried to use SR-IOV virtualizaton for 82599EB(Intel
> XT-520 T2) dual port card with latest ixgbe driver(version:3.11.33) ,
> kernel2.6.32-279.14.1(OS:Centos6.3) ,after configuration and reboot
> It seems that only first
Hi list,
IHAC reported "82571EB Detected Hardware Unit Hang" on HP ProLiant DL360 G6, and
have to reboot the server to recover:
e1000e :06:00.1: eth3: Detected Hardware Unit Hang:
TDH <1a>
TDT <1a>
next_to_use <1a>
next_to_clean<18>
b
26 matches
Mail list logo
