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.
Created attachment 412633[details]
dmesg
Description of problem:
On a small Atom+ION based x86 computer, a weird behavior was observed. Kernel panicked after resume from suspend; after that a screen flickered and the machine resumed correctly; the running gnome session was usable and no malfunction was seen.
Version-Release number of selected component (if applicable):
kernel-2.6.33-1.fc13.i686
How reproducible:
This was the only occassion of suspending/resuming that machine, so I'm not yet sure about reproducability.
Comment 2RHEL Program Management
2010-05-09 13:57:53 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.
(In reply to comment #3)
> Maybe a dup of bug #586967?
[<c0a49479>] ? nmi_cpu_busy+0x0/0x17
[<c080203e>] ? end_local_APIC_setup+0xd3/0xea
[<c08018ca>] ? start_secondary+0x102/0x24e
Yup.
To workaround this issue you can boot with nmi_watchdog=0.
P.
*** This bug has been marked as a duplicate of bug 586967 ***
Created attachment 412633 [details] dmesg Description of problem: On a small Atom+ION based x86 computer, a weird behavior was observed. Kernel panicked after resume from suspend; after that a screen flickered and the machine resumed correctly; the running gnome session was usable and no malfunction was seen. Version-Release number of selected component (if applicable): kernel-2.6.33-1.fc13.i686 How reproducible: This was the only occassion of suspending/resuming that machine, so I'm not yet sure about reproducability.