Bug 14958
Summary: | atl1c timeouts+resets when policy routing is in use | ||
---|---|---|---|
Product: | Drivers | Reporter: | Petr Baudis (pasky) |
Component: | Network | Assignee: | drivers_network (drivers_network) |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | alan, jvargas, mcgrof, nic-devel, niladam, piroisl33t |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.38 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Petr Baudis
2009-12-30 01:43:44 UTC
this may be related to the issue I'm having! I have an AR8152 Fast Ethernet card V1.1 rev C with issues on a specific network. There is a specific network (poorly designed) that runs through 2 DNS servers. It was a small network later added to a large network at a college. When I connect to that network it basically acts like my packages dissappear as they leave the NIC. I get a good connection for 5 seconds then I start getting 100% packet loss! If I ifconfig eth0 down, then ifconfig eth0 up (reset the device) then it connects and I get 5 seconds of good connection. after that its back to 100% packet loss. I'm not the only one experiencing this. My friend has an intel laptop and i have an AMD laptop, both are toshibas, both have the same NIC and both have the same exact problems. Network works fine with any other device, its just this NIC + driver combo. works fine in windows. Also may or may not be related to this issue when I connect a hard wire to the port, NetworkManager doesn't notice. Its as if the card has problems. If I reset the device then it connects. Sometimes it notices that its connected sometimes not. This issue also affects my friends intel laptop as well. its almost like the NIC doesn't wake when there is a wire connected ( just a description not actually the issue) I'd give you logs if I knew what to do, but dmesg shows no errors on the topic. Its not networkmanager either cause it works fine on all other devices and NICs. Oh, this issue also exist on all kernels from .32 -.37 dunno about .38 as its not a full release yet. This problem is exactly being reproduced on my environment using 2.6.38 and 2.6.39 too. As described by submitter, I just had to flush all chains in mangle table with iptables to make it work again. I hope you could fix this soon because routers and gateways are unable to set rules like those ones. I can also confirm this on Ubuntu 10.04 with 2.6.38-13-server. A fix would be highly appreciated. |