Bug 8570 - via_rhine stops making new tcp connections.
Summary: via_rhine stops making new tcp connections.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL: https://bugzilla.kernel.org/show_bug....
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-01 22:38 CET by Dave Hodgins
Modified: 2013-11-23 16:14 CET (History)
1 user (show)

See Also:
Source RPM: kernel-server-latest
CVE:
Status comment:


Attachments
tshark capture showing the driver repying to the syn,ack with a reset (1.49 KB, application/octet-stream)
2013-01-01 22:39 CET, Dave Hodgins
Details
tshark capture after rebooting, where it correctly acks the syn,ack. (18.47 KB, application/octet-stream)
2013-01-01 22:41 CET, Dave Hodgins
Details

Description Dave Hodgins 2013-01-01 22:38:32 CET
As discussed on irc, after some period of time which can be anywhere from
a few hours to a few weeks, the via_rhine driver will stop making new
tcp (out) connections.  I can still ssh into the system, and perform
dns lookups.

This is happening with both the 3.3.8-server-2.mga2 kernel, and the
3.4 kernel.

From lspcidrake ...
via_rhine       : VIA Technologies, Inc.|VT6102 [Rhine-II] [NETWORK_ETHERNET] (rev: 78)

A tshark capture shows the driver is returning a reset, instead of an ack,
in response to the syn,ack.

The driver starts responding correctly, after a reboot.
Comment 1 Dave Hodgins 2013-01-01 22:39:46 CET
Created attachment 3304 [details]
tshark capture showing the driver repying to the syn,ack with a reset
Comment 2 Dave Hodgins 2013-01-01 22:41:07 CET
Created attachment 3305 [details]
tshark capture after rebooting, where it correctly acks the syn,ack.
Dave Hodgins 2013-01-01 23:09:44 CET

URL: (none) => https://bugzilla.kernel.org/show_bug.cgi?id=52151

Thomas Backlund 2013-01-02 00:20:59 CET

CC: (none) => tmb
Assignee: thomas.backlund => tmb

Comment 3 Manuel Hiebel 2013-10-22 12:11:23 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 4 Manuel Hiebel 2013-11-23 16:14:42 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


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