[MICRO-STAR INTERNATIONAL CO., LTD MS-7100] suspend/resume failure [non-free: nvidia]

[Nais]

My system has problems with the suspend/resume process. Sometimes it works flawlessly but I'd say somewhere between 50-70% of the time it doesn't. Why it works at all the other percentage of the time, I'm still unsure.

The issue is that the computer, on those occasions, doesn't seem to go to sleep at all. It just becomes completely unresponsive. Keyboard is not functional. Monitor is still on, just not displaying a video signal. I have an LCD panel on my case and on a successful sleep the power LED turns yellow. That does not happen on these occasions.

Only option is a reboot through the reset button. After restarting I'll get the message about the kernel crash, and that led me to file this report.

I'm currently using Karmic, but this issue had been happening in Jaunty as well. The symptoms are exactly the same.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: francesco 4524 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'CA0106'/'MSI K8N Diamond MB [SB0438] at 0xde00 irq 16'
   Mixer name : 'CA0106'
   Components : ''
   Controls : 30
   Simple ctrls : 18
CurrentDmesg:
 Error: command ['sh', '-c', 'dmesg | comm -13 /var/log/dmesg -'] failed with exit code 1: [ 67.624021] eth1: no IPv6 routers present
 comm: file 2 is not in sorted order
 [ 1216.845666] UDF-fs: Partition marked readonly; forcing readonly mount
 [ 1216.952384] UDF-fs INFO UDF: Mounting volume 'ITSALWAYSSUNNYINPHILA_S3_D2', timestamp 2008/06/25 19:00 (1000)
Date: Fri Sep 11 10:44:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 001 Device 003: ID 13fe:1d00 Kingston Technology Company Inc. DataTraveler 2.0 1GB/4GB Flash Drive / Patriot Xporter 4GB Flash Drive
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
 Bus 002 Device 002: ID 045e:008c Microsoft Corp. Wireless Intellimouse Explorer 2.0
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7100
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-10-generic 2.6.31-10.31
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-10-generic root=UUID=faf0eebd-2589-4b29-b84a-319faeb062b1 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-10.31-generic
RelatedPackageVersions: linux-firmware 1.16
RfKill:

SourcePackage: linux
Tags: resume suspend
Title: [MICRO-STAR INTERNATIONAL CO., LTD MS-7100] suspend/resume failure [non-free: nvidia]
Uname: Linux 2.6.31-10-generic x86_64
UserGroups:

dmi.bios.date: 10/27/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MS-7100
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/27/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7100:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7100:rvr1.0:cvn:ct3:cvr:
dmi.product.name: MS-7100
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

[^_Pepe_^ (jose-angel-fernandez-freire)]

Hi all,

We'd like to know whether this is still an issue for you. If so, please can you try with last kernel version, (Lucid upstream) which is located on http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/?

Thanks in advance.

[paul.drover (paul-drover)]

I see that this issue has been idle for a while. Can only assume that the original poster managed to resolve. I have exactly the same issue in Lucid, and now in Maverick (the move to the alpha was in desperation, and not easily undone).

Where I differ is that I can reproduce the crash at will with a certain sequence of operations. I've also evolved a an operational procedure that avoids the issue.

Firstly I have an older machine AMD Athlone, 1GHz, 1GB ram, several disks, NVidia (older model). I'm running 10.10 Alpha aka Maverick Merkat. I am using the propriatry NVidia drivers.

To reproduce:

- First log in. All is normal.
- Lock terminal with Ctrl-Alt-L (I've remapped it to Ctrl-Alt-KPDelete). Screen saver should appear.
- move mouse so that the screen saver disappears and you are prompted for password to unlock.
- Do not supply the password. Instead select the "switch user" option. This is where my son was helpful in discovering this procedure.
- log in as a different user. All is normal.
- log out.

The expectation at this point is that you'll be returned to the locked screen where the first user would be able to supply original password to regain access. But no!

On logging out as the second user, the screen goes blank. There is no response from the mouse or keyboard (indeed even the CapLock and NumLock LED's are non-responsive). Alt-F1 will not bring forth a console.

Oddly, though, Alt-SysReq-REISUB does reboot the machine.

On my machine, this is 100% reproducable.

To avoid:

My machine is used by two people, myself and my son. We have agreed that when we are finished our sessions, we will not lock the screen and switch users, rather we will logout and log in again. So far this is avoiding the issue.

I would like to see this issue addressed so that the screen locking feature is functional.

So. What do you need from me to move this along?

Paul.

[^_Pepe_^ (jose-angel-fernandez-freire)]

Hi Paul.

Thanks for your comments.

Please, can you confirm that your motherboard is the same as original reporter?

If so, please, after rebooting, can you, please, include new logs by typing apport-collect -p linux 427947 in a terminal?

If not, I encourage you to open a completely new bug.

Thanks

[^_Pepe_^ (jose-angel-fernandez-freire)]

Paul,

Please, can you check if is there any BIOS update in MSI website?

Thanks

[paul.drover (paul-drover)]

Sorry for the delay, I was expecting updates to be emailed as I've experienced in the past. They were not in this case.

I sincerely doubt that we have the same motherboard, but I'll check this evening.

If not, do you still want the apport-collect? How do I get a dump similar to the original posters?

Paul.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]