Via-Rhine onboard chip stop working and could not be reset.

[Carlos Luna]

The network quit to work after some time 30 minutes more or less and is impossible to restart the network or the via-rhine card with rmmod via-rhine and modprobe via-rhine.
Feb 3 13:26:13 ubuntupc kernel: [ 6073.808195] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 4003, PHY status 7849, resetting...

Ubuntu 14.04 LTS
3.13.0-45-generic
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)

I have tested start the kernel with noapic and noacpi options but after several minutes 30 or 45 minutes the USB devices (Mouse -usb genius- and Keyboard -Genius Kb12e ) stop working, so again I must restart the PC.
I think it is a bug related to Kernel. Could be Avahi or network-manager?
This is a long time bug.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-45-generic 3.13.0-45.74
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: caralu74 2405 F.... pulseaudio
 /dev/snd/controlC0: caralu74 2405 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Feb 3 13:58:54 2015
HibernationDevice: RESUME=UUID=1cc04a87-6299-4ae4-b06e-8d4d2e5c5891
InstallationDate: Installed on 2014-08-14 (172 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IwConfig:
 eth0 no wireless extensions.

 eth1 no wireless extensions.

 lo no wireless extensions.
MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7253
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=423d1eff-1f01-4303-a774-0c4cb9918d90 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-45-generic N/A
 linux-backports-modules-3.13.0-45-generic N/A
 linux-firmware 1.127.11
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: V1.2
dmi.board.name: MS-7253
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: 1.00
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrV1.2:bd01/25/2007:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7253:pvr1.00:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7253:rvr1.00:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr:
dmi.product.name: MS-7253
dmi.product.version: 1.00
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-rc7-vivid/

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]