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.

Description of problem:

Red Hat customer came across a series of kernel panics with the following panic string: 


"kernel BUG at lib/idr.c:1157!"


on systems hosting docker with Mesosphere Kubernetes clustering. Systems are all in the same cluster and had active docker containers running. The panics are all due to kmemcg_id value being -1 (0xffffffff) everytime. Customer indicates after adding swap space, the issue no longer occurs. 


Version-Release number of selected component (if applicable):

3.10.0-693.21.1.el7.x86_64


How reproducible:

Unknown. Customer is unsure if it is reproducible


Steps to Reproduce:
1. see above
2.
3.

Actual results:

System panicked 


Expected results:

System stays up 

Additional info:

Vmcore analysis coming as internal

I like to see the vmcore file.
where is the vmcore?

Please note that an unsupported, test x86_64 kernel can be found here:

http://people.redhat.com/atomlin/bugzilla/1593417/

Patch(es) committed on kernel-3.10.0-1048.el7

*** Bug 1700374 has been marked as a duplicate of this bug. ***

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-2019:2029