I am getting these errors occasionally from a ClearOS 6.7 system using an
intel e1000 NIC. They are not catastrophic as the NIC is reset and resumes
working...
Also occasionally it stops dead and doesn't pass any packets - catastrophic.
a "service network restart" will fix this - so created a band aid using this
script while seeking a fix. Sends an email and logs time. Checks every
approx 5 minutes.
The NIC and driver in question...
That's a very old driver circa 2006/2007 :-( - how to update?
The Intel e1000 drivers are now on http://sourceforge.net. The latest is
8.0.35 - and are no longer maintained, so that is the final version.
Unfortunately this source will not compile on a ClearOS 6.7 system.
Elrepo has a kmod e1000 driver rpm at the 8.0.35 level, but naturally will
not install. So what to do?
Fortunately elrepo also has the source "e1000-kmod-8.0.35-1.el6.elrepo.src.rpm"
- at least the driver should compile on a Redhat Enterprise based system. Just
ignore the kmod bit... so downloaded and installed the source rpm. Naturally an
rpmbuilt will not work, but...
went into /root/rpmbuild/BUILD/e1000-8.0.35/src and there was the traditional
e1000 source complete with a Makefile. A 'make' and a 'make install' worked
wonderfully replacing the old e1000.ko with a brand new one...
Naturally you must have the development software installed to do this (see elsewhere
on these forums)
Maybe this technique can be used to update other drivers and of use to somebody?
Now waiting to see if my problem is resolved...
EDIT: Sorry - I forgot a vital step :-(
after installing the source rpm you must "cd /root/rpmbuild/SPECS" and try to rpmbuild
"rpmbuild -ba e1000-kmod.spec". It will fail, but will unpack the source for you in
"/root/rpmbuild/BUILD/e1000-8.0.35/src"
intel e1000 NIC. They are not catastrophic as the NIC is reset and resumes
working...
...
Jan 22 05:42:13 alice kernel: next_to_watch.status <0>
Jan 22 05:42:15 alice kernel: e1000 0000:01:00.0: eth1: Detected Tx Unit Hang
Jan 22 05:42:15 alice kernel: Tx Queue <0>
Jan 22 05:42:15 alice kernel: TDH <c5>
Jan 22 05:42:15 alice kernel: TDT <d3>
Jan 22 05:42:15 alice kernel: next_to_use <d3>
Jan 22 05:42:15 alice kernel: next_to_clean <c3>
Jan 22 05:42:15 alice kernel: buffer_info[next_to_clean]
Jan 22 05:42:15 alice kernel: time_stamp <1c23e7e5>
Jan 22 05:42:15 alice kernel: next_to_watch <c5>
Jan 22 05:42:15 alice kernel: jiffies <1c23fd73>
Jan 22 05:42:15 alice kernel: next_to_watch.status <0>
Jan 22 05:42:17 alice kernel: e1000 0000:01:00.0: eth1: Detected Tx Unit Hang
Jan 22 05:42:17 alice kernel: Tx Queue <0>
Jan 22 05:42:17 alice kernel: TDH <c5>
Jan 22 05:42:17 alice kernel: TDT <d3>
Jan 22 05:42:17 alice kernel: next_to_use <d3>
Jan 22 05:42:17 alice kernel: next_to_clean <c3>
Jan 22 05:42:17 alice kernel: buffer_info[next_to_clean]
Jan 22 05:42:17 alice kernel: time_stamp <1c23e7e5>
Jan 22 05:42:17 alice kernel: next_to_watch <c5>
Jan 22 05:42:17 alice kernel: jiffies <1c240544>
Jan 22 05:42:17 alice kernel: next_to_watch.status <0>
Jan 22 05:42:18 alice kernel: e1000 0000:01:00.0: eth1: Reset adapter
Jan 22 05:42:22 alice kernel: e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
...
Also occasionally it stops dead and doesn't pass any packets - catastrophic.
a "service network restart" will fix this - so created a band aid using this
script while seeking a fix. Sends an email and logs time. Checks every
approx 5 minutes.
#!/bin/bash
# Restart network if the eth1 not communicating
# Version 1.0 A G Ellis
eth1_log_file="/var/log/eth1_log"
while :
do
ping_data=`ping -c 3 192.168.2.54` # ping to DIR-300 returns 0 if ok
rc=$?
if [[ $rc -gt 0 ]];then
/sbin/service network restart
echo "Warning - eth1 has failed on `/bin/hostname`..." \
| /bin/mail -s "Warning - eth1 has failed on `hostname`..." \
admin@sraellis.no-ip.com
/bin/date >> $eth1_log_file
fi
/bin/sleep 295
done
The NIC and driver in question...
01:00.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)
Subsystem: Intel Corporation PRO/1000 GT Desktop Adapter
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17
Memory at fbee0000 (32-bit, non-prefetchable) [size=128K]
Memory at fbec0000 (32-bit, non-prefetchable) [size=128K]
I/O ports at dc00 [size=64]
Expansion ROM at 7f700000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Capabilities: [e4] PCI-X non-bridge device
Kernel driver in use: e1000
Kernel modules: e1000
filename: /lib/modules/2.6.32-573.1.1.v6.i686/kernel/drivers/net/e1000/e1000.ko
version: 7.3.21-k8-NAPI
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics@intel.com>
That's a very old driver circa 2006/2007 :-( - how to update?
The Intel e1000 drivers are now on http://sourceforge.net. The latest is
8.0.35 - and are no longer maintained, so that is the final version.
Unfortunately this source will not compile on a ClearOS 6.7 system.
Elrepo has a kmod e1000 driver rpm at the 8.0.35 level, but naturally will
not install. So what to do?
Fortunately elrepo also has the source "e1000-kmod-8.0.35-1.el6.elrepo.src.rpm"
- at least the driver should compile on a Redhat Enterprise based system. Just
ignore the kmod bit... so downloaded and installed the source rpm. Naturally an
rpmbuilt will not work, but...
went into /root/rpmbuild/BUILD/e1000-8.0.35/src and there was the traditional
e1000 source complete with a Makefile. A 'make' and a 'make install' worked
wonderfully replacing the old e1000.ko with a brand new one...
filename: /lib/modules/2.6.32-573.1.1.v6.i686/kernel/drivers/net/e1000/e1000.ko
version: 8.0.35-NAPI
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics@intel.com>
Naturally you must have the development software installed to do this (see elsewhere
on these forums)
Maybe this technique can be used to update other drivers and of use to somebody?
Now waiting to see if my problem is resolved...
EDIT: Sorry - I forgot a vital step :-(
after installing the source rpm you must "cd /root/rpmbuild/SPECS" and try to rpmbuild
"rpmbuild -ba e1000-kmod.spec". It will fail, but will unpack the source for you in
"/root/rpmbuild/BUILD/e1000-8.0.35/src"
Share this post:
Responses (62)
-
Accepted Answer
Much apologies, I misread "6.7" as "6/7," as in "6 and 7." I am running ClearOS 7, the latest.
command entered, we'll see if the problem goes away before I make it permanent.
Nick Howitt wrote:
Have a look at this thread and see if the "ethtool -K your_NIC tso off" works. The only tweaking of upstream kernels we've done is to add a patch for IMQ interfaces. We've never played around with anything else.
All my ClearOS 6 drivers now live in https://www.howitts.co.uk/clearos/ClearOS_6.x/, but note that ClearOS6.x has been end of life for nearly a year and I don't think my drivers fixed the issues. I suggest you look at upgrading as soon as possible for security reasons, but 7.x will be no better for these drivers. -
Accepted Answer
Have a look at this thread and see if the "ethtool -K your_NIC tso off" works. The only tweaking of upstream kernels we've done is to add a patch for IMQ interfaces. We've never played around with anything else.
All my ClearOS 6 drivers now live in https://www.howitts.co.uk/clearos/ClearOS_6.x/, but note that ClearOS6.x has been end of life for nearly a year and I don't think my drivers fixed the issues. I suggest you look at upgrading as soon as possible for security reasons, but 7.x will be no better for these drivers. -
Accepted Answer
Nick, et.al.
I presume this problem got resolved at some point, as I've been running ClearOS on roughly a dozen machines with these NICs problem-free for a couple of years now.
Unfortunately, the problem has returned.
You mention that you've compiled version 3.3.4-1 ... did that ever make it into the default install? I don't know if I've used the right command, I did modinfo e1000e and the output would seem to suggest I'm now running version 3.2.6-k
I've apparently been experiencing this problem for a few months now, and didn't know it. The only noticeable symptom for me has been that I keep getting disconnected from dalnet, which I've ignored because, well, it's dalnet, that's what it does: disconnects. Meanwhile I've had a law office client that has been having myriad problems with their phone system and file shares, and failed file downloads... I've long suspected their ISP until he finally forwarded me a failure email from his SIP provider, giving a definite date and time... then I found this error in messages.
Personally I can live with it, although it's annoying. I think that client is about ready to drop-kick his server into the androscoggin river, however...
Nick Howitt wrote:
ElRepo released v3.3.4-1 of the e1000e driver last night so I have compiled it for ClearOS 6.x and 7.x and put the files here until my ISP removes my webspace (which he said would finish on 28/04 :S ). I've no idea what the changes are as there is no change log that I can find on Intel's site. -
Accepted Answer
I am having this same issue but with the igb driver on an Intel I210-AT. But, it is only on the second NIC, not the first. I have swapped motherboards (thus swapped NICS) and have the same issue. Also, it doesn't matter if that NIC is plugged into my internet connection or my LAN connection. Thoughts? -
Accepted Answer
-
Accepted Answer
I'm not sure there is much I can do about the installation errors. I could raise it on the ElRepo mailing list, but since the problem appears to go away on removal and re-installation I don't know if they can help. I do nothing to their sources apart from compile them in ClearOS and I don't have the understanding to do any fixing myself. -
Accepted Answer
Nick Howitt wrote:
Unfortunately it is a WFM:
...
It worked both as a clean install and as an update like yours.
Were you running as root when you updated?
yes root...
did a yum remove, reboot, (re)installed without any errors, and reboot... writing files now to server at 112MB/s
when will someone release a new standard that can do 3-4Gb/s? don't need 10Gb/s -
Accepted Answer
Unfortunately it is a WFM:
It worked both as a clean install and as an update like yours.[root@hostname x86_64]# yum localinstall kmod-e1000e-3.3.4-1.clearos7.njh.x86_64.rpm --nogpgcheck
Loaded plugins: clearcenter-marketplace, fastestmirror
ClearCenter Marketplace: fetching repositories...
Examining kmod-e1000e-3.3.4-1.clearos7.njh.x86_64.rpm: kmod-e1000e-3.3.4-1.clearos7.njh.x86_64
Marking kmod-e1000e-3.3.4-1.clearos7.njh.x86_64.rpm as an update to kmod-e1000e-3.3.3-1.clearos7.njh.x86_64
Resolving Dependencies
--> Running transaction check
---> Package kmod-e1000e.x86_64 0:3.3.3-1.clearos7.njh will be updated
---> Package kmod-e1000e.x86_64 0:3.3.4-1.clearos7.njh will be an update
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package
Arch Version Repository Size
================================================================================
Updating:
kmod-e1000e
x86_64 3.3.4-1.clearos7.njh /kmod-e1000e-3.3.4-1.clearos7.njh.x86_64 449 k
Transaction Summary
================================================================================
Upgrade 1 Package
Total size: 449 k
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Updating : kmod-e1000e-3.3.4-1.clearos7.njh.x86_64 1/2
Working. This may take some time ...
Done.
Cleanup : kmod-e1000e-3.3.3-1.clearos7.njh.x86_64 2/2
Working. This may take some time ...
Done.
Verifying : kmod-e1000e-3.3.4-1.clearos7.njh.x86_64 1/2
Verifying : kmod-e1000e-3.3.3-1.clearos7.njh.x86_64 2/2
Updated:
kmod-e1000e.x86_64 0:3.3.4-1.clearos7.njh
Complete!
Were you running as root when you updated? -
Accepted Answer
Eric, Nick
I'd the same errors, but it installed.
After a reboot the driver is loading (i think)
Jun 5 12:41:22 pdebrabander kernel: e1000e: module verification failed: signature and/or required key missing - tainting kernel
Jun 5 12:41:22 pdebrabander kernel: e1000e: Intel(R) PRO/1000 Network Driver - 3.3.4-NAPI
Jun 5 12:41:22 pdebrabander kernel: e1000e: Copyright(c) 1999 - 2016 Intel Corporation.
Jun 5 12:41:22 pdebrabander kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Saw 1 strange error :
Jun 5 13:45:24 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang:#012 TDH <b0>#012 TDT <b8>#012 next_to_use <b8>#012 next_to_clean <ae>#012buffer_info[next_to_clean]:#012 time_stamp <100360638>#012 next_to_watch <b0>#012 jiffies <100360eb0>#012 next_to_watch.status <0>#012MAC Status <80083>#012PHY Status <796d>#012PHY 1000BASE-T Status <7800>#012PHY Extended Status <3000>#012PCI Status <10>
Jun 5 13:45:26 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang:#012 TDH <b0>#012 TDT <b8>#012 next_to_use <b8>#012 next_to_clean <ae>#012buffer_info[next_to_clean]:#012 time_stamp <100360638>#012 next_to_watch <b0>#012 jiffies <100361680>#012 next_to_watch.status <0>#012MAC Status <80083>#012PHY Status <796d>#012PHY 1000BASE-T Status <7800>#012PHY Extended Status <3000>#012PCI Status <10>
Jun 5 13:45:28 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang:#012 TDH <b0>#012 TDT <b8>#012 next_to_use <b8>#012 next_to_clean <ae>#012buffer_info[next_to_clean]:#012 time_stamp <100360638>#012 next_to_watch <b0>#012 jiffies <100361e50>#012 next_to_watch.status <0>#012MAC Status <80083>#012PHY Status <796d>#012PHY 1000BASE-T Status <7800>#012PHY Extended Status <3000>#012PCI Status <10>
Jun 5 13:45:30 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang:#012 TDH <b0>#012 TDT <b8>#012 next_to_use <b8>#012 next_to_clean <ae>#012buffer_info[next_to_clean]:#012 time_stamp <100360638>#012 next_to_watch <b0>#012 jiffies <100362620>#012 next_to_watch.status <0>#012MAC Status <80083>#012PHY Status <796d>#012PHY 1000BASE-T Status <7800>#012PHY Extended Status <3000>#012PCI Status <10>
Jun 5 13:45:32 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang:#012 TDH <b0>#012 TDT <b8>#012 next_to_use <b8>#012 next_to_clean <ae>#012buffer_info[next_to_clean]:#012 time_stamp <100360638>#012 next_to_watch <b0>#012 jiffies <100362df0>#012 next_to_watch.status <0>#012MAC Status <80083>#012PHY Status <796d>#012PHY 1000BASE-T Status <7800>#012PHY Extended Status <3000>#012PCI Status <10>
Jun 5 13:45:32 pdebrabander kernel: ------------[ cut here ]------------
Jun 5 13:45:32 pdebrabander kernel: WARNING: at net/sched/sch_generic.c:303 dev_watchdog+0x270/0x280()
Jun 5 13:45:32 pdebrabander kernel: NETDEV WATCHDOG: enp0s25 (e1000e): transmit queue 0 timed out
Jun 5 13:45:32 pdebrabander kernel: Modules linked in: bluetooth rfkill xt_REDIRECT xt_conntrack nf_nat_tftp nf_conntrack_tftp nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_ftp ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_pptp nf_conntrack_proto_gre arc4 ppp_mppe ppp_generic slhc nf_conntrack_irc nf_conntrack_ftp ip6t_REJECT xt_LOG ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv6 nf_nat_ipv4 nf_nat nf_conntrack ip6table_mangle iptable_mangle ip6table_filter ip6_tables ipt_REJECT xt_multiport iptable_filter snd_hda_codec_analog snd_hda_codec_generic ext4 mbcache jbd2 iTCO_wdt iTCO_vendor_support dell_wmi sparse_keymap ppdev dcdbas snd_hda_intel coretemp snd_hda_codec snd_hda_core snd_hwdep kvm snd_seq snd_seq_device snd_pcm pcspkr
Jun 5 13:45:32 pdebrabander kernel: i2c_i801 sg lpc_ich snd_timer mfd_core snd soundcore wmi parport_pc parport mei_me mei shpchp acpi_cpufreq ip_tables xfs libcrc32c sd_mod crc_t10dif crct10dif_generic sr_mod cdrom crct10dif_common i915 i2c_algo_bit video e1000 serio_raw ahci libahci drm_kms_helper drm ata_generic pata_acpi libata e1000e(OE) ptp pps_core i2c_core dm_mirror dm_region_hash dm_log dm_mod
Jun 5 13:45:32 pdebrabander kernel: CPU: 1 PID: 0 Comm: swapper/1 Tainted: G OE ------------ 3.10.0-327.10.1.v7.x86_64 #1
Jun 5 13:45:32 pdebrabander kernel: Hardware name: Dell Inc. OptiPlex 780 /03NVJ6, BIOS A15 08/06/2013
Jun 5 13:45:32 pdebrabander kernel: ffff8803fbc43d68 bdd4361c6301c772 ffff8803fbc43d20 ffffffff81635cb4
Jun 5 13:45:32 pdebrabander kernel: ffff8803fbc43d58 ffffffff8107b1e0 0000000000000000 ffff8803e2a0c000
Jun 5 13:45:32 pdebrabander kernel: ffff88003695f080 0000000000000001 0000000000000001 ffff8803fbc43dc0
Jun 5 13:45:32 pdebrabander kernel: Call Trace:
Jun 5 13:45:32 pdebrabander kernel: <IRQ> [<ffffffff81635cb4>] dump_stack+0x19/0x1b
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff8107b1e0>] warn_slowpath_common+0x70/0xb0
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff8107b27c>] warn_slowpath_fmt+0x5c/0x80
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff8154d0c0>] dev_watchdog+0x270/0x280
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff8154ce50>] ? dev_graft_qdisc+0x80/0x80
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff8108b086>] call_timer_fn+0x36/0x110
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff8154ce50>] ? dev_graft_qdisc+0x80/0x80
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff8108dd77>] run_timer_softirq+0x237/0x340
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff81084aef>] __do_softirq+0xef/0x280
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff81647d5c>] call_softirq+0x1c/0x30
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff81016fc5>] do_softirq+0x65/0xa0
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff81084e85>] irq_exit+0x115/0x120
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff816488f8>] do_IRQ+0x58/0xf0
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff8163dbad>] common_interrupt+0x6d/0x6d
Jun 5 13:45:32 pdebrabander kernel: <EOI> [<ffffffff81058e96>] ? native_safe_halt+0x6/0x10
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff8101dbcf>] default_idle+0x1f/0xc0
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff8101e4d6>] arch_cpu_idle+0x26/0x30
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff810d62c5>] cpu_startup_entry+0x245/0x290
Jun 5 13:45:32 pdebrabander kernel: [<ffffffff810475fa>] start_secondary+0x1ba/0x230
Jun 5 13:45:32 pdebrabander kernel: ---[ end trace 6861827cec459e5b ]---
Jun 5 13:45:32 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Reset adapter unexpectedly
Jun 5 13:45:34 pdebrabander kernel: e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Afterwards had 1 other error uptill now:
Jun 5 15:30:41 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang:#012 TDH <fa>#012 TDT <3>#012 next_to_use <3>#012 next_to_clean <f9>#012buffer_info[next_to_clean]:#012 time_stamp <100965c7c>#012 next_to_watch <fb>#012 jiffies <100967278>#012 next_to_watch.status <0>#012MAC Status <80083>#012PHY Status <796d>#012PHY 1000BASE-T Status <3800>#012PHY Extended Status <3000>#012PCI Status <10>
Jun 5 15:30:43 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang:#012 TDH <fa>#012 TDT <3>#012 next_to_use <3>#012 next_to_clean <f9>#012buffer_info[next_to_clean]:#012 time_stamp <100965c7c>#012 next_to_watch <fb>#012 jiffies <100967a48>#012 next_to_watch.status <0>#012MAC Status <80083>#012PHY Status <796d>#012PHY 1000BASE-T Status <3800>#012PHY Extended Status <3000>#012PCI Status <10>
Jun 5 15:30:45 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang:#012 TDH <fa>#012 TDT <3>#012 next_to_use <3>#012 next_to_clean <f9>#012buffer_info[next_to_clean]:#012 time_stamp <100965c7c>#012 next_to_watch <fb>#012 jiffies <100968218>#012 next_to_watch.status <0>#012MAC Status <80083>#012PHY Status <796d>#012PHY 1000BASE-T Status <3800>#012PHY Extended Status <3000>#012PCI Status <10>
Jun 5 15:30:45 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Reset adapter unexpectedly
-
Accepted Answer
Nick Howitt wrote:
ElRepo released v3.3.4-1 of the e1000e driver last night so I have compiled it for ClearOS 6.x and 7.x and put the files here until my ISP removes my webspace (which he said would finish on 28/04 :S ). I've no idea what the changes are as there is no change log that I can find on Intel's site.
wget http://homepage.ntlworld.com/howitts/kmod-e1000e-3.3.4-1.clearos7.njh.x86_64.rpm
yum localinstall --nogpgcheck kmod-e1000e-3.3.4-1.clearos7.njh.x86_64.rpm
ran into some problems, but it did install. I have not rebooted yet.
...
# yum localinstall --nogpgcheck kmod-e1000e-3.3.4-1.clearos7.njh.x86_64.rpm
Loaded plugins: clearcenter-marketplace, fastestmirror
ClearCenter Marketplace: fetching repositories...
Examining kmod-e1000e-3.3.4-1.clearos7.njh.x86_64.rpm: kmod-e1000e-3.3.4-1.clearos7.njh.x86_64
Marking kmod-e1000e-3.3.4-1.clearos7.njh.x86_64.rpm as an update to kmod-e1000e-3.3.3-1.clearos7.njh.x86_64
Resolving Dependencies
--> Running transaction check
---> Package kmod-e1000e.x86_64 0:3.3.3-1.clearos7.njh will be updated
---> Package kmod-e1000e.x86_64 0:3.3.4-1.clearos7.njh will be an update
--> Finished Dependency Resolution
Dependencies Resolved
========================================================================================================================
Package Arch Version Repository Size
========================================================================================================================
Updating:
kmod-e1000e x86_64 3.3.4-1.clearos7.njh /kmod-e1000e-3.3.4-1.clearos7.njh.x86_64 449 k
Transaction Summary
========================================================================================================================
Upgrade 1 Package
Total size: 449 k
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Updating : kmod-e1000e-3.3.4-1.clearos7.njh.x86_64 1/2
Working. This may take some time ...
/sbin/weak-modules: line 174: /tmp/weak-modules.D6SXXO/old_initramfs/./usr/lib/modules/3.10.0-327.10.1.v7.x86_64/extra/e1000e/e1000e.ko: Permission denied
/sbin/weak-modules: line 174: /tmp/weak-modules.D6SXXO/old_initramfs/./usr/lib/modules/3.10.0-327.10.1.v7.x86_64/extra/e1000e/e1000e.ko: Permission denied
Done.
Cleanup : kmod-e1000e-3.3.3-1.clearos7.njh.x86_64 2/2
Working. This may take some time ...
Unable to decompress /tmp/weak-modules.9ZLw0w/post_early_cpio.img: Unknown format
Done.
-
Accepted Answer
ElRepo released v3.3.4-1 of the e1000e driver last night so I have compiled it for ClearOS 6.x and 7.x and put the files here until my ISP removes my webspace (which he said would finish on 28/04 :S ). I've no idea what the changes are as there is no change log that I can find on Intel's site. -
Accepted Answer
Nick Howitt wrote:
Patrick de Brabander wrote:
You have to laugh. That is what I had until I swapped it for the i210! I did not need the extra port so I sold it on Ebay (which is where I bought it from). Yes, the INTEL PRO/1000PT Dual Port Gigabit Server Adapter, again, should work out of the box using the e1000e driver or it can use the kmod one (.... but that is what I said about the i210 with the igb driver). From memory it is a PCI-E x4 card but I used it in an x16 slot as I only had x1 or x16 slots. It is also fine to have one port as LAN and one as WAN.
I'm checking out the INTEL PRO/1000PT Dual Port Gigabit Server Adapter.
Is this working with ClearOS 7 ?
And can i use 1 card for both LANs ? (external/internal)
You mentioned it.....
I've not much options due the hardware limitations.
This card is only €19,00, so i can try this and see whether the problem is solved. -
Accepted Answer
Patrick de Brabander wrote:
You have to laugh. That is what I had until I swapped it for the i210! I did not need the extra port so I sold it on Ebay (which is where I bought it from). Yes, the INTEL PRO/1000PT Dual Port Gigabit Server Adapter, again, should work out of the box using the e1000e driver or it can use the kmod one (.... but that is what I said about the i210 with the igb driver). From memory it is a PCI-E x4 card but I used it in an x16 slot as I only had x1 or x16 slots. It is also fine to have one port as LAN and one as WAN.
I'm checking out the INTEL PRO/1000PT Dual Port Gigabit Server Adapter.
Is this working with ClearOS 7 ?
And can i use 1 card for both LANs ? (external/internal) -
Accepted Answer
Nick Howitt wrote:
I'm lost as to where you are now.
I think you have the kmod-e1000e driver installed otherwise you'd be seeing version 3.2.5-k and not 3.3.3-NAPI. You can check with an "ethtool -i your_interface_name"
That is unfortunate about the i210 card. Mine has never given an issue. Perhaps a Dell m/b or BIOS issue? Did you note the error?
ethtool -i enp0s25
driver: e1000e
version: 3.3.3-NAPI
firmware-version: 0.5-3
bus-info: 0000:00:19.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
Yes. It's a MB issue with this card.
What is read on the internet is an incompability with the UEFI and/or ISCSI support of the adapter and older DELL systems
I'm checking out the INTEL PRO/1000PT Dual Port Gigabit Server Adapter.
Is this working with ClearOS 7 ?
And can i use 1 card for both LANs ? (external/internal) -
Accepted Answer
I'm lost as to where you are now.
I think you have the kmod-e1000e driver installed otherwise you'd be seeing version 3.2.5-k and not 3.3.3-NAPI. You can check with an "ethtool -i your_interface_name"
That is unfortunate about the i210 card. Mine has never given an issue. Perhaps a Dell m/b or BIOS issue? Did you note the error? -
Accepted Answer
Hi Nick,
i have bought yhe Intel i210 card, but unfortunately it doesn't work in my server.
Somehow this card is not support in my Dell configuration. It give directly an error during booting and doens't continue loading.
After a closer look in the log files i suddenly noticed that i was looking at the wrong card
The error are with my e1000e card. This is an onboard NIC.
Jun 4 11:48:57 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang:#012 TDH <68>#012 TDT <80>#012 next_to_use <80>#012 next_to_clean <64>#012buffer_info[next_to_clean]:#012 time_stamp <1002139da>#012 next_to_watch <68>#012 jiffies <100213e90>#012 next_to_watch.status <0>#012MAC Status <80083>#012PHY Status <796d>#012PHY 1000BASE-T Status <7800>#012PHY Extended Status <3000>#012PCI Status <10>
Jun 4 11:48:59 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang:#012 TDH <68>#012 TDT <80>#012 next_to_use <80>#012 next_to_clean <64>#012buffer_info[next_to_clean]:#012 time_stamp <1002139da>#012 next_to_watch <68>#012 jiffies <100214660>#012 next_to_watch.status <0>#012MAC Status <80083>#012PHY Status <796d>#012PHY 1000BASE-T Status <7800>#012PHY Extended Status <3000>#012PCI Status <10>
Jun 4 11:49:01 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang:#012 TDH <68>#012 TDT <80>#012 next_to_use <80>#012 next_to_clean <64>#012buffer_info[next_to_clean]:#012 time_stamp <1002139da>#012 next_to_watch <68>#012 jiffies <100214e30>#012 next_to_watch.status <0>#012MAC Status <80083>#012PHY Status <796d>#012PHY 1000BASE-T Status <7800>#012PHY Extended Status <3000>#012PCI Status <10>
Jun 4 11:49:03 pdebrabander kernel: e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang:#012 TDH <68>#012 TDT <80>#012 next_to_use <80>#012 next_to_clean <64>#012buffer_info[next_to_clean]:#012 time_stamp <1002139da>#012 next_to_watch <68>#012 jiffies <100215600>#012 next_to_watch.status <0>#012MAC Status <80083>#012PHY Status <796d>#012PHY 1000BASE-T Status <7800>#012PHY Extended Status <3000>#012PCI Status <10>
I also trid to install the kmod driver, but did not succeed.
Jun 4 11:59:03 pdebrabander kernel: e1000e: module verification failed: signature and/or required key missing - tainting kernel
Jun 4 11:59:03 pdebrabander kernel: e1000e: Intel(R) PRO/1000 Network Driver - 3.3.3-NAPI
Jun 4 11:59:03 pdebrabander kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
Jun 4 11:59:03 pdebrabander kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Jun 4 11:59:03 pdebrabander kernel: e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
Jun 4 11:59:03 pdebrabander kernel: e1000: Copyright (c) 1999-2006 Intel Corporation
-
Accepted Answer
-
Accepted Answer
Patrick de Brabander wrote:
Yes, it works out of the box, or, at least the kernel comes with a recent version of the driver. ElRepo do not even maintain an el7 driver for it as the stock one is OK. I use the ElRepo driver in 6.x as the kernel driver used to lag the ElRepo one by quite a bit and I have not checked the status recently.
Hello Nick,
I've a PCI and PCI x16 slot. So i can use a X1 card.
Is the Intel I210 working out of the box with ClearOS 7 ? -
Accepted Answer
Nick Howitt wrote:
? You need to check your server. As noted earlier e1000 cards are generally PCI and e1000e are generally PCI-E. Which bus do you have (older mainboards in the transition phase had both)? I *think* also that e1000e cards are getting older and have often been replaced by igb cards like the Intel I210 (which I have one of). r8168 cards (PCI-E) are easy to get hold of but need the r8168 driver to work correctly. Tim and I compile the kmod-r8168 for anyone to use. Tony may compile it as well.
Hello Nick,
I've a PCI and PCI x16 slot. So i can use a X1 card.
Is the Intel I210 working out of the box with ClearOS 7 ? -
Accepted Answer
? You need to check your server. As noted earlier e1000 cards are generally PCI and e1000e are generally PCI-E. Which bus do you have (older mainboards in the transition phase had both)? I *think* also that e1000e cards are getting older and have often been replaced by igb cards like the Intel I210 (which I have one of). r8168 cards (PCI-E) are easy to get hold of but need the r8168 driver to work correctly. Tim and I compile the kmod-r8168 for anyone to use. Tony may compile it as well. -
Accepted Answer
-
Accepted Answer
Patrick - I have several E1000 NICs and only one is giving the problem I described, and that only happens once every several days. Have used r8169 NICs and they work fine - just don't mix them with a system that has r8168 based NICs unless you want fun and games. Wonder if your NIC is actually broken or there is some other problem... -
Accepted Answer
Presumably you have a PCI system or is it a mixed PCI/PCI-E? I think RTL-8169 PCI cards are OK, but I don't know much about any of them. PCI will struggle to get full speed on gigabit links because of the PCI bandwidth. PCI-E is better, but for a multi-port card you should use an x4 or greater slot. -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Hi Patrick
No, it is not run by cron. It is a self contained loop that once started will run forever unless killed :-)
Loops every 295 seconds. Started from an entry in /etc/rc.d/rc.local.
In this case eth1 is on the 192.168.2.0/24 network - and pinging another device (192.168.2.54) on that same network that should always be online...
http://tldp.org/LDP/Bash-Beginners-Guide/html/sect_09_02.html
'sleep' in the script should always return with an exit status of zero - so there is no reason for the loop to stop...
Will leave the rest of the commands in the script as homework for you to decipher :-) -
Accepted Answer
Tony Ellis wrote:
...
[/code]
Also occasionally it stops dead and doesn't pass any packets - catastrophic.
a "service network restart" will fix this - so created a band aid using this
script while seeking a fix. Sends an email and logs time. Checks every
approx 5 minutes.
#!/bin/bash
# Restart network if the eth1 not communicating
# Version 1.0 A G Ellis
eth1_log_file="/var/log/eth1_log"
while :
do
ping_data=`ping -c 3 192.168.2.54` # ping to DIR-300 returns 0 if ok
rc=$?
if [[ $rc -gt 0 ]];then
/sbin/service network restart
echo "Warning - eth1 has failed on `/bin/hostname`..." \
| /bin/mail -s "Warning - eth1 has failed on `hostname`..." \
admin@sraellis.no-ip.com
/bin/date >> $eth1_log_file
fi
/bin/sleep 295
done
Hi Tony,
just had today a full list of errors with the network.
So used the band-aid "service network restart" and it is runnnig again.
Just a question about your script.
Are you running this in a cronjob ?
And what address are you ping-ing ? Is this the IP of ETH1 ? -
Accepted Answer
# dmesg | grep e1000e -A 3
[ 0.693470] e1000e: module verification failed: signature and/or required key missing - tainting kernel
[ 0.693890] e1000e: Intel(R) PRO/1000 Network Driver - 3.3.3-NAPI
[ 0.693891] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 0.694032] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 0.694048] e1000e 0000:00:19.0: irq 27 for MSI/MSI-X
[ 0.694060] libata version 3.00 loaded.
[ 0.696126] [drm] Initialized drm 1.1.0 20060810
[ 0.718512] alx 0000:07:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [90:2b:34:da:f5:36]
--
[ 0.949855] e1000e 0000:00:19.0 eth0: registered PHC clock
[ 0.949860] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 90:2b:34:da:f5:34
[ 0.949862] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 0.949908] e1000e 0000:00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
[ 0.949954] ahci 0000:00:1f.2: version 3.0
[ 0.950092] ahci 0000:00:1f.2: irq 28 for MSI/MSI-X
[ 0.960670] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
--
[ 5.792953] e1000e 0000:00:19.0: irq 27 for MSI/MSI-X
[ 5.893834] e1000e 0000:00:19.0: irq 27 for MSI/MSI-X
[ 5.893916] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 7.418216] e1000e: eno1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[ 7.418221] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO
[ 7.418252] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 13.157850] alx 0000:07:00.0: irq 36 for MSI/MSI-X
[ 13.157906] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
poking around in /sys
# ls /sys/class/net/eno1/device/driver/module/version
anaconda-ks.cfg .cshrc
.bash_history kmod-e1000e-3.3.3-1.clearos7.njh.x86_64.rpm
.bash_logout .pki/
.bash_profile .rnd
.bashrc .tcshrc
-
Accepted Answer
-
Accepted Answer
Your shutdown line is a reboot so you're fine.
As far as I know, modinfo gives the result of the latest installed module and not the running module. It will give a result on any module whether it is loaded or not. To update a module without rebooting you need to at least unload the old module and then load in the new one and restart networking. You may also need a "depmod -a" if the installation routine does not do it for you. It is not a good idea to do this if the NIC is in use. A reboot is much easier. -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
I installed using yum as you suggested, confirmed it is running. will be interesting to see if this cures the nic hanging issue.
# modinfo e1000e
filename: /lib/modules/3.10.0-327.10.1.v7.x86_64/extra/e1000e/e1000e.ko
version: 3.3.3-NAPI
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics@intel.com>
rhelversion: 7.2
srcversion: BC7D8BD3880A3E5F62C57D7
-
Accepted Answer
-
Accepted Answer
Nick Howitt wrote:
...try installing my kmod-e1000e package from here.
Install with rpm -ivh kmod-e1000e-3.3.3-1.clearos7.njh.x86_64.rpm? -
Accepted Answer
3.3.3 is very recent so I guess will take a while to get into the kernel natively. The info on Intel's page has an out of date change log so it does not help.
Interestingly, the stock kernel version is later than the previous generally released version (3.1.0.2)!
kmod (ElRepo) drivers should normally survive a kernel upgrade, and, if they don't, ClearOS justs fall back to using the stock kernel module. There was one kernel upgrade for the e1000e and igb NIC's in the ClearOS 6.x kernels which broke compatibility and the drivers needed recompiling, but that is the only time I've ever seen it happen. -
Accepted Answer
Nick Howitt wrote:
I'm not sure this is going the right way. Eric has done a modinfo on e1000, but the error message he reported was for e1000e.
Eric,
If the error is really on e1000e, you can try installing my kmod-e1000e package from here. You can confirm which you are using with a:lspci -k | grep Eth -A 3
FWIW, the e1000 driver is for PCI cards and the e1000e for PCI-E cards.
your driver is ver 3.3.3-1 where the one in the kernel is ver 3.2.5-k. I wonder what was changed in the driver?
# lspci -k | grep Eth -A 2
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04)
Subsystem: Gigabyte Technology Co., Ltd Device e000
Kernel driver in use: e1000e
--
07:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10)
Subsystem: Gigabyte Technology Co., Ltd Device e000
Kernel driver in use: alx
here is the correct modinfo:
# modinfo e1000e
filename: /lib/modules/3.10.0-327.10.1.v7.x86_64/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
version: 3.2.5-k
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics@intel.com>
rhelversion: 7.2
srcversion: 7097C005F85B5C9D374D3FB
alias: pci:v00008086d000015B8sv*sd*bc*sc*i*
alias: pci:v00008086d000015B7sv*sd*bc*sc*i*
alias: pci:v00008086d00001570sv*sd*bc*sc*i*
alias: pci:v00008086d0000156Fsv*sd*bc*sc*i*
alias: pci:v00008086d000015A3sv*sd*bc*sc*i*
alias: pci:v00008086d000015A2sv*sd*bc*sc*i*
alias: pci:v00008086d000015A1sv*sd*bc*sc*i*
alias: pci:v00008086d000015A0sv*sd*bc*sc*i*
alias: pci:v00008086d00001559sv*sd*bc*sc*i*
alias: pci:v00008086d0000155Asv*sd*bc*sc*i*
alias: pci:v00008086d0000153Bsv*sd*bc*sc*i*
alias: pci:v00008086d0000153Asv*sd*bc*sc*i*
alias: pci:v00008086d00001503sv*sd*bc*sc*i*
alias: pci:v00008086d00001502sv*sd*bc*sc*i*
alias: pci:v00008086d000010F0sv*sd*bc*sc*i*
alias: pci:v00008086d000010EFsv*sd*bc*sc*i*
alias: pci:v00008086d000010EBsv*sd*bc*sc*i*
alias: pci:v00008086d000010EAsv*sd*bc*sc*i*
alias: pci:v00008086d00001525sv*sd*bc*sc*i*
alias: pci:v00008086d000010DFsv*sd*bc*sc*i*
alias: pci:v00008086d000010DEsv*sd*bc*sc*i*
alias: pci:v00008086d000010CEsv*sd*bc*sc*i*
alias: pci:v00008086d000010CDsv*sd*bc*sc*i*
alias: pci:v00008086d000010CCsv*sd*bc*sc*i*
alias: pci:v00008086d000010CBsv*sd*bc*sc*i*
alias: pci:v00008086d000010F5sv*sd*bc*sc*i*
alias: pci:v00008086d000010BFsv*sd*bc*sc*i*
alias: pci:v00008086d000010E5sv*sd*bc*sc*i*
alias: pci:v00008086d0000294Csv*sd*bc*sc*i*
alias: pci:v00008086d000010BDsv*sd*bc*sc*i*
alias: pci:v00008086d000010C3sv*sd*bc*sc*i*
alias: pci:v00008086d000010C2sv*sd*bc*sc*i*
alias: pci:v00008086d000010C0sv*sd*bc*sc*i*
alias: pci:v00008086d00001501sv*sd*bc*sc*i*
alias: pci:v00008086d00001049sv*sd*bc*sc*i*
alias: pci:v00008086d0000104Dsv*sd*bc*sc*i*
alias: pci:v00008086d0000104Bsv*sd*bc*sc*i*
alias: pci:v00008086d0000104Asv*sd*bc*sc*i*
alias: pci:v00008086d000010C4sv*sd*bc*sc*i*
alias: pci:v00008086d000010C5sv*sd*bc*sc*i*
alias: pci:v00008086d0000104Csv*sd*bc*sc*i*
alias: pci:v00008086d000010BBsv*sd*bc*sc*i*
alias: pci:v00008086d00001098sv*sd*bc*sc*i*
alias: pci:v00008086d000010BAsv*sd*bc*sc*i*
alias: pci:v00008086d00001096sv*sd*bc*sc*i*
alias: pci:v00008086d0000150Csv*sd*bc*sc*i*
alias: pci:v00008086d000010F6sv*sd*bc*sc*i*
alias: pci:v00008086d000010D3sv*sd*bc*sc*i*
alias: pci:v00008086d0000109Asv*sd*bc*sc*i*
alias: pci:v00008086d0000108Csv*sd*bc*sc*i*
alias: pci:v00008086d0000108Bsv*sd*bc*sc*i*
alias: pci:v00008086d0000107Fsv*sd*bc*sc*i*
alias: pci:v00008086d0000107Esv*sd*bc*sc*i*
alias: pci:v00008086d0000107Dsv*sd*bc*sc*i*
alias: pci:v00008086d000010B9sv*sd*bc*sc*i*
alias: pci:v00008086d000010D5sv*sd*bc*sc*i*
alias: pci:v00008086d000010DAsv*sd*bc*sc*i*
alias: pci:v00008086d000010D9sv*sd*bc*sc*i*
alias: pci:v00008086d00001060sv*sd*bc*sc*i*
alias: pci:v00008086d000010A5sv*sd*bc*sc*i*
alias: pci:v00008086d000010BCsv*sd*bc*sc*i*
alias: pci:v00008086d000010A4sv*sd*bc*sc*i*
alias: pci:v00008086d0000105Fsv*sd*bc*sc*i*
alias: pci:v00008086d0000105Esv*sd*bc*sc*i*
depends: ptp
intree: Y
vermagic: 3.10.0-327.10.1.v7.x86_64 SMP mod_unload modversions
signer: CentOS Linux kernel signing key
sig_key: CB:7F:79:27:7A:10:CF:B2:6D
6:2E:3D:33:A0F:1F:26D:83:AD
sig_hashalgo: sha256
parm: debugebug level (0=none,...,16=all) (int)
parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)
parm: TxIntDelay:Transmit Interrupt Delay (array of int)
parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)
parm: RxIntDelay:Receive Interrupt Delay (array of int)
parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)
parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int)
parm: IntMode:Interrupt Mode (array of int)
parm: SmartPowerDownEnable:Enable PHY smart power down (array of int)
parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)
parm: WriteProtectNVM:Write-protect NVM [WARNING: disabling this can lead to corrupted NVM] (array of int)
parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC (array of int) -
Accepted Answer
Your right Nick - Didn't see that... would be better if Eric really has an NIC requiring the e1000e driver to put that in a separate thread and avoid the (my) confusion which has compounded the problem :-(
Actually, for every rule it seems that there is an exception....
One very early PCI-express NIC from Intel that used an old PCI NIC chipset (82546) and a PCI -> PCI-express bridge requires the e1000 driver...
It's the Intel(R) PRO/1000 P Dual Port Server Adapter for a PCI-express slot.
https://downloadmirror.intel.com/20927/eng/e1000.htm
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »