netdev - atl1e error messages in syslog

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikKb-B5RpMY0S3gbWrJ0FmzJqKmnQ1SiE+fXTZS@mail.gmail.com>
Date:	Sun, 28 Nov 2010 18:20:40 -0600
From:	Jack Byer <ftn768@...il.com>
To:	jcliburn@...il.com, chris.snook@...il.com, jie.yang@...eros.com
Cc:	netdev@...r.kernel.org
Subject: atl1e error messages in syslog

I keep getting this in my syslog. Is it something I should be
concerned about or is it normal?

Nov 28 15:10:08 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=13978) (expect=14539)
Nov 28 15:10:08 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:10:14 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=3653) (expect=4219)
Nov 28 15:10:14 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:11:12 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=41450) (expect=42174)
Nov 28 15:11:12 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:11:39 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=14086) (expect=14679)
Nov 28 15:11:39 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:11:59 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=9855) (expect=10367)
Nov 28 15:11:59 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:12:15 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=8292) (expect=8939)
Nov 28 15:12:15 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:12:19 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=1097) (expect=1766)
Nov 28 15:12:19 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:12:21 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=466) (expect=1101)
Nov 28 15:12:21 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:12:25 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=2918) (expect=3405)
Nov 28 15:12:25 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:12:49 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=14193) (expect=14920)
Nov 28 15:12:49 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:12:54 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=5377) (expect=6007)
Nov 28 15:12:54 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:13:25 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=19948) (expect=20409)
Nov 28 15:13:25 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:15:03 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=59989) (expect=60513)
Nov 28 15:15:03 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:15:30 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=14866) (expect=15700)
Nov 28 15:15:30 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:16:07 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=21605) (expect=22301)
Nov 28 15:16:07 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:17:06 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=37936) (expect=38825)
Nov 28 15:17:06 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:17:17 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=8070) (expect=8518)
Nov 28 15:17:17 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:17:58 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=29990) (expect=30458)
Nov 28 15:17:58 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:18:16 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=11266) (expect=11986)
Nov 28 15:18:16 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:18:29 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=6203) (expect=6652)
Nov 28 15:18:29 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:18:51 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=15253) (expect=15919)
Nov 28 15:18:51 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:19:58 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=50322) (expect=50860)
Nov 28 15:19:58 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
Nov 28 15:19:59 [kernel] ATL1E 0000:02:00.0: eth0: rx sequence number
error (rx=479) (expect=927)
Nov 28 15:19:59 [kernel] ATL1E 0000:02:00.0: eth0: NIC Link is Up
<1000 Mbps Full Duplex>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html