1132db935SJakub Kicinski.. SPDX-License-Identifier: GPL-2.0+ 2132db935SJakub Kicinski 3132db935SJakub Kicinski===================================================== 4132db935SJakub KicinskiLinux Driver for Intel(R) Ethernet Network Connection 5132db935SJakub Kicinski===================================================== 6132db935SJakub Kicinski 7132db935SJakub KicinskiIntel Gigabit Linux driver. 8132db935SJakub KicinskiCopyright(c) 2008-2018 Intel Corporation. 9132db935SJakub Kicinski 10132db935SJakub KicinskiContents 11132db935SJakub Kicinski======== 12132db935SJakub Kicinski 13132db935SJakub Kicinski- Identifying Your Adapter 14132db935SJakub Kicinski- Command Line Parameters 15132db935SJakub Kicinski- Additional Configurations 16132db935SJakub Kicinski- Support 17132db935SJakub Kicinski 18132db935SJakub Kicinski 19132db935SJakub KicinskiIdentifying Your Adapter 20132db935SJakub Kicinski======================== 21132db935SJakub KicinskiFor information on how to identify your adapter, and for the latest Intel 22132db935SJakub Kicinskinetwork drivers, refer to the Intel Support website: 23132db935SJakub Kicinskihttps://www.intel.com/support 24132db935SJakub Kicinski 25132db935SJakub Kicinski 26132db935SJakub KicinskiCommand Line Parameters 27132db935SJakub Kicinski======================= 28132db935SJakub KicinskiIf the driver is built as a module, the following optional parameters are used 29132db935SJakub Kicinskiby entering them on the command line with the modprobe command using this 30132db935SJakub Kicinskisyntax:: 31132db935SJakub Kicinski 32132db935SJakub Kicinski modprobe e1000e [<option>=<VAL1>,<VAL2>,...] 33132db935SJakub Kicinski 34132db935SJakub KicinskiThere needs to be a <VAL#> for each network port in the system supported by 35132db935SJakub Kicinskithis driver. The values will be applied to each instance, in function order. 36132db935SJakub KicinskiFor example:: 37132db935SJakub Kicinski 38132db935SJakub Kicinski modprobe e1000e InterruptThrottleRate=16000,16000 39132db935SJakub Kicinski 40132db935SJakub KicinskiIn this case, there are two network ports supported by e1000e in the system. 41132db935SJakub KicinskiThe default value for each parameter is generally the recommended setting, 42132db935SJakub Kicinskiunless otherwise noted. 43132db935SJakub Kicinski 44132db935SJakub KicinskiNOTE: A descriptor describes a data buffer and attributes related to the data 45132db935SJakub Kicinskibuffer. This information is accessed by the hardware. 46132db935SJakub Kicinski 47132db935SJakub KicinskiInterruptThrottleRate 48132db935SJakub Kicinski--------------------- 49132db935SJakub Kicinski:Valid Range: 0,1,3,4,100-100000 50132db935SJakub Kicinski:Default Value: 3 51132db935SJakub Kicinski 52132db935SJakub KicinskiInterrupt Throttle Rate controls the number of interrupts each interrupt 53132db935SJakub Kicinskivector can generate per second. Increasing ITR lowers latency at the cost of 54132db935SJakub Kicinskiincreased CPU utilization, though it may help throughput in some circumstances. 55132db935SJakub Kicinski 56132db935SJakub KicinskiSetting InterruptThrottleRate to a value greater or equal to 100 57132db935SJakub Kicinskiwill program the adapter to send out a maximum of that many interrupts 58132db935SJakub Kicinskiper second, even if more packets have come in. This reduces interrupt 59132db935SJakub Kicinskiload on the system and can lower CPU utilization under heavy load, 60132db935SJakub Kicinskibut will increase latency as packets are not processed as quickly. 61132db935SJakub Kicinski 62132db935SJakub KicinskiThe default behaviour of the driver previously assumed a static 63132db935SJakub KicinskiInterruptThrottleRate value of 8000, providing a good fallback value for 64132db935SJakub Kicinskiall traffic types, but lacking in small packet performance and latency. 65132db935SJakub KicinskiThe hardware can handle many more small packets per second however, and 66132db935SJakub Kicinskifor this reason an adaptive interrupt moderation algorithm was implemented. 67132db935SJakub Kicinski 68132db935SJakub KicinskiThe driver has two adaptive modes (setting 1 or 3) in which 69132db935SJakub Kicinskiit dynamically adjusts the InterruptThrottleRate value based on the traffic 70132db935SJakub Kicinskithat it receives. After determining the type of incoming traffic in the last 71132db935SJakub Kicinskitimeframe, it will adjust the InterruptThrottleRate to an appropriate value 72132db935SJakub Kicinskifor that traffic. 73132db935SJakub Kicinski 74132db935SJakub KicinskiThe algorithm classifies the incoming traffic every interval into 75132db935SJakub Kicinskiclasses. Once the class is determined, the InterruptThrottleRate value is 76132db935SJakub Kicinskiadjusted to suit that traffic type the best. There are three classes defined: 77132db935SJakub Kicinski"Bulk traffic", for large amounts of packets of normal size; "Low latency", 78132db935SJakub Kicinskifor small amounts of traffic and/or a significant percentage of small 79132db935SJakub Kicinskipackets; and "Lowest latency", for almost completely small packets or 80132db935SJakub Kicinskiminimal traffic. 81132db935SJakub Kicinski 82132db935SJakub Kicinski - 0: Off 83132db935SJakub Kicinski Turns off any interrupt moderation and may improve small packet latency. 84132db935SJakub Kicinski However, this is generally not suitable for bulk throughput traffic due 85132db935SJakub Kicinski to the increased CPU utilization of the higher interrupt rate. 86132db935SJakub Kicinski - 1: Dynamic mode 87132db935SJakub Kicinski This mode attempts to moderate interrupts per vector while maintaining 88132db935SJakub Kicinski very low latency. This can sometimes cause extra CPU utilization. If 89132db935SJakub Kicinski planning on deploying e1000e in a latency sensitive environment, this 90132db935SJakub Kicinski parameter should be considered. 91132db935SJakub Kicinski - 3: Dynamic Conservative mode (default) 92132db935SJakub Kicinski In dynamic conservative mode, the InterruptThrottleRate value is set to 93132db935SJakub Kicinski 4000 for traffic that falls in class "Bulk traffic". If traffic falls in 94132db935SJakub Kicinski the "Low latency" or "Lowest latency" class, the InterruptThrottleRate is 95132db935SJakub Kicinski increased stepwise to 20000. This default mode is suitable for most 96132db935SJakub Kicinski applications. 97132db935SJakub Kicinski - 4: Simplified Balancing mode 98132db935SJakub Kicinski In simplified mode the interrupt rate is based on the ratio of TX and 99132db935SJakub Kicinski RX traffic. If the bytes per second rate is approximately equal, the 100132db935SJakub Kicinski interrupt rate will drop as low as 2000 interrupts per second. If the 101132db935SJakub Kicinski traffic is mostly transmit or mostly receive, the interrupt rate could 102132db935SJakub Kicinski be as high as 8000. 103132db935SJakub Kicinski - 100-100000: 104132db935SJakub Kicinski Setting InterruptThrottleRate to a value greater or equal to 100 105132db935SJakub Kicinski will program the adapter to send at most that many interrupts per second, 106132db935SJakub Kicinski even if more packets have come in. This reduces interrupt load on the 107132db935SJakub Kicinski system and can lower CPU utilization under heavy load, but will increase 108132db935SJakub Kicinski latency as packets are not processed as quickly. 109132db935SJakub Kicinski 110132db935SJakub KicinskiNOTE: InterruptThrottleRate takes precedence over the TxAbsIntDelay and 111132db935SJakub KicinskiRxAbsIntDelay parameters. In other words, minimizing the receive and/or 112132db935SJakub Kicinskitransmit absolute delays does not force the controller to generate more 113132db935SJakub Kicinskiinterrupts than what the Interrupt Throttle Rate allows. 114132db935SJakub Kicinski 115132db935SJakub KicinskiRxIntDelay 116132db935SJakub Kicinski---------- 117132db935SJakub Kicinski:Valid Range: 0-65535 (0=off) 118132db935SJakub Kicinski:Default Value: 0 119132db935SJakub Kicinski 120132db935SJakub KicinskiThis value delays the generation of receive interrupts in units of 1.024 121132db935SJakub Kicinskimicroseconds. Receive interrupt reduction can improve CPU efficiency if 122132db935SJakub Kicinskiproperly tuned for specific network traffic. Increasing this value adds extra 123132db935SJakub Kicinskilatency to frame reception and can end up decreasing the throughput of TCP 124132db935SJakub Kicinskitraffic. If the system is reporting dropped receives, this value may be set 125132db935SJakub Kicinskitoo high, causing the driver to run out of available receive descriptors. 126132db935SJakub Kicinski 127132db935SJakub KicinskiCAUTION: When setting RxIntDelay to a value other than 0, adapters may hang 128132db935SJakub Kicinski(stop transmitting) under certain network conditions. If this occurs a NETDEV 129132db935SJakub KicinskiWATCHDOG message is logged in the system event log. In addition, the 130132db935SJakub Kicinskicontroller is automatically reset, restoring the network connection. To 131132db935SJakub Kicinskieliminate the potential for the hang ensure that RxIntDelay is set to 0. 132132db935SJakub Kicinski 133132db935SJakub KicinskiRxAbsIntDelay 134132db935SJakub Kicinski------------- 135132db935SJakub Kicinski:Valid Range: 0-65535 (0=off) 136132db935SJakub Kicinski:Default Value: 8 137132db935SJakub Kicinski 138132db935SJakub KicinskiThis value, in units of 1.024 microseconds, limits the delay in which a 139132db935SJakub Kicinskireceive interrupt is generated. This value ensures that an interrupt is 140132db935SJakub Kicinskigenerated after the initial packet is received within the set amount of time, 141132db935SJakub Kicinskiwhich is useful only if RxIntDelay is non-zero. Proper tuning, along with 142132db935SJakub KicinskiRxIntDelay, may improve traffic throughput in specific network conditions. 143132db935SJakub Kicinski 144132db935SJakub KicinskiTxIntDelay 145132db935SJakub Kicinski---------- 146132db935SJakub Kicinski:Valid Range: 0-65535 (0=off) 147132db935SJakub Kicinski:Default Value: 8 148132db935SJakub Kicinski 149132db935SJakub KicinskiThis value delays the generation of transmit interrupts in units of 1.024 150132db935SJakub Kicinskimicroseconds. Transmit interrupt reduction can improve CPU efficiency if 151132db935SJakub Kicinskiproperly tuned for specific network traffic. If the system is reporting 152132db935SJakub Kicinskidropped transmits, this value may be set too high causing the driver to run 153132db935SJakub Kicinskiout of available transmit descriptors. 154132db935SJakub Kicinski 155132db935SJakub KicinskiTxAbsIntDelay 156132db935SJakub Kicinski------------- 157132db935SJakub Kicinski:Valid Range: 0-65535 (0=off) 158132db935SJakub Kicinski:Default Value: 32 159132db935SJakub Kicinski 160132db935SJakub KicinskiThis value, in units of 1.024 microseconds, limits the delay in which a 161132db935SJakub Kicinskitransmit interrupt is generated. It is useful only if TxIntDelay is non-zero. 162132db935SJakub KicinskiIt ensures that an interrupt is generated after the initial Packet is sent on 163132db935SJakub Kicinskithe wire within the set amount of time. Proper tuning, along with TxIntDelay, 164132db935SJakub Kicinskimay improve traffic throughput in specific network conditions. 165132db935SJakub Kicinski 166132db935SJakub Kicinskicopybreak 167132db935SJakub Kicinski--------- 168132db935SJakub Kicinski:Valid Range: 0-xxxxxxx (0=off) 169132db935SJakub Kicinski:Default Value: 256 170132db935SJakub Kicinski 171132db935SJakub KicinskiThe driver copies all packets below or equaling this size to a fresh receive 172132db935SJakub Kicinskibuffer before handing it up the stack. 173132db935SJakub KicinskiThis parameter differs from other parameters because it is a single (not 1,1,1 174132db935SJakub Kicinskietc.) parameter applied to all driver instances and it is also available 175132db935SJakub Kicinskiduring runtime at /sys/module/e1000e/parameters/copybreak. 176132db935SJakub Kicinski 177132db935SJakub KicinskiTo use copybreak, type:: 178132db935SJakub Kicinski 179132db935SJakub Kicinski modprobe e1000e.ko copybreak=128 180132db935SJakub Kicinski 181132db935SJakub KicinskiSmartPowerDownEnable 182132db935SJakub Kicinski-------------------- 183132db935SJakub Kicinski:Valid Range: 0,1 184132db935SJakub Kicinski:Default Value: 0 (disabled) 185132db935SJakub Kicinski 186132db935SJakub KicinskiAllows the PHY to turn off in lower power states. The user can turn off this 187132db935SJakub Kicinskiparameter in supported chipsets. 188132db935SJakub Kicinski 189132db935SJakub KicinskiKumeranLockLoss 190132db935SJakub Kicinski--------------- 191132db935SJakub Kicinski:Valid Range: 0,1 192132db935SJakub Kicinski:Default Value: 1 (enabled) 193132db935SJakub Kicinski 194132db935SJakub KicinskiThis workaround skips resetting the PHY at shutdown for the initial silicon 195132db935SJakub Kicinskireleases of ICH8 systems. 196132db935SJakub Kicinski 197132db935SJakub KicinskiIntMode 198132db935SJakub Kicinski------- 199132db935SJakub Kicinski:Valid Range: 0-2 200132db935SJakub Kicinski:Default Value: 0 201132db935SJakub Kicinski 202132db935SJakub Kicinski +-------+----------------+ 203132db935SJakub Kicinski | Value | Interrupt Mode | 204132db935SJakub Kicinski +=======+================+ 205132db935SJakub Kicinski | 0 | Legacy | 206132db935SJakub Kicinski +-------+----------------+ 207132db935SJakub Kicinski | 1 | MSI | 208132db935SJakub Kicinski +-------+----------------+ 209132db935SJakub Kicinski | 2 | MSI-X | 210132db935SJakub Kicinski +-------+----------------+ 211132db935SJakub Kicinski 212132db935SJakub KicinskiIntMode allows load time control over the type of interrupt registered for by 213132db935SJakub Kicinskithe driver. MSI-X is required for multiple queue support, and some kernels and 214132db935SJakub Kicinskicombinations of kernel .config options will force a lower level of interrupt 215132db935SJakub Kicinskisupport. 216132db935SJakub Kicinski 217132db935SJakub KicinskiThis command will show different values for each type of interrupt:: 218132db935SJakub Kicinski 219132db935SJakub Kicinski cat /proc/interrupts 220132db935SJakub Kicinski 221132db935SJakub KicinskiCrcStripping 222132db935SJakub Kicinski------------ 223132db935SJakub Kicinski:Valid Range: 0,1 224132db935SJakub Kicinski:Default Value: 1 (enabled) 225132db935SJakub Kicinski 226132db935SJakub KicinskiStrip the CRC from received packets before sending up the network stack. If 227132db935SJakub Kicinskiyou have a machine with a BMC enabled but cannot receive IPMI traffic after 228132db935SJakub Kicinskiloading or enabling the driver, try disabling this feature. 229132db935SJakub Kicinski 230132db935SJakub KicinskiWriteProtectNVM 231132db935SJakub Kicinski--------------- 232132db935SJakub Kicinski:Valid Range: 0,1 233132db935SJakub Kicinski:Default Value: 1 (enabled) 234132db935SJakub Kicinski 235132db935SJakub KicinskiIf set to 1, configure the hardware to ignore all write/erase cycles to the 236132db935SJakub KicinskiGbE region in the ICHx NVM (in order to prevent accidental corruption of the 237132db935SJakub KicinskiNVM). This feature can be disabled by setting the parameter to 0 during initial 238132db935SJakub Kicinskidriver load. 239132db935SJakub Kicinski 240132db935SJakub KicinskiNOTE: The machine must be power cycled (full off/on) when enabling NVM writes 241132db935SJakub Kicinskivia setting the parameter to zero. Once the NVM has been locked (via the 242132db935SJakub Kicinskiparameter at 1 when the driver loads) it cannot be unlocked except via power 243132db935SJakub Kicinskicycle. 244132db935SJakub Kicinski 245132db935SJakub KicinskiDebug 246132db935SJakub Kicinski----- 247132db935SJakub Kicinski:Valid Range: 0-16 (0=none,...,16=all) 248132db935SJakub Kicinski:Default Value: 0 249132db935SJakub Kicinski 250132db935SJakub KicinskiThis parameter adjusts the level of debug messages displayed in the system logs. 251132db935SJakub Kicinski 252132db935SJakub Kicinski 253132db935SJakub KicinskiAdditional Features and Configurations 254132db935SJakub Kicinski====================================== 255132db935SJakub Kicinski 256132db935SJakub KicinskiJumbo Frames 257132db935SJakub Kicinski------------ 258132db935SJakub KicinskiJumbo Frames support is enabled by changing the Maximum Transmission Unit (MTU) 259132db935SJakub Kicinskito a value larger than the default value of 1500. 260132db935SJakub Kicinski 261132db935SJakub KicinskiUse the ifconfig command to increase the MTU size. For example, enter the 262132db935SJakub Kicinskifollowing where <x> is the interface number:: 263132db935SJakub Kicinski 264132db935SJakub Kicinski ifconfig eth<x> mtu 9000 up 265132db935SJakub Kicinski 266132db935SJakub KicinskiAlternatively, you can use the ip command as follows:: 267132db935SJakub Kicinski 268132db935SJakub Kicinski ip link set mtu 9000 dev eth<x> 269132db935SJakub Kicinski ip link set up dev eth<x> 270132db935SJakub Kicinski 271132db935SJakub KicinskiThis setting is not saved across reboots. The setting change can be made 272132db935SJakub Kicinskipermanent by adding 'MTU=9000' to the file: 273132db935SJakub Kicinski 274132db935SJakub Kicinski- For RHEL: /etc/sysconfig/network-scripts/ifcfg-eth<x> 275132db935SJakub Kicinski- For SLES: /etc/sysconfig/network/<config_file> 276132db935SJakub Kicinski 277132db935SJakub KicinskiNOTE: The maximum MTU setting for Jumbo Frames is 8996. This value coincides 278132db935SJakub Kicinskiwith the maximum Jumbo Frames size of 9018 bytes. 279132db935SJakub Kicinski 280132db935SJakub KicinskiNOTE: Using Jumbo frames at 10 or 100 Mbps is not supported and may result in 281132db935SJakub Kicinskipoor performance or loss of link. 282132db935SJakub Kicinski 283132db935SJakub KicinskiNOTE: The following adapters limit Jumbo Frames sized packets to a maximum of 284132db935SJakub Kicinski4088 bytes: 285132db935SJakub Kicinski 286132db935SJakub Kicinski - Intel(R) 82578DM Gigabit Network Connection 287132db935SJakub Kicinski - Intel(R) 82577LM Gigabit Network Connection 288132db935SJakub Kicinski 289132db935SJakub KicinskiThe following adapters do not support Jumbo Frames: 290132db935SJakub Kicinski 291132db935SJakub Kicinski - Intel(R) PRO/1000 Gigabit Server Adapter 292132db935SJakub Kicinski - Intel(R) PRO/1000 PM Network Connection 293132db935SJakub Kicinski - Intel(R) 82562G 10/100 Network Connection 294132db935SJakub Kicinski - Intel(R) 82562G-2 10/100 Network Connection 295132db935SJakub Kicinski - Intel(R) 82562GT 10/100 Network Connection 296132db935SJakub Kicinski - Intel(R) 82562GT-2 10/100 Network Connection 297132db935SJakub Kicinski - Intel(R) 82562V 10/100 Network Connection 298132db935SJakub Kicinski - Intel(R) 82562V-2 10/100 Network Connection 299132db935SJakub Kicinski - Intel(R) 82566DC Gigabit Network Connection 300132db935SJakub Kicinski - Intel(R) 82566DC-2 Gigabit Network Connection 301132db935SJakub Kicinski - Intel(R) 82566DM Gigabit Network Connection 302132db935SJakub Kicinski - Intel(R) 82566MC Gigabit Network Connection 303132db935SJakub Kicinski - Intel(R) 82566MM Gigabit Network Connection 304132db935SJakub Kicinski - Intel(R) 82567V-3 Gigabit Network Connection 305132db935SJakub Kicinski - Intel(R) 82577LC Gigabit Network Connection 306132db935SJakub Kicinski - Intel(R) 82578DC Gigabit Network Connection 307132db935SJakub Kicinski 308132db935SJakub KicinskiNOTE: Jumbo Frames cannot be configured on an 82579-based Network device if 309132db935SJakub KicinskiMACSec is enabled on the system. 310132db935SJakub Kicinski 311132db935SJakub Kicinski 312132db935SJakub Kicinskiethtool 313132db935SJakub Kicinski------- 314132db935SJakub KicinskiThe driver utilizes the ethtool interface for driver configuration and 315132db935SJakub Kicinskidiagnostics, as well as displaying statistical information. The latest ethtool 316132db935SJakub Kicinskiversion is required for this functionality. Download it at: 317132db935SJakub Kicinski 318132db935SJakub Kicinskihttps://www.kernel.org/pub/software/network/ethtool/ 319132db935SJakub Kicinski 320132db935SJakub KicinskiNOTE: When validating enable/disable tests on some parts (for example, 82578), 321132db935SJakub Kicinskiit is necessary to add a few seconds between tests when working with ethtool. 322132db935SJakub Kicinski 323132db935SJakub Kicinski 324132db935SJakub KicinskiSpeed and Duplex Configuration 325132db935SJakub Kicinski------------------------------ 326132db935SJakub KicinskiIn addressing speed and duplex configuration issues, you need to distinguish 327132db935SJakub Kicinskibetween copper-based adapters and fiber-based adapters. 328132db935SJakub Kicinski 329132db935SJakub KicinskiIn the default mode, an Intel(R) Ethernet Network Adapter using copper 330132db935SJakub Kicinskiconnections will attempt to auto-negotiate with its link partner to determine 331132db935SJakub Kicinskithe best setting. If the adapter cannot establish link with the link partner 332132db935SJakub Kicinskiusing auto-negotiation, you may need to manually configure the adapter and link 333132db935SJakub Kicinskipartner to identical settings to establish link and pass packets. This should 334132db935SJakub Kicinskionly be needed when attempting to link with an older switch that does not 335132db935SJakub Kicinskisupport auto-negotiation or one that has been forced to a specific speed or 336132db935SJakub Kicinskiduplex mode. Your link partner must match the setting you choose. 1 Gbps speeds 337132db935SJakub Kicinskiand higher cannot be forced. Use the autonegotiation advertising setting to 338132db935SJakub Kicinskimanually set devices for 1 Gbps and higher. 339132db935SJakub Kicinski 340132db935SJakub KicinskiSpeed, duplex, and autonegotiation advertising are configured through the 341132db935SJakub Kicinskiethtool utility. 342132db935SJakub Kicinski 343132db935SJakub KicinskiCaution: Only experienced network administrators should force speed and duplex 344132db935SJakub Kicinskior change autonegotiation advertising manually. The settings at the switch must 345132db935SJakub Kicinskialways match the adapter settings. Adapter performance may suffer or your 346132db935SJakub Kicinskiadapter may not operate if you configure the adapter differently from your 347132db935SJakub Kicinskiswitch. 348132db935SJakub Kicinski 349132db935SJakub KicinskiAn Intel(R) Ethernet Network Adapter using fiber-based connections, however, 350132db935SJakub Kicinskiwill not attempt to auto-negotiate with its link partner since those adapters 351132db935SJakub Kicinskioperate only in full duplex and only at their native speed. 352132db935SJakub Kicinski 353132db935SJakub Kicinski 354132db935SJakub KicinskiEnabling Wake on LAN (WoL) 355132db935SJakub Kicinski-------------------------- 356132db935SJakub KicinskiWoL is configured through the ethtool utility. 357132db935SJakub Kicinski 358132db935SJakub KicinskiWoL will be enabled on the system during the next shut down or reboot. For 359132db935SJakub Kicinskithis driver version, in order to enable WoL, the e1000e driver must be loaded 360132db935SJakub Kicinskiprior to shutting down or suspending the system. 361132db935SJakub Kicinski 362132db935SJakub KicinskiNOTE: Wake on LAN is only supported on port A for the following devices: 363132db935SJakub Kicinski- Intel(R) PRO/1000 PT Dual Port Network Connection 364132db935SJakub Kicinski- Intel(R) PRO/1000 PT Dual Port Server Connection 365132db935SJakub Kicinski- Intel(R) PRO/1000 PT Dual Port Server Adapter 366132db935SJakub Kicinski- Intel(R) PRO/1000 PF Dual Port Server Adapter 367132db935SJakub Kicinski- Intel(R) PRO/1000 PT Quad Port Server Adapter 368132db935SJakub Kicinski- Intel(R) Gigabit PT Quad Port Server ExpressModule 369132db935SJakub Kicinski 370132db935SJakub Kicinski 371132db935SJakub KicinskiSupport 372132db935SJakub Kicinski======= 373132db935SJakub KicinskiFor general information, go to the Intel support website at: 374132db935SJakub Kicinski 375132db935SJakub Kicinskihttps://www.intel.com/support/ 376132db935SJakub Kicinski 377132db935SJakub Kicinskior the Intel Wired Networking project hosted by Sourceforge at: 378132db935SJakub Kicinski 379132db935SJakub Kicinskihttps://sourceforge.net/projects/e1000 380132db935SJakub Kicinski 381132db935SJakub KicinskiIf an issue is identified with the released source code on a supported kernel 382132db935SJakub Kicinskiwith a supported adapter, email the specific information related to the issue 383132db935SJakub Kicinskito e1000-devel@lists.sf.net. 384