Thank you for taking the time to report this bug and helping to make Ubuntu better.
Please try the workaround in bug 288281 . If it works, then your problem is a duplicate of that bug - please unsubscribe from this bug and click the "Affects Me Too" link on bug 288281 . If the workaround does not work, then please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team: 1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture. 2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report. 3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report. For your reference, the full description of procedures for kernel- related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance! ** Changed in: linux (Ubuntu) Sourcepackagename: None => linux Status: New => Incomplete -- Network won't re-connect after suspend to RAM https://bugs.launchpad.net/bugs/280981 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
