Hi,
Thanks for the question. My description was not very self explanatory -- I
thought that only the dump would be adequate. This occurred about two reboots
after an attempted suspend. That was my first try with suspend. It did not work
well -- I ended up powering off and then restarting the computer. There was a
long delay on restart. Then this occurred later. It did not really seem that
there should be a causal connection. I have only had this motherboard and cpu
for about 2 weeks so I don't have a lot of comparative data. Well, I do have a
bit more now since I just tried it again.
This time I chose suspend and it quickly shut down. I tried to resume with a
rapid tap to the power button. Instead of resuming it began a reboot. When
reboot was completed I logged in and almost immediately got the crash warning.
"A serious kernel error occurred during a prior suspend". When I chose the
option to report the problem the Xserver exited instantly and I as dropped to a
text display that was showing the shutdown sequence --apparently a way along.
It may have been that it was already in midst of shutting down. No report sent
from that one -- obviously. And no crash reported after a reboot.
Okay. Try it once more. Same result, only this time it didn't shut down during
the bug reporting so you now have another dump instance to look at. So the
initial problem is almost completely repeatable although the later results are
soomewhat variable.
One further note: The first instance occured while I was using KDE, the
remainder with Gnome. And I did have a kernel upgrade between the first
instance and these others that I have just done.
Neal Bierbaum
--- On Tue, 3/17/09, Leann Ogasawara <leann.ogasaw...@canonical.com> wrote:
From: Leann Ogasawara <leann.ogasaw...@canonical.com>
Subject: [Bug 343923] Re: [MICRO-STAR INTERNATIONAL CO., LTD MS-7521]
suspend/resume failure
To: nrbcenter-sw...@yahoo.com
Date: Tuesday, March 17, 2009, 5:17 PM
Hi Neal,
Care to elaborate a bit more. Is this reproducible every time, or say
over 10 suspend/resume cycles. Has suspend ever worked in the past, if
so which kernel release (cat /proc/version_signature)? If you could also
please include any information as to the circumstances leading up to
this failure, for example did your battery run out? Did the machine lock
up, did any messages come out? If it is reproducible could you try to
suspend from VT1, press ctrl-alt-F1, login, and run pm-suspend there. If
you could test and report back here that would be helpful. Thanks in
advance.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
[MICRO-STAR INTERNATIONAL CO.,LTD MS-7521] suspend/resume failure
https://bugs.launchpad.net/bugs/343923
You received this bug notification because you are a direct subscriber
of the bug.
Status in “linux” source package in Ubuntu: Incomplete
Bug description:
had tried a suspend ny reboots before.
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from
resuming properly.
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7521
Package: linux-image-2.6.28-9-generic 2.6.28-9.31
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=f0b08dcc-f60c-4339-9b96-f6ac2fea11ec ro vga=794
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-9.31-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory:
'/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [MICRO-STAR INTERNATIONAL CO.,LTD MS-7521] suspend/resume failure
UserGroups:
--
[MICRO-STAR INTERNATIONAL CO.,LTD MS-7521] suspend/resume failure
https://bugs.launchpad.net/bugs/343923
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
