[MSI MS-6702] suspend/resume failure

This change was made by a bot.

Did this issue occur in a previous version of Ubuntu, or is this a new issue?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 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.14-rc4-trusty/

Thanks for your interest.

Because I'm still very noob to Linux in general I searched for info how to do this.
You wrote to use kernel 3.13 but gave link to 3.14rc4 for trusty ubuntu.Im assuming the latest kernel is the best option and it will work with Lubuntu.
(ill try the generic amd64 3.14rc4 anyway)

Also I'm concerned about boot problems that may-be caused by new kernel because since I installed Lubuntu when I boot all I see is a blank screen after bios image until splash screen.Is this normal? This blank screen when booting is problematic because I don't know if its frozen (it freezes sometimes for no apparent reason) or booting very long because sometimes it boots more than 5mins and other times less than 2 mins (I don't know why)

I mentioned the black screen mainly because the only ways to revert the kernel I found were to boot from the old one from grub and run apt-get purge.Is this the best way to do this? (Im sorry I couldnt find anything else)

Im worried if i will be able to revert because Ive never seen grub on this OS. Ive tried to hold Shift key once but it didn't work.

Thanks again.
28.02.2014, 01:30, "Joseph Salisbury" <email address hidden>:

>  Did this issue occur in a previous version of Ubuntu, or is this a new
>  issue?
>
>  Would it be possible for you to test the latest upstream kernel? Refer
>  to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
>  v3.13 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.14-rc4-trusty/
>
>  ** Changed in: linux (Ubuntu)
>     Importance: Undecided => Medium
>
>  ** Changed in: linux (Ubuntu)
>         Status: Confirmed => Incomplete
>
>  --
>  You received this bug notification because you are subscribed to the bug
>  report.
>  https://bugs.launchpad.net/bugs/1285196
>
>  Title:
>    [MSI MS-6702] suspend/resume failure
>
>  Status in “linux” package in Ubuntu:
>    Incomplete
>
>  Bug description:
>    Lubuntu 14.04 all updates installed including latest bios.
>
>    Clicked suspend from power menu.PC shutdown completely.
>    The next boot went on forever and monitor light was blinking as if no signal was received.Plugged out power cable, powered on and this time it booted normally.
>
>    Athlon 64 Venice cpu.
>    Radeon 9550
>    2gb kingston valueram=1gb stick two 512mb stick
>    Ms 6702 v1.0
>
>    ProblemType: KernelOops
>    DistroRelease: Ubuntu 14.04
>    Package: linux-image-3.13.0-12-generic 3.13.0-12.32
>    ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
>    Uname: Linux 3.13.0-12-generic x86_64
>    Annotation: This occured during a previous suspend and prevented it from resuming properly.
>    ApportVersion: 2.13.2-0ubuntu5
>    Architecture: amd64
>  ...

Ive installed the headers all and amd64 and linux image.(I hope thats what I was meant to do)

oh btw almost always when Packange Installer installs anything I can see this in its terminal
error: invalid string constant "resize-grip", expected valid string constant

and Unable to locate image file in pixmap_path: "/nautilus/breadcrumb_prelight.png"
what causes these errors?

Ill reboot soon and write here the results.

UPDATE: installed succesully.Removed old ___ successfully. Got a message to report this bug to bugzilla.kernel.org
after leaving pc to see if it would resume from suspend for at least 10 mins.Oh well at least I have a newer kernel.

MAYBE THIS IS IMPORTANT it wont resume from hibernation as well. also I never see grub (dont know if this is normal) when pressed shift all I saw was GRUB. in upper left corner.

In what category should i file this in? (Im confused)

I wish I could edit my upper post but I made a bug report here: https://bugzilla.kernel.org/show_bug.cgi?id=71291

I hope this is the right section. Please fix if not.

fdwsgds, hibernation utilizes different components of the kernel, and as such necessitates a different bug report. You are welcome to file a new one regarding this via a terminal:
ubuntu-bug linux

Regarding the originally reported problem of suspend, did this problem not occur in a release prior to Trusty?

Why did you change it to inconfirmed? Ive been told to set is as confirmed by Joseph Salisbury (jsalisbury) above after trying newest kernel.

Ive used Ubuntu 12.04 about two years ago so I dont know if i had this issue then.

01.03.2014, 18:55, "Christopher M. Penalver" <email address hidden>:
> fdwsgds, hibernation utilizes different components of the kernel, and as such necessitates a different bug report. You are welcome to file a new one regarding this via a terminal:
> ubuntu-bug linux
>
> Regarding the originally reported problem of suspend, did this problem
> not occur in a release prior to Trusty?
>
> ** Tags added: kernel-bug-exists-upstream-3.14-rc4 latest-bios-080011
> regression-potential
>
> ** Changed in: linux (Ubuntu)
>        Status: Confirmed => Incomplete
>
> ** Changed in: linux (Ubuntu)
>      Assignee: fdwsgds (mubtcez) => (unassigned)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1285196
>
> Title:
>   [MSI MS-6702] suspend/resume failure
>
> Status in “linux” package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Lubuntu 14.04 all updates installed including latest bios.
>
>   Clicked suspend from power menu.PC shutdown completely.
>   The next boot went on forever and monitor light was blinking as if no signal was received.Plugged out power cable, powered on and this time it booted normally.
>
>   Athlon 64 Venice cpu.
>   Radeon 9550
>   2gb kingston valueram=1gb stick two 512mb stick
>   Ms 6702 v1.0
>
>   ProblemType: KernelOops
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-3.13.0-12-generic 3.13.0-12.32
>   ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
>   Uname: Linux 3.13.0-12-generic x86_64
>   Annotation: This occured during a previous suspend and prevented it from resuming properly.
>   ApportVersion: 2.13.2-0ubuntu5
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
>   CRDA: Error: [Errno 2] No such file or directory: 'iw'
>   Date: Wed Feb 26 06:48:19 2014
>   ExecutablePath: /usr/share/apport/apportcheckresume
>   Failure: suspend/resume
>   HibernationDevice: RESUME=UUID=10bb46ac-a462-4dfa-8745-b10e6d65a599
>   InstallationDate: Installed on 2014-02-08 (18 days ago)
>   InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha amd64 (20140110)
>   InterpreterPath: /usr/bin/python3.4
>   IwConfig:
>    eth0      no wireless extensions.
>
>    lo        no wireless extensions.
>   MachineType: MSI MS-6702
>   ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
>   ProcEnviron:
>    TERM=linux
>    PATH=(custom, no user)
>   ProcFB:
>    0 VESA VGA
>    1 radeondrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-12-generic root=UUID=eeda0a7a-bb36-44c9-95d7-35c70cf679dd ro resume=/dev/sda3 quiet splash vt.handoff=7
>   RelatedPackageVersions:
>    linux-restricted-modules-3.13.0-12-generic N/A
>    linux...

fwdwgds, please stop assigning yourself unless you are going to release a patch that fixes this problem.

If you are asked by a Triager a question inquiring about this issue, like the one asked in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1285196/comments/8 inquiring about if this is known to be a regression, it's at their discretion to mark it Incomplete while waiting for a response.

Despite this, could you please test for this in Quantal via http://releases.ubuntu.com/quantal/ , suspend and resume successively 10+ times, and advise if this problem is reproducible?

Sorry I thought assign fwdwgds means fwdwgds is affected by this problem.Also unfortunately the only storage space I have is used BY L14.04 on pendrive so I cant test using another release.

I dont understand what you wrote about the Triager and onwards.Explain more clearly?

Why dont you agree with Joseph Salisbury; he told me to mark as complete if the bug still exists after updating kernel?

01.03.2014, 19:50, "Christopher M. Penalver" <email address hidden>:

>   fwdwgds, please stop assigning yourself unless you are going to release
>   a patch that fixes this problem.
>
>   If you are asked by a Triager a question inquiring about this issue,
>   like the one asked in
>   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1285196/comments/8
>   inquiring about if this is known to be a regression, it's at their
>   discretion to mark it Incomplete while waiting for a response.
>
>   Despite this, could you please test for this in Quantal via
>   http://releases.ubuntu.com/quantal/ , suspend and resume successively
>   10+ times, and advise if this problem is reproducible?
>
>   ** Changed in: linux (Ubuntu)
>          Status: Confirmed => Incomplete
>
>   ** Changed in: linux (Ubuntu)
>        Assignee: fdwsgds (mubtcez) => (unassigned)
>
>   --
>   You received this bug notification because you are subscribed to the bug
>   report.
>   https://bugs.launchpad.net/bugs/1285196
>
>   Title:
>     [MSI MS-6702] suspend/resume failure
>
>   Status in “linux” package in Ubuntu:
>     Incomplete
>
>   Bug description:
>     Lubuntu 14.04 all updates installed including latest bios.
>
>     Clicked suspend from power menu.PC shutdown completely.
>     The next boot went on forever and monitor light was blinking as if no signal was received.Plugged out power cable, powered on and this time it booted normally.
>
>     Athlon 64 Venice cpu.
>     Radeon 9550
>     2gb kingston valueram=1gb stick two 512mb stick
>     Ms 6702 v1.0
>
>     ProblemType: KernelOops
>     DistroRelease: Ubuntu 14.04
>     Package: linux-image-3.13.0-12-generic 3.13.0-12.32
>     ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
>     Uname: Linux 3.13.0-12-generic x86_64
>     Annotation: This occured during a previous suspend and prevented it from resuming properly.
>     ApportVersion: 2.13.2-0ubuntu5
>     Architecture: amd64
>     AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
>     CRDA: Error: [Errno 2] No such file or directory: 'iw'
>     Date: Wed Feb 26 06:48:19 2014
>     ExecutablePath: /usr/share/apport/apportcheckresume
>     Failure: suspend/resume
>     HibernationDevice: RESUME=UUID=10bb46ac-a462-4dfa-8745-b10e6d65a599
>     InstallationDate: Installed on 2014-02-08 (18 days ago)
>     InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha amd64 (20140110)
>     InterpreterPath: /usr/bin/python3.4
>     IwConfig:
>      eth0      no wireless extensions.
>
>      lo        no wireless exte...