Menu
▾
▴
e1000-devel — Discussion of the Intel Ethernet out-of-tree drivers
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
|
Mar
(1) |
Apr
(9) |
May
(3) |
Jun
|
Jul
(3) |
Aug
(6) |
Sep
|
Oct
(7) |
Nov
|
Dec
|
| 2004 |
Jan
|
Feb
(5) |
Mar
(10) |
Apr
(2) |
May
(22) |
Jun
(8) |
Jul
(4) |
Aug
(8) |
Sep
(3) |
Oct
|
Nov
(36) |
Dec
(52) |
| 2005 |
Jan
(9) |
Feb
(13) |
Mar
(9) |
Apr
|
May
(14) |
Jun
(5) |
Jul
(20) |
Aug
(31) |
Sep
(2) |
Oct
(3) |
Nov
(18) |
Dec
(18) |
| 2006 |
Jan
(36) |
Feb
(16) |
Mar
(76) |
Apr
(78) |
May
(32) |
Jun
(30) |
Jul
(67) |
Aug
(43) |
Sep
(54) |
Oct
(116) |
Nov
(223) |
Dec
(158) |
| 2007 |
Jan
(180) |
Feb
(71) |
Mar
(110) |
Apr
(114) |
May
(203) |
Jun
(100) |
Jul
(238) |
Aug
(191) |
Sep
(177) |
Oct
(171) |
Nov
(211) |
Dec
(159) |
| 2008 |
Jan
(227) |
Feb
(288) |
Mar
(197) |
Apr
(253) |
May
(132) |
Jun
(152) |
Jul
(109) |
Aug
(143) |
Sep
(157) |
Oct
(198) |
Nov
(121) |
Dec
(147) |
| 2009 |
Jan
(105) |
Feb
(61) |
Mar
(191) |
Apr
(161) |
May
(118) |
Jun
(172) |
Jul
(166) |
Aug
(67) |
Sep
(86) |
Oct
(79) |
Nov
(118) |
Dec
(181) |
| 2010 |
Jan
(136) |
Feb
(154) |
Mar
(92) |
Apr
(83) |
May
(101) |
Jun
(66) |
Jul
(118) |
Aug
(78) |
Sep
(134) |
Oct
(131) |
Nov
(132) |
Dec
(104) |
| 2011 |
Jan
(79) |
Feb
(104) |
Mar
(144) |
Apr
(145) |
May
(130) |
Jun
(169) |
Jul
(146) |
Aug
(76) |
Sep
(113) |
Oct
(82) |
Nov
(145) |
Dec
(122) |
| 2012 |
Jan
(132) |
Feb
(106) |
Mar
(145) |
Apr
(238) |
May
(140) |
Jun
(162) |
Jul
(166) |
Aug
(147) |
Sep
(80) |
Oct
(148) |
Nov
(192) |
Dec
(90) |
| 2013 |
Jan
(139) |
Feb
(162) |
Mar
(174) |
Apr
(81) |
May
(261) |
Jun
(301) |
Jul
(106) |
Aug
(175) |
Sep
(305) |
Oct
(222) |
Nov
(95) |
Dec
(120) |
| 2014 |
Jan
(196) |
Feb
(171) |
Mar
(146) |
Apr
(118) |
May
(127) |
Jun
(93) |
Jul
(175) |
Aug
(66) |
Sep
(85) |
Oct
(120) |
Nov
(81) |
Dec
(192) |
| 2015 |
Jan
(141) |
Feb
(133) |
Mar
(189) |
Apr
(126) |
May
(59) |
Jun
(117) |
Jul
(56) |
Aug
(97) |
Sep
(44) |
Oct
(48) |
Nov
(33) |
Dec
(87) |
| 2016 |
Jan
(37) |
Feb
(56) |
Mar
(72) |
Apr
(65) |
May
(66) |
Jun
(65) |
Jul
(98) |
Aug
(54) |
Sep
(84) |
Oct
(68) |
Nov
(69) |
Dec
(60) |
| 2017 |
Jan
(30) |
Feb
(38) |
Mar
(53) |
Apr
(6) |
May
(2) |
Jun
(5) |
Jul
(15) |
Aug
(15) |
Sep
(7) |
Oct
(18) |
Nov
(23) |
Dec
(6) |
| 2018 |
Jan
(39) |
Feb
(5) |
Mar
(34) |
Apr
(26) |
May
(27) |
Jun
(5) |
Jul
(12) |
Aug
(4) |
Sep
|
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2019 |
Jan
(7) |
Feb
(10) |
Mar
(21) |
Apr
(26) |
May
(4) |
Jun
(5) |
Jul
(11) |
Aug
(6) |
Sep
(7) |
Oct
(13) |
Nov
(3) |
Dec
(17) |
| 2020 |
Jan
|
Feb
(3) |
Mar
(3) |
Apr
(5) |
May
(2) |
Jun
(5) |
Jul
|
Aug
|
Sep
(6) |
Oct
(7) |
Nov
(2) |
Dec
(7) |
| 2021 |
Jan
(9) |
Feb
(10) |
Mar
(18) |
Apr
(1) |
May
(3) |
Jun
|
Jul
(16) |
Aug
(2) |
Sep
|
Oct
|
Nov
(9) |
Dec
(2) |
| 2022 |
Jan
(3) |
Feb
|
Mar
(9) |
Apr
(8) |
May
(5) |
Jun
(6) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(7) |
Dec
(2) |
| 2023 |
Jan
(7) |
Feb
(2) |
Mar
(6) |
Apr
|
May
(4) |
Jun
(2) |
Jul
(4) |
Aug
(3) |
Sep
(4) |
Oct
(2) |
Nov
(4) |
Dec
(10) |
| 2024 |
Jan
(4) |
Feb
(2) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
1
(1) |
2
|
3
|
4
|
5
(2) |
|
6
|
7
|
8
(4) |
9
(1) |
10
(4) |
11
|
12
|
|
13
|
14
(5) |
15
(5) |
16
(6) |
17
(1) |
18
(3) |
19
|
|
20
|
21
(4) |
22
(2) |
23
|
24
(2) |
25
(2) |
26
(1) |
|
27
|
28
(1) |
29
|
30
|
|
|
|
|
From: Christian R. <id...@qa...> - 2015-09-28 14:53:59
|
And there we go: [77571.409182] i40e 0000:02:00.1: TX driver issue detected, PF reset issued [77572.245943] bond0: link status up again after 0 ms for interface eth1 [94412.738896] i40e 0000:02:00.1: TX driver issue detected, PF reset issued [94413.569379] bond0: link status up again after 0 ms for interface eth1 [94516.443592] i40e 0000:02:00.1: TX driver issue detected, PF reset issued [94516.718341] bond0: link status up again after 0 ms for interface eth1 [96850.580882] i40e 0000:02:00.0: TX driver issue detected, PF reset issued [96851.036998] bond0: link status up again after 0 ms for interface eth0 [96939.474122] i40e 0000:02:00.1: TX driver issue detected, PF reset issued [96940.217799] bond0: link status up again after 0 ms for interface eth1 [96945.007365] i40e 0000:02:00.1: TX driver issue detected, PF reset issued [96945.225029] bond0: link status up again after 0 ms for interface eth1 [96965.362669] i40e 0000:02:00.1: TX driver issue detected, PF reset issued [96966.255350] bond0: link status up again after 0 ms for interface eth1 [99844.991331] i40e 0000:02:00.0: TX driver issue detected, PF reset issued [99845.360288] bond0: link status up again after 0 ms for interface eth0 [159908.054220] i40e 0000:02:00.1: TX driver issue detected, PF reset issued [159909.165679] bond0: link status up again after 0 ms for interface eth1 [329531.138706] i40e 0000:02:00.1: TX driver issue detected, PF reset issued [329532.167421] bond0: link status up again after 0 ms for interface eth1 On 2015-09-25 16:19, Christian Ruppert wrote: > Hi, > > the card came back and I had to flash it again but it worked perfectly > fine this time :) > So I setup a new Kernel (3.18.20) and the most recent i40e driver > (1.3.39.1) and removed the previous workaround to disable ntuples on > both interfaces. So basically a vanilla setup. > That host is up for several hours no and there was no spam so far and > only one reset yet: > Sep 25 12:38:54 somehost kernel: [77571.409182] i40e 0000:02:00.1: TX > driver issue detected, PF reset issued > Sep 25 12:38:55 somehost kernel: [77572.245943] bond0: link status up > again after 0 ms for interface eth1 > > and here's the requested dmesg again: > [ 0.000000] Initializing cgroup subsys cpuset > [ 0.000000] Initializing cgroup subsys cpu > [ 0.000000] Initializing cgroup subsys cpuacct > [ 0.000000] Linux version 3.18.20 (fud@somehost) (gcc version 4.7.2 > (Debian 4.7.2-5) ) #1 SMP Wed Aug 26 14:25:15 CEST 2015 > [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.18.20 > root=UUID=ea7a13a2-a96b-4165-801a-119b0f0d9b8f ro ipv6.disable=1 > intel_pstate=disable earlyprintk=ttyS0,115200,keep intel_iommu=off > [ 0.000000] e820: BIOS-provided physical RAM map: > [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000099bff] > usable > [ 0.000000] BIOS-e820: [mem 0x0000000000099c00-0x000000000009ffff] > reserved > [ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] > reserved > [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000becc8fff] > usable > [ 0.000000] BIOS-e820: [mem 0x00000000becc9000-0x00000000bed0bfff] > ACPI NVS > [ 0.000000] BIOS-e820: [mem 0x00000000bed0c000-0x00000000ce491fff] > usable > [ 0.000000] BIOS-e820: [mem 0x00000000ce492000-0x00000000ce534fff] > reserved > [ 0.000000] BIOS-e820: [mem 0x00000000ce535000-0x00000000ce5c6fff] > usable > [ 0.000000] BIOS-e820: [mem 0x00000000ce5c7000-0x00000000ce68bfff] > ACPI NVS > [ 0.000000] BIOS-e820: [mem 0x00000000ce68c000-0x00000000cf7fefff] > reserved > [ 0.000000] BIOS-e820: [mem 0x00000000cf7ff000-0x00000000cf7fffff] > usable > [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] > reserved > [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] > reserved > [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] > reserved > [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] > reserved > [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] > reserved > [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] > reserved > [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000082fffffff] > usable > [ 0.000000] console [earlyser0] enabled > [ 0.000000] NX (Execute Disable) protection: active > [ 0.000000] SMBIOS 2.7 present. > [ 0.000000] DMI: Supermicro X9SCL/X9SCM/X9SCL/X9SCM, BIOS 2.2 > 02/20/2015 > [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> > reserved > [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable > [ 0.000000] AGP: No AGP bridge found > [ 0.000000] e820: last_pfn = 0x830000 max_arch_pfn = 0x400000000 > [ 0.000000] MTRR default type: uncachable > [ 0.000000] MTRR fixed ranges enabled: > [ 0.000000] 00000-9FFFF write-back > [ 0.000000] A0000-BFFFF uncachable > [ 0.000000] C0000-CBFFF write-protect > [ 0.000000] CC000-E7FFF uncachable > [ 0.000000] E8000-FFFFF write-protect > [ 0.000000] MTRR variable ranges enabled: > [ 0.000000] 0 base 000000000 mask 800000000 write-back > [ 0.000000] 1 base 800000000 mask FE0000000 write-back > [ 0.000000] 2 base 820000000 mask FF0000000 write-back > [ 0.000000] 3 base 0E0000000 mask FE0000000 uncachable > [ 0.000000] 4 base 0D0000000 mask FF0000000 uncachable > [ 0.000000] 5 disabled > [ 0.000000] 6 disabled > [ 0.000000] 7 disabled > [ 0.000000] 8 disabled > [ 0.000000] 9 disabled > [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new > 0x7010600070106 > [ 0.000000] e820: update [mem 0xd0000000-0xffffffff] usable ==> > reserved > [ 0.000000] e820: last_pfn = 0xcf800 max_arch_pfn = 0x400000000 > [ 0.000000] found SMP MP-table at [mem 0x000fd7b0-0x000fd7bf] > mapped at [ffff8800000fd7b0] > [ 0.000000] Base memory trampoline at [ffff880000093000] 93000 size > 24576 > [ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff] > [ 0.000000] [mem 0x00000000-0x000fffff] page 4k > [ 0.000000] BRK [0x01b02000, 0x01b02fff] PGTABLE > [ 0.000000] BRK [0x01b03000, 0x01b03fff] PGTABLE > [ 0.000000] BRK [0x01b04000, 0x01b04fff] PGTABLE > [ 0.000000] init_memory_mapping: [mem 0x82fe00000-0x82fffffff] > [ 0.000000] [mem 0x82fe00000-0x82fffffff] page 2M > [ 0.000000] BRK [0x01b05000, 0x01b05fff] PGTABLE > [ 0.000000] init_memory_mapping: [mem 0x82c000000-0x82fdfffff] > [ 0.000000] [mem 0x82c000000-0x82fdfffff] page 2M > [ 0.000000] init_memory_mapping: [mem 0x800000000-0x82bffffff] > [ 0.000000] [mem 0x800000000-0x82bffffff] page 2M > [ 0.000000] init_memory_mapping: [mem 0x00100000-0xbecc8fff] > [ 0.000000] [mem 0x00100000-0x001fffff] page 4k > [ 0.000000] [mem 0x00200000-0xbebfffff] page 2M > [ 0.000000] [mem 0xbec00000-0xbecc8fff] page 4k > [ 0.000000] init_memory_mapping: [mem 0xbed0c000-0xce491fff] > [ 0.000000] [mem 0xbed0c000-0xbedfffff] page 4k > [ 0.000000] [mem 0xbee00000-0xce3fffff] page 2M > [ 0.000000] [mem 0xce400000-0xce491fff] page 4k > [ 0.000000] BRK [0x01b06000, 0x01b06fff] PGTABLE > [ 0.000000] BRK [0x01b07000, 0x01b07fff] PGTABLE > [ 0.000000] init_memory_mapping: [mem 0xce535000-0xce5c6fff] > [ 0.000000] [mem 0xce535000-0xce5c6fff] page 4k > [ 0.000000] init_memory_mapping: [mem 0xcf7ff000-0xcf7fffff] > [ 0.000000] [mem 0xcf7ff000-0xcf7fffff] page 4k > [ 0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff] > [ 0.000000] [mem 0x100000000-0x7ffffffff] page 2M > [ 0.000000] RAMDISK: [mem 0x360c0000-0x37057fff] > [ 0.000000] ACPI: Early table checksum verification disabled > [ 0.000000] ACPI: RSDP 0x00000000000F0490 000024 (v02 SUPERM) > [ 0.000000] ACPI: XSDT 0x00000000CE64F088 00008C (v01 SUPERM > SMCI--MB 00000001 AMI 00010013) > [ 0.000000] ACPI: FACP 0x00000000CE65A210 00010C (v05 SUPERM > SMCI--MB 00000001 AMI 00010013) > [ 0.000000] ACPI: DSDT 0x00000000CE64F1A8 00B068 (v02 SUPERM > SMCI--MB 00000000 INTL 20051117) > [ 0.000000] ACPI: FACS 0x00000000CE68A080 000040 > [ 0.000000] ACPI: APIC 0x00000000CE65A320 000092 (v03 SUPERM > SMCI--MB 00000001 AMI 00010013) > [ 0.000000] ACPI: FPDT 0x00000000CE65A3B8 000044 (v01 SUPERM > SMCI--MB 00000001 AMI 00010013) > [ 0.000000] ACPI: MCFG 0x00000000CE65A400 00003C (v01 SUPERM > SMCI--MB 00000001 MSFT 00000097) > [ 0.000000] ACPI: HPET 0x00000000CE65A440 000038 (v01 SUPERM > SMCI--MB 00000001 AMI. 00000005) > [ 0.000000] ACPI: SSDT 0x00000000CE65A478 000397 (v01 SataRe > SataTabl 00001000 INTL 20091112) > [ 0.000000] ACPI: SPMI 0x00000000CE65A810 000040 (v05 A M I > OEMSPMI 00000000 AMI. 00000000) > [ 0.000000] ACPI: SSDT 0x00000000CE65A850 0009A4 (v01 PmRef > Cpu0Ist 00003000 INTL 20051117) > [ 0.000000] ACPI: SSDT 0x00000000CE65B1F8 000B18 (v01 PmRef CpuPm > 00003000 INTL 20051117) > [ 0.000000] ACPI: EINJ 0x00000000CE65BD10 000130 (v01 AMI AMI > EINJ 00000000 00000000) > [ 0.000000] ACPI: ERST 0x00000000CE65BE40 000210 (v01 AMIER AMI > ERST 00000000 00000000) > [ 0.000000] ACPI: HEST 0x00000000CE65C050 0000A8 (v01 AMI AMI > HEST 00000000 00000000) > [ 0.000000] ACPI: BERT 0x00000000CE65C0F8 000030 (v01 AMI AMI > BERT 00000000 00000000) > [ 0.000000] ACPI: Local APIC address 0xfee00000 > [ 0.000000] No NUMA configuration found > [ 0.000000] Faking a node at [mem > 0x0000000000000000-0x000000082fffffff] > [ 0.000000] NODE_DATA(0) allocated [mem 0x82ffdc000-0x82ffdffff] > [ 0.000000] [ffffea0000000000-ffffea001cbfffff] PMD -> > [ffff88080f600000-ffff88082b7fffff] on node 0 > [ 0.000000] Zone ranges: > [ 0.000000] DMA [mem 0x00001000-0x00ffffff] > [ 0.000000] DMA32 [mem 0x01000000-0xffffffff] > [ 0.000000] Normal [mem 0x100000000-0x82fffffff] > [ 0.000000] Movable zone start for each node > [ 0.000000] Early memory node ranges > [ 0.000000] node 0: [mem 0x00001000-0x00098fff] > [ 0.000000] node 0: [mem 0x00100000-0xbecc8fff] > [ 0.000000] node 0: [mem 0xbed0c000-0xce491fff] > [ 0.000000] node 0: [mem 0xce535000-0xce5c6fff] > [ 0.000000] node 0: [mem 0xcf7ff000-0xcf7fffff] > [ 0.000000] node 0: [mem 0x100000000-0x82fffffff] > [ 0.000000] Initmem setup node 0 [mem 0x00001000-0x82fffffff] > [ 0.000000] On node 0 totalpages: 8381562 > [ 0.000000] DMA zone: 56 pages used for memmap > [ 0.000000] DMA zone: 21 pages reserved > [ 0.000000] DMA zone: 3992 pages, LIFO batch:0 > [ 0.000000] DMA32 zone: 11498 pages used for memmap > [ 0.000000] DMA32 zone: 840930 pages, LIFO batch:31 > [ 0.000000] Normal zone: 103040 pages used for memmap > [ 0.000000] Normal zone: 7536640 pages, LIFO batch:31 > [ 0.000000] ACPI: PM-Timer IO Port: 0x408 > [ 0.000000] ACPI: Local APIC address 0xfee00000 > [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled) > [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) > [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) > [ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, > GSI 0-23 > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high > level) > [ 0.000000] ACPI: IRQ0 used by override. > [ 0.000000] ACPI: IRQ9 used by override. > [ 0.000000] Using ACPI (MADT) for SMP configuration information > [ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000 > [ 0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs > [ 0.000000] PM: Registered nosave memory: [mem > 0x00000000-0x00000fff] > [ 0.000000] PM: Registered nosave memory: [mem > 0x00099000-0x00099fff] > [ 0.000000] PM: Registered nosave memory: [mem > 0x0009a000-0x0009ffff] > [ 0.000000] PM: Registered nosave memory: [mem > 0x000a0000-0x000dffff] > [ 0.000000] PM: Registered nosave memory: [mem > 0x000e0000-0x000fffff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xbecc9000-0xbed0bfff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xce492000-0xce534fff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xce5c7000-0xce68bfff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xce68c000-0xcf7fefff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xcf800000-0xdfffffff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xe0000000-0xefffffff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xf0000000-0xfebfffff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xfec00000-0xfec00fff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xfec01000-0xfecfffff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xfed00000-0xfed03fff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xfed04000-0xfed1bfff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xfed1c000-0xfed1ffff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xfed20000-0xfedfffff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xfee00000-0xfee00fff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xfee01000-0xfeffffff] > [ 0.000000] PM: Registered nosave memory: [mem > 0xff000000-0xffffffff] > [ 0.000000] e820: [mem 0xcf800000-0xdfffffff] available for PCI > devices > [ 0.000000] Booting paravirtualized kernel on bare hardware > [ 0.000000] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 > nr_cpu_ids:8 nr_node_ids:1 > [ 0.000000] PERCPU: Embedded 29 pages/cpu @ffff88082fc00000 s80960 > r8192 d29632 u262144 > [ 0.000000] pcpu-alloc: s80960 r8192 d29632 u262144 alloc=1*2097152 > [ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 > [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. > Total pages: 8266947 > [ 0.000000] Policy zone: Normal > [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.18.20 > root=UUID=ea7a13a2-a96b-4165-801a-119b0f0d9b8f ro ipv6.disable=1 > intel_pstate=disable earlyprintk=ttyS0,115200,keep intel_iommu=off > [ 0.000000] Intel-IOMMU: disabled > [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) > [ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340 using > standard form > [ 0.000000] AGP: Checking aperture... > [ 0.000000] AGP: No AGP bridge found > [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area > [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - > bailing! > [ 0.000000] Memory: 32970712K/33526248K available (5512K kernel > code, 966K rwdata, 1832K rodata, 1228K init, 852K bss, 555536K > reserved) > [ 0.000000] Hierarchical RCU implementation. > [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled. > [ 0.000000] RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8. > [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, > nr_cpu_ids=8 > [ 0.000000] NR_IRQS:33024 nr_irqs:488 0 > [ 0.000000] Console: colour VGA+ 80x25 > [ 0.000000] console [tty0] enabled > [ 0.000000] allocated 134217728 bytes of page_cgroup > [ 0.000000] please try 'cgroup_disable=memory' option if you don't > want memory cgroups > [ 0.000000] hpet clockevent registered > [ 0.000000] tsc: Fast TSC calibration failed > [ 0.000000] tsc: PIT calibration matches HPET. 1 loops > [ 0.000000] tsc: Detected 3499.669 MHz processor > [ 0.000025] Calibrating delay loop (skipped), value calculated > using timer frequency.. 6999.33 BogoMIPS (lpj=13998676) > [ 0.010617] pid_max: default: 32768 minimum: 301 > [ 0.015230] ACPI: Core revision 20140926 > [ 0.024681] ACPI: All ACPI Tables successfully acquired > [ 0.039606] Security Framework initialized > [ 0.043611] AppArmor: AppArmor disabled by boot time parameter > [ 0.049421] Yama: becoming mindful. > [ 0.054266] Dentry cache hash table entries: 4194304 (order: 13, > 33554432 bytes) > [ 0.067119] Inode-cache hash table entries: 2097152 (order: 12, > 16777216 bytes) > [ 0.076825] Mount-cache hash table entries: 65536 (order: 7, 524288 > bytes) > [ 0.083636] Mountpoint-cache hash table entries: 65536 (order: 7, > 524288 bytes) > [ 0.091133] Initializing cgroup subsys memory > [ 0.095401] Initializing cgroup subsys devices > [ 0.099824] Initializing cgroup subsys freezer > [ 0.104249] Initializing cgroup subsys net_cls > [ 0.108676] Initializing cgroup subsys blkio > [ 0.112929] Initializing cgroup subsys perf_event > [ 0.117615] Initializing cgroup subsys net_prio > [ 0.122145] CPU: Physical Processor ID: 0 > [ 0.126120] CPU: Processor Core ID: 0 > [ 0.129769] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' > [ 0.129769] ENERGY_PERF_BIAS: View and update with > x86_energy_perf_policy(8) > [ 0.143037] mce: CPU supports 9 MCE banks > [ 0.146959] CPU0: Thermal monitoring enabled (TM1) > [ 0.151728] process: using mwait in idle threads > [ 0.156328] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8 > [ 0.156328] Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0 > [ 0.168125] Freeing SMP alternatives memory: 20K (ffffffff81a26000 > - ffffffff81a2b000) > [ 0.176733] ftrace: allocating 22083 entries in 87 pages > [ 0.197324] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 > [ 0.242968] smpboot: CPU0: Intel(R) Xeon(R) CPU E3-1270 V2 @ > 3.50GHz (fam: 06, model: 3a, stepping: 09) > [ 0.252247] TSC deadline timer enabled > [ 0.252264] Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge > events, full-width counters, Intel PMU driver. > [ 0.262484] ... version: 3 > [ 0.266477] ... bit width: 48 > [ 0.270555] ... generic registers: 4 > [ 0.274548] ... value mask: 0000ffffffffffff > [ 0.279843] ... max period: 0000ffffffffffff > [ 0.285137] ... fixed-purpose events: 3 > [ 0.289130] ... event mask: 000000070000000f > [ 0.295409] x86: Booting SMP configuration: > [ 0.299494] .... node #0, CPUs: #1 > [ 0.316534] NMI watchdog: enabled on all CPUs, permanently consumes > one hw-PMU counter. > [ 0.324669] #2 #3 #4 #5 #6 #7 > [ 0.407240] x86: Booted up 1 node, 8 CPUs > [ 0.411319] smpboot: Total of 8 processors activated (55994.70 > BogoMIPS) > [ 0.424047] devtmpfs: initialized > [ 0.430926] PM: Registering ACPI NVS region [mem > 0xbecc9000-0xbed0bfff] (274432 bytes) > [ 0.438777] PM: Registering ACPI NVS region [mem > 0xce5c7000-0xce68bfff] (806912 bytes) > [ 0.447304] pinctrl core: initialized pinctrl subsystem > [ 0.452519] NET: Registered protocol family 16 > [ 0.468890] cpuidle: using governor ladder > [ 0.488929] cpuidle: using governor menu > [ 0.492803] ACPI FADT declares the system doesn't support PCIe > ASPM, so disable it > [ 0.500309] ACPI: bus type PCI registered > [ 0.504301] acpiphp: ACPI Hot Plug PCI Controller Driver version: > 0.5 > [ 0.510784] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem > 0xe0000000-0xefffffff] (base 0xe0000000) > [ 0.520010] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in > E820 > [ 0.526980] PCI: Using configuration type 1 for base access > [ 0.544821] ACPI: Added _OSI(Module Device) > [ 0.548905] ACPI: Added _OSI(Processor Device) > [ 0.553330] ACPI: Added _OSI(3.0 _SCP Extensions) > [ 0.558017] ACPI: Added _OSI(Processor Aggregator Device) > [ 0.565243] ACPI: Executed 1 blocks of module-level executable AML > code > [ 0.739624] \_SB_:_OSC invalid UUID > [ 0.739625] _OSC request data:1 1f > [ 0.739811] ACPI: Dynamic OEM Table Load: > [ 0.743707] ACPI: SSDT 0xFFFF880807B5C000 00083B (v01 PmRef > Cpu0Cst 00003001 INTL 20051117) > [ 0.764280] ACPI: Dynamic OEM Table Load: > [ 0.768173] ACPI: SSDT 0xFFFF880807049C00 000303 (v01 PmRef ApIst > 00003000 INTL 20051117) > [ 0.788649] ACPI: Dynamic OEM Table Load: > [ 0.792543] ACPI: SSDT 0xFFFF880807007C00 000119 (v01 PmRef ApCst > 00003000 INTL 20051117) > [ 0.813761] ACPI: Interpreter enabled > [ 0.817329] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep > State [\_S2_] (20140926/hwxface-580) > [ 0.826523] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep > State [\_S3_] (20140926/hwxface-580) > [ 0.835727] ACPI: (supports S0 S1 S4 S5) > [ 0.839628] ACPI: Using IOAPIC for interrupt routing > [ 0.844615] HEST: Table parsing has been initialized. > [ 0.849610] PCI: Using host bridge windows from ACPI; if necessary, > use "pci=nocrs" and report a bug > [ 0.863689] ACPI: Power Resource [FN00] (off) > [ 0.868006] ACPI: Power Resource [FN01] (off) > [ 0.872344] ACPI: Power Resource [FN02] (off) > [ 0.876682] ACPI: Power Resource [FN03] (off) > [ 0.881022] ACPI: Power Resource [FN04] (off) > [ 0.885681] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe]) > [ 0.891767] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM > ClockPM Segments MSI] > [ 0.900002] acpi PNP0A08:00: _OSC: platform does not support > [PCIeHotplug PME] > [ 0.907216] acpi PNP0A08:00: _OSC: OS now controls [AER > PCIeCapability] > [ 0.914173] PCI host bridge to bus 0000:00 > [ 0.918169] pci_bus 0000:00: root bus resource [bus 00-fe] > [ 0.923636] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7] > [ 0.929798] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff] > [ 0.935959] pci_bus 0000:00: root bus resource [mem > 0x000a0000-0x000bffff] > [ 0.942817] pci_bus 0000:00: root bus resource [mem > 0x000cc000-0x000cffff] > [ 0.949673] pci_bus 0000:00: root bus resource [mem > 0x000d0000-0x000d3fff] > [ 0.956530] pci_bus 0000:00: root bus resource [mem > 0x000d4000-0x000d7fff] > [ 0.963386] pci_bus 0000:00: root bus resource [mem > 0x000d8000-0x000dbfff] > [ 0.970243] pci_bus 0000:00: root bus resource [mem > 0x000dc000-0x000dffff] > [ 0.977101] pci_bus 0000:00: root bus resource [mem > 0x000e0000-0x000e3fff] > [ 0.983957] pci_bus 0000:00: root bus resource [mem > 0x000e4000-0x000e7fff] > [ 0.990814] pci_bus 0000:00: root bus resource [mem > 0xd0000000-0xfeafffff] > [ 0.997674] pci 0000:00:00.0: [8086:0158] type 00 class 0x060000 > [ 0.997751] pci 0000:00:01.0: [8086:0151] type 01 class 0x060400 > [ 0.997831] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold > [ 0.997870] pci 0000:00:01.0: System wakeup disabled by ACPI > [ 1.003450] pci 0000:00:01.1: [8086:0155] type 01 class 0x060400 > [ 1.003473] pci 0000:00:01.1: PME# supported from D0 D3hot D3cold > [ 1.003502] pci 0000:00:01.1: System wakeup disabled by ACPI > [ 1.009121] pci 0000:00:19.0: [8086:1502] type 00 class 0x020000 > [ 1.009138] pci 0000:00:19.0: reg 0x10: [mem 0xdfb00000-0xdfb1ffff] > [ 1.009145] pci 0000:00:19.0: reg 0x14: [mem 0xdfb25000-0xdfb25fff] > [ 1.009153] pci 0000:00:19.0: reg 0x18: [io 0xf020-0xf03f] > [ 1.009212] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold > [ 1.009246] pci 0000:00:19.0: System wakeup disabled by ACPI > [ 1.014835] pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320 > [ 1.014854] pci 0000:00:1a.0: reg 0x10: [mem 0xdfb24000-0xdfb243ff] > [ 1.014938] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold > [ 1.014983] pci 0000:00:1a.0: System wakeup disabled by ACPI > [ 1.020571] pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400 > [ 1.020648] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold > [ 1.020686] pci 0000:00:1c.0: System wakeup disabled by ACPI > [ 1.026274] pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400 > [ 1.026351] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold > [ 1.026388] pci 0000:00:1c.4: System wakeup disabled by ACPI > [ 1.031981] pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320 > [ 1.032000] pci 0000:00:1d.0: reg 0x10: [mem 0xdfb23000-0xdfb233ff] > [ 1.032084] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold > [ 1.032129] pci 0000:00:1d.0: System wakeup disabled by ACPI > [ 1.037718] pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401 > [ 1.037791] pci 0000:00:1e.0: System wakeup disabled by ACPI > [ 1.043379] pci 0000:00:1f.0: [8086:1c52] type 00 class 0x060100 > [ 1.043532] pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601 > [ 1.043549] pci 0000:00:1f.2: reg 0x10: [io 0xf070-0xf077] > [ 1.043556] pci 0000:00:1f.2: reg 0x14: [io 0xf060-0xf063] > [ 1.043563] pci 0000:00:1f.2: reg 0x18: [io 0xf050-0xf057] > [ 1.043570] pci 0000:00:1f.2: reg 0x1c: [io 0xf040-0xf043] > [ 1.043577] pci 0000:00:1f.2: reg 0x20: [io 0xf000-0xf01f] > [ 1.043584] pci 0000:00:1f.2: reg 0x24: [mem 0xdfb22000-0xdfb227ff] > [ 1.043625] pci 0000:00:1f.2: PME# supported from D3hot > [ 1.043684] pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500 > [ 1.043697] pci 0000:00:1f.3: reg 0x10: [mem 0xdfb21000-0xdfb210ff > 64bit] > [ 1.043716] pci 0000:00:1f.3: reg 0x20: [io 0x0580-0x059f] > [ 1.043832] pci 0000:00:01.0: PCI bridge to [bus 01] > [ 1.048735] pci 0000:02:00.0: [8086:1572] type 00 class 0x020000 > [ 1.048745] pci 0000:02:00.0: reg 0x10: [mem 0xdd800000-0xddffffff > 64bit pref] > [ 1.048755] pci 0000:02:00.0: reg 0x1c: [mem 0xde808000-0xde80ffff > 64bit pref] > [ 1.048764] pci 0000:02:00.0: reg 0x30: [mem 0xdfa80000-0xdfafffff > pref] > [ 1.048800] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold > [ 1.048818] pci 0000:02:00.0: reg 0x184: [mem 0xde400000-0xde40ffff > 64bit pref] > [ 1.048827] pci 0000:02:00.0: reg 0x190: [mem 0xde910000-0xde913fff > 64bit pref] > [ 1.048862] pci 0000:02:00.1: [8086:1572] type 00 class 0x020000 > [ 1.048872] pci 0000:02:00.1: reg 0x10: [mem 0xdd000000-0xdd7fffff > 64bit pref] > [ 1.048882] pci 0000:02:00.1: reg 0x1c: [mem 0xde800000-0xde807fff > 64bit pref] > [ 1.048891] pci 0000:02:00.1: reg 0x30: [mem 0xdfa00000-0xdfa7ffff > pref] > [ 1.048925] pci 0000:02:00.1: PME# supported from D0 D3hot D3cold > [ 1.048942] pci 0000:02:00.1: reg 0x184: [mem 0xde000000-0xde00ffff > 64bit pref] > [ 1.048951] pci 0000:02:00.1: reg 0x190: [mem 0xde810000-0xde813fff > 64bit pref] > [ 1.056725] pci 0000:00:01.1: PCI bridge to [bus 02-03] > [ 1.061856] pci 0000:00:01.1: bridge window [mem > 0xdfa00000-0xdfafffff] > [ 1.061858] pci 0000:00:01.1: bridge window [mem > 0xdd000000-0xdeafffff 64bit pref] > [ 1.061915] pci 0000:00:1c.0: PCI bridge to [bus 04] > [ 1.066903] pci 0000:05:00.0: [8086:10d3] type 00 class 0x020000 > [ 1.066942] pci 0000:05:00.0: reg 0x10: [mem 0xdf900000-0xdf91ffff] > [ 1.066987] pci 0000:05:00.0: reg 0x18: [io 0xe000-0xe01f] > [ 1.067010] pci 0000:05:00.0: reg 0x1c: [mem 0xdf920000-0xdf923fff] > [ 1.067239] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold > [ 1.067289] pci 0000:05:00.0: System wakeup disabled by ACPI > [ 1.080881] pci 0000:00:1c.4: PCI bridge to [bus 05] > [ 1.085759] pci 0000:00:1c.4: bridge window [io 0xe000-0xefff] > [ 1.085762] pci 0000:00:1c.4: bridge window [mem > 0xdf900000-0xdf9fffff] > [ 1.085807] pci 0000:06:03.0: [102b:0532] type 00 class 0x030000 > [ 1.085822] pci 0000:06:03.0: reg 0x10: [mem 0xdc000000-0xdcffffff > pref] > [ 1.085831] pci 0000:06:03.0: reg 0x14: [mem 0xdf800000-0xdf803fff] > [ 1.085839] pci 0000:06:03.0: reg 0x18: [mem 0xdf000000-0xdf7fffff] > [ 1.085948] pci 0000:00:1e.0: PCI bridge to [bus 06] (subtractive > decode) > [ 1.092645] pci 0000:00:1e.0: bridge window [mem > 0xdf000000-0xdf8fffff] > [ 1.092650] pci 0000:00:1e.0: bridge window [mem > 0xdc000000-0xdcffffff 64bit pref] > [ 1.092651] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] > (subtractive decode) > [ 1.092652] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] > (subtractive decode) > [ 1.092653] pci 0000:00:1e.0: bridge window [mem > 0x000a0000-0x000bffff] (subtractive decode) > [ 1.092655] pci 0000:00:1e.0: bridge window [mem > 0x000cc000-0x000cffff] (subtractive decode) > [ 1.092656] pci 0000:00:1e.0: bridge window [mem > 0x000d0000-0x000d3fff] (subtractive decode) > [ 1.092657] pci 0000:00:1e.0: bridge window [mem > 0x000d4000-0x000d7fff] (subtractive decode) > [ 1.092658] pci 0000:00:1e.0: bridge window [mem > 0x000d8000-0x000dbfff] (subtractive decode) > [ 1.092659] pci 0000:00:1e.0: bridge window [mem > 0x000dc000-0x000dffff] (subtractive decode) > [ 1.092660] pci 0000:00:1e.0: bridge window [mem > 0x000e0000-0x000e3fff] (subtractive decode) > [ 1.092661] pci 0000:00:1e.0: bridge window [mem > 0x000e4000-0x000e7fff] (subtractive decode) > [ 1.092662] pci 0000:00:1e.0: bridge window [mem > 0xd0000000-0xfeafffff] (subtractive decode) > [ 1.092690] acpi PNP0A08:00: Disabling ASPM (FADT indicates it is > unsupported) > [ 1.100314] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 > 14 15) > [ 1.107107] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 10 11 12 > 14 15) > [ 1.113962] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 > 14 15) > [ 1.120818] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 > 14 15) > [ 1.127675] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 10 11 12 > 14 15) > [ 1.134531] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 > 14 15) *0, disabled. > [ 1.142515] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 11 12 > 14 15) *0, disabled. > [ 1.150505] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 > 14 15) > [ 1.157484] ACPI: Enabled 4 GPEs in block 00 to 3F > [ 1.162221] vgaarb: setting as boot device: PCI:0000:06:03.0 > [ 1.167794] vgaarb: device added: > PCI:0000:06:03.0,decodes=io+mem,owns=io+mem,locks=none > [ 1.175867] vgaarb: loaded > [ 1.178556] vgaarb: bridge control possible 0000:06:03.0 > [ 1.183909] PCI: Using ACPI for IRQ routing > [ 1.193792] PCI: pci_cache_line_size set to 64 bytes > [ 1.193833] e820: reserve RAM buffer [mem 0x00099c00-0x0009ffff] > [ 1.193834] e820: reserve RAM buffer [mem 0xbecc9000-0xbfffffff] > [ 1.193835] e820: reserve RAM buffer [mem 0xce492000-0xcfffffff] > [ 1.193836] e820: reserve RAM buffer [mem 0xce5c7000-0xcfffffff] > [ 1.193837] e820: reserve RAM buffer [mem 0xcf800000-0xcfffffff] > [ 1.193935] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0 > [ 1.199994] hpet0: 8 comparators, 64-bit 14.318180 MHz counter > [ 1.207831] Switched to clocksource hpet > [ 1.215086] pnp: PnP ACPI init > [ 1.218096] system 00:00: [mem 0xfed40000-0xfed44fff] has been > reserved > [ 1.224641] system 00:00: Plug and Play ACPI device, IDs PNP0c01 > (active) > [ 1.224688] system 00:01: [io 0x0680-0x069f] has been reserved > [ 1.230542] system 00:01: [io 0x1000-0x100f] has been reserved > [ 1.236442] system 00:01: [io 0xffff] has been reserved > [ 1.241736] system 00:01: [io 0xffff] has been reserved > [ 1.247031] system 00:01: [io 0x0400-0x0453] could not be reserved > [ 1.253282] system 00:01: [io 0x0458-0x047f] has been reserved > [ 1.259182] system 00:01: [io 0x0500-0x057f] has been reserved > [ 1.265084] system 00:01: [io 0x164e-0x164f] has been reserved > [ 1.270987] system 00:01: Plug and Play ACPI device, IDs PNP0c02 > (active) > [ 1.271008] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 > (active) > [ 1.271039] system 00:03: [io 0x0454-0x0457] has been reserved > [ 1.276891] system 00:03: Plug and Play ACPI device, IDs INT3f0d > PNP0c02 (active) > [ 1.276924] system 00:04: [io 0x04d0-0x04d1] has been reserved > [ 1.282792] system 00:04: Plug and Play ACPI device, IDs PNP0c02 > (active) > [ 1.282868] system 00:05: [io 0x0a00-0x0a1f] has been reserved > [ 1.288693] system 00:05: [io 0x0a30-0x0a3f] has been reserved > [ 1.294594] system 00:05: Plug and Play ACPI device, IDs PNP0c02 > (active) > [ 1.294751] pnp 00:06: [dma 0 disabled] > [ 1.294780] pnp 00:06: Plug and Play ACPI device, IDs PNP0501 > (active) > [ 1.294921] pnp 00:07: [dma 0 disabled] > [ 1.294947] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 > (active) > [ 1.295019] system 00:08: [io 0x0b00-0x0b7f] has been reserved > [ 1.300845] system 00:08: Plug and Play ACPI device, IDs PNP0c02 > (active) > [ 1.300958] pnp 00:09: [dma 0 disabled] > [ 1.300985] pnp 00:09: Plug and Play ACPI device, IDs PNP0501 > (active) > [ 1.301064] pnp 00:0a: Plug and Play ACPI device, IDs IPI0001 > (active) > [ 1.301198] system 00:0b: [mem 0xfed1c000-0xfed1ffff] has been > reserved > [ 1.307720] system 00:0b: [mem 0xfed10000-0xfed17fff] has been > reserved > [ 1.314314] system 00:0b: [mem 0xfed18000-0xfed18fff] has been > reserved > [ 1.320909] system 00:0b: [mem 0xfed19000-0xfed19fff] has been > reserved > [ 1.327506] system 00:0b: [mem 0xe0000000-0xefffffff] has been > reserved > [ 1.334102] system 00:0b: [mem 0xfed20000-0xfed3ffff] has been > reserved > [ 1.340701] system 00:0b: [mem 0xfed90000-0xfed93fff] has been > reserved > [ 1.347295] system 00:0b: [mem 0xfed45000-0xfed8ffff] has been > reserved > [ 1.353892] system 00:0b: [mem 0xff000000-0xffffffff] has been > reserved > [ 1.360488] system 00:0b: [mem 0xfee00000-0xfeefffff] could not be > reserved > [ 1.367430] system 00:0b: [mem 0xd0000000-0xd0000fff] has been > reserved > [ 1.374027] system 00:0b: Plug and Play ACPI device, IDs PNP0c02 > (active) > [ 1.374113] pnp: PnP ACPI: found 12 devices > [ 1.384167] pci 0000:00:01.0: PCI bridge to [bus 01] > [ 1.389053] pci 0000:00:01.1: PCI bridge to [bus 02-03] > [ 1.394250] pci 0000:00:01.1: bridge window [mem > 0xdfa00000-0xdfafffff] > [ 1.401020] pci 0000:00:01.1: bridge window [mem > 0xdd000000-0xdeafffff 64bit pref] > [ 1.408745] pci 0000:00:1c.0: PCI bridge to [bus 04] > [ 1.413701] pci 0000:00:1c.4: PCI bridge to [bus 05] > [ 1.418641] pci 0000:00:1c.4: bridge window [io 0xe000-0xefff] > [ 1.424718] pci 0000:00:1c.4: bridge window [mem > 0xdf900000-0xdf9fffff] > [ 1.431489] pci 0000:00:1e.0: PCI bridge to [bus 06] > [ 1.436435] pci 0000:00:1e.0: bridge window [mem > 0xdf000000-0xdf8fffff] > [ 1.443203] pci 0000:00:1e.0: bridge window [mem > 0xdc000000-0xdcffffff 64bit pref] > [ 1.450929] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7] > [ 1.450931] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff] > [ 1.450932] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff] > [ 1.450933] pci_bus 0000:00: resource 7 [mem 0x000cc000-0x000cffff] > [ 1.450934] pci_bus 0000:00: resource 8 [mem 0x000d0000-0x000d3fff] > [ 1.450935] pci_bus 0000:00: resource 9 [mem 0x000d4000-0x000d7fff] > [ 1.450936] pci_bus 0000:00: resource 10 [mem 0x000d8000-0x000dbfff] > [ 1.450937] pci_bus 0000:00: resource 11 [mem 0x000dc000-0x000dffff] > [ 1.450938] pci_bus 0000:00: resource 12 [mem 0x000e0000-0x000e3fff] > [ 1.450939] pci_bus 0000:00: resource 13 [mem 0x000e4000-0x000e7fff] > [ 1.450940] pci_bus 0000:00: resource 14 [mem 0xd0000000-0xfeafffff] > [ 1.450941] pci_bus 0000:02: resource 1 [mem 0xdfa00000-0xdfafffff] > [ 1.450942] pci_bus 0000:02: resource 2 [mem 0xdd000000-0xdeafffff > 64bit pref] > [ 1.450943] pci_bus 0000:05: resource 0 [io 0xe000-0xefff] > [ 1.450944] pci_bus 0000:05: resource 1 [mem 0xdf900000-0xdf9fffff] > [ 1.450946] pci_bus 0000:06: resource 1 [mem 0xdf000000-0xdf8fffff] > [ 1.450947] pci_bus 0000:06: resource 2 [mem 0xdc000000-0xdcffffff > 64bit pref] > [ 1.450948] pci_bus 0000:06: resource 4 [io 0x0000-0x0cf7] > [ 1.450949] pci_bus 0000:06: resource 5 [io 0x0d00-0xffff] > [ 1.450950] pci_bus 0000:06: resource 6 [mem 0x000a0000-0x000bffff] > [ 1.450951] pci_bus 0000:06: resource 7 [mem 0x000cc000-0x000cffff] > [ 1.450952] pci_bus 0000:06: resource 8 [mem 0x000d0000-0x000d3fff] > [ 1.450953] pci_bus 0000:06: resource 9 [mem 0x000d4000-0x000d7fff] > [ 1.450954] pci_bus 0000:06: resource 10 [mem 0x000d8000-0x000dbfff] > [ 1.450955] pci_bus 0000:06: resource 11 [mem 0x000dc000-0x000dffff] > [ 1.450956] pci_bus 0000:06: resource 12 [mem 0x000e0000-0x000e3fff] > [ 1.450957] pci_bus 0000:06: resource 13 [mem 0x000e4000-0x000e7fff] > [ 1.450958] pci_bus 0000:06: resource 14 [mem 0xd0000000-0xfeafffff] > [ 1.451014] NET: Registered protocol family 2 > [ 1.455462] TCP established hash table entries: 262144 (order: 9, > 2097152 bytes) > [ 1.463005] TCP bind hash table entries: 65536 (order: 8, 1048576 > bytes) > [ 1.469713] TCP: Hash tables configured (established 262144 bind > 65536) > [ 1.476246] TCP: reno registered > [ 1.479464] UDP hash table entries: 16384 (order: 7, 524288 bytes) > [ 1.485680] UDP-Lite hash table entries: 16384 (order: 7, 524288 > bytes) > [ 1.492306] NET: Registered protocol family 1 > [ 1.496818] PCI: CLS mismatch (64 != 32), using 64 bytes > [ 1.496823] pci 0000:06:03.0: Video device with shadowed ROM > [ 1.496853] Unpacking initramfs... > [ 1.690454] Freeing initrd memory: 15968K (ffff8800360c0000 - > ffff880037058000) > [ 1.697700] PCI-DMA: Using software bounce buffering for IO > (SWIOTLB) > [ 1.704118] software IO TLB [mem 0xca492000-0xce492000] (64MB) > mapped at [ffff8800ca492000-ffff8800ce491fff] > [ 1.714164] RAPL PMU detected, hw unit 2^-16 Joules, API unit is > 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer > [ 1.724674] microcode: CPU0 sig=0x306a9, pf=0x2, revision=0x1b > [ 1.730426] microcode: CPU1 sig=0x306a9, pf=0x2, revision=0x1b > [ 1.736250] microcode: CPU2 sig=0x306a9, pf=0x2, revision=0x1b > [ 1.750730] microcode: CPU3 sig=0x306a9, pf=0x2, revision=0x1b > [ 1.756546] microcode: CPU4 sig=0x306a9, pf=0x2, revision=0x1b > [ 1.762360] microcode: CPU5 sig=0x306a9, pf=0x2, revision=0x1b > [ 1.768179] microcode: CPU6 sig=0x306a9, pf=0x2, revision=0x1b > [ 1.773991] microcode: CPU7 sig=0x306a9, pf=0x2, revision=0x1b > [ 1.779835] microcode: Microcode Update Driver: v2.00 > <ti...@ai...>, Peter Oruba > [ 1.788826] futex hash table entries: 2048 (order: 5, 131072 bytes) > [ 1.795033] audit: initializing netlink subsys (disabled) > [ 1.800388] audit: type=2000 audit(1443100076.548:1): initialized > [ 1.806664] HugeTLB registered 2 MB page size, pre-allocated 0 pages > [ 1.812933] zpool: loaded > [ 1.815517] zbud: loaded > [ 1.818158] VFS: Disk quotas dquot_6.5.2 > [ 1.821997] Dquot-cache hash table entries: 512 (order 0, 4096 > bytes) > [ 1.828445] msgmni has been set to 32768 > [ 1.832595] alg: No test for stdrng (krng) > [ 1.836625] Block layer SCSI generic (bsg) driver version 0.4 > loaded (major 252) > [ 1.844014] io scheduler noop registered > [ 1.847878] io scheduler deadline registered > [ 1.852131] io scheduler cfq registered (default) > [ 1.856959] pcieport 0000:00:01.0: irq 24 for MSI/MSI-X > [ 1.857070] pcieport 0000:00:01.1: irq 25 for MSI/MSI-X > [ 1.857283] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > [ 1.862775] pciehp: PCI Express Hot Plug Controller Driver version: > 0.4 > [ 1.869391] intel_idle: MWAIT substates: 0x1120 > [ 1.869392] intel_idle: v0.4 model 0x3A > [ 1.869393] intel_idle: lapic_timer_reliable_states 0xffffffff > [ 1.869628] ERST: Error Record Serialization Table (ERST) support > is initialized. > [ 1.877034] pstore: Registered erst as persistent store backend > [ 1.882975] GHES: APEI firmware first mode is enabled by WHEA _OSC. > [ 1.889229] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled > [ 1.915898] 00:06: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) > is a 16550A > [ 1.943574] 00:07: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) > is a 16550A > [ 1.971232] 00:09: ttyS2 at I/O 0x3e8 (irq = 10, base_baud = > 115200) is a 16550A > [ 1.978753] Linux agpgart interface v0.103 > [ 1.982831] i8042: PNP: No PS/2 controller found. Probing ports > directly. > [ 1.992701] serio: i8042 KBD port at 0x60,0x64 irq 1 > [ 1.997575] serio: i8042 AUX port at 0x60,0x64 irq 12 > [ 2.002720] mousedev: PS/2 mouse device common for all mice > [ 2.008232] rtc_cmos 00:02: RTC can wake from S4 > [ 2.012908] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0 > [ 2.018943] rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes > nvram, hpet irqs > [ 2.026564] ledtrig-cpu: registered to indicate activity on CPUs > [ 2.032717] AMD IOMMUv2 driver by Joerg Roedel > <joe...@am...> > [ 2.039059] AMD IOMMUv2 functionality not available on this system > [ 2.045283] TCP: cubic registered > [ 2.048521] IPv6: Loaded, but administratively disabled, reboot > required to enable > [ 2.056071] mip6: Mobile IPv6 > [ 2.059020] mip6: mip6_init: can't add xfrm type(destopt) > [ 2.064404] NET: Registered protocol family 17 > [ 2.068836] mpls_gso: MPLS GSO support > [ 2.072972] registered taskstats version 1 > [ 2.077499] rtc_cmos 00:02: setting system clock to 2015-09-24 > 13:07:57 UTC (1443100077) > [ 2.085560] PM: Hibernation image not present or could not be > loaded. > [ 2.086094] Freeing unused kernel memory: 1228K (ffffffff818f3000 - > ffffffff81a26000) > [ 2.093851] Write protecting the kernel read-only data: 8192k > [ 2.100532] Freeing unused kernel memory: 620K (ffff880001565000 - > ffff880001600000) > [ 2.108556] Freeing unused kernel memory: 216K (ffff8800017ca000 - > ffff880001800000) > [ 2.123393] udevd[94]: starting version 175 > [ 2.131920] pps_core: LinuxPPS API ver. 1 registered > [ 2.136823] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 > Rodolfo Giometti <gio...@li...> > [ 2.147106] PTP clock support registered > [ 2.151071] ACPI: bus type USB registered > [ 2.155038] usbcore: registered new interface driver usbfs > [ 2.160469] usbcore: registered new interface driver hub > [ 2.165787] usbcore: registered new device driver usb > [ 2.171019] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k > [ 2.176789] e1000e: Copyright(c) 1999 - 2014 Intel Corporation. > [ 2.182928] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) > Driver > [ 2.189595] ehci-pci: EHCI PCI platform driver > [ 2.194192] i40e: Intel(R) Ethernet Connection XL710 Network Driver > - version 1.3.39.1 > [ 2.197599] e1000e 0000:00:19.0: Interrupt Throttling Rate > (ints/sec) set to dynamic conservative mode > [ 2.197641] e1000e 0000:00:19.0: irq 26 for MSI/MSI-X > [ 2.198073] thermal LNXTHERM:00: registered as thermal_zone0 > [ 2.198073] ACPI: Thermal Zone [TZ00] (28 C) > [ 2.198216] thermal LNXTHERM:01: registered as thermal_zone1 > [ 2.198216] ACPI: Thermal Zone [TZ01] (30 C) > [ 2.231104] i40e: Copyright (c) 2013 - 2015 Intel Corporation. > [ 2.249391] i40e 0000:02:00.0: fw 4.40.35115 api 1.4 nvm 4.53 > 0x80001dc0 1.123.0 > [ 2.256998] SCSI subsystem initialized > [ 2.261957] libata version 3.00 loaded. > [ 2.453377] e1000e 0000:00:19.0 eth0: registered PHC clock > [ 2.458796] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width > x1) 00:25:90:a8:02:51 > [ 2.466693] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network > Connection > [ 2.473600] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: > FFFFFF-0FF > [ 2.480564] ehci-pci 0000:00:1a.0: EHCI Host Controller > [ 2.480631] e1000e 0000:05:00.0: Interrupt Throttling Rate > (ints/sec) set to dynamic conservative mode > [ 2.480663] e1000e 0000:05:00.0: irq 27 for MSI/MSI-X > [ 2.480665] e1000e 0000:05:00.0: irq 28 for MSI/MSI-X > [ 2.480667] e1000e 0000:05:00.0: irq 29 for MSI/MSI-X > [ 2.495076] ehci-pci 0000:00:1a.0: new USB bus registered, assigned > bus number 1 > [ 2.495874] i40e 0000:02:00.0: MAC address: 3c:fd:fe:9c:56:b8 > [ 2.499857] i40e 0000:02:00.0: SAN MAC: 3c:fd:fe:9c:56:ba > [ 2.513542] ehci-pci 0000:00:1a.0: debug port 2 > [ 2.514095] i40e 0000:02:00.0: irq 30 for MSI/MSI-X > [ 2.514098] i40e 0000:02:00.0: irq 31 for MSI/MSI-X > [ 2.514099] i40e 0000:02:00.0: irq 32 for MSI/MSI-X > [ 2.514101] i40e 0000:02:00.0: irq 33 for MSI/MSI-X > [ 2.514103] i40e 0000:02:00.0: irq 34 for MSI/MSI-X > [ 2.514105] i40e 0000:02:00.0: irq 35 for MSI/MSI-X > [ 2.514107] i40e 0000:02:00.0: irq 36 for MSI/MSI-X > [ 2.514108] i40e 0000:02:00.0: irq 37 for MSI/MSI-X > [ 2.514110] i40e 0000:02:00.0: irq 38 for MSI/MSI-X > [ 2.514111] i40e 0000:02:00.0: irq 39 for MSI/MSI-X > [ 2.514113] i40e 0000:02:00.0: irq 40 for MSI/MSI-X > [ 2.514114] i40e 0000:02:00.0: irq 41 for MSI/MSI-X > [ 2.514116] i40e 0000:02:00.0: irq 42 for MSI/MSI-X > [ 2.514118] i40e 0000:02:00.0: irq 43 for MSI/MSI-X > [ 2.514119] i40e 0000:02:00.0: irq 44 for MSI/MSI-X > [ 2.514121] i40e 0000:02:00.0: irq 45 for MSI/MSI-X > [ 2.514122] i40e 0000:02:00.0: irq 46 for MSI/MSI-X > [ 2.514124] i40e 0000:02:00.0: irq 47 for MSI/MSI-X > [ 2.521951] ehci-pci 0000:00:1a.0: cache line size of 64 is not > supported > [ 2.521964] ehci-pci 0000:00:1a.0: irq 16, io mem 0xdfb24000 > [ 2.537912] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00 > [ 2.543607] usb usb1: New USB device found, idVendor=1d6b, > idProduct=0002 > [ 2.550333] usb usb1: New USB device strings: Mfr=3, Product=2, > SerialNumber=1 > [ 2.557541] usb usb1: Product: EHCI Host Controller > [ 2.562399] usb usb1: Manufacturer: Linux 3.18.20 ehci_hcd > [ 2.568471] usb usb1: SerialNumber: 0000:00:1a.0 > [ 2.573164] hub 1-0:1.0: USB hub found > [ 2.576818] hub 1-0:1.0: 2 ports detected > [ 2.580962] ehci-pci 0000:00:1d.0: EHCI Host Controller > [ 2.586095] ehci-pci 0000:00:1d.0: new USB bus registered, assigned > bus number 2 > [ 2.593480] ehci-pci 0000:00:1d.0: debug port 2 > [ 2.599535] e1000e 0000:05:00.0 eth2: registered PHC clock > [ 2.601911] ehci-pci 0000:00:1d.0: cache line size of 64 is not > supported > [ 2.601922] ehci-pci 0000:00:1d.0: irq 23, io mem 0xdfb23000 > [ 2.610602] e1000e 0000:05:00.0 eth2: (PCI Express:2.5GT/s:Width > x1) 00:25:90:a8:02:50 > [ 2.613936] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00 > [ 2.613963] usb usb2: New USB device found, idVendor=1d6b, > idProduct=0002 > [ 2.613964] usb usb2: New USB device strings: Mfr=3, Product=2, > SerialNumber=1 > [ 2.613965] usb usb2: Product: EHCI Host Controller > [ 2.613965] usb usb2: Manufacturer: Linux 3.18.20 ehci_hcd > [ 2.613966] usb usb2: SerialNumber: 0000:00:1d.0 > [ 2.614075] hub 2-0:1.0: USB hub found > [ 2.614078] hub 2-0:1.0: 2 ports detected > [ 2.614192] ahci 0000:00:1f.2: version 3.0 > [ 2.614340] ahci 0000:00:1f.2: irq 48 for MSI/MSI-X > [ 2.614485] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 3 > Gbps 0x3f impl SATA mode > [ 2.614486] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum > part ems apst > [ 2.626630] i40e 0000:02:00.0: PCI-Express: Speed 8.0GT/s Width x8 > [ 2.654604] scsi host0: ahci > [ 2.654992] i40e 0000:02:00.0: Features: PF-id[0] VFs: 64 VSIs: 66 > QP: 8 RX: 1BUF RSS FD_ATR FD_SB NTUPLE DCB VxLAN PTP VEPA > [ 2.657763] scsi host1: ahci > [ 2.658083] scsi host2: ahci > [ 2.658320] scsi host3: ahci > [ 2.658546] scsi host4: ahci > [ 2.658747] scsi host5: ahci > [ 2.658785] ata1: SATA max UDMA/133 abar m2048@0xdfb22000 port > 0xdfb22100 irq 48 > [ 2.658788] ata2: SATA max UDMA/133 abar m2048@0xdfb22000 port > 0xdfb22180 irq 48 > [ 2.658790] ata3: SATA max UDMA/133 abar m2048@0xdfb22000 port > 0xdfb22200 irq 48 > [ 2.658792] ata4: SATA max UDMA/133 abar m2048@0xdfb22000 port > 0xdfb22280 irq 48 > [ 2.658795] ata5: SATA max UDMA/133 abar m2048@0xdfb22000 port > 0xdfb22300 irq 48 > [ 2.658798] ata6: SATA max UDMA/133 abar m2048@0xdfb22000 port > 0xdfb22380 irq 48 > [ 2.670025] i40e 0000:02:00.1: fw 4.40.35115 api 1.4 nvm 4.53 > 0x80001dc0 1.123.0 > [ 2.714122] tsc: Refined TSC clocksource calibration: 3500.024 MHz > [ 2.769612] e1000e 0000:05:00.0 eth2: Intel(R) PRO/1000 Network > Connection > [ 2.776551] e1000e 0000:05:00.0 eth2: MAC: 3, PHY: 8, PBA No: > FFFFFF-0FF > [ 2.890322] usb 1-1: new high-speed USB device number 2 using > ehci-pci > [ 2.916415] i40e 0000:02:00.1: MAC address: 3c:fd:fe:9c:56:b9 > [ 2.926260] i40e 0000:02:00.1: SAN MAC: 3c:fd:fe:9c:56:bb > [ 2.930381] usb 2-1: new high-speed USB device number 2 using > ehci-pci > [ 2.952496] i40e 0000:02:00.1: irq 49 for MSI/MSI-X > [ 2.952503] i40e 0000:02:00.1: irq 50 for MSI/MSI-X > [ 2.952508] i40e 0000:02:00.1: irq 51 for MSI/MSI-X > [ 2.952512] i40e 0000:02:00.1: irq 52 for MSI/MSI-X > [ 2.952516] i40e 0000:02:00.1: irq 53 for MSI/MSI-X > [ 2.952520] i40e 0000:02:00.1: irq 54 for MSI/MSI-X > [ 2.952525] i40e 0000:02:00.1: irq 55 for MSI/MSI-X > [ 2.952537] i40e 0000:02:00.1: irq 56 for MSI/MSI-X > [ 2.952539] i40e 0000:02:00.1: irq 57 for MSI/MSI-X > [ 2.952541] i40e 0000:02:00.1: irq 58 for MSI/MSI-X > [ 2.952543] i40e 0000:02:00.1: irq 59 for MSI/MSI-X > [ 2.952545] i40e 0000:02:00.1: irq 60 for MSI/MSI-X > [ 2.952547] i40e 0000:02:00.1: irq 61 for MSI/MSI-X > [ 2.952549] i40e 0000:02:00.1: irq 62 for MSI/MSI-X > [ 2.952550] i40e 0000:02:00.1: irq 63 for MSI/MSI-X > [ 2.952554] i40e 0000:02:00.1: irq 64 for MSI/MSI-X > [ 2.952556] i40e 0000:02:00.1: irq 65 for MSI/MSI-X > [ 2.952558] i40e 0000:02:00.1: irq 66 for MSI/MSI-X > [ 2.978497] ata5: SATA link down (SStatus 0 SControl 300) > [ 2.983838] ata6: SATA link down (SStatus 0 SControl 300) > [ 2.989225] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > [ 2.995381] ata4: SATA link down (SStatus 0 SControl 300) > [ 3.000756] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > [ 3.007184] ata2: SATA link down (SStatus 0 SControl 300) > [ 3.012510] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) > succeeded > [ 3.012514] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE > LOCK) filtered out > [ 3.020391] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE > CONFIGURATION OVERLAY) filtered out > [ 3.026954] usb 1-1: New USB device found, idVendor=8087, > idProduct=0024 > [ 3.026955] usb 1-1: New USB device strings: Mfr=0, Product=0, > SerialNumber=0 > [ 3.027240] hub 1-1:1.0: USB hub found > [ 3.027332] hub 1-1:1.0: 6 ports detected > [ 3.050510] ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) > succeeded > [ 3.050512] ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE > LOCK) filtered out > [ 3.061847] i40e 0000:02:00.1: PCI-Express: Speed 8.0GT/s Width x8 > [ 3.067012] usb 2-1: New USB device found, idVendor=8087, > idProduct=0024 > [ 3.067013] usb 2-1: New USB device strings: Mfr=0, Product=0, > SerialNumber=0 > [ 3.067296] hub 2-1:1.0: USB hub found > [ 3.067384] hub 2-1:1.0: 6 ports detected > [ 3.090237] i40e 0000:02:00.1: Features: PF-id[1] VFs: 64 VSIs: 66 > QP: 8 RX: 1BUF RSS FD_ATR FD_SB NTUPLE DCB VxLAN PTP VEPA > [ 3.103551] ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE > CONFIGURATION OVERLAY) filtered out > [ 3.112266] ata1.00: ATA-8: INTEL SSDSC2BA200G3, 5DV10250, max > UDMA/133 > [ 3.118799] ata1.00: 390721968 sectors, multi 1: LBA48 NCQ (depth > 31/32) > [ 3.125486] ata3.00: ATAPI: HL-DT-ST DVDRAM GT80N, 1.00, max > UDMA/133 > [ 3.132254] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) > succeeded > [ 3.132259] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE > LOCK) filtered out > [ 3.140106] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE > CONFIGURATION OVERLAY) filtered out > [ 3.148916] ata1.00: configured for UDMA/133 > [ 3.153298] scsi 0:0:0:0: Direct-Access ATA INTEL > SSDSC2BA20 0250 PQ: 0 ANSI: 5 > [ 3.154140] ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) > succeeded > [ 3.154142] ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE > LOCK) filtered out > [ 3.154143] ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE > CONFIGURATION OVERLAY) filtered out > [ 3.156130] ata3.00: configured for UDMA/133 > [ 3.185352] scsi 2:0:0:0: CD-ROM HL-DT-ST DVDRAM GT80N > 1.00 PQ: 0 ANSI: 5 > [ 3.298953] usb 1-1.2: new full-speed USB device number 3 using > ehci-pci > [ 3.323219] sd 0:0:0:0: [sda] 390721968 512-byte logical blocks: > (200 GB/186 GiB) > [ 3.330670] sd 0:0:0:0: [sda] Write Protect is off > [ 3.335418] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > [ 3.335427] sd 0:0:0:0: [sda] Write cache: enabled, read cache: > enabled, doesn't support DPO or FUA > [ 3.338917] sr 2:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer > dvd-ram cd/rw xa/form2 cdda tray > [ 3.338918] cdrom: Uniform CD-ROM driver Revision: 3.20 > [ 3.339081] sr 2:0:0:0: Attached scsi CD-ROM sr0 > [ 3.358408] sd 0:0:0:0: Attached scsi generic sg0 type 0 > [ 3.358668] sda: sda1 sda2 > [ 3.358886] sd 0:0:0:0: [sda] Attached SCSI disk > [ 3.371134] sr 2:0:0:0: Attached scsi generic sg1 type 5 > [ 3.396737] usb 1-1.2: New USB device found, idVendor=0557, > idProduct=2221 > [ 3.403526] usb 1-1.2: New USB device strings: Mfr=1, Product=2, > SerialNumber=0 > [ 3.410814] usb 1-1.2: Product: Hermon USB hidmouse Device > [ 3.416282] usb 1-1.2: Manufacturer: Winbond Electronics Corp > [ 3.423736] hidraw: raw HID events driver (C) Jiri Kosina > [ 3.430436] usbcore: registered new interface driver usbhid > [ 3.435922] usbhid: USB HID core driver > [ 3.440716] input: Winbond Electronics Corp Hermon USB hidmouse > Device as > /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:0557:2221.0001/input/input2 > [ 3.455434] hid-generic 0003:0557:2221.0001: input,hidraw0: USB HID > v1.00 Mouse [Winbond Electronics Corp Hermon USB hidmouse Device] on > usb-0000:00:1a.0-1.2/input0 > [ 3.470147] input: Winbond Electronics Corp Hermon USB hidmouse > Device as > /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/0003:0557:2221.0002/input/input3 > [ 3.484849] hid-generic 0003:0557:2221.0002: input,hidraw1: USB HID > v1.00 Keyboard [Winbond Electronics Corp Hermon USB hidmouse Device] > on usb-0000:00:1a.0-1.2/input1 > [ 3.507384] PM: Starting manual resume from disk > [ 3.511922] PM: Hibernation image partition 8:1 present > [ 3.511923] PM: Looking for hibernation image. > [ 3.512127] PM: Image not found (code -22) > [ 3.512131] PM: Hibernation image not present or could not be > loaded. > [ 3.517313] EXT4-fs (sda2): mounting ext3 file system using the > ext4 subsystem > [ 3.529000] EXT4-fs (sda2): mounted filesystem with ordered data > mode. Opts: (null) > [ 3.715841] Switched to clocksource tsc > [ 3.885031] udevd[667]: starting version 175 > [ 4.011695] input: Power Button as > /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4 > [ 4.020070] ACPI: Power Button [PWRB] > [ 4.023703] input: Power Button as > /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 > [ 4.031033] ACPI: Power Button [PWRF] > [ 4.034781] EDAC MC: Ver: 3.0.0 > [ 4.038626] EDAC MC0: Giving out device to module ie31200_edac > controller IE31200: DEV 0000:00:00.0 (POLLED) > [ 4.115904] ipmi message handler version 39.2 > [ 4.121319] IPMI System Interface driver. > [ 4.126068] ipmi_si: probing via ACPI > [ 4.129851] ipmi_si 00:0a: [io 0x0ca2] regsize 1 spacing 1 irq 0 > [ 4.135777] i40e 0000:02:00.1 rename5: renamed from eth3 > [ 4.141149] ipmi_si: Adding ACPI-specified kcs state machine > [ 4.147092] ipmi_si: probing via SMBIOS > [ 4.147160] input: PC Speaker as > /devices/platform/pcspkr/input/input6 > [ 4.157409] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0 > [ 4.163305] ipmi_si: Adding SMBIOS-specified kcs state machine > duplicate interface > [ 4.170854] ipmi_si: probing via SPMI > [ 4.174504] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0 > [ 4.177849] i40e 0000:02:00.0 rename3: renamed from eth1 > [ 4.185527] ipmi_si: Adding SPMI-specified kcs state machine > [ 4.185655] ACPI Warning: SystemIO range > 0x0000000000000428-0x000000000000042F conflicts with OpRegion > 0x0000000000000400-0x000000000000047F (\PMIO) (20140926/utaddress-254) > [ 4.185658] ACPI: If an ACPI driver is available for this device, > you should use it instead of the native driver > [ 4.185660] ACPI Warning: SystemIO range > 0x0000000000000540-0x000000000000054F conflicts with OpRegion > 0x0000000000000500-0x0000000000000563 (\GPIO) (20140926/utaddress-254) > [ 4.185662] ACPI: If an ACPI driver is available for this device, > you should use it instead of the native driver > [ 4.185662] ACPI Warning: SystemIO range > 0x0000000000000530-0x000000000000053F conflicts with OpRegion > 0x0000000000000500-0x0000000000000563 (\GPIO) (20140926/utaddress-254) > [ 4.185664] ACPI: If an ACPI driver is available for this device, > you should use it instead of the native driver > [ 4.185664] ACPI Warning: SystemIO range > 0x0000000000000500-0x000000000000052F conflicts with OpRegion > 0x0000000000000500-0x0000000000000563 (\GPIO) (20140926/utaddress-254) > [ 4.185665] ACPI: If an ACPI driver is available for this device, > you should use it instead of the native driver > [ 4.185665] lpc_ich: Resource conflict(s) found affecting gpio_ich > [ 4.280990] iTCO_vendor_support: vendor-support=0 > [ 4.304270] duplicate interface > [ 4.307664] ipmi_si: Trying ACPI-specified kcs state machine at i/o > address 0xca2, slave address 0x0, irq 0 > [ 4.318187] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 > [ 4.323711] iTCO_wdt: Found a Cougar Point TCO device (Version=2, > TCOBASE=0x0460) > [ 4.323818] e1000e 0000:00:19.0 eth3: renamed from eth0 > [ 4.336446] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) > [ 4.342474] AVX version of gcm_enc/dec engaged. > [ 4.346907] AES CTR mode by8 optimization enabled > [ 4.351931] i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt > [ 4.352819] alg: No test for __gcm-aes-aesni > (__driver-gcm-aes-aesni) > [ 4.364158] i40e 0000:02:00.1 eth1: renamed from rename5 > [ 4.370154] [drm] Initialized drm 1.1.0 20060810 > [ 4.374797] Error: Driver 'pcspkr' is already registered, > aborting... > [ 4.381228] alg: No test for crc32 (crc32-pclmul) > [ 4.395990] [TTM] Zone kernel: Available graphics memory: 16494382 > kiB > [ 4.396626] i40e 0000:02:00.0 eth0: renamed from rename3 > [ 4.407813] [TTM] Zone dma32: Available graphics memory: 2097152 > kiB > [ 4.414324] [TTM] Initializing pool allocator > [ 4.418678] [TTM] Initializing DMA pool allocator > [ 4.425605] intel_rapl: Found RAPL domain package > [ 4.430215] intel_rapl: Found RAPL domain core > [ 4.446166] fbcon: mgadrmfb (fb0) is primary device > [ 4.489833] ipmi_si 00:0a: Found new BMC (man_id: 0x002a7c, > prod_id: 0x0624, dev_id: 0x20) > [ 4.489843] ipmi_si 00:0a: IPMI kcs interface initialized > [ 4.604074] Console: switching to colour frame buffer device 128x48 > [ 4.698245] mgag200 0000:06:03.0: fb0: mgadrmfb frame buffer device > [ 4.704491] mgag200 0000:06:03.0: registered panic notifier > [ 4.733133] [drm] Initialized mgag200 1.0.0 20110418 for > 0000:06:03.0 on minor 0 > [ 4.975874] Adding 3905532k swap on /dev/sda1. Priority:-1 > extents:1 across:3905532k SSFS > [ 5.002394] EXT4-fs (sda2): re-mounted. Opts: (null) > [ 5.044749] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro > [ 5.077354] loop: module loaded > [ 5.087636] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) > [ 5.101990] nf_conntrack version 0.5.0 (17374463 buckets, 138995704 > max) > [ 5.108653] nf_conntrack: falling back to vmalloc. > [ 5.735510] random: dd urandom read with 92 bits of entropy > available > [ 5.927034] bond0: Setting xmit hash policy to layer3+4 (1) > [ 5.927105] bond0: Setting MII monitoring interval to 100 > [ 5.963685] bond0: Setting LACP rate to slow (0) > [ 6.119830] bond0: Adding slave eth... [truncated message content] |
|
From: Philip W. <an...@su...> - 2015-09-26 10:59:07
|
Hi, I have a project worth $48.8million I'd like to share. Do reply if interested. Thanks. Philip Li Wong |
|
From: Christian R. <id...@qa...> - 2015-09-25 14:19:16
|
Hi, the card came back and I had to flash it again but it worked perfectly fine this time :) So I setup a new Kernel (3.18.20) and the most recent i40e driver (1.3.39.1) and removed the previous workaround to disable ntuples on both interfaces. So basically a vanilla setup. That host is up for several hours no and there was no spam so far and only one reset yet: Sep 25 12:38:54 somehost kernel: [77571.409182] i40e 0000:02:00.1: TX driver issue detected, PF reset issued Sep 25 12:38:55 somehost kernel: [77572.245943] bond0: link status up again after 0 ms for interface eth1 and here's the requested dmesg again: [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.18.20 (fud@somehost) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Wed Aug 26 14:25:15 CEST 2015 [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.18.20 root=UUID=ea7a13a2-a96b-4165-801a-119b0f0d9b8f ro ipv6.disable=1 intel_pstate=disable earlyprintk=ttyS0,115200,keep intel_iommu=off [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000099bff] usable [ 0.000000] BIOS-e820: [mem 0x0000000000099c00-0x000000000009ffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000becc8fff] usable [ 0.000000] BIOS-e820: [mem 0x00000000becc9000-0x00000000bed0bfff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x00000000bed0c000-0x00000000ce491fff] usable [ 0.000000] BIOS-e820: [mem 0x00000000ce492000-0x00000000ce534fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ce535000-0x00000000ce5c6fff] usable [ 0.000000] BIOS-e820: [mem 0x00000000ce5c7000-0x00000000ce68bfff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x00000000ce68c000-0x00000000cf7fefff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000cf7ff000-0x00000000cf7fffff] usable [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000082fffffff] usable [ 0.000000] console [earlyser0] enabled [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] SMBIOS 2.7 present. [ 0.000000] DMI: Supermicro X9SCL/X9SCM/X9SCL/X9SCM, BIOS 2.2 02/20/2015 [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.000000] AGP: No AGP bridge found [ 0.000000] e820: last_pfn = 0x830000 max_arch_pfn = 0x400000000 [ 0.000000] MTRR default type: uncachable [ 0.000000] MTRR fixed ranges enabled: [ 0.000000] 00000-9FFFF write-back [ 0.000000] A0000-BFFFF uncachable [ 0.000000] C0000-CBFFF write-protect [ 0.000000] CC000-E7FFF uncachable [ 0.000000] E8000-FFFFF write-protect [ 0.000000] MTRR variable ranges enabled: [ 0.000000] 0 base 000000000 mask 800000000 write-back [ 0.000000] 1 base 800000000 mask FE0000000 write-back [ 0.000000] 2 base 820000000 mask FF0000000 write-back [ 0.000000] 3 base 0E0000000 mask FE0000000 uncachable [ 0.000000] 4 base 0D0000000 mask FF0000000 uncachable [ 0.000000] 5 disabled [ 0.000000] 6 disabled [ 0.000000] 7 disabled [ 0.000000] 8 disabled [ 0.000000] 9 disabled [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [ 0.000000] e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved [ 0.000000] e820: last_pfn = 0xcf800 max_arch_pfn = 0x400000000 [ 0.000000] found SMP MP-table at [mem 0x000fd7b0-0x000fd7bf] mapped at [ffff8800000fd7b0] [ 0.000000] Base memory trampoline at [ffff880000093000] 93000 size 24576 [ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff] [ 0.000000] [mem 0x00000000-0x000fffff] page 4k [ 0.000000] BRK [0x01b02000, 0x01b02fff] PGTABLE [ 0.000000] BRK [0x01b03000, 0x01b03fff] PGTABLE [ 0.000000] BRK [0x01b04000, 0x01b04fff] PGTABLE [ 0.000000] init_memory_mapping: [mem 0x82fe00000-0x82fffffff] [ 0.000000] [mem 0x82fe00000-0x82fffffff] page 2M [ 0.000000] BRK [0x01b05000, 0x01b05fff] PGTABLE [ 0.000000] init_memory_mapping: [mem 0x82c000000-0x82fdfffff] [ 0.000000] [mem 0x82c000000-0x82fdfffff] page 2M [ 0.000000] init_memory_mapping: [mem 0x800000000-0x82bffffff] [ 0.000000] [mem 0x800000000-0x82bffffff] page 2M [ 0.000000] init_memory_mapping: [mem 0x00100000-0xbecc8fff] [ 0.000000] [mem 0x00100000-0x001fffff] page 4k [ 0.000000] [mem 0x00200000-0xbebfffff] page 2M [ 0.000000] [mem 0xbec00000-0xbecc8fff] page 4k [ 0.000000] init_memory_mapping: [mem 0xbed0c000-0xce491fff] [ 0.000000] [mem 0xbed0c000-0xbedfffff] page 4k [ 0.000000] [mem 0xbee00000-0xce3fffff] page 2M [ 0.000000] [mem 0xce400000-0xce491fff] page 4k [ 0.000000] BRK [0x01b06000, 0x01b06fff] PGTABLE [ 0.000000] BRK [0x01b07000, 0x01b07fff] PGTABLE [ 0.000000] init_memory_mapping: [mem 0xce535000-0xce5c6fff] [ 0.000000] [mem 0xce535000-0xce5c6fff] page 4k [ 0.000000] init_memory_mapping: [mem 0xcf7ff000-0xcf7fffff] [ 0.000000] [mem 0xcf7ff000-0xcf7fffff] page 4k [ 0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff] [ 0.000000] [mem 0x100000000-0x7ffffffff] page 2M [ 0.000000] RAMDISK: [mem 0x360c0000-0x37057fff] [ 0.000000] ACPI: Early table checksum verification disabled [ 0.000000] ACPI: RSDP 0x00000000000F0490 000024 (v02 SUPERM) [ 0.000000] ACPI: XSDT 0x00000000CE64F088 00008C (v01 SUPERM SMCI--MB 00000001 AMI 00010013) [ 0.000000] ACPI: FACP 0x00000000CE65A210 00010C (v05 SUPERM SMCI--MB 00000001 AMI 00010013) [ 0.000000] ACPI: DSDT 0x00000000CE64F1A8 00B068 (v02 SUPERM SMCI--MB 00000000 INTL 20051117) [ 0.000000] ACPI: FACS 0x00000000CE68A080 000040 [ 0.000000] ACPI: APIC 0x00000000CE65A320 000092 (v03 SUPERM SMCI--MB 00000001 AMI 00010013) [ 0.000000] ACPI: FPDT 0x00000000CE65A3B8 000044 (v01 SUPERM SMCI--MB 00000001 AMI 00010013) [ 0.000000] ACPI: MCFG 0x00000000CE65A400 00003C (v01 SUPERM SMCI--MB 00000001 MSFT 00000097) [ 0.000000] ACPI: HPET 0x00000000CE65A440 000038 (v01 SUPERM SMCI--MB 00000001 AMI. 00000005) [ 0.000000] ACPI: SSDT 0x00000000CE65A478 000397 (v01 SataRe SataTabl 00001000 INTL 20091112) [ 0.000000] ACPI: SPMI 0x00000000CE65A810 000040 (v05 A M I OEMSPMI 00000000 AMI. 00000000) [ 0.000000] ACPI: SSDT 0x00000000CE65A850 0009A4 (v01 PmRef Cpu0Ist 00003000 INTL 20051117) [ 0.000000] ACPI: SSDT 0x00000000CE65B1F8 000B18 (v01 PmRef CpuPm 00003000 INTL 20051117) [ 0.000000] ACPI: EINJ 0x00000000CE65BD10 000130 (v01 AMI AMI EINJ 00000000 00000000) [ 0.000000] ACPI: ERST 0x00000000CE65BE40 000210 (v01 AMIER AMI ERST 00000000 00000000) [ 0.000000] ACPI: HEST 0x00000000CE65C050 0000A8 (v01 AMI AMI HEST 00000000 00000000) [ 0.000000] ACPI: BERT 0x00000000CE65C0F8 000030 (v01 AMI AMI BERT 00000000 00000000) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000082fffffff] [ 0.000000] NODE_DATA(0) allocated [mem 0x82ffdc000-0x82ffdffff] [ 0.000000] [ffffea0000000000-ffffea001cbfffff] PMD -> [ffff88080f600000-ffff88082b7fffff] on node 0 [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x00001000-0x00ffffff] [ 0.000000] DMA32 [mem 0x01000000-0xffffffff] [ 0.000000] Normal [mem 0x100000000-0x82fffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00001000-0x00098fff] [ 0.000000] node 0: [mem 0x00100000-0xbecc8fff] [ 0.000000] node 0: [mem 0xbed0c000-0xce491fff] [ 0.000000] node 0: [mem 0xce535000-0xce5c6fff] [ 0.000000] node 0: [mem 0xcf7ff000-0xcf7fffff] [ 0.000000] node 0: [mem 0x100000000-0x82fffffff] [ 0.000000] Initmem setup node 0 [mem 0x00001000-0x82fffffff] [ 0.000000] On node 0 totalpages: 8381562 [ 0.000000] DMA zone: 56 pages used for memmap [ 0.000000] DMA zone: 21 pages reserved [ 0.000000] DMA zone: 3992 pages, LIFO batch:0 [ 0.000000] DMA32 zone: 11498 pages used for memmap [ 0.000000] DMA32 zone: 840930 pages, LIFO batch:31 [ 0.000000] Normal zone: 103040 pages used for memmap [ 0.000000] Normal zone: 7536640 pages, LIFO batch:31 [ 0.000000] ACPI: PM-Timer IO Port: 0x408 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] ACPI: IRQ0 used by override. [ 0.000000] ACPI: IRQ9 used by override. [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000 [ 0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs [ 0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff] [ 0.000000] PM: Registered nosave memory: [mem 0x00099000-0x00099fff] [ 0.000000] PM: Registered nosave memory: [mem 0x0009a000-0x0009ffff] [ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff] [ 0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff] [ 0.000000] PM: Registered nosave memory: [mem 0xbecc9000-0xbed0bfff] [ 0.000000] PM: Registered nosave memory: [mem 0xce492000-0xce534fff] [ 0.000000] PM: Registered nosave memory: [mem 0xce5c7000-0xce68bfff] [ 0.000000] PM: Registered nosave memory: [mem 0xce68c000-0xcf7fefff] [ 0.000000] PM: Registered nosave memory: [mem 0xcf800000-0xdfffffff] [ 0.000000] PM: Registered nosave memory: [mem 0xe0000000-0xefffffff] [ 0.000000] PM: Registered nosave memory: [mem 0xf0000000-0xfebfffff] [ 0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff] [ 0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff] [ 0.000000] PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff] [ 0.000000] PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff] [ 0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff] [ 0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff] [ 0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff] [ 0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff] [ 0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff] [ 0.000000] e820: [mem 0xcf800000-0xdfffffff] available for PCI devices [ 0.000000] Booting paravirtualized kernel on bare hardware [ 0.000000] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:8 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 29 pages/cpu @ffff88082fc00000 s80960 r8192 d29632 u262144 [ 0.000000] pcpu-alloc: s80960 r8192 d29632 u262144 alloc=1*2097152 [ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 8266947 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.18.20 root=UUID=ea7a13a2-a96b-4165-801a-119b0f0d9b8f ro ipv6.disable=1 intel_pstate=disable earlyprintk=ttyS0,115200,keep intel_iommu=off [ 0.000000] Intel-IOMMU: disabled [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form [ 0.000000] AGP: Checking aperture... [ 0.000000] AGP: No AGP bridge found [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing! [ 0.000000] Memory: 32970712K/33526248K available (5512K kernel code, 966K rwdata, 1832K rodata, 1228K init, 852K bss, 555536K reserved) [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled. [ 0.000000] RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=8. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8 [ 0.000000] NR_IRQS:33024 nr_irqs:488 0 [ 0.000000] Console: colour VGA+ 80x25 [ 0.000000] console [tty0] enabled [ 0.000000] allocated 134217728 bytes of page_cgroup [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.000000] hpet clockevent registered [ 0.000000] tsc: Fast TSC calibration failed [ 0.000000] tsc: PIT calibration matches HPET. 1 loops [ 0.000000] tsc: Detected 3499.669 MHz processor [ 0.000025] Calibrating delay loop (skipped), value calculated using timer frequency.. 6999.33 BogoMIPS (lpj=13998676) [ 0.010617] pid_max: default: 32768 minimum: 301 [ 0.015230] ACPI: Core revision 20140926 [ 0.024681] ACPI: All ACPI Tables successfully acquired [ 0.039606] Security Framework initialized [ 0.043611] AppArmor: AppArmor disabled by boot time parameter [ 0.049421] Yama: becoming mindful. [ 0.054266] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes) [ 0.067119] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes) [ 0.076825] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes) [ 0.083636] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes) [ 0.091133] Initializing cgroup subsys memory [ 0.095401] Initializing cgroup subsys devices [ 0.099824] Initializing cgroup subsys freezer [ 0.104249] Initializing cgroup subsys net_cls [ 0.108676] Initializing cgroup subsys blkio [ 0.112929] Initializing cgroup subsys perf_event [ 0.117615] Initializing cgroup subsys net_prio [ 0.122145] CPU: Physical Processor ID: 0 [ 0.126120] CPU: Processor Core ID: 0 [ 0.129769] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [ 0.129769] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) [ 0.143037] mce: CPU supports 9 MCE banks [ 0.146959] CPU0: Thermal monitoring enabled (TM1) [ 0.151728] process: using mwait in idle threads [ 0.156328] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8 [ 0.156328] Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0 [ 0.168125] Freeing SMP alternatives memory: 20K (ffffffff81a26000 - ffffffff81a2b000) [ 0.176733] ftrace: allocating 22083 entries in 87 pages [ 0.197324] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 0.242968] smpboot: CPU0: Intel(R) Xeon(R) CPU E3-1270 V2 @ 3.50GHz (fam: 06, model: 3a, stepping: 09) [ 0.252247] TSC deadline timer enabled [ 0.252264] Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver. [ 0.262484] ... version: 3 [ 0.266477] ... bit width: 48 [ 0.270555] ... generic registers: 4 [ 0.274548] ... value mask: 0000ffffffffffff [ 0.279843] ... max period: 0000ffffffffffff [ 0.285137] ... fixed-purpose events: 3 [ 0.289130] ... event mask: 000000070000000f [ 0.295409] x86: Booting SMP configuration: [ 0.299494] .... node #0, CPUs: #1 [ 0.316534] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. [ 0.324669] #2 #3 #4 #5 #6 #7 [ 0.407240] x86: Booted up 1 node, 8 CPUs [ 0.411319] smpboot: Total of 8 processors activated (55994.70 BogoMIPS) [ 0.424047] devtmpfs: initialized [ 0.430926] PM: Registering ACPI NVS region [mem 0xbecc9000-0xbed0bfff] (274432 bytes) [ 0.438777] PM: Registering ACPI NVS region [mem 0xce5c7000-0xce68bfff] (806912 bytes) [ 0.447304] pinctrl core: initialized pinctrl subsystem [ 0.452519] NET: Registered protocol family 16 [ 0.468890] cpuidle: using governor ladder [ 0.488929] cpuidle: using governor menu [ 0.492803] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [ 0.500309] ACPI: bus type PCI registered [ 0.504301] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.510784] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000) [ 0.520010] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820 [ 0.526980] PCI: Using configuration type 1 for base access [ 0.544821] ACPI: Added _OSI(Module Device) [ 0.548905] ACPI: Added _OSI(Processor Device) [ 0.553330] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.558017] ACPI: Added _OSI(Processor Aggregator Device) [ 0.565243] ACPI: Executed 1 blocks of module-level executable AML code [ 0.739624] \_SB_:_OSC invalid UUID [ 0.739625] _OSC request data:1 1f [ 0.739811] ACPI: Dynamic OEM Table Load: [ 0.743707] ACPI: SSDT 0xFFFF880807B5C000 00083B (v01 PmRef Cpu0Cst 00003001 INTL 20051117) [ 0.764280] ACPI: Dynamic OEM Table Load: [ 0.768173] ACPI: SSDT 0xFFFF880807049C00 000303 (v01 PmRef ApIst 00003000 INTL 20051117) [ 0.788649] ACPI: Dynamic OEM Table Load: [ 0.792543] ACPI: SSDT 0xFFFF880807007C00 000119 (v01 PmRef ApCst 00003000 INTL 20051117) [ 0.813761] ACPI: Interpreter enabled [ 0.817329] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140926/hwxface-580) [ 0.826523] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20140926/hwxface-580) [ 0.835727] ACPI: (supports S0 S1 S4 S5) [ 0.839628] ACPI: Using IOAPIC for interrupt routing [ 0.844615] HEST: Table parsing has been initialized. [ 0.849610] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.863689] ACPI: Power Resource [FN00] (off) [ 0.868006] ACPI: Power Resource [FN01] (off) [ 0.872344] ACPI: Power Resource [FN02] (off) [ 0.876682] ACPI: Power Resource [FN03] (off) [ 0.881022] ACPI: Power Resource [FN04] (off) [ 0.885681] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe]) [ 0.891767] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.900002] acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug PME] [ 0.907216] acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability] [ 0.914173] PCI host bridge to bus 0000:00 [ 0.918169] pci_bus 0000:00: root bus resource [bus 00-fe] [ 0.923636] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7] [ 0.929798] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff] [ 0.935959] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff] [ 0.942817] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff] [ 0.949673] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff] [ 0.956530] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff] [ 0.963386] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff] [ 0.970243] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff] [ 0.977101] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff] [ 0.983957] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff] [ 0.990814] pci_bus 0000:00: root bus resource [mem 0xd0000000-0xfeafffff] [ 0.997674] pci 0000:00:00.0: [8086:0158] type 00 class 0x060000 [ 0.997751] pci 0000:00:01.0: [8086:0151] type 01 class 0x060400 [ 0.997831] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold [ 0.997870] pci 0000:00:01.0: System wakeup disabled by ACPI [ 1.003450] pci 0000:00:01.1: [8086:0155] type 01 class 0x060400 [ 1.003473] pci 0000:00:01.1: PME# supported from D0 D3hot D3cold [ 1.003502] pci 0000:00:01.1: System wakeup disabled by ACPI [ 1.009121] pci 0000:00:19.0: [8086:1502] type 00 class 0x020000 [ 1.009138] pci 0000:00:19.0: reg 0x10: [mem 0xdfb00000-0xdfb1ffff] [ 1.009145] pci 0000:00:19.0: reg 0x14: [mem 0xdfb25000-0xdfb25fff] [ 1.009153] pci 0000:00:19.0: reg 0x18: [io 0xf020-0xf03f] [ 1.009212] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold [ 1.009246] pci 0000:00:19.0: System wakeup disabled by ACPI [ 1.014835] pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320 [ 1.014854] pci 0000:00:1a.0: reg 0x10: [mem 0xdfb24000-0xdfb243ff] [ 1.014938] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold [ 1.014983] pci 0000:00:1a.0: System wakeup disabled by ACPI [ 1.020571] pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400 [ 1.020648] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 1.020686] pci 0000:00:1c.0: System wakeup disabled by ACPI [ 1.026274] pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400 [ 1.026351] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold [ 1.026388] pci 0000:00:1c.4: System wakeup disabled by ACPI [ 1.031981] pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320 [ 1.032000] pci 0000:00:1d.0: reg 0x10: [mem 0xdfb23000-0xdfb233ff] [ 1.032084] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold [ 1.032129] pci 0000:00:1d.0: System wakeup disabled by ACPI [ 1.037718] pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401 [ 1.037791] pci 0000:00:1e.0: System wakeup disabled by ACPI [ 1.043379] pci 0000:00:1f.0: [8086:1c52] type 00 class 0x060100 [ 1.043532] pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601 [ 1.043549] pci 0000:00:1f.2: reg 0x10: [io 0xf070-0xf077] [ 1.043556] pci 0000:00:1f.2: reg 0x14: [io 0xf060-0xf063] [ 1.043563] pci 0000:00:1f.2: reg 0x18: [io 0xf050-0xf057] [ 1.043570] pci 0000:00:1f.2: reg 0x1c: [io 0xf040-0xf043] [ 1.043577] pci 0000:00:1f.2: reg 0x20: [io 0xf000-0xf01f] [ 1.043584] pci 0000:00:1f.2: reg 0x24: [mem 0xdfb22000-0xdfb227ff] [ 1.043625] pci 0000:00:1f.2: PME# supported from D3hot [ 1.043684] pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500 [ 1.043697] pci 0000:00:1f.3: reg 0x10: [mem 0xdfb21000-0xdfb210ff 64bit] [ 1.043716] pci 0000:00:1f.3: reg 0x20: [io 0x0580-0x059f] [ 1.043832] pci 0000:00:01.0: PCI bridge to [bus 01] [ 1.048735] pci 0000:02:00.0: [8086:1572] type 00 class 0x020000 [ 1.048745] pci 0000:02:00.0: reg 0x10: [mem 0xdd800000-0xddffffff 64bit pref] [ 1.048755] pci 0000:02:00.0: reg 0x1c: [mem 0xde808000-0xde80ffff 64bit pref] [ 1.048764] pci 0000:02:00.0: reg 0x30: [mem 0xdfa80000-0xdfafffff pref] [ 1.048800] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold [ 1.048818] pci 0000:02:00.0: reg 0x184: [mem 0xde400000-0xde40ffff 64bit pref] [ 1.048827] pci 0000:02:00.0: reg 0x190: [mem 0xde910000-0xde913fff 64bit pref] [ 1.048862] pci 0000:02:00.1: [8086:1572] type 00 class 0x020000 [ 1.048872] pci 0000:02:00.1: reg 0x10: [mem 0xdd000000-0xdd7fffff 64bit pref] [ 1.048882] pci 0000:02:00.1: reg 0x1c: [mem 0xde800000-0xde807fff 64bit pref] [ 1.048891] pci 0000:02:00.1: reg 0x30: [mem 0xdfa00000-0xdfa7ffff pref] [ 1.048925] pci 0000:02:00.1: PME# supported from D0 D3hot D3cold [ 1.048942] pci 0000:02:00.1: reg 0x184: [mem 0xde000000-0xde00ffff 64bit pref] [ 1.048951] pci 0000:02:00.1: reg 0x190: [mem 0xde810000-0xde813fff 64bit pref] [ 1.056725] pci 0000:00:01.1: PCI bridge to [bus 02-03] [ 1.061856] pci 0000:00:01.1: bridge window [mem 0xdfa00000-0xdfafffff] [ 1.061858] pci 0000:00:01.1: bridge window [mem 0xdd000000-0xdeafffff 64bit pref] [ 1.061915] pci 0000:00:1c.0: PCI bridge to [bus 04] [ 1.066903] pci 0000:05:00.0: [8086:10d3] type 00 class 0x020000 [ 1.066942] pci 0000:05:00.0: reg 0x10: [mem 0xdf900000-0xdf91ffff] [ 1.066987] pci 0000:05:00.0: reg 0x18: [io 0xe000-0xe01f] [ 1.067010] pci 0000:05:00.0: reg 0x1c: [mem 0xdf920000-0xdf923fff] [ 1.067239] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold [ 1.067289] pci 0000:05:00.0: System wakeup disabled by ACPI [ 1.080881] pci 0000:00:1c.4: PCI bridge to [bus 05] [ 1.085759] pci 0000:00:1c.4: bridge window [io 0xe000-0xefff] [ 1.085762] pci 0000:00:1c.4: bridge window [mem 0xdf900000-0xdf9fffff] [ 1.085807] pci 0000:06:03.0: [102b:0532] type 00 class 0x030000 [ 1.085822] pci 0000:06:03.0: reg 0x10: [mem 0xdc000000-0xdcffffff pref] [ 1.085831] pci 0000:06:03.0: reg 0x14: [mem 0xdf800000-0xdf803fff] [ 1.085839] pci 0000:06:03.0: reg 0x18: [mem 0xdf000000-0xdf7fffff] [ 1.085948] pci 0000:00:1e.0: PCI bridge to [bus 06] (subtractive decode) [ 1.092645] pci 0000:00:1e.0: bridge window [mem 0xdf000000-0xdf8fffff] [ 1.092650] pci 0000:00:1e.0: bridge window [mem 0xdc000000-0xdcffffff 64bit pref] [ 1.092651] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode) [ 1.092652] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode) [ 1.092653] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode) [ 1.092655] pci 0000:00:1e.0: bridge window [mem 0x000cc000-0x000cffff] (subtractive decode) [ 1.092656] pci 0000:00:1e.0: bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode) [ 1.092657] pci 0000:00:1e.0: bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode) [ 1.092658] pci 0000:00:1e.0: bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode) [ 1.092659] pci 0000:00:1e.0: bridge window [mem 0x000dc000-0x000dffff] (subtractive decode) [ 1.092660] pci 0000:00:1e.0: bridge window [mem 0x000e0000-0x000e3fff] (subtractive decode) [ 1.092661] pci 0000:00:1e.0: bridge window [mem 0x000e4000-0x000e7fff] (subtractive decode) [ 1.092662] pci 0000:00:1e.0: bridge window [mem 0xd0000000-0xfeafffff] (subtractive decode) [ 1.092690] acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported) [ 1.100314] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15) [ 1.107107] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 10 11 12 14 15) [ 1.113962] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15) [ 1.120818] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15) [ 1.127675] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 10 11 12 14 15) [ 1.134531] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 1.142515] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled. [ 1.150505] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15) [ 1.157484] ACPI: Enabled 4 GPEs in block 00 to 3F [ 1.162221] vgaarb: setting as boot device: PCI:0000:06:03.0 [ 1.167794] vgaarb: device added: PCI:0000:06:03.0,decodes=io+mem,owns=io+mem,locks=none [ 1.175867] vgaarb: loaded [ 1.178556] vgaarb: bridge control possible 0000:06:03.0 [ 1.183909] PCI: Using ACPI for IRQ routing [ 1.193792] PCI: pci_cache_line_size set to 64 bytes [ 1.193833] e820: reserve RAM buffer [mem 0x00099c00-0x0009ffff] [ 1.193834] e820: reserve RAM buffer [mem 0xbecc9000-0xbfffffff] [ 1.193835] e820: reserve RAM buffer [mem 0xce492000-0xcfffffff] [ 1.193836] e820: reserve RAM buffer [mem 0xce5c7000-0xcfffffff] [ 1.193837] e820: reserve RAM buffer [mem 0xcf800000-0xcfffffff] [ 1.193935] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0 [ 1.199994] hpet0: 8 comparators, 64-bit 14.318180 MHz counter [ 1.207831] Switched to clocksource hpet [ 1.215086] pnp: PnP ACPI init [ 1.218096] system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved [ 1.224641] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active) [ 1.224688] system 00:01: [io 0x0680-0x069f] has been reserved [ 1.230542] system 00:01: [io 0x1000-0x100f] has been reserved [ 1.236442] system 00:01: [io 0xffff] has been reserved [ 1.241736] system 00:01: [io 0xffff] has been reserved [ 1.247031] system 00:01: [io 0x0400-0x0453] could not be reserved [ 1.253282] system 00:01: [io 0x0458-0x047f] has been reserved [ 1.259182] system 00:01: [io 0x0500-0x057f] has been reserved [ 1.265084] system 00:01: [io 0x164e-0x164f] has been reserved [ 1.270987] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active) [ 1.271008] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active) [ 1.271039] system 00:03: [io 0x0454-0x0457] has been reserved [ 1.276891] system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active) [ 1.276924] system 00:04: [io 0x04d0-0x04d1] has been reserved [ 1.282792] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active) [ 1.282868] system 00:05: [io 0x0a00-0x0a1f] has been reserved [ 1.288693] system 00:05: [io 0x0a30-0x0a3f] has been reserved [ 1.294594] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active) [ 1.294751] pnp 00:06: [dma 0 disabled] [ 1.294780] pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active) [ 1.294921] pnp 00:07: [dma 0 disabled] [ 1.294947] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active) [ 1.295019] system 00:08: [io 0x0b00-0x0b7f] has been reserved [ 1.300845] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active) [ 1.300958] pnp 00:09: [dma 0 disabled] [ 1.300985] pnp 00:09: Plug and Play ACPI device, IDs PNP0501 (active) [ 1.301064] pnp 00:0a: Plug and Play ACPI device, IDs IPI0001 (active) [ 1.301198] system 00:0b: [mem 0xfed1c000-0xfed1ffff] has been reserved [ 1.307720] system 00:0b: [mem 0xfed10000-0xfed17fff] has been reserved [ 1.314314] system 00:0b: [mem 0xfed18000-0xfed18fff] has been reserved [ 1.320909] system 00:0b: [mem 0xfed19000-0xfed19fff] has been reserved [ 1.327506] system 00:0b: [mem 0xe0000000-0xefffffff] has been reserved [ 1.334102] system 00:0b: [mem 0xfed20000-0xfed3ffff] has been reserved [ 1.340701] system 00:0b: [mem 0xfed90000-0xfed93fff] has been reserved [ 1.347295] system 00:0b: [mem 0xfed45000-0xfed8ffff] has been reserved [ 1.353892] system 00:0b: [mem 0xff000000-0xffffffff] has been reserved [ 1.360488] system 00:0b: [mem 0xfee00000-0xfeefffff] could not be reserved [ 1.367430] system 00:0b: [mem 0xd0000000-0xd0000fff] has been reserved [ 1.374027] system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active) [ 1.374113] pnp: PnP ACPI: found 12 devices [ 1.384167] pci 0000:00:01.0: PCI bridge to [bus 01] [ 1.389053] pci 0000:00:01.1: PCI bridge to [bus 02-03] [ 1.394250] pci 0000:00:01.1: bridge window [mem 0xdfa00000-0xdfafffff] [ 1.401020] pci 0000:00:01.1: bridge window [mem 0xdd000000-0xdeafffff 64bit pref] [ 1.408745] pci 0000:00:1c.0: PCI bridge to [bus 04] [ 1.413701] pci 0000:00:1c.4: PCI bridge to [bus 05] [ 1.418641] pci 0000:00:1c.4: bridge window [io 0xe000-0xefff] [ 1.424718] pci 0000:00:1c.4: bridge window [mem 0xdf900000-0xdf9fffff] [ 1.431489] pci 0000:00:1e.0: PCI bridge to [bus 06] [ 1.436435] pci 0000:00:1e.0: bridge window [mem 0xdf000000-0xdf8fffff] [ 1.443203] pci 0000:00:1e.0: bridge window [mem 0xdc000000-0xdcffffff 64bit pref] [ 1.450929] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7] [ 1.450931] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff] [ 1.450932] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff] [ 1.450933] pci_bus 0000:00: resource 7 [mem 0x000cc000-0x000cffff] [ 1.450934] pci_bus 0000:00: resource 8 [mem 0x000d0000-0x000d3fff] [ 1.450935] pci_bus 0000:00: resource 9 [mem 0x000d4000-0x000d7fff] [ 1.450936] pci_bus 0000:00: resource 10 [mem 0x000d8000-0x000dbfff] [ 1.450937] pci_bus 0000:00: resource 11 [mem 0x000dc000-0x000dffff] [ 1.450938] pci_bus 0000:00: resource 12 [mem 0x000e0000-0x000e3fff] [ 1.450939] pci_bus 0000:00: resource 13 [mem 0x000e4000-0x000e7fff] [ 1.450940] pci_bus 0000:00: resource 14 [mem 0xd0000000-0xfeafffff] [ 1.450941] pci_bus 0000:02: resource 1 [mem 0xdfa00000-0xdfafffff] [ 1.450942] pci_bus 0000:02: resource 2 [mem 0xdd000000-0xdeafffff 64bit pref] [ 1.450943] pci_bus 0000:05: resource 0 [io 0xe000-0xefff] [ 1.450944] pci_bus 0000:05: resource 1 [mem 0xdf900000-0xdf9fffff] [ 1.450946] pci_bus 0000:06: resource 1 [mem 0xdf000000-0xdf8fffff] [ 1.450947] pci_bus 0000:06: resource 2 [mem 0xdc000000-0xdcffffff 64bit pref] [ 1.450948] pci_bus 0000:06: resource 4 [io 0x0000-0x0cf7] [ 1.450949] pci_bus 0000:06: resource 5 [io 0x0d00-0xffff] [ 1.450950] pci_bus 0000:06: resource 6 [mem 0x000a0000-0x000bffff] [ 1.450951] pci_bus 0000:06: resource 7 [mem 0x000cc000-0x000cffff] [ 1.450952] pci_bus 0000:06: resource 8 [mem 0x000d0000-0x000d3fff] [ 1.450953] pci_bus 0000:06: resource 9 [mem 0x000d4000-0x000d7fff] [ 1.450954] pci_bus 0000:06: resource 10 [mem 0x000d8000-0x000dbfff] [ 1.450955] pci_bus 0000:06: resource 11 [mem 0x000dc000-0x000dffff] [ 1.450956] pci_bus 0000:06: resource 12 [mem 0x000e0000-0x000e3fff] [ 1.450957] pci_bus 0000:06: resource 13 [mem 0x000e4000-0x000e7fff] [ 1.450958] pci_bus 0000:06: resource 14 [mem 0xd0000000-0xfeafffff] [ 1.451014] NET: Registered protocol family 2 [ 1.455462] TCP established hash table entries: 262144 (order: 9, 2097152 bytes) [ 1.463005] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 1.469713] TCP: Hash tables configured (established 262144 bind 65536) [ 1.476246] TCP: reno registered [ 1.479464] UDP hash table entries: 16384 (order: 7, 524288 bytes) [ 1.485680] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes) [ 1.492306] NET: Registered protocol family 1 [ 1.496818] PCI: CLS mismatch (64 != 32), using 64 bytes [ 1.496823] pci 0000:06:03.0: Video device with shadowed ROM [ 1.496853] Unpacking initramfs... [ 1.690454] Freeing initrd memory: 15968K (ffff8800360c0000 - ffff880037058000) [ 1.697700] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 1.704118] software IO TLB [mem 0xca492000-0xce492000] (64MB) mapped at [ffff8800ca492000-ffff8800ce491fff] [ 1.714164] RAPL PMU detected, hw unit 2^-16 Joules, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer [ 1.724674] microcode: CPU0 sig=0x306a9, pf=0x2, revision=0x1b [ 1.730426] microcode: CPU1 sig=0x306a9, pf=0x2, revision=0x1b [ 1.736250] microcode: CPU2 sig=0x306a9, pf=0x2, revision=0x1b [ 1.750730] microcode: CPU3 sig=0x306a9, pf=0x2, revision=0x1b [ 1.756546] microcode: CPU4 sig=0x306a9, pf=0x2, revision=0x1b [ 1.762360] microcode: CPU5 sig=0x306a9, pf=0x2, revision=0x1b [ 1.768179] microcode: CPU6 sig=0x306a9, pf=0x2, revision=0x1b [ 1.773991] microcode: CPU7 sig=0x306a9, pf=0x2, revision=0x1b [ 1.779835] microcode: Microcode Update Driver: v2.00 <ti...@ai...>, Peter Oruba [ 1.788826] futex hash table entries: 2048 (order: 5, 131072 bytes) [ 1.795033] audit: initializing netlink subsys (disabled) [ 1.800388] audit: type=2000 audit(1443100076.548:1): initialized [ 1.806664] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 1.812933] zpool: loaded [ 1.815517] zbud: loaded [ 1.818158] VFS: Disk quotas dquot_6.5.2 [ 1.821997] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 1.828445] msgmni has been set to 32768 [ 1.832595] alg: No test for stdrng (krng) [ 1.836625] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 1.844014] io scheduler noop registered [ 1.847878] io scheduler deadline registered [ 1.852131] io scheduler cfq registered (default) [ 1.856959] pcieport 0000:00:01.0: irq 24 for MSI/MSI-X [ 1.857070] pcieport 0000:00:01.1: irq 25 for MSI/MSI-X [ 1.857283] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 1.862775] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [ 1.869391] intel_idle: MWAIT substates: 0x1120 [ 1.869392] intel_idle: v0.4 model 0x3A [ 1.869393] intel_idle: lapic_timer_reliable_states 0xffffffff [ 1.869628] ERST: Error Record Serialization Table (ERST) support is initialized. [ 1.877034] pstore: Registered erst as persistent store backend [ 1.882975] GHES: APEI firmware first mode is enabled by WHEA _OSC. [ 1.889229] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.915898] 00:06: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A [ 1.943574] 00:07: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A [ 1.971232] 00:09: ttyS2 at I/O 0x3e8 (irq = 10, base_baud = 115200) is a 16550A [ 1.978753] Linux agpgart interface v0.103 [ 1.982831] i8042: PNP: No PS/2 controller found. Probing ports directly. [ 1.992701] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 1.997575] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 2.002720] mousedev: PS/2 mouse device common for all mice [ 2.008232] rtc_cmos 00:02: RTC can wake from S4 [ 2.012908] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0 [ 2.018943] rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs [ 2.026564] ledtrig-cpu: registered to indicate activity on CPUs [ 2.032717] AMD IOMMUv2 driver by Joerg Roedel <joe...@am...> [ 2.039059] AMD IOMMUv2 functionality not available on this system [ 2.045283] TCP: cubic registered [ 2.048521] IPv6: Loaded, but administratively disabled, reboot required to enable [ 2.056071] mip6: Mobile IPv6 [ 2.059020] mip6: mip6_init: can't add xfrm type(destopt) [ 2.064404] NET: Registered protocol family 17 [ 2.068836] mpls_gso: MPLS GSO support [ 2.072972] registered taskstats version 1 [ 2.077499] rtc_cmos 00:02: setting system clock to 2015-09-24 13:07:57 UTC (1443100077) [ 2.085560] PM: Hibernation image not present or could not be loaded. [ 2.086094] Freeing unused kernel memory: 1228K (ffffffff818f3000 - ffffffff81a26000) [ 2.093851] Write protecting the kernel read-only data: 8192k [ 2.100532] Freeing unused kernel memory: 620K (ffff880001565000 - ffff880001600000) [ 2.108556] Freeing unused kernel memory: 216K (ffff8800017ca000 - ffff880001800000) [ 2.123393] udevd[94]: starting version 175 [ 2.131920] pps_core: LinuxPPS API ver. 1 registered [ 2.136823] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <gio...@li...> [ 2.147106] PTP clock support registered [ 2.151071] ACPI: bus type USB registered [ 2.155038] usbcore: registered new interface driver usbfs [ 2.160469] usbcore: registered new interface driver hub [ 2.165787] usbcore: registered new device driver usb [ 2.171019] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [ 2.176789] e1000e: Copyright(c) 1999 - 2014 Intel Corporation. [ 2.182928] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 2.189595] ehci-pci: EHCI PCI platform driver [ 2.194192] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.3.39.1 [ 2.197599] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 2.197641] e1000e 0000:00:19.0: irq 26 for MSI/MSI-X [ 2.198073] thermal LNXTHERM:00: registered as thermal_zone0 [ 2.198073] ACPI: Thermal Zone [TZ00] (28 C) [ 2.198216] thermal LNXTHERM:01: registered as thermal_zone1 [ 2.198216] ACPI: Thermal Zone [TZ01] (30 C) [ 2.231104] i40e: Copyright (c) 2013 - 2015 Intel Corporation. [ 2.249391] i40e 0000:02:00.0: fw 4.40.35115 api 1.4 nvm 4.53 0x80001dc0 1.123.0 [ 2.256998] SCSI subsystem initialized [ 2.261957] libata version 3.00 loaded. [ 2.453377] e1000e 0000:00:19.0 eth0: registered PHC clock [ 2.458796] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:25:90:a8:02:51 [ 2.466693] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection [ 2.473600] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF [ 2.480564] ehci-pci 0000:00:1a.0: EHCI Host Controller [ 2.480631] e1000e 0000:05:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 2.480663] e1000e 0000:05:00.0: irq 27 for MSI/MSI-X [ 2.480665] e1000e 0000:05:00.0: irq 28 for MSI/MSI-X [ 2.480667] e1000e 0000:05:00.0: irq 29 for MSI/MSI-X [ 2.495076] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1 [ 2.495874] i40e 0000:02:00.0: MAC address: 3c:fd:fe:9c:56:b8 [ 2.499857] i40e 0000:02:00.0: SAN MAC: 3c:fd:fe:9c:56:ba [ 2.513542] ehci-pci 0000:00:1a.0: debug port 2 [ 2.514095] i40e 0000:02:00.0: irq 30 for MSI/MSI-X [ 2.514098] i40e 0000:02:00.0: irq 31 for MSI/MSI-X [ 2.514099] i40e 0000:02:00.0: irq 32 for MSI/MSI-X [ 2.514101] i40e 0000:02:00.0: irq 33 for MSI/MSI-X [ 2.514103] i40e 0000:02:00.0: irq 34 for MSI/MSI-X [ 2.514105] i40e 0000:02:00.0: irq 35 for MSI/MSI-X [ 2.514107] i40e 0000:02:00.0: irq 36 for MSI/MSI-X [ 2.514108] i40e 0000:02:00.0: irq 37 for MSI/MSI-X [ 2.514110] i40e 0000:02:00.0: irq 38 for MSI/MSI-X [ 2.514111] i40e 0000:02:00.0: irq 39 for MSI/MSI-X [ 2.514113] i40e 0000:02:00.0: irq 40 for MSI/MSI-X [ 2.514114] i40e 0000:02:00.0: irq 41 for MSI/MSI-X [ 2.514116] i40e 0000:02:00.0: irq 42 for MSI/MSI-X [ 2.514118] i40e 0000:02:00.0: irq 43 for MSI/MSI-X [ 2.514119] i40e 0000:02:00.0: irq 44 for MSI/MSI-X [ 2.514121] i40e 0000:02:00.0: irq 45 for MSI/MSI-X [ 2.514122] i40e 0000:02:00.0: irq 46 for MSI/MSI-X [ 2.514124] i40e 0000:02:00.0: irq 47 for MSI/MSI-X [ 2.521951] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported [ 2.521964] ehci-pci 0000:00:1a.0: irq 16, io mem 0xdfb24000 [ 2.537912] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00 [ 2.543607] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 2.550333] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.557541] usb usb1: Product: EHCI Host Controller [ 2.562399] usb usb1: Manufacturer: Linux 3.18.20 ehci_hcd [ 2.568471] usb usb1: SerialNumber: 0000:00:1a.0 [ 2.573164] hub 1-0:1.0: USB hub found [ 2.576818] hub 1-0:1.0: 2 ports detected [ 2.580962] ehci-pci 0000:00:1d.0: EHCI Host Controller [ 2.586095] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2 [ 2.593480] ehci-pci 0000:00:1d.0: debug port 2 [ 2.599535] e1000e 0000:05:00.0 eth2: registered PHC clock [ 2.601911] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported [ 2.601922] ehci-pci 0000:00:1d.0: irq 23, io mem 0xdfb23000 [ 2.610602] e1000e 0000:05:00.0 eth2: (PCI Express:2.5GT/s:Width x1) 00:25:90:a8:02:50 [ 2.613936] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00 [ 2.613963] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 2.613964] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.613965] usb usb2: Product: EHCI Host Controller [ 2.613965] usb usb2: Manufacturer: Linux 3.18.20 ehci_hcd [ 2.613966] usb usb2: SerialNumber: 0000:00:1d.0 [ 2.614075] hub 2-0:1.0: USB hub found [ 2.614078] hub 2-0:1.0: 2 ports detected [ 2.614192] ahci 0000:00:1f.2: version 3.0 [ 2.614340] ahci 0000:00:1f.2: irq 48 for MSI/MSI-X [ 2.614485] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 3 Gbps 0x3f impl SATA mode [ 2.614486] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst [ 2.626630] i40e 0000:02:00.0: PCI-Express: Speed 8.0GT/s Width x8 [ 2.654604] scsi host0: ahci [ 2.654992] i40e 0000:02:00.0: Features: PF-id[0] VFs: 64 VSIs: 66 QP: 8 RX: 1BUF RSS FD_ATR FD_SB NTUPLE DCB VxLAN PTP VEPA [ 2.657763] scsi host1: ahci [ 2.658083] scsi host2: ahci [ 2.658320] scsi host3: ahci [ 2.658546] scsi host4: ahci [ 2.658747] scsi host5: ahci [ 2.658785] ata1: SATA max UDMA/133 abar m2048@0xdfb22000 port 0xdfb22100 irq 48 [ 2.658788] ata2: SATA max UDMA/133 abar m2048@0xdfb22000 port 0xdfb22180 irq 48 [ 2.658790] ata3: SATA max UDMA/133 abar m2048@0xdfb22000 port 0xdfb22200 irq 48 [ 2.658792] ata4: SATA max UDMA/133 abar m2048@0xdfb22000 port 0xdfb22280 irq 48 [ 2.658795] ata5: SATA max UDMA/133 abar m2048@0xdfb22000 port 0xdfb22300 irq 48 [ 2.658798] ata6: SATA max UDMA/133 abar m2048@0xdfb22000 port 0xdfb22380 irq 48 [ 2.670025] i40e 0000:02:00.1: fw 4.40.35115 api 1.4 nvm 4.53 0x80001dc0 1.123.0 [ 2.714122] tsc: Refined TSC clocksource calibration: 3500.024 MHz [ 2.769612] e1000e 0000:05:00.0 eth2: Intel(R) PRO/1000 Network Connection [ 2.776551] e1000e 0000:05:00.0 eth2: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF [ 2.890322] usb 1-1: new high-speed USB device number 2 using ehci-pci [ 2.916415] i40e 0000:02:00.1: MAC address: 3c:fd:fe:9c:56:b9 [ 2.926260] i40e 0000:02:00.1: SAN MAC: 3c:fd:fe:9c:56:bb [ 2.930381] usb 2-1: new high-speed USB device number 2 using ehci-pci [ 2.952496] i40e 0000:02:00.1: irq 49 for MSI/MSI-X [ 2.952503] i40e 0000:02:00.1: irq 50 for MSI/MSI-X [ 2.952508] i40e 0000:02:00.1: irq 51 for MSI/MSI-X [ 2.952512] i40e 0000:02:00.1: irq 52 for MSI/MSI-X [ 2.952516] i40e 0000:02:00.1: irq 53 for MSI/MSI-X [ 2.952520] i40e 0000:02:00.1: irq 54 for MSI/MSI-X [ 2.952525] i40e 0000:02:00.1: irq 55 for MSI/MSI-X [ 2.952537] i40e 0000:02:00.1: irq 56 for MSI/MSI-X [ 2.952539] i40e 0000:02:00.1: irq 57 for MSI/MSI-X [ 2.952541] i40e 0000:02:00.1: irq 58 for MSI/MSI-X [ 2.952543] i40e 0000:02:00.1: irq 59 for MSI/MSI-X [ 2.952545] i40e 0000:02:00.1: irq 60 for MSI/MSI-X [ 2.952547] i40e 0000:02:00.1: irq 61 for MSI/MSI-X [ 2.952549] i40e 0000:02:00.1: irq 62 for MSI/MSI-X [ 2.952550] i40e 0000:02:00.1: irq 63 for MSI/MSI-X [ 2.952554] i40e 0000:02:00.1: irq 64 for MSI/MSI-X [ 2.952556] i40e 0000:02:00.1: irq 65 for MSI/MSI-X [ 2.952558] i40e 0000:02:00.1: irq 66 for MSI/MSI-X [ 2.978497] ata5: SATA link down (SStatus 0 SControl 300) [ 2.983838] ata6: SATA link down (SStatus 0 SControl 300) [ 2.989225] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 2.995381] ata4: SATA link down (SStatus 0 SControl 300) [ 3.000756] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 3.007184] ata2: SATA link down (SStatus 0 SControl 300) [ 3.012510] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded [ 3.012514] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out [ 3.020391] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out [ 3.026954] usb 1-1: New USB device found, idVendor=8087, idProduct=0024 [ 3.026955] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 3.027240] hub 1-1:1.0: USB hub found [ 3.027332] hub 1-1:1.0: 6 ports detected [ 3.050510] ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded [ 3.050512] ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out [ 3.061847] i40e 0000:02:00.1: PCI-Express: Speed 8.0GT/s Width x8 [ 3.067012] usb 2-1: New USB device found, idVendor=8087, idProduct=0024 [ 3.067013] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 3.067296] hub 2-1:1.0: USB hub found [ 3.067384] hub 2-1:1.0: 6 ports detected [ 3.090237] i40e 0000:02:00.1: Features: PF-id[1] VFs: 64 VSIs: 66 QP: 8 RX: 1BUF RSS FD_ATR FD_SB NTUPLE DCB VxLAN PTP VEPA [ 3.103551] ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out [ 3.112266] ata1.00: ATA-8: INTEL SSDSC2BA200G3, 5DV10250, max UDMA/133 [ 3.118799] ata1.00: 390721968 sectors, multi 1: LBA48 NCQ (depth 31/32) [ 3.125486] ata3.00: ATAPI: HL-DT-ST DVDRAM GT80N, 1.00, max UDMA/133 [ 3.132254] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded [ 3.132259] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out [ 3.140106] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out [ 3.148916] ata1.00: configured for UDMA/133 [ 3.153298] scsi 0:0:0:0: Direct-Access ATA INTEL SSDSC2BA20 0250 PQ: 0 ANSI: 5 [ 3.154140] ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded [ 3.154142] ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out [ 3.154143] ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out [ 3.156130] ata3.00: configured for UDMA/133 [ 3.185352] scsi 2:0:0:0: CD-ROM HL-DT-ST DVDRAM GT80N 1.00 PQ: 0 ANSI: 5 [ 3.298953] usb 1-1.2: new full-speed USB device number 3 using ehci-pci [ 3.323219] sd 0:0:0:0: [sda] 390721968 512-byte logical blocks: (200 GB/186 GiB) [ 3.330670] sd 0:0:0:0: [sda] Write Protect is off [ 3.335418] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 3.335427] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 3.338917] sr 2:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray [ 3.338918] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 3.339081] sr 2:0:0:0: Attached scsi CD-ROM sr0 [ 3.358408] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 3.358668] sda: sda1 sda2 [ 3.358886] sd 0:0:0:0: [sda] Attached SCSI disk [ 3.371134] sr 2:0:0:0: Attached scsi generic sg1 type 5 [ 3.396737] usb 1-1.2: New USB device found, idVendor=0557, idProduct=2221 [ 3.403526] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.410814] usb 1-1.2: Product: Hermon USB hidmouse Device [ 3.416282] usb 1-1.2: Manufacturer: Winbond Electronics Corp [ 3.423736] hidraw: raw HID events driver (C) Jiri Kosina [ 3.430436] usbcore: registered new interface driver usbhid [ 3.435922] usbhid: USB HID core driver [ 3.440716] input: Winbond Electronics Corp Hermon USB hidmouse Device as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:0557:2221.0001/input/input2 [ 3.455434] hid-generic 0003:0557:2221.0001: input,hidraw0: USB HID v1.00 Mouse [Winbond Electronics Corp Hermon USB hidmouse Device] on usb-0000:00:1a.0-1.2/input0 [ 3.470147] input: Winbond Electronics Corp Hermon USB hidmouse Device as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/0003:0557:2221.0002/input/input3 [ 3.484849] hid-generic 0003:0557:2221.0002: input,hidraw1: USB HID v1.00 Keyboard [Winbond Electronics Corp Hermon USB hidmouse Device] on usb-0000:00:1a.0-1.2/input1 [ 3.507384] PM: Starting manual resume from disk [ 3.511922] PM: Hibernation image partition 8:1 present [ 3.511923] PM: Looking for hibernation image. [ 3.512127] PM: Image not found (code -22) [ 3.512131] PM: Hibernation image not present or could not be loaded. [ 3.517313] EXT4-fs (sda2): mounting ext3 file system using the ext4 subsystem [ 3.529000] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 3.715841] Switched to clocksource tsc [ 3.885031] udevd[667]: starting version 175 [ 4.011695] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4 [ 4.020070] ACPI: Power Button [PWRB] [ 4.023703] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 [ 4.031033] ACPI: Power Button [PWRF] [ 4.034781] EDAC MC: Ver: 3.0.0 [ 4.038626] EDAC MC0: Giving out device to module ie31200_edac controller IE31200: DEV 0000:00:00.0 (POLLED) [ 4.115904] ipmi message handler version 39.2 [ 4.121319] IPMI System Interface driver. [ 4.126068] ipmi_si: probing via ACPI [ 4.129851] ipmi_si 00:0a: [io 0x0ca2] regsize 1 spacing 1 irq 0 [ 4.135777] i40e 0000:02:00.1 rename5: renamed from eth3 [ 4.141149] ipmi_si: Adding ACPI-specified kcs state machine [ 4.147092] ipmi_si: probing via SMBIOS [ 4.147160] input: PC Speaker as /devices/platform/pcspkr/input/input6 [ 4.157409] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0 [ 4.163305] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface [ 4.170854] ipmi_si: probing via SPMI [ 4.174504] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0 [ 4.177849] i40e 0000:02:00.0 rename3: renamed from eth1 [ 4.185527] ipmi_si: Adding SPMI-specified kcs state machine [ 4.185655] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20140926/utaddress-254) [ 4.185658] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 4.185660] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140926/utaddress-254) [ 4.185662] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 4.185662] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140926/utaddress-254) [ 4.185664] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 4.185664] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140926/utaddress-254) [ 4.185665] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 4.185665] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 4.280990] iTCO_vendor_support: vendor-support=0 [ 4.304270] duplicate interface [ 4.307664] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0 [ 4.318187] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [ 4.323711] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460) [ 4.323818] e1000e 0000:00:19.0 eth3: renamed from eth0 [ 4.336446] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 4.342474] AVX version of gcm_enc/dec engaged. [ 4.346907] AES CTR mode by8 optimization enabled [ 4.351931] i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt [ 4.352819] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [ 4.364158] i40e 0000:02:00.1 eth1: renamed from rename5 [ 4.370154] [drm] Initialized drm 1.1.0 20060810 [ 4.374797] Error: Driver 'pcspkr' is already registered, aborting... [ 4.381228] alg: No test for crc32 (crc32-pclmul) [ 4.395990] [TTM] Zone kernel: Available graphics memory: 16494382 kiB [ 4.396626] i40e 0000:02:00.0 eth0: renamed from rename3 [ 4.407813] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [ 4.414324] [TTM] Initializing pool allocator [ 4.418678] [TTM] Initializing DMA pool allocator [ 4.425605] intel_rapl: Found RAPL domain package [ 4.430215] intel_rapl: Found RAPL domain core [ 4.446166] fbcon: mgadrmfb (fb0) is primary device [ 4.489833] ipmi_si 00:0a: Found new BMC (man_id: 0x002a7c, prod_id: 0x0624, dev_id: 0x20) [ 4.489843] ipmi_si 00:0a: IPMI kcs interface initialized [ 4.604074] Console: switching to colour frame buffer device 128x48 [ 4.698245] mgag200 0000:06:03.0: fb0: mgadrmfb frame buffer device [ 4.704491] mgag200 0000:06:03.0: registered panic notifier [ 4.733133] [drm] Initialized mgag200 1.0.0 20110418 for 0000:06:03.0 on minor 0 [ 4.975874] Adding 3905532k swap on /dev/sda1. Priority:-1 extents:1 across:3905532k SSFS [ 5.002394] EXT4-fs (sda2): re-mounted. Opts: (null) [ 5.044749] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro [ 5.077354] loop: module loaded [ 5.087636] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) [ 5.101990] nf_conntrack version 0.5.0 (17374463 buckets, 138995704 max) [ 5.108653] nf_conntrack: falling back to vmalloc. [ 5.735510] random: dd urandom read with 92 bits of entropy available [ 5.927034] bond0: Setting xmit hash policy to layer3+4 (1) [ 5.927105] bond0: Setting MII monitoring interval to 100 [ 5.963685] bond0: Setting LACP rate to slow (0) [ 6.119830] bond0: Adding slave eth0 [ 6.119841] i40e 0000:02:00.0 eth0: already using mac address 3c:fd:fe:9c:56:b8 [ 6.123689] i40e 0000:02:00.0 eth0: NIC Link is Up 10 Gbps Full Duplex, Flow Control: None [ 6.123746] bond0: Enslaving eth0 as a backup interface with an up link [ 6.126208] bond0: Adding slave eth1 [ 6.126212] i40e 0000:02:00.1 eth1: set new mac address 3c:fd:fe:9c:56:b8 [ 6.135693] i40e 0000:02:00.1 eth1: NIC Link is Up 10 Gbps Full Duplex, Flow Control: None [ 6.135756] bond0: Enslaving eth1 as a backup interface with an up link [ 7.145905] random: nonblocking pool is initialized [ 12.460991] Process accounting resumed [ 12.918920] e1000e 0000:00:19.0: irq 26 for MSI/MSI-X [ 13.021814] e1000e 0000:00:19.0: irq 26 for MSI/MSI-X [ 13.279044] nf_conntrack: falling back to vmalloc. [ 13.323161] ip_tables: (C) 2000-2006 Netfilter Core Team On 2015-08-27 16:43, Rose, Gregory V wrote: >> -----Original Message----- >> From: Christian Ruppert [mailto:id...@qa...] >> Sent: Thursday, August 27, 2015 4:54 AM >> To: Fujinaka, Todd >> Cc: Rose, Gregory V; e10...@li... >> Subject: RE: [E1000-devel] X710 / i40e interface resets >> >> Well, that's it for now anyway... >> >> ... >> Power cycle is required to complete the update process. >> Tool execution completed with the following status: All operations >> completed successfully >> >> The card doesn't even appear in "lspci" anymore... :/ I used a Win7 to >> flash it since a co-worker already broke one when flashing via Linux. >> No >> idea how to unbrick it. > > Christian, > > I'm very sorry to hear that. It is pretty rare for this sort of thing > to happen but not unheard of. Please contact su...@in... to get > help replacing the part. > > - Greg > >> >> >> On 2015-08-27 01:25, Fujinaka, Todd wrote: >> > Attachments don't work on this mailing list (though they may have >> > gotten to Greg). Please file a bug on e1000.sourceforge.net and attach >> > the files there. >> > >> > Todd Fujinaka >> > Software Application Engineer >> > Networking Division (ND) >> > Intel Corporation >> > tod...@in... >> > (503) 712-4565 >> > >> > -----Original Message----- >> > From: Christian Ruppert [mailto:id...@qa...] >> > Sent: Wednesday, August 26, 2015 10:24 AM >> > To: Rose, Gregory V >> > Cc: e10...@li... >> > Subject: Re: [E1000-devel] X710 / i40e interface resets >> > >> > On 2015-08-26 01:19, Rose, Gregory V wrote: >> >>> -----Original Message----- >> >>> From: Christian Ruppert [mailto:id...@qa...] >> >>> Sent: Friday, August 21, 2015 7:06 AM >> >>> To: Rose, Gregory V >> >>> Cc: e10...@li... >> >>> Subject: RE: [E1000-devel] X710 / i40e interface resets >> >>> >> >>> On 2015-07-28 18:51, Rose, Gregory V wrote: >> >>> >> -----Original Message----- >> >>> >> From: Christian Ruppert [mailto:id...@qa...] >> >>> >> Sent: Tuesday, July 28, 2015 5:43 AM >> >>> >> To: Rose, Gregory V >> >>> >> Cc: e10...@li... >> >>> >> Subject: RE: [E1000-devel] X710 / i40e interface resets >> >>> >> >> >> >> >> [snip] >> >> >> >>> > I've been told that the Tx driver issue detected message is due to >> >>> > a MDD (Malicious Driver Detection) event. We need to find out what >> >>> > is causing that so if you could please send me your system log and >> >>> > the output of ethtool <intf> and ethtool -i <intf> perhaps I can >> >>> > see what might be occurring. If not then we'll have to debug >> further. >> >>> >> >>> See the initial Mail for ethtool -k and so on. Also: >> >>> # ethtool eth0 >> >>> Settings for eth0: >> >>> Supported ports: [ FIBRE ] >> >>> Supported link modes: 1000baseT/Full >> >>> 10000baseT/Full >> >>> S... [truncated message content] |
|
From: Anitha S. <ani...@gm...> - 2015-09-25 06:18:37
|
hi, we have tested without VMware environment. the issue is still seen. while upgrading kernel, vlan tagging is being stripped out. Please let me know if you have any inputs. Thanks, Anitha On Fri, Sep 18, 2015 at 12:00 PM, Anitha Subramanian < ani...@gm...> wrote: > Hi, > > vlan is not working when we upgrade linux kernel from 2.6.32-431.el6.i686 > to 2.6.32-573.3.1.el6.i686. > > Tried e1000 drivers: > e1000 7.3.21 > e1000 8.0.35-NAPI > when testing with one of above e1000 driver versions, we have tried to use > intermediate kernel versions between working and failure of vlan trunking, > the results of uname are below. > kernel-2.6.32-431.el6.i686 - passed > kernel-2.6.32-504.16.2.el6.i686 -passed > kernel-2.6.32-504.23.4.el6.i686 -not working > kernel-2.6.32-504.30.3.el6.i686 - not working > kernel-2.6.32-573.3.1.el6.i686 -not working > Linux centos-6.5 2.6.36 -passed > Linux centos-6.5 3.5.0 - not working > > we have tried both embedded and standalone drivers and the result is same. > the vlan tagged packets are received in linux and linux is removing its tag > and gives to our application. so we see vlan ping failure with "wrong > cable" message. > as mentioned in search forum, we have tried to turn on/off rx-vlan-filter > and offload setting, but we could not change it, as it is denoted as > [fixed]. > just to confirm the issue with pcnet32 driver with failure kernel, > eventhough rx-vlan-filter is off as below, still facing issue. > [root@localhost drivers]# ethtool -k eth5 | grep vlan > rx-vlan-offload: off [fixed] > tx-vlan-offload: off [fixed] > rx-vlan-filter: off [fixed] > vlan-challenged: off [fixed] > > we don't have the option to use e1000e driver. > Please let me know if any specific information is required. can you please > suggest us the latest stable kernel of 3.x version and e1000 driver > combination where rx vlan tagging works ? > > Appreciate your inputs on this. > > Thanks, > Anitha > > PS: below bug is raised. but as per Todd suggestion in below mail thread, > sending this email to alias. > https://sourceforge.net/p/e1000/bugs/491/ > > > > ---------- Forwarded message ---------- > From: Todd Fujinaka <htf...@us...> > Date: Wed, Sep 16, 2015 at 7:36 PM > Subject: [e1000:bugs] #491 vlan tag removed in promiscuous mode with > kernel 2.6.32-573.3.1.el6.i686 and e1000 driver > To: "[e1000:bugs]" <49...@bu...> > > > > - *status*: open --> closed > - *Comment*: > > e1000 drivers are supported by the community. Please try the e1000-devel > mailing list or contact vmware. > ------------------------------ > > > > > > |
|
From: Alexander D. <ale...@gm...> - 2015-09-24 02:59:51
|
On 09/23/2015 07:35 PM, YeYin wrote: > Hi, all, > > > When I enable SR-IOV with ixgbevf: > > [ 56.126379] ixgbevf 0000:01:10.0: enabling device (0000 -> 0002) > [ 56.263462] ixgbevf 0000:01:10.0: PF still in reset state. Is the PF interface up? > [ 56.355415] ixgbevf 0000:01:10.0: Assigning random MAC address > [ 56.425444] ixgbevf: probe of 0000:01:10.0 failed with error -15 > > > > However I enable SR-IOV with igbvf: > > > [ 63.974721] igbvf 0000:01:12.1: enabling device (0000 -> 0002) > [ 64.044339] igbvf 0000:01:12.1: irq 151 for MSI/MSI-X > [ 64.044350] igbvf 0000:01:12.1: irq 152 for MSI/MSI-X > [ 64.044360] igbvf 0000:01:12.1: irq 153 for MSI/MSI-X > [ 64.045505] igbvf 0000:01:12.1: PF still in reset state. Is the PF interface up? > [ 64.133980] igbvf 0000:01:12.1: Assigning random MAC address. > [ 64.203651] igbvf 0000:01:12.1: PF still resetting > [ 64.260990] igbvf 0000:01:12.1: Intel(R) I350 Virtual Function > [ 64.330564] igbvf 0000:01:12.1: Address: 0e:ce:51:a0:4b:9f > > > > As we can see, igbvf will complete VF initialization when found PF in reset state. However, ixgbevf will return error(IXGBE_ERR_RESET_FAILED) when found PF in reset state. Obviously, igbvf ignored this error. > However, the following was written on the 82576 datasheet: > > > Until a RSTD condition is detected, the VFs should access only the VFMailbox register and should not attempt to activate the interrupt mechanism or the transmit and receive process. > > > Is this a bug of igbvf ? > > > Thanks, > Ye It's just a difference of opinion in implementation. Back when I worked on igbvf I felt that it should allow you to load the driver even if the PF is not present as trying to reload it after the fact can be a pain. So as a result the igbvf driver will assign itself a random MAC address and report link down until the PF is loaded. One side effect of that is that it will come up with a random MAC address in that situation so if you do this frequently you might notice udev creating a number of rules for ethX interfaces if it isn't using PCIe slot naming. The decision for the ixgbevf driver was to require a the user to reload/rescan if the VF driver is loaded before the PF is up. This forced the interface to wait until the PF was up and ready to assign MAC addresses so that the VF should have a consistent address. Though I think there might be a code difference in the end of the function ixgbevf_sw_init between the driver on e1000.sf.net and the one in the Linux kernel. From what I can tell the one in the kernel might load with a random MAC address like igbvf while the out-of-tree driver will fail with the error as you have described. - Alex |
|
From: Y. <ey...@qq...> - 2015-09-24 02:36:24
|
Hi, all, When I enable SR-IOV with ixgbevf: [ 56.126379] ixgbevf 0000:01:10.0: enabling device (0000 -> 0002) [ 56.263462] ixgbevf 0000:01:10.0: PF still in reset state. Is the PF interface up? [ 56.355415] ixgbevf 0000:01:10.0: Assigning random MAC address [ 56.425444] ixgbevf: probe of 0000:01:10.0 failed with error -15 However I enable SR-IOV with igbvf: [ 63.974721] igbvf 0000:01:12.1: enabling device (0000 -> 0002) [ 64.044339] igbvf 0000:01:12.1: irq 151 for MSI/MSI-X [ 64.044350] igbvf 0000:01:12.1: irq 152 for MSI/MSI-X [ 64.044360] igbvf 0000:01:12.1: irq 153 for MSI/MSI-X [ 64.045505] igbvf 0000:01:12.1: PF still in reset state. Is the PF interface up? [ 64.133980] igbvf 0000:01:12.1: Assigning random MAC address. [ 64.203651] igbvf 0000:01:12.1: PF still resetting [ 64.260990] igbvf 0000:01:12.1: Intel(R) I350 Virtual Function [ 64.330564] igbvf 0000:01:12.1: Address: 0e:ce:51:a0:4b:9f As we can see, igbvf will complete VF initialization when found PF in reset state. However, ixgbevf will return error(IXGBE_ERR_RESET_FAILED) when found PF in reset state. Obviously, igbvf ignored this error. However, the following was written on the 82576 datasheet: Until a RSTD condition is detected, the VFs should access only the VFMailbox register and should not attempt to activate the interrupt mechanism or the transmit and receive process. Is this a bug of igbvf ? Thanks, Ye |
|
From: Skidmore, D. C <don...@in...> - 2015-09-22 17:12:21
|
Hey Tal Abudi, The Fake Tx hang message means that the stack is trying to reset the driver since it "thinks" we are hung however the driver doesn't believe that there is anything it can transmit. This is most often cased but excessive flow control or a faulty switch. What does your ethtool stats show? And you might what to test with FC disabled (assuming you have it enabled currently) to see if the messages go away. Thanks, -Don Skidmore <don...@in...> > -----Original Message----- > From: Tal Abudi [mailto:tal...@gm...] > Sent: Monday, September 21, 2015 11:37 PM > To: e10...@li... > Subject: [E1000-devel] Fake TX hangs > > Hi All > My system is experiencing strange fake TX hangs. I'm running ixgbe > 3.9.15 on a modified 2.6.18 Linux (with multi queue enabled, Per TX queue > lock). > > ixgbe 0000:82:00.1: eth0: Fake Tx hang detected with timeout of 5 seconds > NETDEV WATCHDOG: eth0: transmit timed out ixgbe 0000:82:00.1: eth0: Fake > Tx hang detected with timeout of 10 seconds NETDEV WATCHDOG: eth0: > transmit timed out ixgbe 0000:82:00.1: eth0: Fake Tx hang detected with > timeout of 20 seconds > > And this keeps going on. > The messages are from ixgbe_tx_timeout() which is invoked from > dev_watchdog() (sch_generic.c) > > I instrumented the kernel and the ixgbe driver and found that > ixgbe_maybe_stop_tx() stop a tx queue in ixgbe_xmit_frame_ring(). > > Please help me figure out where the queue is restart or the device is > restarted. > Looking at ethtool -S show tx_restart_queue as 0. > I'm running a Spirent Avalanche test so it's quite consistent. > > Any leads ? > Thanks ! > > -- > Best regards, > Tal Abudi > > ------------------------------------------------------------------------------ > _______________________________________________ > E1000-devel mailing list > E10...@li... > https://lists.sourceforge.net/lists/listinfo/e1000-devel > To learn more about Intel® Ethernet, visit > http://communities.intel.com/community/wired |
|
From: Tal A. <tal...@gm...> - 2015-09-22 06:37:24
|
Hi All My system is experiencing strange fake TX hangs. I'm running ixgbe 3.9.15 on a modified 2.6.18 Linux (with multi queue enabled, Per TX queue lock). ixgbe 0000:82:00.1: eth0: Fake Tx hang detected with timeout of 5 seconds NETDEV WATCHDOG: eth0: transmit timed out ixgbe 0000:82:00.1: eth0: Fake Tx hang detected with timeout of 10 seconds NETDEV WATCHDOG: eth0: transmit timed out ixgbe 0000:82:00.1: eth0: Fake Tx hang detected with timeout of 20 seconds And this keeps going on. The messages are from ixgbe_tx_timeout() which is invoked from dev_watchdog() (sch_generic.c) I instrumented the kernel and the ixgbe driver and found that ixgbe_maybe_stop_tx() stop a tx queue in ixgbe_xmit_frame_ring(). Please help me figure out where the queue is restart or the device is restarted. Looking at ethtool -S show tx_restart_queue as 0. I'm running a Spirent Avalanche test so it's quite consistent. Any leads ? Thanks ! -- Best regards, Tal Abudi |
|
From: Skidmore, D. C <don...@in...> - 2015-09-21 16:53:39
|
These version numbers don't mean as much as you would expect them too. We try very hard to keep the source forge driver has close as possible to the current in kernel driver but there are differences for various reasons. (i.e. kcompat issues, differing module parameters, etc). That said we are even a little bit more out of sync at the moment, after pushing some additional support upstream that hasn't been included in the source forge driver yet. My hope was to sync them back up around a 4.2.x version, in a month or two. As for 4.1 kernel support, we are currently working on a point release for the source forge driver (4.1.x) that will include 4.1 kernel support. I expect it to be on source forge sometime later this week. Thanks, -Don <don...@in...> > -----Original Message----- > From: Stefan Priebe - Profihost AG [mailto:s.p...@pr...] > Sent: Monday, September 21, 2015 9:28 AM > To: Rose, Gregory V > Cc: e10...@li... > Subject: Re: [E1000-devel] new ixgbe driver for kernel 4.1 and newer? > > The included one is 4.0.1. sourceforge is at 4.1.2 > > Stefan > > Excuse my typo sent from my mobile phone. > > > Am 21.09.2015 um 17:54 schrieb Rose, Gregory V > <gre...@in...>: > > > > The 4.1 kernel should have an up to date driver included in the kernel. > > > > - Greg > > > >> -----Original Message----- > >> From: Stefan Priebe - Profihost AG [mailto:s.p...@pr...] > >> Sent: Monday, September 21, 2015 8:03 AM > >> To: e10...@li... > >> Subject: [E1000-devel] new ixgbe driver for kernel 4.1 and newer? > >> > >> Hi, > >> > >> the current ixgbe driver available is not compatible with kernel 4.1 > >> and newer. > >> > >> Does anybody know when there is a newer version compatible with > >> kernel 4.1? > >> > >> Stefan > >> > >> --------------------------------------------------------------------- > >> ----- > >> ---- > >> _______________________________________________ > >> E1000-devel mailing list > >> E10...@li... > >> https://lists.sourceforge.net/lists/listinfo/e1000-devel > >> To learn more about Intel® Ethernet, visit > >> http://communities.intel.com/community/wired |
|
From: Stefan P. - P. AG <s.p...@pr...> - 2015-09-21 16:28:16
|
The included one is 4.0.1. sourceforge is at 4.1.2 Stefan Excuse my typo sent from my mobile phone. > Am 21.09.2015 um 17:54 schrieb Rose, Gregory V <gre...@in...>: > > The 4.1 kernel should have an up to date driver included in the kernel. > > - Greg > >> -----Original Message----- >> From: Stefan Priebe - Profihost AG [mailto:s.p...@pr...] >> Sent: Monday, September 21, 2015 8:03 AM >> To: e10...@li... >> Subject: [E1000-devel] new ixgbe driver for kernel 4.1 and newer? >> >> Hi, >> >> the current ixgbe driver available is not compatible with kernel 4.1 and >> newer. >> >> Does anybody know when there is a newer version compatible with kernel >> 4.1? >> >> Stefan >> >> -------------------------------------------------------------------------- >> ---- >> _______________________________________________ >> E1000-devel mailing list >> E10...@li... >> https://lists.sourceforge.net/lists/listinfo/e1000-devel >> To learn more about Intel® Ethernet, visit >> http://communities.intel.com/community/wired |
|
From: Rose, G. V <gre...@in...> - 2015-09-21 16:00:43
|
The 4.1 kernel should have an up to date driver included in the kernel. - Greg > -----Original Message----- > From: Stefan Priebe - Profihost AG [mailto:s.p...@pr...] > Sent: Monday, September 21, 2015 8:03 AM > To: e10...@li... > Subject: [E1000-devel] new ixgbe driver for kernel 4.1 and newer? > > Hi, > > the current ixgbe driver available is not compatible with kernel 4.1 and > newer. > > Does anybody know when there is a newer version compatible with kernel > 4.1? > > Stefan > > -------------------------------------------------------------------------- > ---- > _______________________________________________ > E1000-devel mailing list > E10...@li... > https://lists.sourceforge.net/lists/listinfo/e1000-devel > To learn more about Intel® Ethernet, visit > http://communities.intel.com/community/wired |
|
From: Stefan P. - P. AG <s.p...@pr...> - 2015-09-21 15:03:03
|
Hi, the current ixgbe driver available is not compatible with kernel 4.1 and newer. Does anybody know when there is a newer version compatible with kernel 4.1? Stefan |
|
From: Rose, G. V <gre...@in...> - 2015-09-18 14:18:46
|
From: Shankar Krishnamurthy [mailto:sha...@ci...]
Sent: Tuesday, September 15, 2015 11:00 PM
To: Rose, Gregory V; Shankar Krishnamurthy; e10...@li...
Subject: RE: [E1000-devel] Vlan Table in I40e XL710
Thanks for response.
> Why? You're setting a VLAN filter with the tag value of 25. Why do promiscuous mode in addition?
--> I was confirming that I am _not_ setting p.VPE (essentially disabling VLAN promiscuous ). We are in same page.
Still the packets are not going through.
To set and clear a VLAN filter should not require any call to the i40e_aq_set_and_clr_vsi_vlan_promiscuous() function at all.
Use the MAC+VLAN filters.
- Greg
'set' is just the opcode name ' i40e_aqc_set_vsi_promiscuous_modes' - same is used to 'clear' I guess.
The following code does this when 'set=0' is passed.
i40e_status i40e_aq_set_and_clr_vsi_vlan_promiscuous(struct i40e_hw *hw,
u16 seid, bool set, struct i40e_asq_cmd_details *cmd_details)
{
struct i40e_aq_desc desc;
struct i40e_aqc_set_vsi_promiscuous_modes *cmd =
(struct i40e_aqc_set_vsi_promiscuous_modes *)&desc.params.raw;
i40e_status status;
u16 flags = 0;
i40e_fill_default_direct_cmd_desc(&desc,
i40e_aqc_opc_set_vsi_promiscuous_modes);
if (set)
flags |= I40E_AQC_SET_VSI_PROMISC_VLAN;
cmd->promiscuous_flags = CPU_TO_LE16(flags);
cmd->valid_flags = CPU_TO_LE16(I40E_AQC_SET_VSI_PROMISC_VLAN);
cmd->seid = CPU_TO_LE16(seid);
status = i40e_asq_send_command(hw, &desc, NULL, 0, cmd_details);
return status;
}
In the contrary, this is not the way to set p.VPE=0 (as described in L2 filtering algorithm) or someother/additional action needs to be taken, please let me know
thanks,
Shankar.
-----Original Message-----
From: Rose, Gregory V [mailto:gre...@in...]
Sent: Tuesday, September 15, 2015 3:43 PM
To: Shankar Krishnamurthy <sha...@ci...<mailto:sha...@ci...>>; e10...@li...<mailto:e10...@li...>
Subject: RE: [E1000-devel] Vlan Table in I40e XL710
> -----Original Message-----
> From: Shankar Krishnamurthy [mailto:sha...@ci...]
> Sent: Tuesday, September 15, 2015 2:57 PM
> To: e10...@li...<mailto:e10...@li...>
> Subject: [E1000-devel] Vlan Table in I40e XL710
>
> Hi fortville Experts,
>
> Was trying to use VLAN Table (for filtering) in conjunction with
> MACVLAN table mentioned in "7.4.8.3 L2 Filtering Algorithm" (also cut
> n' pasted
> below)
>
> My test scenario:
> 1. In SRIOV mode, gave one VF to VM. For that, I added the
> corresponding MAC into MACVLAN table with vlan=25 2. Added VLAN table
> with vlan=25. (For p.VPE=0 I used
> 'i40e_aqc_opc_set_vsi_promiscuous_modes' opcode with vlan
> promiscuous.)
>
Why? You're setting a VLAN filter with the tag value of 25. Why do promiscuous mode in addition?
> Now the packets are coming into this VM.
>
> 1. Now, I delete the vlan=25 entry in the VLAN table (expecting that
> packets stop coming in) 2. Packets are still coming in.
Turn off promiscuous mode.
- Greg
>
> But I am confused with this behavior. According the algorithm below,
> Namely:
> " EFilter = MFilter and (VFilter or p.VPE} and AddressType == Unicast;"
>
> The packets should have stopped coming in. What am I missing?
>
> Is there any global setting /register that I need to toggle for the
> VLAN table to be effective?
>
> Is VSI setup needs additional flags? Not sure
>
> thanks,
> Shankar.
>
> I40e Driver Version: 1.2.37
>
> 7.4.8.3 L2 Filtering Algorithm
> The following pseudo code describes the algorithm used to determine if
> a packet passes the L2 filtering element.
> // Global parameters
> // Define Lookup tables
> MacVlan Table: Array of {MAC (MAC Address), VLAN (VLAN tag)} Ethernet
> Controller XL710 - Internal Switch
> 728
> Mac Table: Array of {MAC (MAC Address)} VLAN table: Array of {VLAN
> (VLAN tag)} HashMacVlan Table: Array of {HashMAC (Hash Values), VLAN
> (VLAN tag), AddressType} HashMac Table: Array of {HashMAC (Hash
> Values) , AddressType} EtherType Table : Array of {Etype (Ethertypes
> Values)} MacEtherType Table: Array of {MAC (MAC Address), Etype
> (Ethertype value)} // Define Virtual ports modes Port.PUE //
> Promiscuous Unicast Enable Port.PME // Promiscuous Multicast Enable
> Port.BAM // Broadcast Enable Port.VPE // Promiscuous VLAN enable
> Port.MaxSize: Max Packet size
> L2_function(Packet)
> // Variables
> MFilter: = False // MAC Filtering
> VFilter: = False // VLAN Filtering
> EFilter: = False // Exclusive Filtering NEPMFilter = False // Non
> Exclusive Perfect MAC Filtering NEPFilter = False // Non Exclusive
> Perfect Filtering NEIPMFilter = False // Non Exclusive Imperfect MAC
> Filtering NEIPFilter = False // Non Exclusive Imperfect Filtering Pass
> = False // Final decision.
> //Define packet parameters
> DA = Packet.DA //Destination Address of the packet VID = Packet.VLAN
> ID // Vlan tag of the packet Etype = Packet.Ethertype // Ethertype of
> the packet AddressType //Type of address of the DA. Can be Unicast,
> Multicast or Broadcast.
> HDA = HashFunction(DA).
> PSize: Packet size. This do not include any tag or other header
> removed by previous stages or to be added by following stages.
>
> // Exclusive Filters
> For Each entry e in MacVlan Table
> If (DA == e.MAC and (VID == e.VLAN or (VID == NULL and e.VLAN == 0))
> MFilter = True; For Each entry e in Mac Table If (DA == e.MAC) MFilter
> = True; For Each entry e in Ethertype Table If (Etype == e.Etype)
> MFilter = True; For Each entry e in MacEthertype Table If (DA == e.MAC
> and Etype == e.Etype) MFilter = True; For Each entry e in Vlan Table
> If (VID == e.VLAN or (VID == NULL and e.VLAN == 0)) VFilter = True; //
> VLAN filters are ANDed with the previous filters unless promiscuous
> VLAN is enabled EFilter = MFilter and (VFilter or p.VPE} and
> AddressType == Unicast; // Non Exclusive Perfect Filters If
> (AddressType == Unicast and p.PUE == 1) NEPMFilter = True; If
> (AddressType == Multicast and (p.PME == 1 or MFilter)) NEPMFilter =
> True; If (AddressType == Broadcast and (p.BAM == 1 or MFilter))
> NEPMFilter = True; // VLAN filters are ANDed with the previous filters
> unless promiscuous VLAN is enabled NEPFilter = NEPMFilter and (VFilter
> or p.VPE}; // Non Exclusive Imperfect Filters For Each entry e in
> HashMACVlan Table If (HDA == e.HashMAC and (VID == e.VLAN or (VID ==
> NULL and e.VLAN == 0)) and AddressType == e.AddressType) NEIPMFilter =
> True; For Each entry e in HashMAC Table If (HDA == e.HashMAC and
> AddressType == e.AddressType) NEIPMFilter = True; // VLAN filters are
> ANDed with the previous filters unless promiscuous VLAN is enabled
> NIEPFilter = NIEPMFilter and (VFilter or p.VPE}; // Packet size
> filtering is done at the queue level, so it is not part of the switch
> algorithm Pass = (EFilter or NEPFilter or NEIPFilter) Return Pass; }
>
> -----Original Message-----
> From: Ronciak, John [mailto:joh...@in...]
> Sent: Tuesday, September 15, 2015 10:40 AM
> To: Fujinaka, Todd <tod...@in...<mailto:tod...@in...>>;
> zhe...@pr...<mailto:zhe...@pr...>; e10...@li...<mailto:e10...@li...>
> Subject: Re: [E1000-devel] Intel 82551IL chips
>
> As long as there is no copy and pasting from the Linux driver to the
> QNX driver it should not be a problem. I'm not a lawyer but that's
> generally the case. That said, since the driver works after another a
> second reboot it's probably not related to the driver. This is
> probably something that is related to the system during the PCI
> enumeration of devices. Are all the other devices seen on a cold boot? Is there an equivalent to 'lspci'
> in QNX? If so what's it show on the first boot from power-off? Are
> all the devices seen at that point or are some missing?
>
> Cheers,
> John
>
> > -----Original Message-----
> > From: Fujinaka, Todd [mailto:tod...@in...]
> > Sent: Tuesday, September 15, 2015 9:43 AM
> > To:
> > zhe...@pr...<mailto:zhe...@pr...<mailto:zhe...@pr...%3cmailto:zhe...@pr...>>;
> e10...@li...<mailto:e1000-<mailto:e10...@li...%3cmailto:e1000->
> de...@li...<mailto:de...@li...>>
> > Subject: Re: [E1000-devel] Intel 82551IL chips
> >
> > The 82551L has been EOLed for about nine years by my estimation. We
> > don't have any further support for it.
> >
> > Also, it is probably a violation of the GPL to start with the Linux
> > driver to work on the QNX driver. I would suggest trying the FreeBSD
> driver.
> >
> > Todd Fujinaka
> > Software Application Engineer
> > Networking Division (ND)
> > Intel Corporation
> > tod...@in...<mailto:tod...@in...<mailto:tod...@in...%3cmailto:tod...@in...>>
> > (503) 712-4565
> >
> > -----Original Message-----
> > From: Желобанов Дмитрий Владимирович
> > [mailto:zhe...@pr...]
> > Sent: Tuesday, September 15, 2015 5:15 AM
> > To: e10...@li...<mailto:e1000-<mailto:e10...@li...%3cmailto:e1000->
> de...@li...<mailto:de...@li...>>
> > Subject: [E1000-devel] Intel 82551IL chips
> >
> > Hello,
> >
> > We use chips 82551IL (did 0x1209 rev 0x10) in our embedded platforms.
> > Our devices run QNX operation system. We faced with an issue:
> > sometimes our devices don't receive Ethernet packets right after
> > boot at all, only reboot helps to revive the devices. We think the
> > root problem is in hardware- software communication with the
> > Ethernet controller, or rather in QNX Ethernet driver.
> > I looked in Linux driver (e100.c) and found, the driver uploads
> > special firmware in chips like ours.
> >
> > So, could you give us a document which clarifies changes in
> > d102e_ucode.bin firmware from the original on chip microcode?
> >
> > Желобанов Д.В.
> > ООО <Прософт-Системы>, г. Екатеринбург.
> >
> >
> > --------------------------------------------------------------------
> > --
> > -------- _______________________________________________
> > E1000-devel mailing list
> > E10...@li...<mailto:E1000-<mailto:E10...@li...%3cmailto:E1000->
> de...@li...<mailto:de...@li...>>
> > https://lists.sourceforge.net/lists/listinfo/e1000-devel
> > To learn more about Intel® Ethernet, visit
> > http://communities.intel.com/community/wired
>
> ----------------------------------------------------------------------
> ----
> ----
> _______________________________________________
> E1000-devel mailing list
> E10...@li...<mailto:E1000-<mailto:E10...@li...%3cmailto:E1000->
> de...@li...<mailto:de...@li...>>
> https://lists.sourceforge.net/lists/listinfo/e1000-devel
> To learn more about Intel® Ethernet, visit
> http://communities.intel.com/community/wired
|
|
From: Hodek, R. <rom...@si...> - 2015-09-18 06:31:39
|
> Give me some time on this. I'm not sure if I found an error in our > documentation or not. No problem, I'm not in a hurry ;-) Roman |
|
From: Anitha S. <ani...@gm...> - 2015-09-18 06:30:21
|
Hi, vlan is not working when we upgrade linux kernel from 2.6.32-431.el6.i686 to 2.6.32-573.3.1.el6.i686. Tried e1000 drivers: e1000 7.3.21 e1000 8.0.35-NAPI when testing with one of above e1000 driver versions, we have tried to use intermediate kernel versions between working and failure of vlan trunking, the results of uname are below. kernel-2.6.32-431.el6.i686 - passed kernel-2.6.32-504.16.2.el6.i686 -passed kernel-2.6.32-504.23.4.el6.i686 -not working kernel-2.6.32-504.30.3.el6.i686 - not working kernel-2.6.32-573.3.1.el6.i686 -not working Linux centos-6.5 2.6.36 -passed Linux centos-6.5 3.5.0 - not working we have tried both embedded and standalone drivers and the result is same. the vlan tagged packets are received in linux and linux is removing its tag and gives to our application. so we see vlan ping failure with "wrong cable" message. as mentioned in search forum, we have tried to turn on/off rx-vlan-filter and offload setting, but we could not change it, as it is denoted as [fixed]. just to confirm the issue with pcnet32 driver with failure kernel, eventhough rx-vlan-filter is off as below, still facing issue. [root@localhost drivers]# ethtool -k eth5 | grep vlan rx-vlan-offload: off [fixed] tx-vlan-offload: off [fixed] rx-vlan-filter: off [fixed] vlan-challenged: off [fixed] we don't have the option to use e1000e driver. Please let me know if any specific information is required. can you please suggest us the latest stable kernel of 3.x version and e1000 driver combination where rx vlan tagging works ? Appreciate your inputs on this. Thanks, Anitha PS: below bug is raised. but as per Todd suggestion in below mail thread, sending this email to alias. https://sourceforge.net/p/e1000/bugs/491/ ---------- Forwarded message ---------- From: Todd Fujinaka <htf...@us...> Date: Wed, Sep 16, 2015 at 7:36 PM Subject: [e1000:bugs] #491 vlan tag removed in promiscuous mode with kernel 2.6.32-573.3.1.el6.i686 and e1000 driver To: "[e1000:bugs]" <49...@bu...> - *status*: open --> closed - *Comment*: e1000 drivers are supported by the community. Please try the e1000-devel mailing list or contact vmware. ------------------------------ |
|
From: Fujinaka, T. <tod...@in...> - 2015-09-17 18:26:59
|
Give me some time on this. I'm not sure if I found an error in our documentation or not.
Thanks.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
tod...@in...
(503) 712-4565
-----Original Message-----
From: Fujinaka, Todd [mailto:tod...@in...]
Sent: Monday, September 14, 2015 7:37 AM
To: Hodek, Roman; e10...@li...
Subject: Re: [E1000-devel] Wrong EEMNGCNF register
Thanks! I'll look into this today.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
tod...@in...
(503) 712-4565
-----Original Message-----
From: Hodek, Roman [mailto:rom...@si...]
Sent: Monday, September 14, 2015 4:16 AM
To: e10...@li...
Subject: [E1000-devel] Wrong EEMNGCNF register
Hello there!
I've recently stumbled about the fact that igb driver uses a wrong EEMNGCTL register for some mac types.
This register is used in e1000_82575.c:igb_get_cfg_done_82575() and defined in
e1000_regs.h:
#define E1000_EEMNGCTL 0x01010 /* MNG EEprom Control */
But at least my i210 docs tell me a different offset for this register, 0x12030 to be exact. So I've added some code to use the correct register at least for the Springville in my application (0x1533):
--- a/drivers/net/ethernet/intel/igb/e1000_82575.c 2015-09-08
19:15:29.000000000 +0200
+++ b/drivers/net/ethernet/intel/igb/e1000_82575.c 2015-09-11
16:41:51.000000000 +0200
@@ -1259,8 +1258,18 @@
{
s32 timeout = PHY_CFG_TIMEOUT;
s32 ret_val = 0;
+ u32 reg;
u32 mask = E1000_NVM_CFG_DONE_PORT_0;
+ switch (hw->mac.type) {
+ case e1000_i210:
+ reg = E1000_EEMNGCTL_I210;
+ break;
+ default:
+ reg = E1000_EEMNGCTL;
+ break;
+ }
+
if (hw->bus.func == 1)
mask = E1000_NVM_CFG_DONE_PORT_1;
else if (hw->bus.func == E1000_FUNC_2) @@ -1269,7 +1278,7 @@
mask = E1000_NVM_CFG_DONE_PORT_3;
while (timeout) {
- if (rd32(E1000_EEMNGCTL) & mask)
+ if (rd32(reg) & mask)
break;
usleep_range(1000,2000);
timeout--;
--- a/drivers/net/ethernet/intel/igb/e1000_regs.h 2015-09-11
16:27:55.000000000 +0200
+++ b/drivers/net/ethernet/intel/igb/e1000_regs.h 2015-09-11
16:42:02.000000000 +0200
@@ -70,6 +70,7 @@
#define E1000_PBS 0x01008 /* Packet Buffer Size */
#define E1000_EEMNGCTL 0x01010 /* MNG EEprom Control */ #define E1000_EEARBC_I210 0x12024 /* EEPROM Auto Read Bus Control */
+#define E1000_EEMNGCTL_I210 0x12030 /* MNG EEprom Control */
#define E1000_EEWR 0x0102C /* EEPROM Write Register - RW */
#define E1000_I2CCMD 0x01028 /* SFPI2C Command Register - RW */
#define E1000_FRTIMER 0x01048 /* Free Running Timer - RW */
With that change, I can save ~ 200ms while turning on Ethernet, which otherwise get lost while waiting for the timeout.
However, I don't know which MAC types are really affected by the move of EEMNGCTL. Maybe it's better to use a condition like (hw->mac.type >=
e1000_i210) or similar, or to expand the cases in the switch stmt. I think you might know better ;-)
Roman
------------------------------------------------------------------------------
_______________________________________________
E1000-devel mailing list
E10...@li...
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
------------------------------------------------------------------------------
_______________________________________________
E1000-devel mailing list
E10...@li...
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
|
|
From: Ronciak, J. <joh...@in...> - 2015-09-16 22:57:30
|
HI Dmirty,
I would have no idea of where to get that information from today. That code was written over 12 years ago. I sure there was an errata back then but where to find something that old would be a problem. Also, since the drivers that are in FreeBSD today and in Linux do not have reports of this happening it make sense that this is a QNX only issue. I'd take a look at the FreeBSD driver to see how different it is from the one you are using. Since QNX has never been on our supported OS list we have never tested it ourselves. So we have no idea if other QNX users are seeing this or not, especially since it on such old HW.
Sorry I can't be more help. Try to debug code that 12 or more years old when it's not our driver is very problematic for us.
Cheers,
John
> -----Original Message-----
> From: Желобанов Дмитрий Владимирович
> [mailto:zhe...@pr...]
> Sent: Tuesday, September 15, 2015 10:20 PM
> To: Ronciak, John; Fujinaka, Todd; e10...@li...
> Subject: RE: Intel 82551IL chips
>
> I want to give a small addition: even the chip is EOL, but we have a big
> number of embedded devices with the chip on board. All devices installed in
> the field and, unfortunately, we do must support the devices!
>
> -----Original Message-----
> From: Желобанов Дмитрий Владимирович
> Sent: Wednesday, September 16, 2015 10:08 AM
> To: 'Ronciak, John'; Fujinaka, Todd; e10...@li...
> Subject: RE: Intel 82551IL chips
>
> Hello,
>
> Of course I wouldn't copy-paste Linux driver into QNX. As a matter of fact,
> we have the source code for QNX, it names devnp-speedo.
> I just want to fix the QNX driver by inspiration of the Linux driver. By the way,
> the QNX network kernel is a port of the FreeBSD kernel.
>
> The device is visible on PCI bus when the driver doesn't receive packets.
> Let me give you more details on the issue:
> When the driver stops receiving: the "RX packet counter" is about 200, and
> we have the message in the slog: <timeout sending 20, stat 80> I looked in
> the source code and found lines which issues the message:
> #define SCB_STATUS 0x00 /* Command Unit Status */
> #define SCB_BYTE2 2
>
> int iobase = speedo->iobase + SCB_STATUS + SCB_BYTE2;
> int timeout;
>
> /*
> * wait for the previous command to finish
> */
> if (SPEEDO_IN8(iobase) != 0x00) {
> for(timeout = 1000000; timeout && (SPEEDO_IN8(iobase));
> timeout--)
> nsec_delay(1000);
> if (!timeout) {
> log(LOG_ERR,
> "timeout sending %x, stat %x", bcmd,
> SPEEDO_IN8(iobase));
> return -1;
> }
> }
>
> I do want to know what the comment from the Linux driver means:
> * Based on comments in the source code for the FreeBSD fxp
> * driver, the FIRMWARE_D102E ucode includes both CPUSaver and
> *
> * "fixes for bugs in the B-step hardware (specifically, bugs
> * with Inline Receive)."
> *
> * So we must fail if it cannot be loaded.
>
> It seems as it is our case, because PCI enumeration gives:
> Class = Network (Ethernet)
> Vendor ID = 8086h, Intel Corporation
> Device ID = 1209h, 8255xER/82551IT Fast Ethernet Controller
> PCI index = 1h
> Class Codes = 020000h
> Revision ID = 10h
>
> Could you give me a document which describes the statement "fixes for bugs
> in the B-step hardware (specifically, bugs with Inline Receive)."?
>
> Dmitry Zhelobanov
> Prosoft-Systems, Russia, Ekaterinburg
>
>
>
> -----Original Message-----
> From: Ronciak, John [mailto:joh...@in...]
> Sent: Tuesday, September 15, 2015 10:40 PM
> To: Fujinaka, Todd; Желобанов Дмитрий Владимирович; e1000-
> de...@li...
> Subject: RE: Intel 82551IL chips
>
> As long as there is no copy and pasting from the Linux driver to the QNX
> driver it should not be a problem. I'm not a lawyer but that's generally the
> case. That said, since the driver works after another a second reboot it's
> probably not related to the driver. This is probably something that is related
> to the system during the PCI enumeration of devices. Are all the other
> devices seen on a cold boot? Is there an equivalent to 'lspci' in QNX? If so
> what's it show on the first boot from power-off? Are all the devices seen at
> that point or are some missing?
>
> Cheers,
> John
>
> > -----Original Message-----
> > From: Fujinaka, Todd [mailto:tod...@in...]
> > Sent: Tuesday, September 15, 2015 9:43 AM
> > To: zhe...@pr...; e10...@li...
> > Subject: Re: [E1000-devel] Intel 82551IL chips
> >
> > The 82551L has been EOLed for about nine years by my estimation. We
> > don't have any further support for it.
> >
> > Also, it is probably a violation of the GPL to start with the Linux
> > driver to work on the QNX driver. I would suggest trying the FreeBSD driver.
> >
> > Todd Fujinaka
> > Software Application Engineer
> > Networking Division (ND)
> > Intel Corporation
> > tod...@in...
> > (503) 712-4565
> >
> > -----Original Message-----
> > From: Желобанов Дмитрий Владимирович
> > [mailto:zhe...@pr...]
> > Sent: Tuesday, September 15, 2015 5:15 AM
> > To: e10...@li...
> > Subject: [E1000-devel] Intel 82551IL chips
> >
> > Hello,
> >
> > We use chips 82551IL (did 0x1209 rev 0x10) in our embedded platforms.
> > Our devices run QNX operation system. We faced with an issue:
> > sometimes our devices don't receive Ethernet packets right after boot
> > at all, only reboot helps to revive the devices. We think the root
> > problem is in hardware- software communication with the Ethernet
> > controller, or rather in QNX Ethernet driver.
> > I looked in Linux driver (e100.c) and found, the driver uploads
> > special firmware in chips like ours.
> >
> > So, could you give us a document which clarifies changes in
> > d102e_ucode.bin firmware from the original on chip microcode?
> >
> > Желобанов Д.В.
> > ООО <Прософт-Системы>, г. Екатеринбург.
> >
> >
> > ----------------------------------------------------------------------
> > -------- _______________________________________________
> > E1000-devel mailing list
> > E10...@li...
> > https://lists.sourceforge.net/lists/listinfo/e1000-devel
> > To learn more about Intel® Ethernet, visit
> > http://communities.intel.com/community/wired
|
|
From: Ronciak, J. <joh...@in...> - 2015-09-16 21:54:48
|
The first upstream kernel was 3.19. Is that what you are asking?
Cheers,
John
> -----Original Message-----
> From: Gooch, Stephen (Wind River) [mailto:ste...@in...]
> Sent: Wednesday, September 16, 2015 1:21 PM
> To: e10...@li...
> Subject: [E1000-devel] Driver Version for 15aa x552
>
> Hello,
>
> Which version of ixgbe or other driver added support for:
>
> * vendor: 8086 ("Intel Corporation"), device: 15aa ("Ethernet Connection
> X552 10 GbE Backplane")
> * vendor: 8086 ("Intel Corporation"), device: 15ab ("Ethernet Connection
> X552 10 GbE Backplane")
> * vendor: 8086 ("Intel Corporation"), device: 15ad ("Ethernet Connection
> X552/X557-AT 10GBASE-T")
> ?
>
> - Stephen Gooch
>
|
|
From: Gooch, S. (W. River) <ste...@in...> - 2015-09-16 20:21:04
|
Hello,
Which version of ixgbe or other driver added support for:
* vendor: 8086 ("Intel Corporation"), device: 15aa ("Ethernet Connection X552 10 GbE Backplane")
* vendor: 8086 ("Intel Corporation"), device: 15ab ("Ethernet Connection X552 10 GbE Backplane")
* vendor: 8086 ("Intel Corporation"), device: 15ad ("Ethernet Connection X552/X557-AT 10GBASE-T")
?
- Stephen Gooch
|
|
From: Shankar K. <sha...@ci...> - 2015-09-16 05:59:47
|
Thanks for response.
> Why? You're setting a VLAN filter with the tag value of 25. Why do promiscuous mode in addition?
--> I was confirming that I am _not_ setting p.VPE (essentially disabling VLAN promiscuous ). We are in same page.
Still the packets are not going through.
'set' is just the opcode name ' i40e_aqc_set_vsi_promiscuous_modes' - same is used to 'clear' I guess.
The following code does this when 'set=0' is passed.
i40e_status i40e_aq_set_and_clr_vsi_vlan_promiscuous(struct i40e_hw *hw,
u16 seid, bool set, struct i40e_asq_cmd_details *cmd_details)
{
struct i40e_aq_desc desc;
struct i40e_aqc_set_vsi_promiscuous_modes *cmd =
(struct i40e_aqc_set_vsi_promiscuous_modes *)&desc.params.raw;
i40e_status status;
u16 flags = 0;
i40e_fill_default_direct_cmd_desc(&desc,
i40e_aqc_opc_set_vsi_promiscuous_modes);
if (set)
flags |= I40E_AQC_SET_VSI_PROMISC_VLAN;
cmd->promiscuous_flags = CPU_TO_LE16(flags);
cmd->valid_flags = CPU_TO_LE16(I40E_AQC_SET_VSI_PROMISC_VLAN);
cmd->seid = CPU_TO_LE16(seid);
status = i40e_asq_send_command(hw, &desc, NULL, 0, cmd_details);
return status;
}
In the contrary, this is not the way to set p.VPE=0 (as described in L2 filtering algorithm) or someother/additional action needs to be taken, please let me know
thanks,
Shankar.
-----Original Message-----
From: Rose, Gregory V [mailto:gre...@in...]
Sent: Tuesday, September 15, 2015 3:43 PM
To: Shankar Krishnamurthy <sha...@ci...>; e10...@li...
Subject: RE: [E1000-devel] Vlan Table in I40e XL710
> -----Original Message-----
> From: Shankar Krishnamurthy [mailto:sha...@ci...]
> Sent: Tuesday, September 15, 2015 2:57 PM
> To: e10...@li...<mailto:e10...@li...>
> Subject: [E1000-devel] Vlan Table in I40e XL710
>
> Hi fortville Experts,
>
> Was trying to use VLAN Table (for filtering) in conjunction with
> MACVLAN table mentioned in "7.4.8.3 L2 Filtering Algorithm" (also cut
> n' pasted
> below)
>
> My test scenario:
> 1. In SRIOV mode, gave one VF to VM. For that, I added the
> corresponding MAC into MACVLAN table with vlan=25 2. Added VLAN table
> with vlan=25. (For p.VPE=0 I used
> 'i40e_aqc_opc_set_vsi_promiscuous_modes' opcode with vlan
> promiscuous.)
>
Why? You're setting a VLAN filter with the tag value of 25. Why do promiscuous mode in addition?
> Now the packets are coming into this VM.
>
> 1. Now, I delete the vlan=25 entry in the VLAN table (expecting that
> packets stop coming in) 2. Packets are still coming in.
Turn off promiscuous mode.
- Greg
>
> But I am confused with this behavior. According the algorithm below,
> Namely:
> " EFilter = MFilter and (VFilter or p.VPE} and AddressType == Unicast;"
>
> The packets should have stopped coming in. What am I missing?
>
> Is there any global setting /register that I need to toggle for the
> VLAN table to be effective?
>
> Is VSI setup needs additional flags? Not sure
>
> thanks,
> Shankar.
>
> I40e Driver Version: 1.2.37
>
> 7.4.8.3 L2 Filtering Algorithm
> The following pseudo code describes the algorithm used to determine if
> a packet passes the L2 filtering element.
> // Global parameters
> // Define Lookup tables
> MacVlan Table: Array of {MAC (MAC Address), VLAN (VLAN tag)} Ethernet
> Controller XL710 - Internal Switch
> 728
> Mac Table: Array of {MAC (MAC Address)} VLAN table: Array of {VLAN
> (VLAN tag)} HashMacVlan Table: Array of {HashMAC (Hash Values), VLAN
> (VLAN tag), AddressType} HashMac Table: Array of {HashMAC (Hash
> Values) , AddressType} EtherType Table : Array of {Etype (Ethertypes
> Values)} MacEtherType Table: Array of {MAC (MAC Address), Etype
> (Ethertype value)} // Define Virtual ports modes Port.PUE //
> Promiscuous Unicast Enable Port.PME // Promiscuous Multicast Enable
> Port.BAM // Broadcast Enable Port.VPE // Promiscuous VLAN enable
> Port.MaxSize: Max Packet size
> L2_function(Packet)
> // Variables
> MFilter: = False // MAC Filtering
> VFilter: = False // VLAN Filtering
> EFilter: = False // Exclusive Filtering NEPMFilter = False // Non
> Exclusive Perfect MAC Filtering NEPFilter = False // Non Exclusive
> Perfect Filtering NEIPMFilter = False // Non Exclusive Imperfect MAC
> Filtering NEIPFilter = False // Non Exclusive Imperfect Filtering Pass
> = False // Final decision.
> //Define packet parameters
> DA = Packet.DA //Destination Address of the packet VID = Packet.VLAN
> ID // Vlan tag of the packet Etype = Packet.Ethertype // Ethertype of
> the packet AddressType //Type of address of the DA. Can be Unicast,
> Multicast or Broadcast.
> HDA = HashFunction(DA).
> PSize: Packet size. This do not include any tag or other header
> removed by previous stages or to be added by following stages.
>
> // Exclusive Filters
> For Each entry e in MacVlan Table
> If (DA == e.MAC and (VID == e.VLAN or (VID == NULL and e.VLAN == 0))
> MFilter = True; For Each entry e in Mac Table If (DA == e.MAC) MFilter
> = True; For Each entry e in Ethertype Table If (Etype == e.Etype)
> MFilter = True; For Each entry e in MacEthertype Table If (DA == e.MAC
> and Etype == e.Etype) MFilter = True; For Each entry e in Vlan Table
> If (VID == e.VLAN or (VID == NULL and e.VLAN == 0)) VFilter = True; //
> VLAN filters are ANDed with the previous filters unless promiscuous
> VLAN is enabled EFilter = MFilter and (VFilter or p.VPE} and
> AddressType == Unicast; // Non Exclusive Perfect Filters If
> (AddressType == Unicast and p.PUE == 1) NEPMFilter = True; If
> (AddressType == Multicast and (p.PME == 1 or MFilter)) NEPMFilter =
> True; If (AddressType == Broadcast and (p.BAM == 1 or MFilter))
> NEPMFilter = True; // VLAN filters are ANDed with the previous filters
> unless promiscuous VLAN is enabled NEPFilter = NEPMFilter and (VFilter
> or p.VPE}; // Non Exclusive Imperfect Filters For Each entry e in
> HashMACVlan Table If (HDA == e.HashMAC and (VID == e.VLAN or (VID ==
> NULL and e.VLAN == 0)) and AddressType == e.AddressType) NEIPMFilter =
> True; For Each entry e in HashMAC Table If (HDA == e.HashMAC and
> AddressType == e.AddressType) NEIPMFilter = True; // VLAN filters are
> ANDed with the previous filters unless promiscuous VLAN is enabled
> NIEPFilter = NIEPMFilter and (VFilter or p.VPE}; // Packet size
> filtering is done at the queue level, so it is not part of the switch
> algorithm Pass = (EFilter or NEPFilter or NEIPFilter) Return Pass; }
>
> -----Original Message-----
> From: Ronciak, John [mailto:joh...@in...]
> Sent: Tuesday, September 15, 2015 10:40 AM
> To: Fujinaka, Todd <tod...@in...<mailto:tod...@in...>>;
> zhe...@pr...<mailto:zhe...@pr...>; e10...@li...<mailto:e10...@li...>
> Subject: Re: [E1000-devel] Intel 82551IL chips
>
> As long as there is no copy and pasting from the Linux driver to the
> QNX driver it should not be a problem. I'm not a lawyer but that's
> generally the case. That said, since the driver works after another a
> second reboot it's probably not related to the driver. This is
> probably something that is related to the system during the PCI
> enumeration of devices. Are all the other devices seen on a cold boot? Is there an equivalent to 'lspci'
> in QNX? If so what's it show on the first boot from power-off? Are
> all the devices seen at that point or are some missing?
>
> Cheers,
> John
>
> > -----Original Message-----
> > From: Fujinaka, Todd [mailto:tod...@in...]
> > Sent: Tuesday, September 15, 2015 9:43 AM
> > To:
> > zhe...@pr...<mailto:zhe...@pr...<mailto:zhe...@pr...<mailto:zhe...@pr...>>;
> e10...@li...<mailto:e1000-<mailto:e10...@li...<mailto:e1000->
> de...@li...<mailto:de...@li...>>
> > Subject: Re: [E1000-devel] Intel 82551IL chips
> >
> > The 82551L has been EOLed for about nine years by my estimation. We
> > don't have any further support for it.
> >
> > Also, it is probably a violation of the GPL to start with the Linux
> > driver to work on the QNX driver. I would suggest trying the FreeBSD
> driver.
> >
> > Todd Fujinaka
> > Software Application Engineer
> > Networking Division (ND)
> > Intel Corporation
> > tod...@in...<mailto:tod...@in...<mailto:tod...@in...<mailto:tod...@in...>>
> > (503) 712-4565
> >
> > -----Original Message-----
> > From: Желобанов Дмитрий Владимирович
> > [mailto:zhe...@pr...]
> > Sent: Tuesday, September 15, 2015 5:15 AM
> > To: e10...@li...<mailto:e1000-<mailto:e10...@li...<mailto:e1000->
> de...@li...<mailto:de...@li...>>
> > Subject: [E1000-devel] Intel 82551IL chips
> >
> > Hello,
> >
> > We use chips 82551IL (did 0x1209 rev 0x10) in our embedded platforms.
> > Our devices run QNX operation system. We faced with an issue:
> > sometimes our devices don't receive Ethernet packets right after
> > boot at all, only reboot helps to revive the devices. We think the
> > root problem is in hardware- software communication with the
> > Ethernet controller, or rather in QNX Ethernet driver.
> > I looked in Linux driver (e100.c) and found, the driver uploads
> > special firmware in chips like ours.
> >
> > So, could you give us a document which clarifies changes in
> > d102e_ucode.bin firmware from the original on chip microcode?
> >
> > Желобанов Д.В.
> > ООО <Прософт-Системы>, г. Екатеринбург.
> >
> >
> > --------------------------------------------------------------------
> > --
> > -------- _______________________________________________
> > E1000-devel mailing list
> > E10...@li...<mailto:E1000-<mailto:E10...@li...<mailto:E1000->
> de...@li...<mailto:de...@li...>>
> > https://lists.sourceforge.net/lists/listinfo/e1000-devel
> > To learn more about Intel® Ethernet, visit
> > http://communities.intel.com/community/wired
>
> ----------------------------------------------------------------------
> ----
> ----
> _______________________________________________
> E1000-devel mailing list
> E10...@li...<mailto:E1000-<mailto:E10...@li...<mailto:E1000->
> de...@li...<mailto:de...@li...>>
> https://lists.sourceforge.net/lists/listinfo/e1000-devel
> To learn more about Intel® Ethernet, visit
> http://communities.intel.com/community/wired
|
|
From: Желобанов Д. В. <zhe...@pr...> - 2015-09-16 05:19:43
|
I want to give a small addition: even the chip is EOL, but we have a big number of embedded devices with the chip on board. All devices installed in the field and, unfortunately, we do must support the devices!
-----Original Message-----
From: Желобанов Дмитрий Владимирович
Sent: Wednesday, September 16, 2015 10:08 AM
To: 'Ronciak, John'; Fujinaka, Todd; e10...@li...
Subject: RE: Intel 82551IL chips
Hello,
Of course I wouldn't copy-paste Linux driver into QNX. As a matter of fact, we have the source code for QNX, it names devnp-speedo.
I just want to fix the QNX driver by inspiration of the Linux driver. By the way, the QNX network kernel is a port of the FreeBSD kernel.
The device is visible on PCI bus when the driver doesn't receive packets.
Let me give you more details on the issue:
When the driver stops receiving: the "RX packet counter" is about 200, and we have the message in the slog: <timeout sending 20, stat 80> I looked in the source code and found lines which issues the message:
#define SCB_STATUS 0x00 /* Command Unit Status */
#define SCB_BYTE2 2
int iobase = speedo->iobase + SCB_STATUS + SCB_BYTE2;
int timeout;
/*
* wait for the previous command to finish
*/
if (SPEEDO_IN8(iobase) != 0x00) {
for(timeout = 1000000; timeout && (SPEEDO_IN8(iobase)); timeout--)
nsec_delay(1000);
if (!timeout) {
log(LOG_ERR,
"timeout sending %x, stat %x", bcmd, SPEEDO_IN8(iobase));
return -1;
}
}
I do want to know what the comment from the Linux driver means:
* Based on comments in the source code for the FreeBSD fxp
* driver, the FIRMWARE_D102E ucode includes both CPUSaver and
*
* "fixes for bugs in the B-step hardware (specifically, bugs
* with Inline Receive)."
*
* So we must fail if it cannot be loaded.
It seems as it is our case, because PCI enumeration gives:
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 1209h, 8255xER/82551IT Fast Ethernet Controller
PCI index = 1h
Class Codes = 020000h
Revision ID = 10h
Could you give me a document which describes the statement "fixes for bugs in the B-step hardware (specifically, bugs with Inline Receive)."?
Dmitry Zhelobanov
Prosoft-Systems, Russia, Ekaterinburg
-----Original Message-----
From: Ronciak, John [mailto:joh...@in...]
Sent: Tuesday, September 15, 2015 10:40 PM
To: Fujinaka, Todd; Желобанов Дмитрий Владимирович; e10...@li...
Subject: RE: Intel 82551IL chips
As long as there is no copy and pasting from the Linux driver to the QNX driver it should not be a problem. I'm not a lawyer but that's generally the case. That said, since the driver works after another a second reboot it's probably not related to the driver. This is probably something that is related to the system during the PCI enumeration of devices. Are all the other devices seen on a cold boot? Is there an equivalent to 'lspci' in QNX? If so what's it show on the first boot from power-off? Are all the devices seen at that point or are some missing?
Cheers,
John
> -----Original Message-----
> From: Fujinaka, Todd [mailto:tod...@in...]
> Sent: Tuesday, September 15, 2015 9:43 AM
> To: zhe...@pr...; e10...@li...
> Subject: Re: [E1000-devel] Intel 82551IL chips
>
> The 82551L has been EOLed for about nine years by my estimation. We
> don't have any further support for it.
>
> Also, it is probably a violation of the GPL to start with the Linux
> driver to work on the QNX driver. I would suggest trying the FreeBSD driver.
>
> Todd Fujinaka
> Software Application Engineer
> Networking Division (ND)
> Intel Corporation
> tod...@in...
> (503) 712-4565
>
> -----Original Message-----
> From: Желобанов Дмитрий Владимирович
> [mailto:zhe...@pr...]
> Sent: Tuesday, September 15, 2015 5:15 AM
> To: e10...@li...
> Subject: [E1000-devel] Intel 82551IL chips
>
> Hello,
>
> We use chips 82551IL (did 0x1209 rev 0x10) in our embedded platforms.
> Our devices run QNX operation system. We faced with an issue:
> sometimes our devices don't receive Ethernet packets right after boot
> at all, only reboot helps to revive the devices. We think the root
> problem is in hardware- software communication with the Ethernet
> controller, or rather in QNX Ethernet driver.
> I looked in Linux driver (e100.c) and found, the driver uploads
> special firmware in chips like ours.
>
> So, could you give us a document which clarifies changes in
> d102e_ucode.bin firmware from the original on chip microcode?
>
> Желобанов Д.В.
> ООО <Прософт-Системы>, г. Екатеринбург.
>
>
> ----------------------------------------------------------------------
> -------- _______________________________________________
> E1000-devel mailing list
> E10...@li...
> https://lists.sourceforge.net/lists/listinfo/e1000-devel
> To learn more about Intel® Ethernet, visit
> http://communities.intel.com/community/wired
|
|
From: Желобанов Д. В. <zhe...@pr...> - 2015-09-16 05:08:24
|
Hello,
Of course I wouldn't copy-paste Linux driver into QNX. As a matter of fact, we have the source code for QNX, it names devnp-speedo.
I just want to fix the QNX driver by inspiration of the Linux driver. By the way, the QNX network kernel is a port of the FreeBSD kernel.
The device is visible on PCI bus when the driver doesn't receive packets.
Let me give you more details on the issue:
When the driver stops receiving: the "RX packet counter" is about 200, and we have the message in the slog: <timeout sending 20, stat 80>
I looked in the source code and found lines which issues the message:
#define SCB_STATUS 0x00 /* Command Unit Status */
#define SCB_BYTE2 2
int iobase = speedo->iobase + SCB_STATUS + SCB_BYTE2;
int timeout;
/*
* wait for the previous command to finish
*/
if (SPEEDO_IN8(iobase) != 0x00) {
for(timeout = 1000000; timeout && (SPEEDO_IN8(iobase)); timeout--)
nsec_delay(1000);
if (!timeout) {
log(LOG_ERR,
"timeout sending %x, stat %x", bcmd, SPEEDO_IN8(iobase));
return -1;
}
}
I do want to know what the comment from the Linux driver means:
* Based on comments in the source code for the FreeBSD fxp
* driver, the FIRMWARE_D102E ucode includes both CPUSaver and
*
* "fixes for bugs in the B-step hardware (specifically, bugs
* with Inline Receive)."
*
* So we must fail if it cannot be loaded.
It seems as it is our case, because PCI enumeration gives:
Class = Network (Ethernet)
Vendor ID = 8086h, Intel Corporation
Device ID = 1209h, 8255xER/82551IT Fast Ethernet Controller
PCI index = 1h
Class Codes = 020000h
Revision ID = 10h
Could you give me a document which describes the statement "fixes for bugs in the B-step hardware (specifically, bugs with Inline Receive)."?
Dmitry Zhelobanov
Prosoft-Systems, Russia, Ekaterinburg
-----Original Message-----
From: Ronciak, John [mailto:joh...@in...]
Sent: Tuesday, September 15, 2015 10:40 PM
To: Fujinaka, Todd; Желобанов Дмитрий Владимирович; e10...@li...
Subject: RE: Intel 82551IL chips
As long as there is no copy and pasting from the Linux driver to the QNX driver it should not be a problem. I'm not a lawyer but that's generally the case. That said, since the driver works after another a second reboot it's probably not related to the driver. This is probably something that is related to the system during the PCI enumeration of devices. Are all the other devices seen on a cold boot? Is there an equivalent to 'lspci' in QNX? If so what's it show on the first boot from power-off? Are all the devices seen at that point or are some missing?
Cheers,
John
> -----Original Message-----
> From: Fujinaka, Todd [mailto:tod...@in...]
> Sent: Tuesday, September 15, 2015 9:43 AM
> To: zhe...@pr...; e10...@li...
> Subject: Re: [E1000-devel] Intel 82551IL chips
>
> The 82551L has been EOLed for about nine years by my estimation. We
> don't have any further support for it.
>
> Also, it is probably a violation of the GPL to start with the Linux
> driver to work on the QNX driver. I would suggest trying the FreeBSD driver.
>
> Todd Fujinaka
> Software Application Engineer
> Networking Division (ND)
> Intel Corporation
> tod...@in...
> (503) 712-4565
>
> -----Original Message-----
> From: Желобанов Дмитрий Владимирович
> [mailto:zhe...@pr...]
> Sent: Tuesday, September 15, 2015 5:15 AM
> To: e10...@li...
> Subject: [E1000-devel] Intel 82551IL chips
>
> Hello,
>
> We use chips 82551IL (did 0x1209 rev 0x10) in our embedded platforms.
> Our devices run QNX operation system. We faced with an issue:
> sometimes our devices don't receive Ethernet packets right after boot
> at all, only reboot helps to revive the devices. We think the root
> problem is in hardware- software communication with the Ethernet
> controller, or rather in QNX Ethernet driver.
> I looked in Linux driver (e100.c) and found, the driver uploads
> special firmware in chips like ours.
>
> So, could you give us a document which clarifies changes in
> d102e_ucode.bin firmware from the original on chip microcode?
>
> Желобанов Д.В.
> ООО <Прософт-Системы>, г. Екатеринбург.
>
>
> ----------------------------------------------------------------------
> -------- _______________________________________________
> E1000-devel mailing list
> E10...@li...
> https://lists.sourceforge.net/lists/listinfo/e1000-devel
> To learn more about Intel® Ethernet, visit
> http://communities.intel.com/community/wired
|
|
From: Rose, G. V <gre...@in...> - 2015-09-15 22:43:00
|
> -----Original Message-----
> From: Shankar Krishnamurthy [mailto:sha...@ci...]
> Sent: Tuesday, September 15, 2015 2:57 PM
> To: e10...@li...
> Subject: [E1000-devel] Vlan Table in I40e XL710
>
> Hi fortville Experts,
>
> Was trying to use VLAN Table (for filtering) in conjunction with MACVLAN
> table mentioned in "7.4.8.3 L2 Filtering Algorithm" (also cut n' pasted
> below)
>
> My test scenario:
> 1. In SRIOV mode, gave one VF to VM. For that, I added the corresponding
> MAC into MACVLAN table with vlan=25
> 2. Added VLAN table with vlan=25. (For p.VPE=0 I used
> 'i40e_aqc_opc_set_vsi_promiscuous_modes' opcode with vlan promiscuous.)
>
Why? You're setting a VLAN filter with the tag value of 25. Why do promiscuous mode in addition?
> Now the packets are coming into this VM.
>
> 1. Now, I delete the vlan=25 entry in the VLAN table (expecting that
> packets stop coming in)
> 2. Packets are still coming in.
Turn off promiscuous mode.
- Greg
>
> But I am confused with this behavior. According the algorithm below,
> Namely:
> " EFilter = MFilter and (VFilter or p.VPE} and AddressType == Unicast;"
>
> The packets should have stopped coming in. What am I missing?
>
> Is there any global setting /register that I need to toggle for the VLAN
> table to be effective?
>
> Is VSI setup needs additional flags? Not sure
>
> thanks,
> Shankar.
>
> I40e Driver Version: 1.2.37
>
> 7.4.8.3 L2 Filtering Algorithm
> The following pseudo code describes the algorithm used to determine if a
> packet passes the L2 filtering
> element.
> // Global parameters
> // Define Lookup tables
> MacVlan Table: Array of {MAC (MAC Address), VLAN (VLAN tag)}
> Ethernet Controller XL710 - Internal Switch
> 728
> Mac Table: Array of {MAC (MAC Address)}
> VLAN table: Array of {VLAN (VLAN tag)}
> HashMacVlan Table: Array of {HashMAC (Hash Values), VLAN (VLAN tag),
> AddressType}
> HashMac Table: Array of {HashMAC (Hash Values) , AddressType}
> EtherType Table : Array of {Etype (Ethertypes Values)}
> MacEtherType Table: Array of {MAC (MAC Address), Etype (Ethertype value)}
> // Define Virtual ports modes
> Port.PUE // Promiscuous Unicast Enable
> Port.PME // Promiscuous Multicast Enable
> Port.BAM // Broadcast Enable
> Port.VPE // Promiscuous VLAN enable
> Port.MaxSize: Max Packet size
> L2_function(Packet)
> // Variables
> MFilter: = False // MAC Filtering
> VFilter: = False // VLAN Filtering
> EFilter: = False // Exclusive Filtering
> NEPMFilter = False // Non Exclusive Perfect MAC Filtering
> NEPFilter = False // Non Exclusive Perfect Filtering
> NEIPMFilter = False // Non Exclusive Imperfect MAC Filtering
> NEIPFilter = False // Non Exclusive Imperfect Filtering
> Pass = False // Final decision.
> //Define packet parameters
> DA = Packet.DA //Destination Address of the packet
> VID = Packet.VLAN ID // Vlan tag of the packet
> Etype = Packet.Ethertype // Ethertype of the packet
> AddressType //Type of address of the DA. Can be Unicast, Multicast or
> Broadcast.
> HDA = HashFunction(DA).
> PSize: Packet size. This do not include any tag or other header removed by
> previous stages or to be added by following stages.
>
> // Exclusive Filters
> For Each entry e in MacVlan Table
> If (DA == e.MAC and (VID == e.VLAN or (VID == NULL and e.VLAN == 0))
> MFilter = True;
> For Each entry e in Mac Table
> If (DA == e.MAC) MFilter = True;
> For Each entry e in Ethertype Table
> If (Etype == e.Etype) MFilter = True;
> For Each entry e in MacEthertype Table
> If (DA == e.MAC and Etype == e.Etype) MFilter = True;
> For Each entry e in Vlan Table
> If (VID == e.VLAN or (VID == NULL and e.VLAN == 0)) VFilter = True;
> // VLAN filters are ANDed with the previous filters unless promiscuous
> VLAN is enabled
> EFilter = MFilter and (VFilter or p.VPE} and AddressType == Unicast;
> // Non Exclusive Perfect Filters
> If (AddressType == Unicast and p.PUE == 1) NEPMFilter = True;
> If (AddressType == Multicast and (p.PME == 1 or MFilter)) NEPMFilter =
> True;
> If (AddressType == Broadcast and (p.BAM == 1 or MFilter)) NEPMFilter =
> True;
> // VLAN filters are ANDed with the previous filters unless promiscuous
> VLAN is enabled
> NEPFilter = NEPMFilter and (VFilter or p.VPE};
> // Non Exclusive Imperfect Filters
> For Each entry e in HashMACVlan Table
> If (HDA == e.HashMAC and (VID == e.VLAN or (VID == NULL and e.VLAN == 0))
> and AddressType == e.AddressType) NEIPMFilter = True;
> For Each entry e in HashMAC Table
> If (HDA == e.HashMAC and AddressType == e.AddressType) NEIPMFilter = True;
> // VLAN filters are ANDed with the previous filters unless promiscuous
> VLAN is enabled
> NIEPFilter = NIEPMFilter and (VFilter or p.VPE};
> // Packet size filtering is done at the queue level, so it is not part of
> the switch algorithm
> Pass = (EFilter or NEPFilter or NEIPFilter)
> Return Pass;
> }
>
> -----Original Message-----
> From: Ronciak, John [mailto:joh...@in...]
> Sent: Tuesday, September 15, 2015 10:40 AM
> To: Fujinaka, Todd <tod...@in...>;
> zhe...@pr...; e10...@li...
> Subject: Re: [E1000-devel] Intel 82551IL chips
>
> As long as there is no copy and pasting from the Linux driver to the QNX
> driver it should not be a problem. I'm not a lawyer but that's generally
> the case. That said, since the driver works after another a second reboot
> it's probably not related to the driver. This is probably something that
> is related to the system during the PCI enumeration of devices. Are all
> the other devices seen on a cold boot? Is there an equivalent to 'lspci'
> in QNX? If so what's it show on the first boot from power-off? Are all
> the devices seen at that point or are some missing?
>
> Cheers,
> John
>
> > -----Original Message-----
> > From: Fujinaka, Todd [mailto:tod...@in...]
> > Sent: Tuesday, September 15, 2015 9:43 AM
> > To: zhe...@pr...<mailto:zhe...@pr...>;
> e10...@li...<mailto:e1000-
> de...@li...>
> > Subject: Re: [E1000-devel] Intel 82551IL chips
> >
> > The 82551L has been EOLed for about nine years by my estimation. We
> > don't have any further support for it.
> >
> > Also, it is probably a violation of the GPL to start with the Linux
> > driver to work on the QNX driver. I would suggest trying the FreeBSD
> driver.
> >
> > Todd Fujinaka
> > Software Application Engineer
> > Networking Division (ND)
> > Intel Corporation
> > tod...@in...<mailto:tod...@in...>
> > (503) 712-4565
> >
> > -----Original Message-----
> > From: Желобанов Дмитрий Владимирович
> > [mailto:zhe...@pr...]
> > Sent: Tuesday, September 15, 2015 5:15 AM
> > To: e10...@li...<mailto:e1000-
> de...@li...>
> > Subject: [E1000-devel] Intel 82551IL chips
> >
> > Hello,
> >
> > We use chips 82551IL (did 0x1209 rev 0x10) in our embedded platforms.
> > Our devices run QNX operation system. We faced with an issue:
> > sometimes our devices don't receive Ethernet packets right after boot
> > at all, only reboot helps to revive the devices. We think the root
> > problem is in hardware- software communication with the Ethernet
> > controller, or rather in QNX Ethernet driver.
> > I looked in Linux driver (e100.c) and found, the driver uploads
> > special firmware in chips like ours.
> >
> > So, could you give us a document which clarifies changes in
> > d102e_ucode.bin firmware from the original on chip microcode?
> >
> > Желобанов Д.В.
> > ООО <Прософт-Системы>, г. Екатеринбург.
> >
> >
> > ----------------------------------------------------------------------
> > -------- _______________________________________________
> > E1000-devel mailing list
> > E10...@li...<mailto:E1000-
> de...@li...>
> > https://lists.sourceforge.net/lists/listinfo/e1000-devel
> > To learn more about Intel® Ethernet, visit
> > http://communities.intel.com/community/wired
>
> --------------------------------------------------------------------------
> ----
> _______________________________________________
> E1000-devel mailing list
> E10...@li...<mailto:E1000-
> de...@li...>
> https://lists.sourceforge.net/lists/listinfo/e1000-devel
> To learn more about Intel® Ethernet, visit
> http://communities.intel.com/community/wired
|
|
From: Shankar K. <sha...@ci...> - 2015-09-15 22:31:51
|
Hi fortville Experts,
Was trying to use VLAN Table (for filtering) in conjunction with MACVLAN table mentioned in "7.4.8.3 L2 Filtering Algorithm" (also cut n' pasted below)
My test scenario:
1. In SRIOV mode, gave one VF to VM. For that, I added the corresponding MAC into MACVLAN table with vlan=25
2. Added VLAN table with vlan=25. (For p.VPE=0 I used 'i40e_aqc_opc_set_vsi_promiscuous_modes' opcode with vlan promiscuous.)
Now the packets are coming into this VM.
1. Now, I delete the vlan=25 entry in the VLAN table (expecting that packets stop coming in)
2. Packets are still coming in.
But I am confused with this behavior. According the algorithm below, Namely:
" EFilter = MFilter and (VFilter or p.VPE} and AddressType == Unicast;"
The packets should have stopped coming in. What am I missing?
Is there any global setting /register that I need to toggle for the VLAN table to be effective?
Is VSI setup needs additional flags? Not sure
thanks,
Shankar.
I40e Driver Version: 1.2.37
7.4.8.3 L2 Filtering Algorithm
The following pseudo code describes the algorithm used to determine if a packet passes the L2 filtering
element.
// Global parameters
// Define Lookup tables
MacVlan Table: Array of {MAC (MAC Address), VLAN (VLAN tag)}
Ethernet Controller XL710 - Internal Switch
728
Mac Table: Array of {MAC (MAC Address)}
VLAN table: Array of {VLAN (VLAN tag)}
HashMacVlan Table: Array of {HashMAC (Hash Values), VLAN (VLAN tag), AddressType}
HashMac Table: Array of {HashMAC (Hash Values) , AddressType}
EtherType Table : Array of {Etype (Ethertypes Values)}
MacEtherType Table: Array of {MAC (MAC Address), Etype (Ethertype value)}
// Define Virtual ports modes
Port.PUE // Promiscuous Unicast Enable
Port.PME // Promiscuous Multicast Enable
Port.BAM // Broadcast Enable
Port.VPE // Promiscuous VLAN enable
Port.MaxSize: Max Packet size
L2_function(Packet)
// Variables
MFilter: = False // MAC Filtering
VFilter: = False // VLAN Filtering
EFilter: = False // Exclusive Filtering
NEPMFilter = False // Non Exclusive Perfect MAC Filtering
NEPFilter = False // Non Exclusive Perfect Filtering
NEIPMFilter = False // Non Exclusive Imperfect MAC Filtering
NEIPFilter = False // Non Exclusive Imperfect Filtering
Pass = False // Final decision.
//Define packet parameters
DA = Packet.DA //Destination Address of the packet
VID = Packet.VLAN ID // Vlan tag of the packet
Etype = Packet.Ethertype // Ethertype of the packet
AddressType //Type of address of the DA. Can be Unicast, Multicast or Broadcast.
HDA = HashFunction(DA).
PSize: Packet size. This do not include any tag or other header removed by previous stages or to be added by following stages.
// Exclusive Filters
For Each entry e in MacVlan Table
If (DA == e.MAC and (VID == e.VLAN or (VID == NULL and e.VLAN == 0)) MFilter = True;
For Each entry e in Mac Table
If (DA == e.MAC) MFilter = True;
For Each entry e in Ethertype Table
If (Etype == e.Etype) MFilter = True;
For Each entry e in MacEthertype Table
If (DA == e.MAC and Etype == e.Etype) MFilter = True;
For Each entry e in Vlan Table
If (VID == e.VLAN or (VID == NULL and e.VLAN == 0)) VFilter = True;
// VLAN filters are ANDed with the previous filters unless promiscuous VLAN is enabled
EFilter = MFilter and (VFilter or p.VPE} and AddressType == Unicast;
// Non Exclusive Perfect Filters
If (AddressType == Unicast and p.PUE == 1) NEPMFilter = True;
If (AddressType == Multicast and (p.PME == 1 or MFilter)) NEPMFilter = True;
If (AddressType == Broadcast and (p.BAM == 1 or MFilter)) NEPMFilter = True;
// VLAN filters are ANDed with the previous filters unless promiscuous VLAN is enabled
NEPFilter = NEPMFilter and (VFilter or p.VPE};
// Non Exclusive Imperfect Filters
For Each entry e in HashMACVlan Table
If (HDA == e.HashMAC and (VID == e.VLAN or (VID == NULL and e.VLAN == 0)) and AddressType == e.AddressType) NEIPMFilter = True;
For Each entry e in HashMAC Table
If (HDA == e.HashMAC and AddressType == e.AddressType) NEIPMFilter = True;
// VLAN filters are ANDed with the previous filters unless promiscuous VLAN is enabled
NIEPFilter = NIEPMFilter and (VFilter or p.VPE};
// Packet size filtering is done at the queue level, so it is not part of the switch algorithm
Pass = (EFilter or NEPFilter or NEIPFilter)
Return Pass;
}
-----Original Message-----
From: Ronciak, John [mailto:joh...@in...]
Sent: Tuesday, September 15, 2015 10:40 AM
To: Fujinaka, Todd <tod...@in...>; zhe...@pr...; e10...@li...
Subject: Re: [E1000-devel] Intel 82551IL chips
As long as there is no copy and pasting from the Linux driver to the QNX driver it should not be a problem. I'm not a lawyer but that's generally the case. That said, since the driver works after another a second reboot it's probably not related to the driver. This is probably something that is related to the system during the PCI enumeration of devices. Are all the other devices seen on a cold boot? Is there an equivalent to 'lspci' in QNX? If so what's it show on the first boot from power-off? Are all the devices seen at that point or are some missing?
Cheers,
John
> -----Original Message-----
> From: Fujinaka, Todd [mailto:tod...@in...]
> Sent: Tuesday, September 15, 2015 9:43 AM
> To: zhe...@pr...<mailto:zhe...@pr...>; e10...@li...<mailto:e10...@li...>
> Subject: Re: [E1000-devel] Intel 82551IL chips
>
> The 82551L has been EOLed for about nine years by my estimation. We
> don't have any further support for it.
>
> Also, it is probably a violation of the GPL to start with the Linux
> driver to work on the QNX driver. I would suggest trying the FreeBSD driver.
>
> Todd Fujinaka
> Software Application Engineer
> Networking Division (ND)
> Intel Corporation
> tod...@in...<mailto:tod...@in...>
> (503) 712-4565
>
> -----Original Message-----
> From: Желобанов Дмитрий Владимирович
> [mailto:zhe...@pr...]
> Sent: Tuesday, September 15, 2015 5:15 AM
> To: e10...@li...<mailto:e10...@li...>
> Subject: [E1000-devel] Intel 82551IL chips
>
> Hello,
>
> We use chips 82551IL (did 0x1209 rev 0x10) in our embedded platforms.
> Our devices run QNX operation system. We faced with an issue:
> sometimes our devices don't receive Ethernet packets right after boot
> at all, only reboot helps to revive the devices. We think the root
> problem is in hardware- software communication with the Ethernet
> controller, or rather in QNX Ethernet driver.
> I looked in Linux driver (e100.c) and found, the driver uploads
> special firmware in chips like ours.
>
> So, could you give us a document which clarifies changes in
> d102e_ucode.bin firmware from the original on chip microcode?
>
> Желобанов Д.В.
> ООО <Прософт-Системы>, г. Екатеринбург.
>
>
> ----------------------------------------------------------------------
> -------- _______________________________________________
> E1000-devel mailing list
> E10...@li...<mailto:E10...@li...>
> https://lists.sourceforge.net/lists/listinfo/e1000-devel
> To learn more about Intel® Ethernet, visit
> http://communities.intel.com/community/wired
------------------------------------------------------------------------------
_______________________________________________
E1000-devel mailing list
E10...@li...<mailto:E10...@li...>
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
|
|
From: Ronciak, J. <joh...@in...> - 2015-09-15 17:40:15
|
As long as there is no copy and pasting from the Linux driver to the QNX driver it should not be a problem. I'm not a lawyer but that's generally the case. That said, since the driver works after another a second reboot it's probably not related to the driver. This is probably something that is related to the system during the PCI enumeration of devices. Are all the other devices seen on a cold boot? Is there an equivalent to 'lspci' in QNX? If so what's it show on the first boot from power-off? Are all the devices seen at that point or are some missing? Cheers, John > -----Original Message----- > From: Fujinaka, Todd [mailto:tod...@in...] > Sent: Tuesday, September 15, 2015 9:43 AM > To: zhe...@pr...; e10...@li... > Subject: Re: [E1000-devel] Intel 82551IL chips > > The 82551L has been EOLed for about nine years by my estimation. We don't > have any further support for it. > > Also, it is probably a violation of the GPL to start with the Linux driver to > work on the QNX driver. I would suggest trying the FreeBSD driver. > > Todd Fujinaka > Software Application Engineer > Networking Division (ND) > Intel Corporation > tod...@in... > (503) 712-4565 > > -----Original Message----- > From: Желобанов Дмитрий Владимирович > [mailto:zhe...@pr...] > Sent: Tuesday, September 15, 2015 5:15 AM > To: e10...@li... > Subject: [E1000-devel] Intel 82551IL chips > > Hello, > > We use chips 82551IL (did 0x1209 rev 0x10) in our embedded platforms. Our > devices run QNX operation system. We faced with an issue: sometimes our > devices don't receive Ethernet packets right after boot at all, only reboot > helps to revive the devices. We think the root problem is in hardware- > software communication with the Ethernet controller, or rather in QNX > Ethernet driver. > I looked in Linux driver (e100.c) and found, the driver uploads special > firmware in chips like ours. > > So, could you give us a document which clarifies changes in d102e_ucode.bin > firmware from the original on chip microcode? > > Желобанов Д.В. > ООО <Прософт-Системы>, г. Екатеринбург. > > > ------------------------------------------------------------------------------ > _______________________________________________ > E1000-devel mailing list > E10...@li... > https://lists.sourceforge.net/lists/listinfo/e1000-devel > To learn more about Intel® Ethernet, visit > http://communities.intel.com/community/wired |
