Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 720764

Summary: [abrt] kernel: BUG: soft lockup - CPU#0 stuck for 67s! [java:20189]
Product: Red Hat Enterprise Linux 6 Reporter: Red Hat Case Diagnostics <case-diagnostics>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: jwest
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1078688824
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-05 22:24:04 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: backtrace none

Description Red Hat Case Diagnostics 2011-07-12 17:15:47 UTC
This description generated by Andreas from an ABRT report
architecture: x86_64
cmdline: not_applicable
component: kernel
executable: kernel
kernel: 2.6.32-131.4.1.el6.x86_64
package: kernel
reason: BUG: soft lockup - CPU#0 stuck for 67s! [java:20189]
release: Red Hat Enterprise Linux Server release 6.1 (Santiago)
reproduce: 1.unknown
2.
3.

time: 1310490414
uid: 0
backtrace: BUG: soft lockup - CPU#0 stuck for 67s! [java:20189]
Modules linked in: fuse nfsd lockd nfs_acl auth_rpcgss exportfs autofs4 sunrpc ipv6 dm_mirror dm_region_hash dm_log uinput microcode virtio_balloon snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore snd_page_alloc virtio_net i2c_piix4 i2c_core ext4 mbcache jbd2 virtio_blk virtio_pci virtio_ring virtio pata_acpi ata_generic ata_piix dm_mod [last unloaded: speedstep_lib]
CPU 0:
Modules linked in: fuse nfsd lockd nfs_acl auth_rpcgss exportfs autofs4 sunrpc ipv6 dm_mirror dm_region_hash dm_log uinput microcode virtio_balloon snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore snd_page_alloc virtio_net i2c_piix4 i2c_core ext4 mbcache jbd2 virtio_blk virtio_pci virtio_ring virtio pata_acpi ata_generic ata_piix dm_mod [last unloaded: speedstep_lib]
Pid: 20189, comm: java Not tainted 2.6.32-131.4.1.el6.x86_64 #1 KVM
RIP: 0010:[<ffffffff8104671a>]  [<ffffffff8104671a>] flush_tlb_others_ipi+0x11a/0x130
RSP: 0018:ffff88027782fd68  EFLAGS: 00000246
RAX: 0000000000000000 RBX: ffff88027782fda8 RCX: 0000000000000004
RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff81d51418
RBP: ffffffff8100bc8e R08: 0000000000000000 R09: 0000000000000008
R10: 0000000000000000 R11: 0000000000000206 R12: ffff88027782fda8
R13: ffffffff8100bc8e R14: ffff880270647ed0 R15: ffff8803cbb2b748
FS:  00007f1ea53d6700(0000) GS:ffff880028200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007f22ffb9c000 CR3: 00000002d7c0a000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
[<ffffffff81046728>] ? flush_tlb_others_ipi+0x128/0x130
[<ffffffff810467a6>] ? native_flush_tlb_others+0x76/0x90
[<ffffffff8104697c>] ? flush_tlb_mm+0x5c/0xa0
[<ffffffff8113e809>] ? mprotect_fixup+0x619/0x760
[<ffffffff8113ead5>] ? sys_mprotect+0x185/0x250
[<ffffffff8100b172>] ? system_call_fastpath+0x16/0x1b

Comment 2 Red Hat Case Diagnostics 2011-07-12 17:16:26 UTC
Created attachment 512478 [details]
File: backtrace

Comment 5 Jeremy West 2011-10-05 22:24:04 UTC
Closing this bug, since the associated customer case has closed.  Please feel free to re-open this if new information becomes available.