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 674427 - BUG: soft lockup
Summary: BUG: soft lockup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-01 20:44 UTC by daryl herzmann
Modified: 2013-02-26 17:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-26 17:07:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
syslog output (5.18 KB, text/plain)
2011-02-01 20:44 UTC, daryl herzmann
no flags Details
2.6.32-122.el6.x86_64 oops (3.36 KB, text/plain)
2011-04-11 19:58 UTC, daryl herzmann
no flags Details

Description daryl herzmann 2011-02-01 20:44:57 UTC
Created attachment 476478 [details]
syslog output

I have a Dell PowerEdge T410 that ran RHEL5 64bit without any issues.  I installed RHEL6 64bit on it and have had nothing but system lock ups requiring hard resets.  I have 15 other T410s running without issue, so perhaps this is a pure hardware problem, but this machine does run a different workload than the others.  Regardless, I'm attaching what came to syslog and would be happy to do anything else you guys may ask for.  Thanks!

Comment 2 RHEL Program Management 2011-04-04 02:49:17 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 3 daryl herzmann 2011-04-11 19:58:22 UTC
Created attachment 491338 [details]
2.6.32-122.el6.x86_64 oops

Captured another oops and found a reproducing situation :(  Appears to be something with NFS access.

Comment 4 daryl herzmann 2011-05-03 15:50:18 UTC
Is this a dup of #672305 ?

Comment 5 daryl herzmann 2011-09-23 17:31:00 UTC
Issue with R410s, perhaps related

https://bugzilla.redhat.com/show_bug.cgi?id=710265

Comment 6 RHEL Program Management 2011-10-07 15:21:44 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 7 daryl herzmann 2012-07-27 15:43:01 UTC
I am no longer reproducing this issue, so you might as well close as INVALID or something.


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