Description of problem:
Kernel update to version 2.6.9-67.0.20.EL. Kernel panics twice and the
system had to be rebooted each time. Have reverted back to 2.6.9-67.0.15.EL
Kernel updates on Jun 27 17:00. First kernel panic on June 29 2:12, second
kernel panic on June 30 14:59
Have attached relevant log entries.
Version-Release number of selected component (if applicable):
Kernel update to version 2.6.9-67.0.20.EL
Steps to Reproduce:
1. Just running the updated kernel
Kernel Panic Twice
Created attachment 310639 [details]
extracted kernel log entries in /var/log/message
Created attachment 311326 [details]
kernel panic log
Same problem experienced 4 days after installing 2.6.9-67.0.20.ELsmp kernel on
a system that previously had no stability issues.
seeing a similar issue on two of my 4.6 boxes running MailScanner as MX filters.
Same here. It panics during heavy IO via MySQL.
The problem is in next_thread function, I'm assigning this issue to Vitaly.
This is a race between release_task() and sys_times()->next_thread()
Created attachment 311625 [details]
lock sighand->siglock in release_task()
This patch fixes the problem
Created attachment 311626 [details]
Created attachment 311684 [details]
simpler version of patch
Unhash process with locked sighahd->siglock.
We had two of these this weekend. Previously stable systems were upgraded to
the latest kernel and two locked last night, not even making 24 hours. In my
opinion this bug should be urgent.
*** Bug 455274 has been marked as a duplicate of this bug. ***
This is to backout the patch in 4.8.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Committed in 78.1.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
For the time being orignal two sys_times patches ( bz 435280) have been
reverted back to solve the issue.
Following are the reverted commits.
We've just had an RHEL 4.7 box crash with this one.
Is there any timescale for the fix to be released through the normal channels?
*** Bug 456997 has been marked as a duplicate of this bug. ***
*** Bug 456993 has been marked as a duplicate of this bug. ***
Updating PM score.
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 therefore 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.