Quantcast
Channel: Intel Communities : Discussion List - Wired Ethernet
Viewing all 4405 articles
Browse latest View live

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

$
0
0

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

KMODE_EXCEPTION_NOT_HANDLED

IRQL_NOT_LESS_OR_EQUAL

nvlddmkm.sys

ntoskrnl.exe

 

Hello, I have recently arrived at the end of any forum as well as different topic on the internet on the problems written above. Does anyone have any idea how to fix this.

 

If you need more precision do not hesitate. thank you in advance for your help


Intel(R) Ethernet Connection (2) I219-V - Waking from sleep causes 10Mbp/s and no connectivity until rebooting or reconnecting cable.

$
0
0

Setup:

  • I have a Gigabyte GA-B150M-D3H motherboard with an Intel i5-6500 CPU and 8Gb DDR4 GSkill RAM.
  • I have wired ethernet with a CAT5e cable plugged from the Ethernet port into a TP-Link Gigabit 5 port switch and then eventually onto a TP-Link ADSL2 Router.
  • I am using a static IP setup (Static IP, Gateway, Subnet mask).
  • I am running Windows 10 Home 64bit
  • I am running Kaspersky 2017 Internet Security (I have uninstalled Kaspersky Secure Connection)
  • I am running the supplied Gigabyte drivers for the Intel Ethernet Adapter on the board (Version 20.7 - listed as 12.15.22.3 in the driver properties)

 

Problem:

  • Waking from S1 sleep causes the adapter to intialise at 10Mb/s and have no connectivity. The only solution is 1) reboot or 2) remove and re-insert the CAT5e cable. This cable has worked at Gigabit speeds for years on the previous Motherboard I had which had a Realtek based ethernet adapter on a GA-X38-DQ6.

 

Event Logs:

  • When the problem occurs: "Intel(R) Ethernet Connection (2) I219-V Network link has been established at 10Mbps full duplex."
  • When the system works fine: "Intel(R) Ethernet Connection (2) I219-V Network link has been established at 1Gbps full duplex."

 

Things I have tried:

I have tried the following Intel drivers:

  • 20.4.1 (from the Intel site)
  • 20.7 (from the Gigabyte site)
  • 21.1 (from the Intel site)

I have tried disabling all of the power management properties in the Intel driver properties

Bringing up a new board with an XL710.

$
0
0

We are bringing up a new board with an XL710.

 

Need eeupdate/lanconf or whatever is now being used to program these.

Is the NVMupdate all that is needed?

What about the image file?

 

We've done 82576 and i210s in the past, has the process changed?

Thanks

Need compatible information for Intel X520-SR2 cards

$
0
0

Hi All,

 

We brought Intel X520-SR2 card with compatible modules. But in datasheet it showing it support IEEE 802.3 network standards.

 

Now we are planing to buy a Netgear XS708E 10G Switch  [Eight 100/1000/10000 Mbps RJ45 ports with one combo port supporting 10-Gigabit SFP+ fiber].

10-Gigabit SFP+ fiber port support [IEEE 802.3aq 10GBASE-LRM, IEEE 802.3ae 10GBase Ethernet, IEEE 802.3an 10GBase-T].

 

Please give me confirmation, weather  X520-SR2 is compatible with Netgear XS708E switch SFP port or not.

 

Please help me regarding this.

Obsolete driver for (2) I219-LM on Windows Update for Windows 7 ?

$
0
0

Hi,

 

I have read somewhere that Intel is NOT (directly) responsible for whatever Intel driver Microsoft is pushing through Windows update.

 

However I would like to ask a question, after a bit of context.

 

I have business laptop configured Windows 7 Enterprise, x64, SP 1:

 

     Microsoft Windows [Version 6.1.7601]

 

absolutely up to date.

 

The wired network is built with

 

     "Intel® Ethernet Connection (2) I219-LM"

 

so I have installed latest version of

 

     "Intel® Network Adapter Driver for Windows 7 / ProWin64.exe"

 

which is Version:21.1 (Latest)Date:10/11/2016

 

the specific version on the file driver as shown in Device Manager being:  12.15.23.7 dated 07/26/2016

 

So far so good.

 

Then why Microsoft Windows Update for Windows 7 keeps pushing a obsolete driver dated November 2015 update with the following description:

 

     Intel - LAN, LAN (Server) - Intel(R) Ethernet Connection (2) I219-LM

     Download size: 731 KB

     You may need to restart your computer for this update to take effect.

     Update type: Optional

     Intel LAN, LAN (Server) software update released in November, 2015

 

I mean even if it is optional, what is the point ? because it is definitely confusing.

 

What do you think ?

 

Please advise.

 

Hassan

How do you enable promiscuous mode on l219-LM updating drive does not seem to help

$
0
0

l219-LM using wireshark or NI observer same results nic is not in promiscuous mode OS Windows 10

Intel(R) 82579V Gigabit Network Connection Driver

$
0
0

PB for upgrading Driver for this card

during upgradind msg "impossible to upgrade driver installed, remove before upgrading"

i have desintalled the old driver et reboot

But i always read the same msg inquiring to remove old driver ??????

have a special program to ensure remove for the old driver ???

 

old driver is dated : 10/08/2012 and version number is : 12.2.45.0

 

best reagards

 

Patrick Larquey

Intel 82579v - Code 10 - media disconnected

$
0
0

After long shutdown and then power up ( eg. Power up in morning ) 82579v adapter shows Windows driver code 10 - with media disconnected status in ipconfig.

Shutdown and restart does not fix.  Hard power off while machine running, wait 60 seconds and power on usually fix.  Bio reset default also fix.

Problem re-occurs if machine is shutdown and powered off for a few hours.

 

It is not cabling or router since problem is resolved by one of the above power cycle steps.

 

Configuration:

  Motherboard: Asus P8Z77-V Pro

  Bios: Asus 2104 ( latest )

  OS: Windows 10-x64

  Network Driver: Intel 12.5.31.4  / ProSet 21.1.30.0

 

Applied NVRam update ( 82579VSKU ) adapter is now 82579V - no longer bounces to LM.

Tried:

  Older BIOS

  Microsoft Windows 10 Driver

 

Problem appears similar to:

https://communities.intel.com/message/264820

https://communities.intel.com/thread/110194


intel ethernet connection i219-v code 10 Error all the time

$
0
0

Hello,

First i am from germany so sry for my english at some points.

I build a new pc installed all drivers. All are working fine but the driver for the Ethernet adapter is just not working. I installed the Driver cd from the mainboard did not work, I installed the intel Driver did not work and i installed driver from the mainboard website did not work also....

What can i do i installed windows again it did not help.

Did a Cmos reset did not help.

Checket the bios settings did not help.

I Need help....

 

Thanks for reading

Taktlos.

gigabyte ct desktop adapter

$
0
0

For my old XP box, installed ref'd adapter & drivers and have since been experiencing connectivity issues.  When it works it is fantastic but periodically drops connection with msg "Network cable is unplugged".   By going to Device Mgr and changing any setting on the adapter, it will re-connect & everything is fine until next time.  The exact model is  Intel EXPI9301CTBLK Network Adapter 10/100/1000Mbps PCI-Express 1 x RJ45 (there wasn't an installation CD).  The BIOS tab is asking to be flashed but I have no idea where that file might be (The Driver Update Utility has problems with XP).  The downloads page on the support site has no link to an installation CD which I believe is called "Ethernet Adapters Connections CD".  The one link I was able to find doesn't indicate support for this adapter.  Any help would be greatly appreciated.  TIA

Why not for intel 9400PT 82572GI wired ethernet driver?

$
0
0

Only find intel®82572 and 82572EI, not found 82572GI

Red Rock Canyon - EPL Verification Test

$
0
0

Hello to ALL,

I want to measure EPL RefClk for RRC,

According to the datasheet , "As a guideline, total phase jitter of the clock source should be less than 0.25 ps RMS"

i have some questions:

1) What is total phase jitter (RMS) ? is it "Random Jitter"? is it measure with Scope or Spectrum (like phase noise)?

2) How much bandwidth is enough to measure this clock?

 

thanks,

Yuval.

Intel(R) Ethernet Connection (2) I219-V - Waking from sleep causes 10Mbp/s and no connectivity until rebooting or reconnecting cable.

$
0
0

Setup:

  • I have a Gigabyte GA-B150M-D3H motherboard with an Intel i5-6500 CPU and 8Gb DDR4 GSkill RAM.
  • I have wired ethernet with a CAT5e cable plugged from the Ethernet port into a TP-Link Gigabit 5 port switch and then eventually onto a TP-Link ADSL2 Router.
  • I am using a static IP setup (Static IP, Gateway, Subnet mask).
  • I am running Windows 10 Home 64bit
  • I am running Kaspersky 2017 Internet Security (I have uninstalled Kaspersky Secure Connection)
  • I am running the supplied Gigabyte drivers for the Intel Ethernet Adapter on the board (Version 20.7 - listed as 12.15.22.3 in the driver properties)

 

Problem:

  • Waking from S1 sleep causes the adapter to intialise at 10Mb/s and have no connectivity. The only solution is 1) reboot or 2) remove and re-insert the CAT5e cable. This cable has worked at Gigabit speeds for years on the previous Motherboard I had which had a Realtek based ethernet adapter on a GA-X38-DQ6.

 

Event Logs:

  • When the problem occurs: "Intel(R) Ethernet Connection (2) I219-V Network link has been established at 10Mbps full duplex."
  • When the system works fine: "Intel(R) Ethernet Connection (2) I219-V Network link has been established at 1Gbps full duplex."

 

Things I have tried:

I have tried the following Intel drivers:

  • 20.4.1 (from the Intel site)
  • 20.7 (from the Gigabyte site)
  • 21.1 (from the Intel site)

I have tried disabling all of the power management properties in the Intel driver properties

I350 EEPROM setting PCIe Link Speed

$
0
0

I want to change I350 PCIe  link speed to Gen1 from EEPROM but I don't know address, who can help~ 1.jpg

I want to install shared storage use fcoe on two sersers,the adapter is intel x520-DA2. I use command''dcbtool sc p6p1 app:0 e:1" on diffrent server,when using "fcoeadm -i p6p2.1002-fcoe" to scan the status of port name and node name,get the same value.ho

$
0
0

#first server

root@sdb-1 ~]# fcoeadm -i p6p2.1002-fcoe

    Description:      82599ES 10-Gigabit SFI/SFP+ Network Connection

    Revision:         01

    Manufacturer:     Intel Corporation

    Serial Number:    90E2BA26EE3E

    Driver:           ixgbe 3.21.2

    Number of Ports:  1

 

        Symbolic Name:     fcoe v0.1 over p6p2.1002-fcoe

        OS Device Name:    host11

        Node Name:         0x1000001B2194DC83

        Port Name:         0x2000001B2194DC83

        FabricName:        0x100050EB1AF120AC

        Speed:             10 Gbit

        Supported Speed:   1 Gbit, 10 Gbit

        MaxFrameSize:      2048

        FC-ID (Port ID):   0x050000

        State:             Online

 

#second server

[root@dct1 ~]# fcoeadm -i p6p2.1002-fcoe

    Description:      82599ES 10-Gigabit SFI/SFP+ Network Connection

    Revision:         01

    Manufacturer:     Intel Corporation

    Serial Number:    90E2BA0DE616

    Driver:           ixgbe 3.21.2

    Number of Ports:  1

 

        Symbolic Name:     fcoe v0.1 over p6p2.1002-fcoe

        OS Device Name:    host11

        Node Name:         0x1000001B2194DC83

        Port Name:         0x2000001B2194DC83

        FabricName:        0x0000000000000000

        Speed:             10 Gbit

        Supported Speed:   1 Gbit, 10 Gbit

        MaxFrameSize:      2048

        FC-ID (Port ID):   0x000000

        State:             Linkdown


I need more details of 82579's link drop issue for trouble confirmation

$
0
0

I have frequent link down trouble in our customer factory but can't re-produce in our bench.

The frequent link down port uses the 82579 nic and I found out the below issue.

 

kernel/git/torvalds/linux.git - Linux kernel source tree

 

It seems the relaxation of link down condition, but can't understand detail work around.

The modifed registers lost in 82579's specification, So, please share the information.

 

* MSE

  what of MSE?  how condition leads link down?

* original valule

  please share the threshold and counter's original values and meenings.

 

Thanks,

Why not for intel 9400PT 82572GI wired ethernet driver?

$
0
0

Only find intel®82572 and 82572EI, not found 82572GI

I210: Device ID 1533 is sometimes 1531

$
0
0

Dear Intel Community

 

In our device we have two WGI210IT ethernet controllers and we are facing an issue with them: Very rarley, let's say less than once per 100 boot ups, we see that the device ID is 1531 instead of 1533. At the moment we cannot reproduce it, it just appears sometimes on our devices.

 

lspci under linux shows it like this:

01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

02:00.0 Ethernet controller: Intel Corporation Device 1531 (rev 03)

 

After a reboot the Ethernet controller has ID 1533 again:

01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

 

Early at bootup of Linux the following message apears:

kernel: pci 0000:02:00.0: [8086:1531] type 00 class 0x020000

So it we doubt that any operating system related action causes the wrong ID.

 

The configuration is as follows:

- Ethernet controller firmware: Dev_Start_I210_Copper_SMB_8Mb_A2_3.25_0.03.bin

- Changes in Flash (On some devices done with Lanconf.exe under DOS and in others with eeupdate64e under Linux):

--> Word 0x20: Set bit 4 to '1' (disables Gbit Ethernet)

--> Changed MAC Address

- Gigabit Ethernet is not supported on HW side. MDI_PLUS_2 / MDI_MINUS_2 / MDI_PLUS_3 / MDI_MINUS_3 are pull-up to 1.5V via 49.9R resistors

- Flash: MX25L1606EZNI-12G

- 33R resistors in SPI lines (NVM_SI, NVM_SO, SVM_SK, NVM_CS#)

- Pin 12 is pulled-down with 10k (strap pin --> non secure mode)

 

Hardware checks:

- The I210 and the flash are powered from the same 3.3V source. First flash access happens after 25ms after 3.3V is reached. The flash itself requires 200us to be ready after Vmin is reached. So the flash is ready at first access.

- The signal levels of all SPI lines are fine.

- The solder points are checked and nothing wrong was seen.

 

We checked a few register values while the problem was seen:

Read at 0x90012010 | 0x40 0x2A 0x48 0x00 (Base address is 0x90000000)

The 1533 controller shows:

Read at 0x91312010 | 0x40 0x2B 0x08 0x06 (Base address is 0x91300000)

Differences:

EEPROM-Mode Control Register - EEC (0x12010) bit 8 is '0'. --> EE_PRES: No Flash with correct signature or empty iNVM

EEPROM-Mode Control Register - EEC (0x12010) bit 22 is '0'. --> Reserved: No info from datasheet

EEPROM-Mode Control Register - EEC (0x12010) bit 25 is '0'. --> SEC1VAL: Sector 1 not valid (but not meaning full due to bit 8 is '0')

EEPROM-Mode Control Register - EEC (0x12010) bit 26 is '0'. --> FLUDONE: No flash update done

 

Have you got any idea what could cause this problem?

 

Thank you in advance and best regards

Stefan

i40e / X710-DA2 segfault on Ubuntu 16.04

$
0
0

Hello!

I have a problem with running X710-DA2 on my servers. When I try to load the i40e driver it crashes. It happened on a stock fw, drivers, etc. and on the upgraded versions too.

 

Platform: Supermicro X9DRW with dual Intel(R) Xeon(R) CPU E5-2620, latest BIOS

OS: Ubuntu 16.04.1 LTS, linux 4.4.0-57

NIC firmware: fw 5.0.40043 api 1.5 nvm 5.04 0x800024c6 0.0.0 (latest)

i40e driver: 1.5.25 (latest, downloaded and compiled)

Modules installed: GBC Photonics SP-MM85030D-GP -SFP+

 

dmesg:

 

Jan  3 18:01:58 ceph6 kernel: [  739.510036] i40e: Intel(R) 40-10 Gigabit Ethernet Connection Network Driver - version 1.5.25

Jan  3 18:01:58 ceph6 kernel: [  739.510041] i40e: Copyright(c) 2013 - 2016 Intel Corporation.

Jan  3 18:01:58 ceph6 kernel: [  739.527324] i40e 0000:04:00.0: fw 5.0.40043 api 1.5 nvm 5.04 0x800024c6 0.0.0

Jan  3 18:01:58 ceph6 kernel: [  739.765165] i40e 0000:04:00.0: MAC address: 3c:fd:fe:a2:19:54

Jan  3 18:01:58 ceph6 kernel: [  739.789909] i40e 0000:04:00.0: AQ command Config VSI BW allocation per TC failed = 14

Jan  3 18:01:58 ceph6 kernel: [  739.789912] i40e 0000:04:00.0: Failed configuring TC map 255 for VSI 390

Jan  3 18:01:58 ceph6 kernel: [  739.789915] i40e 0000:04:00.0: failed to configure TCs for main VSI tc_map 0x000000ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL

Jan  3 18:01:59 ceph6 kernel: [  739.833189] divide error: 0000 [#1] SMP

Jan  3 18:01:59 ceph6 kernel: [  739.833324] Modules linked in: i40e(OE+) vxlan ip6_udp_tunnel udp_tunnel intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ipmi_ssif kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni

_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper input_leds joydev sb_edac cryptd serio_raw edac_core ipmi_si mei_me 8250_fintek mei ipmi_msghandler shpchp ioatdma lpc_ich mac_hid autofs4 hid_generic usbhid hid psmouse isci

igb ahci libsas libahci dca ptp scsi_transport_sas megaraid_sas pps_core i2c_algo_bit wmi fjes

Jan  3 18:01:59 ceph6 kernel: [  739.835034] CPU: 0 PID: 2386 Comm: insmod Tainted: G           OE   4.4.0-57-generic #78-Ubuntu

Jan  3 18:01:59 ceph6 kernel: [  739.835306] Hardware name: Supermicro X9DRW/X9DRW, BIOS 3.0c 03/24/2014

Jan  3 18:01:59 ceph6 kernel: [  739.835518] task: ffff880868b9f000 ti: ffff88046c1c0000 task.ti: ffff88046c1c0000

Jan  3 18:01:59 ceph6 kernel: [  739.835754] RIP: 0010:[<ffffffffc03a4faf>]  [<ffffffffc03a4faf>] i40e_pf_config_rss+0x1ef/0x230 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  739.836059] RSP: 0018:ffff88046c1c37a0  EFLAGS: 00010246

Jan  3 18:01:59 ceph6 kernel: [  739.836227] RAX: 0000000000000000 RBX: ffff88086bd33c00 RCX: 0000000000000000

Jan  3 18:01:59 ceph6 kernel: [  739.836452] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000200

Jan  3 18:01:59 ceph6 kernel: [  739.836679] RBP: ffff88046c1c3808 R08: ffff88046fc1a120 R09: ffff88046f8032c0

Jan  3 18:01:59 ceph6 kernel: [  739.836904] R10: ffff88086bd33c00 R11: 0000000000000000 R12: 0000000000000000

Jan  3 18:01:59 ceph6 kernel: [  739.837130] R13: ffff88046da74008 R14: ffff88046c099000 R15: ffff88046da74000

Jan  3 18:01:59 ceph6 kernel: [  739.837359] FS:  00007f5815768700(0000) GS:ffff88046fc00000(0000) knlGS:0000000000000000

Jan  3 18:01:59 ceph6 kernel: [  739.837615] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Jan  3 18:01:59 ceph6 kernel: [  739.837796] CR2: 00007fe8a4fcc13c CR3: 000000046a7f2000 CR4: 00000000000406f0

Jan  3 18:01:59 ceph6 kernel: [  739.838022] Stack:

Jan  3 18:01:59 ceph6 kernel: [  739.838085]  0000000000000005 00000000001c0ac0 00000000000e0000 ffff88046c1c37e8

Jan  3 18:01:59 ceph6 kernel: [  739.838335]  ffffffffc03b9e39 ffff88046da74f28 ffff88046da74008 00000000ffd84a52

Jan  3 18:01:59 ceph6 kernel: [  739.847061]  ffff88046da74000 0000000000000000 ffff88046da74008 0000000000000000

Jan  3 18:01:59 ceph6 kernel: [  739.855800] Call Trace:

Jan  3 18:01:59 ceph6 kernel: [  739.864529]  [<ffffffffc03b9e39>] ? i40e_write_rx_ctl+0x39/0x90 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  739.873487]  [<ffffffffc03a7ba8>] i40e_setup_pf_switch+0x308/0x590 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  739.882566]  [<ffffffffc03ab5c0>] i40e_probe.part.58+0xd50/0x1be0 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  739.891572]  [<ffffffff813fcbdd>] ? radix_tree_lookup+0xd/0x10

Jan  3 18:01:59 ceph6 kernel: [  739.900540]  [<ffffffff810da827>] ? irq_to_desc+0x17/0x20

Jan  3 18:01:59 ceph6 kernel: [  739.909424]  [<ffffffff810de48e>] ? irq_get_irq_data+0xe/0x20

Jan  3 18:01:59 ceph6 kernel: [  739.918278]  [<ffffffff81057695>] ? mp_map_pin_to_irq+0xb5/0x300

Jan  3 18:01:59 ceph6 kernel: [  739.927153]  [<ffffffff814b55cc>] ? acpi_ut_remove_reference+0x2e/0x31

Jan  3 18:01:59 ceph6 kernel: [  739.936072]  [<ffffffff811ed69b>] ? __slab_free+0xcb/0x2c0

Jan  3 18:01:59 ceph6 kernel: [  739.944972]  [<ffffffff81057e98>] ? mp_map_gsi_to_irq+0x98/0xc0

Jan  3 18:01:59 ceph6 kernel: [  739.953757]  [<ffffffff8104f72e>] ? acpi_register_gsi_ioapic+0xbe/0x180

Jan  3 18:01:59 ceph6 kernel: [  739.962466]  [<ffffffff81495726>] ? acpi_pci_irq_enable+0x1bf/0x1e4

Jan  3 18:01:59 ceph6 kernel: [  739.971114]  [<ffffffff817058c8>] ? pci_conf1_read+0xb8/0xf0

Jan  3 18:01:59 ceph6 kernel: [  739.979739]  [<ffffffff817093e3>] ? raw_pci_read+0x23/0x40

Jan  3 18:01:59 ceph6 kernel: [  739.988340]  [<ffffffff8143bc3c>] ? pci_bus_read_config_word+0x9c/0xb0

Jan  3 18:01:59 ceph6 kernel: [  739.996976]  [<ffffffff81444ced>] ? do_pci_enable_device+0xdd/0x110

Jan  3 18:01:59 ceph6 kernel: [  740.005459]  [<ffffffff81446104>] ? pci_enable_device_flags+0xe4/0x130

Jan  3 18:01:59 ceph6 kernel: [  740.013867]  [<ffffffffc03ac46e>] i40e_probe+0x1e/0x30 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  740.022228]  [<ffffffff81447585>] local_pci_probe+0x45/0xa0

Jan  3 18:01:59 ceph6 kernel: [  740.030571]  [<ffffffff814489c3>] pci_device_probe+0x103/0x150

Jan  3 18:01:59 ceph6 kernel: [  740.038806]  [<ffffffff8155a7a2>] driver_probe_device+0x222/0x4a0

Jan  3 18:01:59 ceph6 kernel: [  740.046946]  [<ffffffff8155aaa4>] __driver_attach+0x84/0x90

Jan  3 18:01:59 ceph6 kernel: [  740.055009]  [<ffffffff8155aa20>] ? driver_probe_device+0x4a0/0x4a0

Jan  3 18:01:59 ceph6 kernel: [  740.063118]  [<ffffffff815583cc>] bus_for_each_dev+0x6c/0xc0

Jan  3 18:01:59 ceph6 kernel: [  740.071205]  [<ffffffff81559f5e>] driver_attach+0x1e/0x20

Jan  3 18:01:59 ceph6 kernel: [  740.079029]  [<ffffffff81559a9b>] bus_add_driver+0x1eb/0x280

Jan  3 18:01:59 ceph6 kernel: [  740.086629]  [<ffffffffc01ea000>] ? 0xffffffffc01ea000

Jan  3 18:01:59 ceph6 kernel: [  740.093977]  [<ffffffff8155b3b0>] driver_register+0x60/0xe0

Jan  3 18:01:59 ceph6 kernel: [  740.101076]  [<ffffffff81446eac>] __pci_register_driver+0x4c/0x50

Jan  3 18:01:59 ceph6 kernel: [  740.107997]  [<ffffffffc01ea0a6>] i40e_init_module+0xa6/0x1000 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  740.114831]  [<ffffffff81002123>] do_one_initcall+0xb3/0x200

Jan  3 18:01:59 ceph6 kernel: [  740.121523]  [<ffffffff811ecbd3>] ? kmem_cache_alloc_trace+0x183/0x1f0

Jan  3 18:01:59 ceph6 kernel: [  740.128183]  [<ffffffff8118d9f3>] do_init_module+0x5f/0x1cf

Jan  3 18:01:59 ceph6 kernel: [  740.134706]  [<ffffffff8110a98f>] load_module+0x166f/0x1c10

Jan  3 18:01:59 ceph6 kernel: [  740.141064]  [<ffffffff81106f30>] ? __symbol_put+0x60/0x60

Jan  3 18:01:59 ceph6 kernel: [  740.147352]  [<ffffffff81214760>] ? kernel_read+0x50/0x80

Jan  3 18:01:59 ceph6 kernel: [  740.153662]  [<ffffffff8110b174>] SYSC_finit_module+0xb4/0xe0

Jan  3 18:01:59 ceph6 kernel: [  740.159956]  [<ffffffff8110b1be>] SyS_finit_module+0xe/0x10

Jan  3 18:01:59 ceph6 kernel: [  740.166220]  [<ffffffff818374f2>] entry_SYSCALL_64_fastpath+0x16/0x71

Jan  3 18:01:59 ceph6 kernel: [  740.172496] Code: 40 5b 41 5c 41 5d 41 5e 41 5f 5d c3 41 0f b7 be a8 04 00 00 31 c9 41 0f b7 b6 aa 04 00 00 66 85 ff 0f 84 5a ff ff ff 89 c8 31 d2 <66> f7 f6 88 14 0b 48 83 c1 01 66 39 cf 77 ed e9 42 ff ff ff 4c

Jan  3 18:01:59 ceph6 kernel: [  740.185825] RIP  [<ffffffffc03a4faf>] i40e_pf_config_rss+0x1ef/0x230 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  740.192377]  RSP <ffff88046c1c37a0>

Jan  3 18:01:59 ceph6 kernel: [  740.215988] ---[ end trace ab2ce900f55f1c7a ]---

 

After that one of the interfaces appears in the system, but it's unaccesible:

root@ceph6:~# ip link set up eth2

RTNETLINK answers: Invalid argument

 

 

Kind regards,

Dominik

can't upgrade f/w of XL710 - nvmupdate64e returns Access error

$
0
0

Hi all,

I tried tp upgrade the fw of xl710..

systems is Debian 8.6

root@D2E:~/XL710/Linux_x64# uname -r

3.16.0-4-amd64

DPDK 16.04

Any idea ?

Thanks

Lior

 

 

 

root@D2E:~/XL710/Linux_x64# ./nvmupdate64e

 

 

Intel(R) Ethernet NVM Update Tool

NVMUpdate version 1.26.17.11

Copyright (C) 2013 - 2016 Intel Corporation.

 

 

 

 

WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update.

Inventory in progress. Please wait [**........]

 

 

 

 

Num Description                            Device-Id B:D   Adapter Status

=== ====================================== ========= ===== ====================

01) Intel(R) I350 Gigabit Network Connecti 8086-1521 04:00 Update not available

02) Intel(R) Ethernet I/O Module XL710-Q2  8086-1583 02:00 Access error       

03) Intel(R) Ethernet Converged Network Ad 8086-1572 06:00 Access error       

 

 

 

 

Tool execution completed with the following status: Device not found

Press any key to exit.

Viewing all 4405 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>