Bug 576055
| Summary: | Kernel trap on stopping cpuspeed service | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Pat Gunn <pgunn> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 13 | CC: | anton, dougsland, gansalmon, itamar, jonathan, kernel-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-03-30 16:32:31 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: |
|
||||||
btw - I've not seen this problem when I was running Fedora 11 on this laptop before. It's happened consistently since migration to Fedora 13Alpha. Created attachment 402741 [details]
serial console log
It happens to my system, too. Here is the complete serial console log from boot to shutdown (via clicking icon on Gnome desktop login screen, without ever logging in.)
*** This bug has been marked as a duplicate of bug 572868 *** |
Description of problem:Every time I shut down my system, when the "cpuspeed" service is stopped it spits an ugly kernel trap message onto the screen before shutdown finishes. The shutdown completes ok though. Version-Release number of selected component (if applicable): 2.6.33.1 How reproducible: 100% Steps to Reproduce: 1. Stop the cpuspeed service (yields problem when done manually too) Actual results: Kernel trap message during shutdown Expected results:No such message Additional info: [ INFO: possible recursive locking detected ] 2.6.33-1.fc13.x86_64 #1 --------------------------------------------- cpuspeed/2496 is trying to acquire lock: (s_active){++++.+}, at: [<ffffffff81176f02>] sysfs_addrm_finish+0x36/0x55 but task is already holding lock: (s_active){++++.+}, at: [<ffffffff811770bd>] sysfs_get_active_two+0x24/0x48 other info that might help us debug this: 4 locks held by cpuspeed/2496: #0: (&buffer->mutex){+.+.+.}, at: [<ffffffff81175b9f>] sysfs_write_file+0x3c/0x144 #1: (s_active){++++.+}, at: [<ffffffff811770bd>] sysfs_get_active_two+0x24/0x48 #2: (s_active){++++.+}, at: [<ffffffff811770ca>] sysfs_get_active_two+0x31/0x48 #3: (dbs_mutex){+.+.+.}, at: [<ffffffffa038bda2>] cpufreq_governor_dbs+0x2a0/0x352 [cpufreq_ondemand] stack backtrace: Pid: 2496, comm: cpuspeed Not tainted 2.6.33-1.fc13.x86_64 #1 Call Trace: [<ffffffff8107e94f>] __lock_acquire+0xcb5/0xd2c [<ffffffff8107cf48>] ? mark_held_locks+0x52/0x70 [<ffffffff8107d329>] ? debug_check_no_locks_freed+0x12e/0x145 [<ffffffff8107d1c8>] ? trace_hardirqs_on_caller+0x111/0x135 [<ffffffff8107eaa2>] lock_acquire+0xdc/0x102 [<ffffffff81176f02>] ? sysfs_addrm_finish+0x36/0x55 [<ffffffff8107c300>] ? lockdep_init_map+0x9e/0x113 [<ffffffff8117690f>] sysfs_deactivate+0x9a/0x103 [<ffffffff81176f02>] ? sysfs_addrm_finish+0x36/0x55 [<ffffffff8107120a>] ? sched_clock_cpu+0xc3/0xce [<ffffffff81476e44>] ? __mutex_unlock_slowpath+0x120/0x132 [<ffffffff81176f02>] sysfs_addrm_finish+0x36/0x55 [<ffffffff81175254>] sysfs_hash_and_remove+0x53/0x6a [<ffffffff811782f9>] sysfs_remove_group+0x91/0xca [<ffffffffa038bdb6>] cpufreq_governor_dbs+0x2b4/0x352 [cpufreq_ondemand] [<ffffffff8107d1f9>] ? trace_hardirqs_on+0xd/0xf [<ffffffff813a289b>] __cpufreq_governor+0x9b/0xde [<ffffffff813a36e7>] __cpufreq_set_policy+0x1ce/0x275 [<ffffffff813a3c0b>] store_scaling_governor+0x1a7/0x1fb [<ffffffff813a3f14>] ? handle_update+0x0/0x39 [<ffffffff8147775f>] ? down_write+0x7a/0x81 [<ffffffff813a34f4>] store+0x61/0x86 [<ffffffff81175c6b>] sysfs_write_file+0x108/0x144 [<ffffffff8111ed9d>] vfs_write+0xae/0x10b [<ffffffff8107d1c8>] ? trace_hardirqs_on_caller+0x111/0x135 [<ffffffff8111eeba>] sys_write+0x4a/0x6e [<ffffffff81009c72>] system_call_fastpath+0x16/0x1b