Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 161986 - RHEL3 U5 panic in kmem_cache_grow
RHEL3 U5 panic in kmem_cache_grow
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Larry Woodman
Brian Brock
Depends On:
Blocks: 156320
  Show dependency treegraph
Reported: 2005-06-28 16:45 EDT by Issue Tracker
Modified: 2007-11-30 17:07 EST (History)
3 users (show)

See Also:
Fixed In Version: RHSA-2005-663
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-28 11:27:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:663 qe-ready SHIPPED_LIVE Important: Updated kernel packages available for Red Hat Enterprise Linux 3 Update 6 2005-09-28 00:00:00 EDT

  None (edit)
Description Issue Tracker 2005-06-28 16:45:29 EDT
Escalated to Bugzilla from IssueTracker
Comment 1 Larry Woodman 2005-06-28 16:48:54 EDT
I gave Willie at amazon a kernel with the fix for this problem.  I am witing to
hear back from him on testing results.

Larry Woodman
Comment 2 Larry Woodman 2005-07-07 14:27:46 EDT
This is the clear_pte() corruption bug that was still in RHEL3-U5.

Larry Woodman

*** This bug has been marked as a duplicate of 156023 ***
Comment 5 Ernie Petrides 2005-07-13 19:31:17 EDT
Reopening and adding back to proposed list.  This is not a dup of bug 156023.
Comment 6 Ernie Petrides 2005-07-13 19:32:13 EDT
A fix for this problem has just been committed to the RHEL3 U6
patch pool this evening (in kernel version 2.4.21-32.11.EL).
Comment 12 Red Hat Bugzilla 2005-09-28 11:27:02 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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