Bug 1048585
| Summary: | [abrt] kernel BUG at drivers/cpufreq/cpufreq.c:79! | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | 黃健毅 <johnny.jy.ooi+fedorabugzilla> | ||||
| Component: | kernel | Assignee: | Stanislaw Gruszka <sgruszka> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | aplattner, gansalmon, itamar, johnny.jy.ooi+fedorabugzilla, jonathan, kernel-maint, madhu.chinakonda, michele | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/a7af1fcbe1751acb4b806581d557a05873687437 | ||||||
| Whiteboard: | abrt_hash:45e02bfa5abea94387dc2fb0df0ab159e64a8113 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-02-27 14:38:42 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
黃健毅
2014-01-05 14:25:30 UTC
Created attachment 845763 [details]
File: dmesg
Interesting. This was supposed to be fixed: http://lkml.indiana.edu/hypermail/linux/kernel/1309.2/02320.html via commit 26ca8694344af4c833d22590c5b77d6b9cff0722 Author: Viresh Kumar <viresh.kumar> Date: Fri Sep 20 22:37:31 2013 +0530 cpufreq: check cpufreq driver is valid and cpufreq isn't disabled in cpufreq_get() cpufreq_get() can be called from external drivers which might not be aware if cpufreq driver is registered or not. And so we should actually check if cpufreq driver is registered or not and also if cpufreq is active or disabled, at the beginning of cpufreq_get(). Otherwise call to lock_policy_rwsem_read() might hit BUG_ON(!policy). Reported-and-tested-by: Linus Walleij <linus.walleij> Signed-off-by: Viresh Kumar <viresh.kumar> Reviewed-by: Srivatsa S. Bhat <srivatsa.bhat.ibm.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki> Which hit 3.12 That bug was triggered by reading or writing some sysfs file, do you know what file was that ? Does it happen any-time you read/write this file ? (In reply to Stanislaw Gruszka from comment #3) > That bug was triggered by reading or writing some sysfs file, do you know > what file was that ? Does it happen any-time you read/write this file ? No, unfortunately not. This pops up after bringing my laptop out of hibernation, if that helps. As for what file, I have no idea which file it was trying to read at the time. Maybe it was as it was trying to hibernate that it tried to do something? *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. I can see a few fixes on 3.13 that could help with this bug. Could you test that kernel to see if problem happen again, i.e. run script like below for few hours: while true ; do echo "0" > /sys/class/rtc/rtc0/wakealarm echo "+300" > /sys/class/rtc/rtc0/wakealarm pm-hibernate done Unfortunately, I can't test this any longer, as I've migrated the affected laptop away from Fedora. I'll mark this bug as closed and if it reoccurs for someone else on a more recent kernel version, they can open a new bug. |