| Summary: | sys-power/pm-utils-1.2.5 failed to wake up the machine after suspending | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | peng shao <shallpion> |
| Component: | [OLD] Core system | Assignee: | Freedesktop bugs <freedesktop-bugs> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | major | CC: | anton.bugs, tetromino |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
the log part from /var/log/messages
pm-suspend.log |
||
|
Description
peng shao
2009-10-05 06:36:05 UTC
Created attachment 206059 [details]
the log part from /var/log/messages
I cut this typical part from /var/log/messages
Created attachment 206061 [details]
pm-suspend.log
it seems that at least the suspending is normal
Please either set the assign field correctly or let bug wranglers do it. Thanks (In reply to comment #3) > Please either set the assign field correctly or let bug wranglers do it. > > Thanks > I apologize for an inconvenience but I am sorry that I did not understand what you suggested me to do :( Could you please tell me where I made the mistakes? Thank you very much. The reason this bug was assigned improperly is because it was filed under component "GNOME", and I do not believe that the filer has appropriate privileges to change the assignee to anything other than the default of gnome@g.o (most components default to bug-wranglers@g.o, but Games, GNOME, Hardened, Java, KDE, and Printing default to their respective herds, which can result in incorrect assignments). Long story short, I don't think the bug filer actually did anything wrong, except for placing the bug under the wrong component, which is not completely unheard of. (In reply to comment #5) > The reason this bug was assigned improperly is because it was filed under > component "GNOME", and I do not believe that the filer has appropriate > privileges to change the assignee to anything other than the default of > gnome@g.o (most components default to bug-wranglers@g.o, but Games, GNOME, > Hardened, Java, KDE, and Printing default to their respective herds, which can > result in incorrect assignments). > > Long story short, I don't think the bug filer actually did anything wrong, > except for placing the bug under the wrong component, which is not completely > unheard of. > Thank you very much for pointing out my mistake. My wild guess is this might be a bug about the kernel, so I changed it into Core System. I wish I did not make mistake again. I apologize for my mistake again. By the way, I do not know if I met the same bug as the one mentioned below: http://bugzilla.kernel.org/show_bug.cgi?id=13149 Thank you. I managed to fix it using workaround described in https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/417599 Basically, there are 2 bugs in have_kms function. First, it detects KMS falsely, second there is a typo fixed by upstream (http://cgit.freedesktop.org/pm-utils/commit/?id=e5cdb5bb6a573a36b0c872c889c8b8f25009cc45). So, I put "return 1" in front of that function and resume has started to work. ps. echo "mem" > /sys/power/state worked fine. Freedesktop, this bug might lead to filesystem corruption, please consider fixing it rather urgent. fixed in 1.2.6.1, thanks for reporting. (In reply to comment #8) > fixed in 1.2.6.1, thanks for reporting. > It would be nice if you could bump this version to the portage then. Thanks.. |
