dmesg | tail
[ 3271.396443] e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-NAPI
[ 3271.396449] e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
[ 3271.396496] e1000e 0000:02:00.0: Disabling ASPM L0s L1
[ 3271.396517] e1000e 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 3271.396545] e1000e 0000:02:00.0: setting latency timer to 64
[ 3271.396942] e1000e 0000:02:00.0: irq 47 for MSI/MSI-X
[ 3271.449063] e1000e 0000:02:00.0: (unregistered net_device): The NVM Checksum Is Not Valid
[ 3271.460261] e1000e 0000:02:00.0: PCI INT A disabled
[ 3271.460280] e1000e: probe of 0000:02:00.0 failed with error -5
[ 3792.263145] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev-e1000e instead
Пользователь решил продолжить мысль 15 Сентября 2011, 03:46:35:
ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:18:f3:7a:13:b2
inet addr:192.168.100.7 Bcast:192.168.100.255 Mask:255.255.255.0
inet6 addr: fe80::218:f3ff:fe7a:13b2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20443 errors:0 dropped:0 overruns:0 frame:0
TX packets:15787 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:25060846 (25.0 MB) TX bytes:1841193 (1.8 MB)
Interrupt:21 Base address:0x1000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:720 (720.0 B) TX bytes:720 (720.0 B)
Пользователь решил продолжить мысль 15 Сентября 2011, 03:49:59:
В файле README от драйвера нашел вот такое
82573(V/L/E) TX Unit Hang Messages
----------------------------------
Several adapters with the 82573 chipset display "TX unit hang" messages
during normal operation with the e1000e driver. The issue appears both with
TSO enabled and disabled, and is caused by a power management function that
is enabled in the EEPROM. Early releases of the chipsets to vendors had the
EEPROM bit that enabled the feature. After the issue was discovered newer
adapters were released with the feature disabled in the EEPROM.
If you encounter the problem in an adapter, and the chipset is an 82573-based
one, you can verify that your adapter needs the fix by using ethtool:
# ethtool -e eth0
Offset Values
------ ------
0x0000 00 12 34 56 fe dc 30 0d 46 f7 f4 00 ff ff ff ff
0x0010 ff ff ff ff 6b 02 8c 10 d9 15 8c 10 86 80 de 83
^^
The value at offset 0x001e (de) has bit 0 unset. This enables the problematic
power saving feature. In this case, the EEPROM needs to read "df" at offset
0x001e.
A one-time EEPROM fix is available as a shell script. This script will verify
that the adapter is applicable to the fix and if the fix is needed or not. If
the fix is required, it applies the change to the EEPROM and updates the
checksum. The user must reboot the system after applying the fix if changes
were made to the EEPROM.
Example output of the script:
# bash fixeep-82573-dspd.sh eth0
eth0: is a "82573E Gigabit Ethernet Controller"
This fixup is applicable to your hardware
executing command: ethtool -E eth0 magic 0x109a8086 offset 0x1e value 0xdf
Change made. You *MUST* reboot your machine before changes take effect!
The script can be downloaded at
http://e1000.sourceforge.net/files/fixeep-82573-dspd.shу меня имено этот чип, но устройства eth1 нету патч не запустить