Comment 6 for bug 672591

I no longer have this computer, so I can't tell you.

On Wed, Jul 25, 2012 at 5:13 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> Jonathan Reeve, thank you for reporting this and helping make Ubuntu
> better. Maverick reached EOL on April 10, 2012.
> Please see this document for currently supported Ubuntu releases:
> https://wiki.ubuntu.com/Releases
>
> We were wondering if this is still an issue in a supported release? If
> so, can you try with the latest development release of Ubuntu? ISO CD
> images are available from http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you run the following command in a
> supported release from a Terminal (Applications->Accessories->Terminal).
> It will automatically gather and attach updated debug information to
> this report.
>
> apport-collect -p linux <replace-with-bug-number>
>
> Also, if you could test the latest upstream kernel available that would
> be great. It will allow additional upstream developers to examine the
> issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do
> not test the kernel in the daily folder, but the one all the way at the
> bottom. Once you've tested the upstream kernel, please remove the
> 'needs-upstream-testing' tag. This can be done by clicking on the yellow
> pencil icon next to the tag located at the bottom of the bug description
> and deleting the 'needs-upstream-testing' text. As well, please comment
> on which kernel version specifically you tested.
>
> 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', and comment
> as to why specifically you were unable to test it.
>
> Please let us know your results. Thanks in advance.
>
> Helpful Bug Reporting Links:
> https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
>
> https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
>
> https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
>
> https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug
>
> ** Description changed:
>
> I had some problems resuming from suspend with my MSI Wind U100. It
> seemed to power up, but all I got was a blank screen. Sometimes, I would
> get 2-3 seconds when I could move the mouse around OK, but then it would
> inevitably freeze and I'd be forced to hard-reset the machine by
> physically powering it off. It would be completely unresponsive to any
> keyboard or trackpad commands, including switching to other terminals
> (ctrl+alt+f1, etc). Interestingly, this would only happen when I was
> running on battery power. On AC power, suspend and resume worked fine,
> but once I was on battery power, my laptop would freeze upon resume and
> I'd be forced to hard-reset. Even more interestingly, I could suspend
> and resume fine on AC power, but then once I unplugged the power cord,
> the computer would immediately freeze again.
>
> After reading a post on ubuntuforums
> (http://ubuntuforums.org/showthread.php?p=10089125#post10089125) where
> other laptop users mention messages about their Realtek wireless cards,
> I decided to try removing the r8187se module and seeing if it resumed
> - from suspend while on battery power. Amazingly, everything worked. So
> - then I edited /etc/pm/config.d/unload_module to add the line
> - SUSPEND_MODULES="r8187se" and now everything works fine.
> + from suspend while on battery power. Amazingly, everything worked.
> +
> + WORKAROUND: So then I edited /etc/pm/config.d/unload_module to add the
> + line SUSPEND_MODULES="r8187se" and now everything works fine.
>
> So I'm not sure how to pinpoint the exact problem, but according to my
> experience and the forum posters' experiences, this has only been a
> problem since Maverick. It may be as recent as the latest kernel update,
> but no older than the kernel update that came with 10.10. So it might be
> a problem with the new kernel and the r8187se module, or it might be a
> problem with something else about the way these computers suspend and
> resume.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: linux-image-2.6.35-22-generic 2.6.35-22.35
> Regression: Yes
> Reproducible: Yes
> ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
> Uname: Linux 2.6.35-22-generic i686
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> AplayDevices:
> - **** List of PLAYBACK Hardware Devices ****
> - card 0: Intel [HDA Intel], device 0: ALC1200 Analog [ALC1200 Analog]
> - Subdevices: 1/1
> - Subdevice #0: subdevice #0
> + **** List of PLAYBACK Hardware Devices ****
> + card 0: Intel [HDA Intel], device 0: ALC1200 Analog [ALC1200 Analog]
> + Subdevices: 1/1
> + Subdevice #0: subdevice #0
> Architecture: i386
> ArecordDevices:
> - **** List of CAPTURE Hardware Devices ****
> - card 0: Intel [HDA Intel], device 0: ALC1200 Analog [ALC1200 Analog]
> - Subdevices: 1/1
> - Subdevice #0: subdevice #0
> + **** List of CAPTURE Hardware Devices ****
> + card 0: Intel [HDA Intel], device 0: ALC1200 Analog [ALC1200 Analog]
> + Subdevices: 1/1
> + Subdevice #0: subdevice #0
> AudioDevicesInUse:
> - USER PID ACCESS COMMAND
> - /dev/snd/controlC0: jon 1378 F.... pulseaudio
> + USER PID ACCESS COMMAND
> + /dev/snd/controlC0: jon 1378 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> - Card hw:0 'Intel'/'HDA Intel at 0xffe00000 irq 42'
> - Mixer name : 'Realtek ALC1200'
> - Components : 'HDA:10ec0888,14620110,00100101'
> - Controls : 17
> - Simple ctrls : 10
> + Card hw:0 'Intel'/'HDA Intel at 0xffe00000 irq 42'
> + Mixer name : 'Realtek ALC1200'
> + Components : 'HDA:10ec0888,14620110,00100101'
> + Controls : 17
> + Simple ctrls : 10
> Date: Mon Nov 8 21:52:23 2010
> HibernationDevice: RESUME=UUID=6772b5de-d2c3-4cc0-a071-d58978ea2061
> InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release
> i386 (20101007)
> MachineType: MICRO-STAR INTERNATIONAL CO., LTD U-100
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic
> root=UUID=c6d18b94-3c3a-4d36-b476-db5b1b329d4b ro acpi_sleep=nonvs quiet
> splash
> ProcEnviron:
> - LANG=en_US.utf8
> - SHELL=/bin/bash
> + LANG=en_US.utf8
> + SHELL=/bin/bash
> RelatedPackageVersions: linux-firmware 1.38
> RfKill:
> -
> +
> SourcePackage: linux
> StagingDrivers: r8187se
> Title: [STAGING]
> dmi.bios.date: 10/06/2008
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 4.6.3
> dmi.board.asset.tag: To be filled by O.E.M.
> dmi.board.name: U-100
> dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
> dmi.board.version: Ver.001
> 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: Ver.001
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd10/06/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnU-100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU-100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvrVer.001:
> dmi.product.name: U-100
> dmi.product.version: Ver.001
> dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
>
> ** Summary changed:
>
> - Can't resume after suspend with r8187se module loaded
> + 10ec:8199 Can't resume after suspend with r8187se module loaded
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Low
>
> ** 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/672591
>
> Title:
> 10ec:8199 Can't resume after suspend with r8187se module loaded
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/672591/+subscriptions
>