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.
DescriptionVratislav Bendel
2018-03-26 10:32:26 UTC
Description of problem:
Customer's java application can cause panic, apparently after the CPU performs invpcid flush.
Customer bisected this to the following commit:
commit c6f35cdfc82ca083c041a24fdf33e1b84f80912d
[x86] mm/kaiser: use invpcid to flush the two kaiser PCID AISD
From what I understand, then apparently the following might be the problem (however I don't currently understand why):
static inline void __native_flush_tlb(void)
{
- __load_cr3(native_read_cr3());
+ if (!static_cpu_has(X86_FEATURE_INVPCID)) {
+ __load_cr3(native_read_cr3());
+ return;
+ }
+ /*
+ * Note, this works with CR4.PCIDE=0 or 1.
+ */
+ invpcid_flush_all_nonglobals();
}
Other modifications done by the commit are either under #CONFIG_KAISER or #CONFIG_X86_64, which are not included into .i686 build.
Additionally, disabling invpcid on boot-cmd-line *seems to resolve* the problem. (using 'noinvpcid' boot parameter)
Version-Release number of selected component (if applicable):
kernel-2.6.32-696.18.7.el6.i686
How reproducible:
Always
Steps to Reproduce:
TBA
Actual results:
0xf error_code page_fault panic
Expected results:
no panic
Additional info:
Usage of 'noinvpcid' boot-param in -696.18.7 version is exclusive to #CONFIG_X86_64, however on upstream it's general.
Customer has tested the workaround ('noinvpcid') on -696.18.7.test kernel, simply modified to enable it on .i686.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2018:1854
Description of problem: Customer's java application can cause panic, apparently after the CPU performs invpcid flush. Customer bisected this to the following commit: commit c6f35cdfc82ca083c041a24fdf33e1b84f80912d [x86] mm/kaiser: use invpcid to flush the two kaiser PCID AISD From what I understand, then apparently the following might be the problem (however I don't currently understand why): static inline void __native_flush_tlb(void) { - __load_cr3(native_read_cr3()); + if (!static_cpu_has(X86_FEATURE_INVPCID)) { + __load_cr3(native_read_cr3()); + return; + } + /* + * Note, this works with CR4.PCIDE=0 or 1. + */ + invpcid_flush_all_nonglobals(); } Other modifications done by the commit are either under #CONFIG_KAISER or #CONFIG_X86_64, which are not included into .i686 build. Additionally, disabling invpcid on boot-cmd-line *seems to resolve* the problem. (using 'noinvpcid' boot parameter) Version-Release number of selected component (if applicable): kernel-2.6.32-696.18.7.el6.i686 How reproducible: Always Steps to Reproduce: TBA Actual results: 0xf error_code page_fault panic Expected results: no panic Additional info: Usage of 'noinvpcid' boot-param in -696.18.7 version is exclusive to #CONFIG_X86_64, however on upstream it's general. Customer has tested the workaround ('noinvpcid') on -696.18.7.test kernel, simply modified to enable it on .i686.