ı have the same problem in 12.04 x64 ubuntu. when I resumed from the
suspend mode, ksoftirqd and kworker uses %100 of cpu. I have the trouble
for 3 years.
please warn me about the information you need
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Please do not change the status of this bug without an explanation.
** Changed in: linux (Ubuntu)
Status: New = Fix Released
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this
** Changed in: linux (Ubuntu)
Status: Fix Released = New
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
If you are still experiencing the issue, please file a separate report.
Your problem is different.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a
** Changed in: linux (Ubuntu)
Status: Fix Released = Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You
I'm running Ubuntu on HP dv5-1050ee (AMD Turion X2 64 bit) and this has
been occuring everytime the system resumes from suspend mode. have to
force shut down and switch on again.
Will the update manager get the relevant update to solve this issue ?
How do I get the logs and post it for the
As far as I can tell, the issue is alive and well--the bug persists.
Every detail of the error initially described by Trampas on 2009-10-28
is present (i.e. need to resume twice from sleep when going to sleep
with power cord on and resuming with power cord off). So perhaps this
bug did not have
** Changed in: linux (Ubuntu)
Status: Fix Released = Incomplete
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of Ubuntu
Bugs,
@Charles: Please provide a reason for the incomplete status.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this
Hi,
I just discovered KernelOops problem after a wake up from the
'suspend' mode. Rather than submitting a new bug report I attached it to
the already started discussion.
The system is stable so far. It is not a mission critical desktop, and I
can simply ignore these system reports. Just
Hi mojsha,
Thanks for your report. Since this issue is fixed for most people, I
would recommend filing your issue as a separate report. It may be due to
a different problem.
Thank you!
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
Hi, for those that have the system instability, I finally got around to
writing a report. Please confirm and supply any info over at bug 490893
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You
The issue reported here is actually resolved with the fix applied to bug
https://bugs.edge.launchpad.net/ubuntu/+bug/464552 . As that bug has
been marked Fix Released, I'll update the status here to reflect the
same. Thanks.
** Changed in: linux (Ubuntu)
Status: In Progress = Fix
** Changed in: linux (Ubuntu)
Status: Fix Released = Fix Committed
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of Ubuntu
Bugs,
Chris: please don't change the bug status without a valid reason.
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You
Hello,
I don't want to sound impatient, but how is progress on this going? The
comments and the large amount of changes in status kind of confuse me.
Thanks,
Ruben
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
Hi Mate,
No idea :)
I think there must be some kind of mix up with email addresses or
something.
I'm subscribed to this bug probably for the same reasons you are, but I
don't have anything
to do with fixing it.
Also, I agree, the status messages are bit overwhelming ...
Cheers
Simon.
There's a bug for the ridiculous amounts of emails that are sent by LP.
I encourage you to chime in on it:
https://bugs.launchpad.net/launchpad/+bug/440519
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
[ cut here ]
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x80/0x90()
Hardware name: To Be Filled By O.E.M.
Component: resume devices
Modules linked in: nfs lockd nfs_acl auth_rpcgss sunrpc binfmt_misc ppdev
During the resume I got an on screen message about /home sda(6) being
unreachable or words to that effect. But I can access it.
The icons on the desktop for several files are not displayed correctly.
I'd like to suggest that this is NOT a low priority since a normal
start-up is fraught with
@DaveR
If you have got the fix that was released, and are still getting a bug.
It is something not related to this one. The fix has been released and
this particular bug should be gone. Any other issues should have their
own filing.
--
WARNING: at
2 problems -
1 - when you're filing the bug from a crash report you can't see the
name/title of the bug so you have to pick one from memory of what the
error message was. If the message wasn't the bug title I picked I'm
sorry but it sounded that way. In the future I won't bother.
2 - If a fix
@DaveR
I do not believe that Michael meant any offense, it's just that at times
things get in the wrong place, and need to get sorted out.
1: I've had the same issue. We could try sending Launchpad a
suggestion, or as a workaround, try copying and pasting into another
window to have the system
This is not my bug. Don't know why I got this email
Chauncellor wrote:
Excuse me, but what are we supposed to put in the but report? That it
gives us this error when we resume and we have system instability? That
would only get a dupe report.
We're getting an error, and our system is
Sorry, this is not the bug I reported and I don't know why I got this.
David Tombs wrote:
@Chauncellor: I didn't (and don't) mean any offense, sorry. You and
others have different symptoms from this report because _this_ report is
simply a warning and has no other symptoms. Believe me, I have
I did not intend to offend. In fact I would like all bugs to be fixed.
While attempting to give each unique issue a chance to not be buried in
another bug. Even if you report it and it some gets labeled a dupe, or
mislabeled. You can exert that it is not. I just believe it is
advantageous to make
Excuse me, but what are we supposed to put in the but report? That it
gives us this error when we resume and we have system instability? That
would only get a dupe report.
We're getting an error, and our system is faulting. This bug report is
saying that there's an error. We're just adding to it.
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released = Fix Committed
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released = Fix Committed
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi,
Sorry if this is a noob-question, but does Fix Committed mean, that we
can expect an update shortly? Or does this mean, the fix will be
included in Karmic+1?
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
Rackstar: Fix Commited means that shortly the fix will be released
through updates.
I don't know what the heck's going on, though.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this
This is great
Nice work everyone!
On Mon, Nov 2, 2009 at 11:59 AM, kdronan kerry.ro...@yahoo.com wrote:
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released = Fix Committed
--
WARNING: at
@Chauncellor: I didn't (and don't) mean any offense, sorry. You and
others have different symptoms from this report because _this_ report is
simply a warning and has no other symptoms. Believe me, I have the exact
same OOPS and no system instability. If you have system instability as
well, then
In other news, the fix is obviously not released, so I'm setting back to
In Progress.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of
None taken, and none meant, David.
However, what package should I file this against? What logs can I
provide? All I can say right now is that the computer slowly dies and
cries until it just hangs after resume, and the only hint I have is that
kernel error.
--
WARNING: at
@David, no problem. I have report it because I have similar symptoms
like other people here. After resume something was broken.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug
Same problem on an Acer 5737Z
It happens when I hibernate my notebook.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of Ubuntu
Bugs,
Could everyone please stop spamming this report?
If you have the same symptoms as described in the bug description (that
is, _just the warning_ and no other issues), then please do not reply
with me too because the bug is already being worked on. It's not
hardware-specific, so it's not necessary
I get that error every time I resume my computer - The difference for me
is that my computer really is unstable. Completely unusable.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this
For me as well, the screens are freezed after I resume from suspend to
ram. I use the radeonhd driver.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you
Happens on my desktop after every Suspend To RAM event. Haven't noticed
any stability problems, however - I can carry on as normal after the
issue occurs.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
HP TC1100 and ZV5300 (nvidia drivers enabled) both consistently getting this
error on suspend and boot.
In both cases (though more consistently on the TC1100) the system hard freezes
every so often.
This is AFTER two full clean karmic installs on both machines from
release ISOs and all
ничего вроде не произошло но неприятно
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
It sometimes takes up to 30 seconds to resume. Occasionally, when I open the
laptop lid to resume, the login screen quickly flashes, and then it goes to
sleep again; when I then press the power button, it successfully resumes.
I have the same problem on a MacBookPro5,5: Resuming takes always
To add to my experience, I'll say that system failure does not happen
every time, but I find my system more unreliable when I resume. I am
using the restriced NVidia 185 drivers and Compiz.
The horrible experience is just doing any task at all when the failures
start. I'll change windows, and it
My laptop is Lenovo R61 with Nvidia NVS 140 discrete graphics.
This failure does not happen every time too, but I can say that almost always
when I suspend laptop with any Openoffice application or Java based application
such as Eclipse 3.5 IDE running.
--
WARNING: at
I concur with Crazy Man Dan: I observe the same pattern of failure to
resume and brief password screen flash, relative to AC vs battery
situation.
MacBookPro 5,5 with ubuntu 9.10.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
I observed no changes in activity when my system reported this bug to
me. It simply appeared randomly when I wasn't really doing anything. I
have Karmic, and I installed it only a few days ago. i used the Wubi
downloader to install it on top of WIndows XP SP3. I have never used any
Linux OS
Same problem on Dell Studio 1555 with ATI graphics card.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Same as others, I can carry on as normal after Suspend. But it's not
waking after monitor is shut off which is probably related ... major
PITA as I have to reboot to access my system.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
On a fresh install of Ubuntu 9.10, this bug always occurs after a clean
boot (not just after waking up from standby).
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug
lxowle +1
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Same as for lxowle above. Kernel crash report after both a clean boot
(on a fresh install) and after resume. On at least two machines.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received
Same here, I also get the kernel crash report
/build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80() after a clean boot.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
i get it after resume, and sometimes fail to resume with kernel panic
no problem in 9.04
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member
i've had this problem since ubuntu 8.10 in whitch i used the non-free
ati drivers, and now i have 9.10 with free drivers and is the same [amd
cuad core, ati 58xx dual screen] some times in 8.10 i had some sata
problems and the system did not came up ever... force reboot, and the
times it did came
Got the same message after every str. Sometimes my usb keyboard is even
dead, but my (ps2)mouse not. I am using and Athlon64 on 690G ATI with
onboard graphics, open source drivers and 64bit karmic.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
I have the same problem since I've upgraded to 9.10; everything was fine
on 9.04. I think the problem might be related to the complex interaction
between suspend and auto screensaver. When I manually put my computer to
suspend, the screensaver is not on of course, but I when I try to
resume, it
i have this problem when i upgraded to 9.10 and it occurs quite randomly
but about once every single day. I have an hp pavillion a6432f pc
(desktop).
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
I get this kernel oops message consistently on a Dell XPS M1530 with Ubuntu
9.10 (upgraded from 9.04). BIOS is version A12, everything in Ubuntu is
up-to-date. Probably not related to this message, but I now need to remove the
power cable and reinsert it for the brightness to change to the AC
I too have been getting this on my laptop - Gateway MD7818u. I've only
noticed it since the upgrade to 9.10.
On my machine, it only occurs when the suspend / resume was activated
through the lid switch, and only if the AC cable was removed while the
machine was asleep. It does not occur if the
I get this when I close the lid on mt HP G60.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
Get this warning after resuming from hibernating.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I do not know what is the problem in the original report: 9 seconds are
not so long and there are no great delay for single task.
But I attach my dmesg because it is interesting noting:
[75692.370095] tifm_7xx1 :04:06.2: restoring config space at offset 0x1
(was 0x210, writing 0x216)
Also here: warning appears after resuming from suspend to disk
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
I'm seeing this consistently on resume. Hardware: ASUS EEE PC 900A with
Karmic UNR.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of
Here 900A with Ubuntu 9.10 standard, no UNR.
comment of Sam Ruby saves me testing of UNR, thanks.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a
I also get this pretty consistently on resume, with Dell XPS M1710 and
Ubuntu 9.10 standard.
It sometimes takes up to 30 seconds to resume. Occasionally, when I open the
laptop lid to resume, the login screen quickly flashes, and then it goes to
sleep again; when I then press the power button, it
Been getting this pretty consistently on 9.10 on a Biostar TA790GXB
motherboard (w/ AMD 790GX chipset) and a Phenom II x4 940 processor
whenever coming out of suspend.
As well, sometimes I lose sound when coming out of suspend due to this
error.
--
WARNING: at
I updated to Karmic this morning. Had also kernelproblems with the
latest betaversion. After the update no problems, the whole day. Due to
energysettings my system went to sleepmode. After resume I got the
kernelproblem - again.
--
WARNING: at
FYI:
http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface#Power_States
The ACPI specification contains numerous related components, for
hardware and software programming, as well as a unified standard for
device power interaction and bus configuration. As a document that
I have exactly same problem when suspending with Karmic.
Occurs very often. I think all the times.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a
Like virtually everyone posting here, I too have this problem. I have a
Macbook pro 3,1 with Karmic 9.10. When I wake the computer by opening
the lid, this occurs. If anyone with a macbook pro reads this, it seems
like I can keep the computer from going back to sleep by pressing the
power
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released = In Progress
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released = In Progress
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You
OK!
What about :
Changed in linux (Ubuntu):
status: Fix Released → In Progress
Does it will just have to upgrade linux with update??
Thank.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
@David, this issue happens even when I use proprietary nvidia driver. I
have tested both available versions (173 and 185).
I think that this problem is about USB subsystem that don't wakeup
properly and hangs system or combination of it. Proprietary nvidia
driver don't cause black screen. USB
@Jan, well, either way it's a different bug from this one, since this
one has no actually harmful side-effects. You should probably file a
different report.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
@David, is it really different bug? My apport fetched exactly the same
bug as is in subject.
My system has the same symptoms as other people here. In short: System
is unresponsive after resume. I tried to connect to system via SSH and
it works. Who of that people tried to login via ssh after
** Changed in: linux (Ubuntu)
Status: In Progress = Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete = In Progress
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You
I've noticed that my bug is now marked as a duplicate of this one,
however there is a not-so-subtle difference: my laptop *will not*
suspend or hibernate, it freezes before it has the chance to do so.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
My Gateway M-6309 Laptop suspends and hibernates (Great) ; but the notice of
kernel prob pops up and of course the
sound is dead. Must reboot to activate it again :o(
I have noticed this has been going on for sometime with others as well
Is pulse audio still the culprit?
I keep wanting to get
@Jan: No offense meant, but I do think you (and possibly others here)
have a different issue. If you'll notice the original bug description,
and Andy Whitcroft's responses, you'll see that they're only talking
about the warning itself (regarding resume timing) and not other
symptoms.
This warning
William, I use a USB AudioHub which must be re-enabled using the
PulseAudio applet, which is one of my startups. It defaults to internal
speakers after suspending.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
Jan, your issue sounds like a different one, Bug #128413.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
My lenovo T61P will resume with lid switch, get login screen then go back to
sleep. I have to then resume using power button. This is with 9.10 rc Nvidia
185 and virtualbox installed.
Trampas
On Wed, Oct 28, 2009 at 1:43 AM, Nifty violentse...@gmail.com wrote:
Got this error once after resume
I get this same error message after resume from suspend to ram with a MacBook
Pro 1,1.
No proprietary drives in use here.
As far as I can tell, the computer works fine within the same session (sound
and video), even the screensaver.
--
WARNING: at
My lenovo T61P will resume with lid switch, get login screen then go back to
sleep. I have to then resume using power button. This is with 9.10 rc Nvidia
185 and virtualbox installed.
I get the same problem with MacBookPro 5,5, also with nvidia and
proprietary driver 185 installed.
--
WARNING:
' My lenovo T61P will resume with lid switch, get login screen then go back to
sleep. I have to then resume using power button. This is with 9.10 rc Nvidia
185 and virtualbox installed.
I get the same problem with MacBookPro 5,5, also with nvidia and
proprietary driver 185 installed.'
I get the
I have the same problem.
I can't get form suspend to ramusing usb keyboard like in vista. I must
use power button than it beeps 4 times. Screen is withnout signal, USB
subsystem is dead. USB keyboard and mouse are without power. I can login
using ssh from another comuter.
lsusb before suspend:
Hi All,
Same symptoms for me on a Dell Studio XPS 16 running ATI non-free
drivers.
Another issue, trying to see if this related, is that on resume, both my
external display and laptop display are activated even though I'm using
only external display normally. I have to logout and log back in to
I have the same problem. I am using the last nvidia proprietary module
available to karmic and my $HOME is encrypted (I don't know if this is
related, but in previous Ubuntu releases, suspend did not work with my
$HOME encrypted).
--
WARNING: at
Same issue using latest nvidia proprietary driver on HP Mini 311 with
Atom 280/nVidia 9400M Ion LE. Seems to work fine afterwards.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
You received this
Got this error once after resume from suspend at SONY VAIO SZ21 (C2D 2.4GHz,
G45, GF9300GS)
External usb audio device (Logitech AudioHub) is attached
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/417842
@Astenorh -- indeed so. If the resume works correctly with this warning
it can pretty much be ignored. As you indicate upstream has just upped
this warning timeout as it is triggering more often than it should to be
useful:
commit 04bf7539c08d64184736cdc5e4ad617eda77eb0f
Author: Rafael J.
I looked up in the kernel source code, what it was related to! It simply
means the resume took too long. However according to the source the
timing is based on jiffies (whatever that is) which is not a a good
timebase. The developpers would prefer a hardward timer.
Also when looking at the latest
My macbook pro does take quite a long time to wake up. I don't see any
issue after it wakes up either. I agree its an annoyance, but I don't
believe it should be reported as a bug to the user. It is definitely
confusing to the newbie end user. Yes I am using 2 proprietary modules,
one for my
Anyone who sees an oops other than the resume took too long oops
should make sure to file a separate bug for that.
I don't think I've gotten the too slow oops for a while, so I think
this bug is fixed for me.
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
1 - 100 of 149 matches
Mail list logo
