| Summary: | Unsighty "comm: pm-suspend Not tainted 3.3.0-4.fc16.x86_64" message | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hin-Tak Leung <htl10> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-10-26 13:25:48 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Hin-Tak Leung
2012-03-29 22:06:53 UTC
Are you still seeing this with the 3.4 or 3.5 kernel updates? # Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient). Haven't seen it for a while, and don't have the problem for as far syslog goes (23rd sep). # last |grep reboot reboot system boot 3.6.2-4.fc17.x86 Thu Oct 25 19:42 - 14:23 (18:41) reboot system boot 3.6.1-1.fc17.x86 Thu Oct 18 02:58 - 18:41 (7+15:42) reboot system boot 3.6.1-1.fc17.x86 Mon Oct 15 14:04 - 01:58 (2+11:54) reboot system boot 3.6.1-1.fc17.x86 Sat Oct 13 04:51 - 13:03 (2+08:12) reboot system boot 3.5.6-1.fc17.x86 Thu Oct 11 03:47 - 03:51 (2+00:03) reboot system boot 3.5.5-2.fc17.x86 Sat Oct 6 16:51 - 02:46 (4+09:54) reboot system boot 3.5.5-2.fc17.x86 Sat Oct 6 06:58 - 02:46 (4+19:48) reboot system boot 3.5.5-2.fc17.x86 Sat Oct 6 05:29 - 05:57 (00:28) reboot system boot 3.5.5-2.fc17.x86 Sat Oct 6 02:35 - 02:40 (00:04) reboot system boot 3.5.5-2.fc17.x86 Fri Oct 5 20:58 - 21:04 (00:06) reboot system boot 3.5.5-2.fc17.x86 Fri Oct 5 14:58 - 20:56 (05:58) reboot system boot 3.5.4-2.fc17.x86 Tue Oct 2 11:17 - 14:57 (3+03:39) reboot system boot 3.5.4-1.fc17.x86 Thu Sep 27 08:51 - 11:17 (5+02:25) reboot system boot 3.5.4-1.fc17.x86 Tue Sep 25 08:10 - 08:51 (2+00:40) reboot system boot 3.5.4-1.fc17.x86 Tue Sep 25 02:43 - 08:51 (2+06:07) reboot system boot 3.5.4-1.fc17.x86 Tue Sep 25 02:39 - 02:42 (00:03) reboot system boot 3.5.4-1.fc17.x86 Sun Sep 23 01:29 - 02:38 (2+01:09) |