Bug 52151 - via_rhine stops making new tcp connections.
Summary: via_rhine stops making new tcp connections.
Status: NEW
Alias: None
Product: Networking
Classification: Unclassified
Component: IPV4 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Stephen Hemminger
URL: https://bugs.mageia.org/show_bug.cgi?...
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-01 22:09 UTC by David W. Hodgins
Modified: 2013-01-16 20:55 UTC (History)
0 users

See Also:
Kernel Version: 3.3.8-server-2.mga2
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Output of lspci, zcat /proc/config.gz, dmesg, ss commands (143.58 KB, text/plain)
2013-01-05 22:47 UTC, David W. Hodgins
Details
dmesg output (40.62 KB, text/plain)
2013-01-16 20:55 UTC, David W. Hodgins
Details

Description David W. Hodgins 2013-01-01 22:09:12 UTC
As shown in the pcap file
https://bugs.mageia.org/attachment.cgi?id=3304
after a period of time ranging from hours to weeks,
the driver starts replying to syn,ack messages with reset,
instead of ack messages.

Rebooting corrects the problem, as shown by the pcap file
https://bugs.mageia.org/attachment.cgi?id=3305
Comment 1 Stephen Hemminger 2013-01-01 22:52:19 UTC
Probably not via-rhine related at all. The driver doesn't do the
TCP processing, that is done by hardware independant networking code.
You need to look at the open connections, and other statistics.

Useful information:
  lspci # shows hardware info
  dmesg # shows kernel log messages
config used to build kernel
  ss -a (or netstat) shows open connections
Comment 2 David W. Hodgins 2013-01-02 00:07:46 UTC
Thanks for the quick response.  Next time it happens, I'll add the additional
information.
Comment 3 David W. Hodgins 2013-01-05 22:47:49 UTC
Created attachment 90521 [details]
Output of lspci, zcat /proc/config.gz, dmesg, ss commands

I was out when it happened again. As shown, during the two hours since
outbound connections stopped working, dmesg was overwritten by a spammer.

The ss output looks normal for this system, where I'm using ssh to connect
to it, and have a couple of other systems using autossh to connect to it,
so that I can connect to them.

After reporting the bug, I switched to kernel version 3.4.24-server-2.mga2
Comment 4 David W. Hodgins 2013-01-16 20:55:59 UTC
Created attachment 91411 [details]
dmesg output

Now that it's happened again, I've been able to get proper
dmesg output, but as shown, there are no error messages
being generated related to networking.

Note You need to log in before you can comment on or make changes to this bug.