Attansic L1 eth0 keeps constantly going down then up

Rayet · 2013-07-22 13:16:02

As per title, eth0 keeps disconnecting and reconnecting especially during high load but not when idle, most likely because, well, it's idle. I have no idea if it's a driver problem or just a hardware defect, though I hope it's not the latter.

I'm using the vanilla Arch 64 bit kernel. The problem presents itself even on a 32 bit kernel and even with the ufw firewall disabled. However, I haven't flushed the rules after disabling the firewall which I will try later. Here are more details about my ethernet controller and sysctl.conf:

Qualcomm Atheros Attansic L1 Gigabit Ethernet (rev b0), driver/module: atl1

02:00.0 Ethernet controller: Qualcomm Atheros Attansic L1 Gigabit Ethernet (rev b0)
	Subsystem: ASUSTeK Computer Inc. Device 1415
	Flags: bus master, fast devsel, latency 0, IRQ 49
	Memory at fe1c0000 (64-bit, non-prefetchable) [size=256K]
	Expansion ROM at fe1a0000 [disabled] [size=128K]
	Capabilities: [40] Power Management version 2
	Capabilities: [48] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [58] Express Endpoint, MSI 00
	Capabilities: [6c] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Kernel driver in use: atl1
	Kernel modules: atl1

sysctl.conf, only parts related to networking:

# Protection from the SYN flood attack.
net.ipv4.tcp_syncookies = 1

# Disable packet forwarding.
net.ipv4.ip_forward = 0
net.ipv6.conf.all.forwarding = 0

#### ipv4 networking ####

## TCP SYN cookie protection
## helps protect against SYN flood attacks
## only kicks in when net.ipv4.tcp_max_syn_backlog is reached
net.ipv4.tcp_syncookies = 1

## protect against tcp time-wait assassination hazards
## drop RST packets for sockets in the time-wait state
## (not widely supported outside of linux, but conforms to RFC)
net.ipv4.tcp_rfc1337 = 1

## tcp timestamps
## + protect against wrapping sequence numbers (at gigabit speeds)
## + round trip time calculation implemented in TCP
## - causes extra overhead and allows uptime detection by scanners like nmap
## enable @ gigabit speeds
net.ipv4.tcp_timestamps = 0
#net.ipv4.tcp_timestamps = 1

## source address verification (sanity checking)
## helps protect against spoofing attacks
net.ipv4.conf.all.rp_filter = 1

## disable ALL packet forwarding (not a router, disable it)
net.ipv4.ip_forward = 0

## log martian packets
net.ipv4.conf.all.log_martians = 1

## ignore echo broadcast requests to prevent being part of smurf attacks
net.ipv4.icmp_echo_ignore_broadcasts = 1

## optionally, ignore all echo requests
## this is NOT recommended, as it ignores echo requests on localhost as well
#net.ipv4.icmp_echo_ignore_all = 1

## ignore bogus icmp errors
net.ipv4.icmp_ignore_bogus_error_responses = 1

## IP source routing (insecure, disable it)
net.ipv4.conf.all.accept_source_route = 0

## send redirects (not a router, disable it)
net.ipv4.conf.all.send_redirects = 0

## ICMP routing redirects (only secure)
net.ipv4.conf.all.accept_redirects = 0
net.ipv4.conf.all.secure_redirects = 1

# Enable IPv6 Privacy Extensions
net.ipv6.conf.default.use_tempaddr = 2
net.ipv6.conf.all.use_tempaddr = 2

Temperatures look fine. Environment: around 28 C, CPU cores: 45-48 C, Nvidia graphics card: 62-68 C (8600M GT has always been that hot for me even older generations, again no idea why).

If it's hardware-related, I could save up for an ethernet to usb card or an ethernet express card. I'm more inclined towards an express card because of USB's CPU utilization and shared bus between all USB ports and I'd rather use it for external devices like HDDs. However, ethernet express cards are rather expensive, between 25 and 60 euros here, and I don't know if I should opt for a cheaper alternative which could lack shielding or be a clone.

Any help is appreciated greatly. Thank you in advance.

Edit:
Forgot to add dmesg's output.

[    8.518175] atl1 0000:02:00.0: version 2.1.3
[   13.471976] atl1 0000:02:00.0: irq 49 for MSI/MSI-X
[   13.472104] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[   99.704173] atl1 0000:02:00.0: eth0 link is down
[  101.279006] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[  101.308117] atl1 0000:02:00.0: eth0 link is down
[  102.947715] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[  106.427952] atl1 0000:02:00.0: eth0 link is down
[  108.053870] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[  242.239498] atl1 0000:02:00.0: eth0 link is down
[  243.842384] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[  363.858664] atl1 0000:02:00.0: eth0 link is down
[  365.453320] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[  444.478455] atl1 0000:02:00.0: eth0 link is down
[  446.039661] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[  659.321157] atl1 0000:02:00.0: eth0 link is down
[  660.929705] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[  661.531185] atl1 0000:02:00.0: eth0 link is down
[  663.085447] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[  775.755396] atl1 0000:02:00.0: eth0 link is down
[  777.291540] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[  828.348018] atl1 0000:02:00.0: eth0 link is down
[  829.967311] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[  972.208987] atl1 0000:02:00.0: eth0 link is down
[  973.810362] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[ 1176.850175] atl1 0000:02:00.0: eth0 link is down
[ 1178.466031] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[ 1207.856123] atl1 0000:02:00.0: eth0 link is down
[ 1209.493219] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[ 1363.706768] atl1 0000:02:00.0: eth0 link is down
[ 1365.335095] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[ 1382.682982] atl1 0000:02:00.0: eth0 link is down
[ 1384.274151] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[ 1414.406624] atl1 0000:02:00.0: eth0 link is down
[ 1415.954979] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[ 1433.954594] atl1 0000:02:00.0: eth0 link is down
[ 1435.572408] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[ 1510.688833] atl1 0000:02:00.0: eth0 link is down
[ 1512.310093] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[ 1645.993075] atl1 0000:02:00.0: eth0 link is down
[ 1647.595327] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex

Another thing. Disabling wake-on-lan on eth0 has no effect, even when done manually with ethtool, the output shows that wol is disabled but on poweroff the ethernet port's led on the router to which the laptop is connected is still on. I guess this could point to a defective ethernet controller, sigh.

Last edited by Rayet (2013-07-22 13:21:33)

Arch Linux

#1 2013-07-22 13:16:02

Attansic L1 eth0 keeps constantly going down then up

Board footer