This server is running the latest kernel hotfix and it crashed at 21:03:17 CST on 4 Nov 2004. ---------- Action by: jneedle Wow, Roland figured this out. We got lucky. Just happens to be something he recently found and fixed in 2.6, but has never before been seen in RHEL3. See http://lkml.org/lkml/2004/10/23/26. We'll need to backport that to RHEL3 and run it by rhkernel-list, then figure out the right delivery vehicle. If this is the first time they've run into this, would it be safe to take some time to review and figure this out? Again it's an issue without a reproducer, so it's tricky to declare fixed with certainty. As always, it would be great to understand how they ran into this so we could proactively test an environment similar to theirs.
Peter, I would have assigned this to Ingo if you hadn't already assigned it to yourself. For now, I've just added him to the cc: list (and added the Issue Tracker id).
We need this for the hot fix. If 139713 takes more time then expected we may have to reassign, alright for now.
Created attachment 109996 [details] backport of 2.6 patch fixing this This patch applies to both RHEL-3 and RHEL-4 branches as-is.
*** Bug 145331 has been marked as a duplicate of this bug. ***
The RHEL-4 bugzilla for this problem is bug 145590.
A fix for this problem has just been committed to the RHEL3 U5 patch pool this evening (in kernel version 2.4.21-27.10.EL).
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. http://rhn.redhat.com/errata/RHSA-2005-294.html