Bug 1093703

Summary: [abrt] WARNING: CPU: 0 PID: 4 at include/linux/kref.h:47 kobject_get+0x3e/0x50()
Product: [Fedora] Fedora Reporter: Guo Zhijian <gzjboy>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b1d9f0fbbefe53fef16242f2a826b690ab9d2777
Whiteboard: abrt_hash:57b3993f998f2234f291fd5b33d802e6e271319a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-23 14:49:13 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 Flags
File: dmesg none

Description Guo Zhijian 2014-05-02 12:03:17 UTC
Additional info:
reporter:       libreport-2.2.2
WARNING: CPU: 0 PID: 4 at include/linux/kref.h:47 kobject_get+0x3e/0x50()
Modules linked in: acpi_cpufreq(+) nfsd auth_rpcgss nfs_acl lockd sunrpc broadcom tg3 ptp pps_core
CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 3.14.2-200.fc20.x86_64 #1
Hardware name: LENOVO                           IdeaPad Y560    /KL3                             , BIOS 30CN62WW   07/23/2010
Workqueue: kacpi_notify acpi_os_execute_deferred
 0000000000000000 000000002eb048b3 ffff880139b71a60 ffffffff816eec92
 0000000000000000 ffff880139b71a98 ffffffff8108a1bd ffff8800b52ce000
 0000000000000202 ffff880139b71cd0 0000000000000003 ffff8800b776eb10
Call Trace:
 [<ffffffff816eec92>] dump_stack+0x45/0x56
 [<ffffffff8108a1bd>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff8108a2ea>] warn_slowpath_null+0x1a/0x20
 [<ffffffff8135613e>] kobject_get+0x3e/0x50
 [<ffffffff81585005>] cpufreq_cpu_get+0x75/0xc0
 [<ffffffff815852ed>] cpufreq_get_policy+0x1d/0x130
 [<ffffffff813fda85>] cpu_has_cpufreq.part.2+0x2d/0x4b
 [<ffffffff810bc935>] ? check_preempt_curr+0x75/0xa0
 [<ffffffff816f4bbe>] ? __down_common+0xaf/0xfe
 [<ffffffff813edcba>] ? acpi_ns_check_object_type+0x136/0x1d8
 [<ffffffff813ce6f8>] ? acpi_os_release_object+0xe/0x12
 [<ffffffff813f8809>] ? acpi_ut_delete_object_desc+0x49/0x4c
 [<ffffffff813f6eca>] ? acpi_ut_update_ref_count+0x25b/0x2b6
 [<ffffffff813ff038>] ? thermal_get_trend+0x3e/0xd5
 [<ffffffff810d6772>] ? up+0x32/0x50
 [<ffffffff813fdabc>] cpu_has_cpufreq+0x19/0x1b
 [<ffffffff813fdc40>] processor_get_cur_state+0x37/0x8a
 [<ffffffff81556af7>] thermal_zone_trip_update+0xf7/0x360
 [<ffffffff81556d76>] step_wise_throttle+0x16/0x90
 [<ffffffff81554b1f>] handle_thermal_trip+0x5f/0x180
 [<ffffffff81554cdd>] thermal_zone_device_update+0x9d/0x110
 [<ffffffff813ff0ed>] acpi_thermal_check+0x1e/0x20
 [<ffffffff813ffa41>] acpi_thermal_notify+0x3c/0xb6
 [<ffffffff813d1c59>] acpi_device_notify+0x19/0x1b
 [<ffffffff813e1f7c>] acpi_ev_notify_dispatch+0x44/0x5c
 [<ffffffff813cd8fe>] acpi_os_execute_deferred+0x14/0x20
 [<ffffffff810a6886>] process_one_work+0x176/0x430
 [<ffffffff810a74db>] worker_thread+0x11b/0x3a0
 [<ffffffff810a73c0>] ? rescuer_thread+0x370/0x370
 [<ffffffff810ae211>] kthread+0xe1/0x100
 [<ffffffff810ae130>] ? insert_kthread_work+0x40/0x40
 [<ffffffff816fef7c>] ret_from_fork+0x7c/0xb0
 [<ffffffff810ae130>] ? insert_kthread_work+0x40/0x40

Comment 1 Guo Zhijian 2014-05-02 12:03:24 UTC
Created attachment 891785 [details]
File: dmesg

Comment 2 Justin M. Forbes 2014-05-21 19:40:26 UTC
*********** 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.14.4-200.fc20.  Please test this kernel update (or newer) 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.

Comment 3 Justin M. Forbes 2014-06-23 14:49:13 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.