Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 635504

Summary: BUG: warning at drivers/base/core.c:101/device_release()
Product: Red Hat Enterprise Linux 5 Reporter: Zhang Kexin <kzhang>
Component: kernelAssignee: John Feeney <jfeeney>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: low Docs Contact:
Priority: low    
Version: 5.6CC: peterm
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: 2010-09-20 15:50:45 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:

Description Zhang Kexin 2010-09-20 02:46:17 UTC 
Description of problem:
dmesg error when install rhel5.5 x86_64 on dell-per810-01.lab.bos.redhat.com

Version-Release number of selected component (if applicable):
2.6.18-194.el5

How reproducible:
every time.

Steps to Reproduce:
1. install rhel5.5 x86_64
2.
3.
  
Actual results:
There are following messages in dmesg:

BUG: warning at drivers/base/core.c:101/device_release() (Not tainted)

Call Trace:
 [<ffffffff80342131>] kobject_cleanup+0x53/0x7e
 [<ffffffff8034215c>] kobject_release+0x0/0x9
 [<ffffffff80236bca>] kref_put+0x6f/0x7a
 [<ffffffff882db0f6>] :power_meter:acpi_power_meter_add+0x158/0x16e
 [<ffffffff8038b91f>] acpi_bus_driver_init+0x30/0x57
 [<ffffffff8038cb3d>] acpi_bus_register_driver+0x95/0xd4
 [<ffffffff8820e032>] :power_meter:acpi_power_meter_init+0x25/0x34
 [<ffffffff802a28e8>] sys_init_module+0xaf/0x1f2
 [<ffffffff80260106>] system_call+0x86/0x8b
 [<ffffffff80260080>] system_call+0x0/0x8b

Expected results:


Additional info:
Comment 1 Matthew Garrett 2010-09-20 15:50:45 UTC 

*** This bug has been marked as a duplicate of bug 576246 ***