After sleep (suspend), NVidia MCP55 Ethernet is broken [Intrepid]

Bug #312144 reported by Sami Mäkinen
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Stefan Bader

Bug Description

The issue is almost the same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/136836

Unlike for some others, for me an Intrepid installation with default settings has networking correctly working.

After suspending and resuming, network no longer works.

"rmmod forcedeth; modprobe forcedeth msi=0 msix=0" resolves the situation fully.

If I add "options forcedeth msi=0 msix=0" to "/etc/modprobe.d/forcedeth" the networking will still not automatically work after first resume, but then it is enough to run "rmmod forcedeth; modprobe forcedeth" after sleep to get it working again. After successive suspend+resume everything works automatically without running commands.

Linux 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux

So there is a workaround, but the workaround requires root privileges and is manual work, so not good.

Revision history for this message
Sami Mäkinen (sami-makinen-helsinki) wrote :

Assigning to Stefan Bader, who was working on the closely related bug 136836. Should I do this or not?

Changed in linux:
assignee: nobody → stefan-bader
Revision history for this message
Sami Mäkinen (sami-makinen-helsinki) wrote :

wrong stefan bader in last assignment, sorry

Changed in linux:
assignee: stefan-bader → stefan-bader-canonical
Revision history for this message
Sami Mäkinen (sami-makinen-helsinki) wrote :

PS: After the first suspend, and then fixing the issue by re-inserting the kernel module, on successive suspends (same session, without rebooting, etc) the network works automatically.

description: updated
Revision history for this message
Laszlo Almasi (almalaci) wrote :

This is the only way I managed to restore network after suspend, thank you. It works the same way for me, no automatic way but at least there's something

Revision history for this message
Laszlo Almasi (almalaci) wrote :

Still manual work but once done, it's permanent:
After editing /etc/modprobe.d/forcedeth you need to update initramfs:
update-initramfs -u -k $(uname -r)

Found it in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/136836

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Sami,

Care to test and confirm if this issue remains with the most recent pre-release of Jaunty 9.04 (currently Alpha4) - http://cdimage.ubuntu.com/releases/jaunty/ . It contains a newer 2.6.28 based kernel. You should be able to test suspend via a LiveCD. Please let us know your results. If the issue remains, per the kernel team's bug policy, please also attach the following information. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

It would also be best to capture your dmesg output after a suspend/resume cycle. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Changed in linux:
status: New → Incomplete
Revision history for this message
vista killer (vistakiller) wrote :

I have the same problem. First i give this in terminal

sudo -i; MODULE="forcedeth"; echo "SUSPEND_MODULES=\"$MODULE\"" >/etc/pm/config.d/01suspend_modules; exit

and after the suspend i give

sudo /etc/init.d/networking restart

now every time i give network restart the network work again. My system is kubuntu jaunty 9.04

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.