Hello,<br />
<br />
One of my routers runs (stock) CentOS 6.2 x86_64 and has an Intel NIC inside (Intel Corporation 82574L Gigabit Network Connection [8086:10d3]), managed by the e1000e kernel module.<br />
<br />
After a while, the system locks completely, requiring a cold reboot.<br />
<br />
<br />
Looking in /var/log/messages, I get (excerpt):<br />
Mar 21 11:24:37 example kernel: e1000e: Intel(R) PRO/1000 Network Driver - 1.4.4-k<br />
Mar 21 11:24:37 example kernel: e1000e: Copyright(c) 1999 - 2011 Intel Corporation.<br />
Mar 21 11:24:37 example kernel: e1000e 0000:01:00.0: Disabling ASPM L0s <br />
Mar 21 11:24:37 example kernel: e1000e 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16<br />
Mar 21 11:24:37 example kernel: e1000e 0000:01:00.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:1b:21:d4:7b:84<br />
Mar 21 11:24:37 example kernel: e1000e 0000:01:00.0: eth0: Intel(R) PRO/1000 Network Connection<br />
Mar 21 11:24:37 example kernel: e1000e 0000:01:00.0: eth0: MAC: 3, PHY: 8, PBA No: E46981-006<br />
Mar 21 11:24:37 example kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx<br />
Mar 23 13:31:43 example kernel: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out<br />
Mar 23 13:31:43 example kernel: xt_CLASSIFY xt_AUDIT ipt_LOG xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ipta<br />
ble_mangle nfnetlink iptable_filter ip_tables autofs4 sunrpc cpufreq_ondemand acpi_cpufreq freq_table mperf ipv6 uinput ppdev parport_pc parpo<br />
rt r8169 mii atl1e(U) e1000e sg microcode i2c_i801 iTCO_wdt iTCO_vendor_support shpchp snd_hda_codec_via snd_hda_intel snd_hda_codec snd_hwdep<br />
snd_seq snd_seq_device snd_pcm snd_timer snd soundcore snd_page_alloc ext4 mbcache jbd2 sd_mod crc_t10dif sr_mod cdrom ahci i915 drm_kms_help<br />
er drm i2c_algo_bit i2c_core video output dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan]<br />
Mar 23 13:31:43 example kernel: e1000e 0000:01:00.0: eth0: Reset adapter<br />
Mar 23 13:31:50 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:31:50 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:31:50 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:31:50 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:31:50 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:31:50 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:31:50 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:31:50 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:32:05 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:32:05 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:32:05 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:32:05 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:32:05 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:32:05 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:32:05 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:32:05 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:32:20 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
Mar 23 13:32:20 example kernel: e1000e 0000:01:00.0: eth0: Error reading PHY register<br />
<br />
[...]<br />
<br />
<br />
Instead, the system should work normally.<br />
<br />
<br />
Best regards,<br />
R?zvan
↧
