RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 605229 - [abrt] kernel: WARNING: at arch/x86/kernel/cpu/perf_event_amd.c:326 amd_pmu_cpu_starting+0x118/0x150() (Not tainted)
Summary: [abrt] kernel: WARNING: at arch/x86/kernel/cpu/perf_event_amd.c:326 amd_pmu_c...
Keywords:
Status: CLOSED DUPLICATE of bug 604880
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard: abrt_hash:877946657
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-17 13:23 UTC by Siddharth Nagar
Modified: 2010-06-17 17:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-17 17:11:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
File: backtrace (635 bytes, text/plain)
2010-06-17 13:23 UTC, Siddharth Nagar
no flags Details

Description Siddharth Nagar 2010-06-17 13:23:26 UTC
abrt version: 1.1.4
architecture: x86_64
cmdline: not_applicable
component: kernel
executable: kernel
kernel: 2.6.32-30.el6.x86_64
package: kernel
reason: WARNING: at arch/x86/kernel/cpu/perf_event_amd.c:326 amd_pmu_cpu_starting+0x118/0x150() (Not tainted)
release: Red Hat Enterprise Linux Server release 6.0 Beta (Santiago)
How to reproduce: System was idle at the time of this crash

backtrace
-----
WARNING: at arch/x86/kernel/cpu/perf_event_amd.c:326 amd_pmu_cpu_starting+0x118/0x150() (Not tainted)
Hardware name: AZ217AV-ABA e9300z
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.32-30.el6.x86_64 #1
Call Trace:
[<ffffffff8106a483>] warn_slowpath_common+0x83/0xc0
[<ffffffff8106a4d4>] warn_slowpath_null+0x14/0x20
[<ffffffff81024e58>] amd_pmu_cpu_starting+0x118/0x150
[<ffffffff814cadf9>] x86_pmu_notifier+0x5c/0x6a
[<ffffffff814d9345>] notifier_call_chain+0x55/0x80
[<ffffffff810950c6>] raw_notifier_call_chain+0x16/0x20
[<ffffffff814cebe0>] notify_cpu_starting+0x36/0x38
[<ffffffff814cd129>] start_secondary+0x11a/0x23f

Comment 1 Siddharth Nagar 2010-06-17 13:23:28 UTC
Created attachment 424813 [details]
File: backtrace

Comment 3 RHEL Program Management 2010-06-17 13:33:45 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 4 Eric Sandeen 2010-06-17 17:11:55 UTC

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


Note You need to log in before you can comment on or make changes to this bug.