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.

Created attachment 431045 [details]
panic screenshot

Description of problem:
kernel panic during suspend to disk.

Version-Release number of selected component (if applicable):
kernel-debug-2.6.32-44.el6
RHEL6.0-20100707.4

How reproducible:
Once.

Moving out to RHEL 6.1, if QE can reproduce the problem for us then we can reopen the issue.

I've looked at the code forwards, backward, and upside down, looking for a situation where the cpu_hotplug.lock is acquired after a cpu's cpu_policy_rwsem.

I can't find one :/.  This could be a symptom of the strange race described in the description of cpu_hotplug_begin() ... but it doesn't feel like that is the cause.

This has happened one time, and doesn't appear to be easily reproducible so I'm moving this to 6.1 for now.

P.

Has this happened again?  I cannot find any bugs on suspend/resume on the x200 in bugzilla ...

P.

I had Cai's x200 here for a few days and used it diagnose another failure with suspend/resume.

I did not see the type of issue being reported in this BZ.

P.