10ec:8168 [MSI P35 Neo] Network not working after resume from suspend

Bug #1212199 reported by Anca Emanuel
144
This bug affects 30 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

http://www.webupd8.org/2013/01/fix-wireless-or-wired-network-not.html
workaround not working

related ? info:
https://github.com/torvalds/linux/commit/2a15cd2ff488a9fdb55e5e34060f499853b27c77

I am running Ubuntu 13.10 with the latest updates

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-2-generic 3.11.0-2.5
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: emanuel 1634 F.... pulseaudio
CurrentDmesg: [ 18.315564] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Date: Wed Aug 14 13:42:10 2013
HibernationDevice: RESUME=UUID=c295bea4-fefe-4d3b-8f12-ee5b580946db
InstallationDate: Installed on 2013-05-02 (103 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130502)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7360
MarkForUpload: True
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=86fe6e26-730a-49ee-9ef7-096ce5dedeb0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-2-generic N/A
 linux-backports-modules-3.11.0-2-generic N/A
 linux-firmware 1.113
RfKill:

SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.10
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7360
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd11/11/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7360:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7360:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7360
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

Revision history for this message
Anca Emanuel (anca-emanuel) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: needs-full-computer-modl
tags: added: needs-full-computer-model needs-upstream-testing regression-potential
removed: needs-full-computer-modl
tags: added: needs-suspend-log resume suspend
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

 full computer model: no name, made by me.

Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

needs-upstream-testing: I'm allready running:
emanuel@test:~$ cat /proc/version_signature
Ubuntu 3.11.0-2.5-generic 3.11.0-rc5

Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

The log at comment #4 was with workaround from http://www.webupd8.org/2013/01/fix-wireless-or-wired-network-not.html
i.e.: sudo gedit /etc/pm/config.d/unload_modules
add line: SUSPEND_MODULES="$SUSPEND_MODULES r8169"

Now: the log whout that

Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

WORKING with kernel:
emanuel@test:~$ uname -r
3.7.10-030710-generic

Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

Ok. Something else is to blame (mir ?) because I tested suspend and resume from menu (mouse click on suspend) and it works with the latest kernel (3.11.0-rc5 from Ubuntu).
And is NOT working if I press sleep button on my keyboard.

Revision history for this message
Anca Emanuel (anca-emanuel) wrote :
Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

@ comment #8: Nope. If I wait enough time like more than 5 seconds (network from resume) is NOT working (from menu or keyboard).

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

It sounds like this bug does not exist with kernel 3.7.10 per comment #7.

Do you happen to know if this bug was introduced in v3.8, and if so, what release candidate? If you don't know, can you test some v3.8 kernels to identify when this bug was introduced:

v3.8-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc1-raring/
v3.8-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc4-raring/
v3.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring/

tags: added: performing-bisect
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

@Joseph Salisbury: I did not wait enough in suspend time (If I hear my hdd is powering off, then wait 1 second, then press something on keyboard to resume). That is working on every kernel tried including 3.7.10
But If I wait some time, when I resume my PC, the network is not working.

Sorry for confusion.

tags: added: needs-full-motherboard-model
removed: needs-full-computer-model
Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

needs-full-motherboard-model: MSI P35 Neo-F

from dmidecode:
System Information
 Manufacturer: MICRO-STAR INTERNATIONAL CO.,LTD
 Product Name: MS-7360
 Version: 1.0

Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

Today I can not reproduce the problem.

Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

Anca Emanuel, as per http://eu.msi.com/product/mb/P35-Neo.html#/?div=BIOS an update is available for your BIOS (v2.10). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Thank you for your understanding.

tags: added: bios-outdated-v2.10
Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

> BIOS (v2.10). If you update to this, does it change anything?

http://forum-en.msi.com/index.php?topic=140304.0
[quote]NO! This will kill your machine. Your board can use 1.xx BIOSes only.[/quote]
I updated my bios last year.

https://forum-en.msi.com/index.php?topic=139992.msg1046522#msg1046522
[quote]There are 2 BIOS versions for MS-7360, all of them could be named "P35 Neo-F/P35 Neo-FI/G33 Neo-F"
Some of of them are using BIOS 1.xx, others are using BIOS 2.xx[/quote]

tags: removed: performing-bisect
description: updated
Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

I can not exclude the crappy quality of the mainboard:
http://www.newegg.com/Product/Product.aspx?Item=N82E16813130095
(click on feedback tab)

I get mixed results.
I shut down my PC over night. Then in the morning it might work to suspend.
And some times it is not connecting from the start. (I need to go to menu and click Enable Networking (actually disable it), then again to have it working (observed this very few times over the last years))

And from the last few days of testing: After a number of hours working I experience the behavior presented in the screenshot at post #9. With this "feature": restart from menu: click on it and nothing happens. But it works from command line: "sudo reboot".

Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

Is there any other info I missed to give ? (status: incomplete)

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Just to clarify comment #12. There are no earlier kernels that do not exhibit this bug?

Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

@ Comment #19:
I can not reproduce that behavior (in comment #12).

I can reproduce this: restart, from LightDM login, click on suspend, resume works.
This is with kernel 3.2 (log attached) and the latest kernel.

If I log on and suspend, then resume, now the desktop is not responding any more.
Of course Alt+SysRQ+REISUB works.

Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

It is random...

look here:
[ 19.628061] r8169 0000:03:00.0: eth0: link up

first resume:
[ 56.600158] r8169 0000:03:00.0: eth0: link up

second resume:
[ 80.542365] Restarting tasks ... done.
and no network

Revision history for this message
thndsr (stijnverwaaijen) wrote :

Maybe this helps: killing network-manager immediately brings back the connection on my machine.

Revision history for this message
thndsr (stijnverwaaijen) wrote :

On first resume it's always fine. I tried kernel 3.8, 3.9 and 3.10 and they make no difference.

Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

theenduser, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

tags: removed: needs-full-motherboard-model
summary: - Network not working after resume from suspend (r8169)
+ 10ec:8168 [MSI P35 Neo] Network not working after resume from suspend
Revision history for this message
Felix Moreno (felix-justdust) wrote :

same problem here with two different laptos using ubuntu 13.10 with gnome-panel after resume network (wired and wifi) doesn't work and i have to restart computer...

Revision history for this message
panther_d (dk-mailbox) wrote :

Same problem here, since update to 13.10

All three supposed workarounds don't help
- set if to promisc mode on resume (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/771857)
- reload module on resume (http://superuser.com/questions/180103/ubuntu-cant-connect-to-the-internet-restart-required)
- the suspend_modules thing (http://www.webupd8.org/2013/01/fix-wireless-or-wired-network-not.html)

Highly annoying!

Revision history for this message
panther_d (dk-mailbox) wrote :

Hm, correction: the issue is with the NetworkManager hanging upon resume - no matter which eth hardware is used (I just removed the realtec card and use a intel NIC (e1000e), same issue.

Revision history for this message
Christoph Paul (christoph-paulpaul) wrote :

Having the same problem. After resume all network-devices are listed as DEACTIVATED. Re-ACTIVATING doesn't help. Only option is to reboot to get it back working.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Revision history for this message
Paul Smedley (paul-smedley) wrote :

here I can get network back up using:
sudo ifconfig eth0 down
sudo ifconfig eth0 up
sudo dhclient eth0

Revision history for this message
Paul Smedley (paul-smedley) wrote :

I see the same symptoms - R8169 is the network module, motherboard is a Gigabyte GA-P67A-UD3R-B3

Revision history for this message
Christoph Paul (christoph-paulpaul) wrote :

I have still no solution but I have found a workaround:

Create a new shellscript named hibernate.sh. Open it with gedit and paste the following code:

gnome-screensaver-command -l
dbus-send --system --print-reply \
    --dest="org.freedesktop.UPower" \
    /org/freedesktop/UPower \
    org.freedesktop.UPower.Suspend

Save it and make it executable. If you want you can create a .desktop file for it. When you run this script it will send your pc into hibernate-mode including the lockscreen. When you wake your pc now networking works. When you use sleep-mode or hibernate-mode the normal way it doesn't.

Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

Felix Moreno / panther_d / Christoph Paul / Paul Smedley, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

Revision history for this message
Christoph Paul (christoph-paulpaul) wrote :

done filing bug report.

Revision history for this message
Liam Proven (lproven) wrote :

Happening to me as well on Toshiba Satellite Pro P300-1AY.

Looks like Bug #1235864 & Bug #1247468

Revision history for this message
Laurens Bosscher (laurens-laurensbosscher) wrote :

I can confirm this on driver=r8169 with firmware=rtl8168e-3_0.0.4 03/27/12.

Revision history for this message
Eustaquio Rangel (eustaquiorangel) wrote :

Happening to me as well on Dell Vostro 1310 (hey, look, the same version as Ubuntu!). Was working really well with 13.04.

Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

Liam Proven / Laurens Bosscher / Eustaquio Rangel, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions or comments, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

Revision history for this message
Dee (dmusil-x) wrote :

happens to me on lenovo z560, Xubuntu 12.04 - wifi is working, but RJ45/eth0 does not work, sometimes card is not even blinking the led ligts

Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

Dee, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions or comments, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

ATsch (atsch10)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Revision history for this message
Liam Proven (lproven) wrote :

@penalvch:

Can you or someone please explain to me how opening a new bug will help? There are already 4 that I can find which are all describing exactly the same problem, which has been extant since before Saucy was released.

I am commenting here as this one has at least 25 subscribers, whereas the others have fewer.

It seems to be the same problem as Bug #1235864 , Bug #1247468 and Bug #1252121 at least.

Furthermore there is no obvious way to file a report against a particular package. The problem occurs in network-manager and restarting that daemon seems to sort it out; however it is visible in nm-applet and it is possibly caused by the kernel. What should we file reports against?

Please explain to us what we should do and how. I don't see how additional reports will help.

Revision history for this message
Akronix (akronix) wrote :

I'm experiencing this issue too. I use the workaround showed here: https://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade

Revision history for this message
Anca Emanuel (anca-emanuel) wrote : Re: [Bug 1212199] Re: 10ec:8168 [MSI P35 Neo] Network not working after resume from suspend
Download full text (3.2 KiB)

I no longer have this motherboard. Some people replaced bad capacitors
and is working ok for them.
On Mon, Jul 23, 2018 at 4:26 PM Akronix <email address hidden> wrote:
>
> *** This bug is a duplicate of bug 1184262 ***
> https://bugs.launchpad.net/bugs/1184262
>
> I'm experiencing this issue too. I use the workaround showed here:
> https://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-
> after-16-04-upgrade
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1212199
>
> Title:
> 10ec:8168 [MSI P35 Neo] Network not working after resume from suspend
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> http://www.webupd8.org/2013/01/fix-wireless-or-wired-network-not.html
> workaround not working
>
> related ? info:
> https://github.com/torvalds/linux/commit/2a15cd2ff488a9fdb55e5e34060f499853b27c77
>
> I am running Ubuntu 13.10 with the latest updates
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.10
> Package: linux-image-3.11.0-2-generic 3.11.0-2.5
> ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
> Uname: Linux 3.11.0-2-generic x86_64
> ApportVersion: 2.12-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: emanuel 1634 F.... pulseaudio
> CurrentDmesg: [ 18.315564] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> Date: Wed Aug 14 13:42:10 2013
> HibernationDevice: RESUME=UUID=c295bea4-fefe-4d3b-8f12-ee5b580946db
> InstallationDate: Installed on 2013-05-02 (103 days ago)
> InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130502)
> IwConfig:
> eth0 no wireless extensions.
>
> lo no wireless extensions.
> MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7360
> MarkForUpload: True
> ProcFB: 0 nouveaufb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=86fe6e26-730a-49ee-9ef7-096ce5dedeb0 ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-3.11.0-2-generic N/A
> linux-backports-modules-3.11.0-2-generic N/A
> linux-firmware 1.113
> RfKill:
>
> SourcePackage: linux
> StagingDrivers: zram
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 11/11/2008
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: V1.10
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: MS-7360
> dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
> dmi.board.version: 1.0
> dmi.chassis.asset.tag: To Be Filled By O.E.M.
> dmi.chassis.type: 3
> dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
> dmi.chassis.version: 1.0
> dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd11/11/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7360:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7360:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
> dmi.product.name: MS-7360
> dmi.product.version: 1.0
> dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/u...

Read more...

Brad Figg (brad-figg)
tags: added: cscc
To post a comment you must log in.