| Summary: | nmi_watchdog settings is not preserved during suspend/resume | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Travis Gummels <tgummels> |
| Component: | kernel | Assignee: | Don Zickus <dzickus> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | CC: | arozansk, ddumas, woodard, ypu |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-17 13:34: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
Travis Gummels
2011-03-02 03:05:09 UTC
I am unable to reproduce it. Could you recheck that the nmi_watchdog is still disabled after the resume (by cat /proc/sys/kernel/nmi_watchdog)? Was the powertop running during the suspend or did you restart it after resume? OK here it is: [root@snog Desktop]# cat /proc/sys/kernel/nmi_watchdog 1 [root@snog Desktop]# echo 0 > /proc/sys/kernel/nmi_watchdog [root@snog Desktop]# cat /proc/sys/kernel/nmi_watchdog 0 <suspend, then resume> [root@snog Desktop]# cat /proc/sys/kernel/nmi_watchdog 1 [root@snog Desktop]# Thanks, so it seems the PowerTOP is right, because the nmi_watchdog is really enabled on your machine after resume. However I am still unable to reproduce this on my test machine (T400). Maybe it is kernel or something else who is re-enabling the nmi_watchdog on your machine, thus it is not the PowerTOP fault. I never thought it was powertop. I believe that suspend/resume however that works needs to save the state of the nmi_watchdog during the suspend and restore it after resume. For some reason that is not working right ATM. Are you disabling nmi_watchdog using the like I did in the original example command line in rc.local or in the kernel command line? > I never thought it was powertop. > It should be reassigned to kernel or elsewhere. I can not handle this in PowerTOP. > I believe that suspend/resume however that works needs to save the state of the > nmi_watchdog during the suspend and restore it after resume. For some reason > that is not working right ATM. > I think it should be handled by kernel. It is also possible to create the pm-utils suspend hook, but I do not like such user-space hacks. > Are you disabling nmi_watchdog using the like I did in the original example > command line in rc.local or in the kernel command line? > I used same steps as in comment 2 but I was not able to reproduce this on my HW (RHEL-6.1 nightly). Reproduced on T500, steps to reproduce: # cat /proc/sys/kernel/nmi_watchdog 1 # echo 0 > /proc/sys/kernel/nmi_watchdog # cat /proc/sys/kernel/nmi_watchdog 0 # echo mem > /sys/power/state ... [resume] # cat /proc/sys/kernel/nmi_watchdog 1 Tested in runlevels 1, 3, 5. Reassigning to kernel for further investigation. Find the same problem in RHEL 6.1 guest in KVM test. The guest kernel always report "NMI watchdog disabled for cpu0: unable to create perf event: -2" even when NI watchdog is disable in RHEL 6.1 guest in AMD host, but not find this problem in INTEL host. I think the patches I submitted for bz684649 will fix this. I need to double check. I am brewing building those patches, it should be done in about an hour if someone wants to quickly test to see if it resolves their issue. http://brewweb.devel.redhat.com/brew/taskinfo?taskID=3187569 Cheers, Don Can someone try the -128.el6 kernel or later and see if the problem still exists? Cheers, Don Hi, Can people test RHEL-6.1 to see if this is fixed. I believe it is. Cheers, Don Thanks Ben. Closing this out as fix already. Cheers, Don |