similar to: 7.1 RC E1000 fix

I'm having problems getting PF + ALTQ to work on em(4) interfaces under 8.0-RELEASE. Kernel was rebuilt with the additional options necessary for ALTQ and what not. Same basic configuration works fine under 7.2-RELEASE. Basically, the queues create successfully but running a pfctl -vsq shows a zero packet/byte count for all queues, even the interface's root queues. This same problem is

For those that may have run across the story on Slashdot about this NIC, here is our statement: Recently there were a few stories published, based on a blog post by an end-user, suggesting specific network packets may cause the Intel? 82574L Gigabit Ethernet Controller to become unresponsive until corrected by a full platform power cycle. Intel was made aware of this issue in September 2012 by

Hi, I noticed that network connection of one of my boxes got significantly slow just after upgrading it to 8.0R. The box has an em0 (82547EI) and worked fine with 7.2R. The symptoms are: - A ping to a host on the same LAN takes 990ms RTT, it reduces gradually to around 1ms, and then it returns to around 1s. The rate was about 2ms/ping. - The response is quite slow, but no packet

Hello, I install Centos'es from PXE, with vmlinuz and initrd provided by images/pxeboot from the first CD of centos 3.4. The server is a PowerEdge 1850 with two integrated e1000 nic interfaces. So kernel is booting, then it comes to the screen which ask for one nic to do a dhcp query. I choose eth0, dhcp server reply well and then i get an ip address, dns'es, etc. And nothing else

Hello everyone, I am trying to tweak some of the sysctl tunables for the ix (ixgbe) driver in FreeBSD 9.2 since I am experiencing less than ideal performance and it seems like I can't find any: # sysctl -a | grep -i ixgbe device ixgbe I am running 9.2-RC4. Any input appreciated. Thanks, -- Rumen Telbizov Unix Systems Administrator <http://telbizov.com>

I have an amd64 7.1 install on a SuperMicro C2SBA+ and I see the following in dmesg.. sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: configured irq 3 not

Have you experienced this? What's going on when this occurs? What do I need to do to keep it from occurring? Please advise. Thanks. Dec 4 10:18:17 localhost kernel: e1000: eth1 NIC Link is Down Dec 4 10:18:19 localhost kernel: e1000: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX Dec 4 10:18:21 localhost kernel: e1000: eth1 NIC Link is Down Dec 4 10:18:23 localhost kernel:

On 05/10/2018 02:53 PM, Ihar Hrachyshka wrote: > Hi, > > In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, > link on the interface becomes ready several seconds after 'ifup' is > executed What is your definition of "becomes ready"? Are you looking at the output of "ip link show" in the guest? Or are you watching "brctl

On Fri, Jan 17, 2020 at 3:16 PM david <david at daku.org> wrote: > > Folks > > I know that support for the network adaptors supported by the 'e1000' > driver have been removed from the base distribution. However, I have > exactly that controller (Broadcom Gigabit Ethernet PCI, not > PCIe). Is there a way for me to add support for that on Centos > 8.1?

At 03:27 PM 1/17/2020, Akemi Yagi wrote: >On Fri, Jan 17, 2020 at 3:16 PM david <david at daku.org> wrote: > > > > Folks > > > > I know that support for the network adaptors supported by the 'e1000' > > driver have been removed from the base distribution. However, I have > > exactly that controller (Broadcom Gigabit Ethernet PCI, not > >

On Fri, Mar 23, 2018 at 12:35:36PM +0100, Pino Toscano wrote: > So far v2v did not read the model of network interfaces, resulting in > "virtio" as the model for such interfaces. > > Start reading the model, if available, mapping only E1000 for now. Looks sensible, ACK. > There are also other models, e.g. PCNet32 or VmxNet3, but they are > ignored for now: reading

My system configuration: ASUS M2A-VM motherboard AMD Athlon 64 X2 4200+ 2.2 GHz 4x A-DATA 1GB DDR2 800 memory 2x Intel 10/100/1000 Pro/1000 GT Desktop Network Adapter 2x Seagate Barracuda 250GB HD (RAID 1, software RAID) CentOS 5 x86_64; Kernel 2.6.23 (custom built); Version 7.6.9.2 e1000 driver The symptoms of this problem are outlined at: http://e1000.sourceforge.net/wiki/index.php/Issues[1]

I recently noticed that after starting xend ethtool no longer work for my e1000 card. In my 2.X box which is a P4, ethtool is working after xend start. Same version of e1000 on both boxes. The unstable box is a Tyan 2462 SMP, FC4 dom0 The 2.X box is Dell P330 UP, Centos 4.1 domO Until xend start ethtool is fine, in both setups I am using the e1000 as eth0. Regards, Ted

Still chasing a hang that has dogged me for quite some time. This time I noticed the console logging output showed that processing stopped right on the five-minute interval when cron would have kicked off bsdsar, which in turn ran vmstat. The system is a Supermicro P4PDE motherboard with dual Xeons and hyperthreading enabled. Kernel debugging results are available at

On Thu, May 10, 2018 at 11:53:23AM -0700, Ihar Hrachyshka wrote: > Hi, > > In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, > link on the interface becomes ready several seconds after 'ifup' is > executed, which for some buggy images like cirros may slow down boot > process for up to 1 minute [2]. If we switch from e1000 to virtio, the > link is

I am using centos 5 x86_64 AMD64 X2 4200+. I am current on yum update. My machine has two ethernet cards. e1000 (eth0) and forcedeth (eth1) [root at fsdsigns2 ~]# more /etc/modprobe.conf alias eth0 e1000 alias eth1 forcedeth sometimes on boot the forcedeth driver thinks it is eth0: [root at fsdsigns2 ~]# dmesg | grep eth forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.

[This email is either empty or too large to be displayed at this time]

Hi, try to use virtio instead... Atte. Daniel Romero P. On Thu, May 10, 2018 at 3:53 PM, Ihar Hrachyshka <ihrachys@redhat.com> wrote: > Hi, > > In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, > link on the interface becomes ready several seconds after 'ifup' is > executed, which for some buggy images like cirros may slow down boot > process

I'm pretty consistently getting crashed KVM VMs under network I/O load when using the e1000 and virtio NIC models, with the follow message in dmesg: qemu-kvm[8785]: segfault at d0 ip 00000031e3200a08 sp 0000000047784080 error 4 in libnvidia-tls.so.285.05.23[31e3200000+3000] qemu-kvm[8791]: segfault at d0 ip 00000031e3200a08 sp 0000000049f89080 error 4 in

Hello all. I''ve upgraded my drives, and in doing so loaded FC8. Latest kernel-xen.x86_64 (2.6.21.7-5) and xen.x86_64 (3.1.2-5) available, using 2 Intel NICs with e1000 driver. All worked fine on FC5 with custom domU FC5 with pcifront and NIC drivers in kernel. Now, I''m unable to get the NICs to function inside my domU. The are visible in lspci, and ipconfig. DomU dmesg