VIA Technologies VT6102 Rhine-II Ethernet ACPI S3 State resume bug with Linux kernel 2.6.32 onwards

[Brace Computer Laboratory]

Hi,

I will like to report that when I put the computer into Suspend to RAM or ACPI S3 State in Ubuntu 10.04.4 LTS 32-bit and Xubuntu 12.04 32-bit, I no longer have network access after I wake up the system.
Resume does work very reliably, but I lose the network after the resume.
Of course, the network works fine prior to putting the system into ACPI S3 State.
This does not happen with Ubuntu 8.04.4 LTS 32-bit with the same mainboard, so it appears that some developer "broke" the device driver between Linux kernel 2.6.24 (Ubuntu 8.04) and 2.6.32 (Ubuntu 10.04).
The bug is still with Linux kernel 3.2 (Xubuntu 12.04).
Please fix this bug before Ubuntu 10.04's Linux kernel goes EOL.
This is the only bug I know that my ASRock 775DUAL-VSTA mainboard has with Linux.

System Profile:
- ASRock 775DUAL-VSTA mainboard
 * VIA Technologies PT880 Ultra North Bridge
 * VIA Technologies VT8237A South Bridge
 * VIA Technologies VT6102 Rhine-II onboard Ethernet (the part of VT8237A South Bridge)
 * VIA Technologies VT6103 Ethernet external PHY
 * BIOS Version 3.10 (last release)
- Multiple partition boot system with the following images
 * Ubuntu 8.04.4 LTS 32-bit
 * Ubuntu 10.04.4 LTS 32-bit
 * Xubuntu 12.04 32-bit
Regards,
Kevin Brace

[Brace Computer Laboratory (bracecomputerlab)]

Hi,

I just discovered that Launch Pad Bug # 267779 is identical to the bug I am observing.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/267779

It has been 4 to 5 years since the bug was first reported, and I cannot believe that this bug is still in the fairly current Linux kernel (3.2).
Typing in the following commands in Terminal does seem to get my Ethernet access back.

~$ sudo rmmod via_rhine
~$ sudo modprobe via_rhine

Of course, remove "~$" when one types in the commands.
Still I want a more permanent solution by getting the bug fixed.

Regards,

Kevin Brace

[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.12 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.12-saucy/

[Launchpad Janitor (janitor)]

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