DetailsA few bugs, including one in ext3 that could cause a kernel panic In the 2.4.18-3 kernel, a timing change exposed a previously-unseen SolutionBefore applying this update, make sure all previously released errata
relevant to your system have been applied. The procedure for upgrading the kernel manually is documented at: http://www.redhat.com/support/docs/howto/kernel-upgrade/ Please read the directions for your architecture carefully before proceeding with the kernel upgrade. Please note that this update is also available via Red Hat Network. Many people find this to be an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. Note that you need to select the kernel explicitly on default configurations of up2date. If you experienced the filesystem panic, you are recommended to check filesystem consistency. This bug will show up as one of "kernel BUG at journal.c:406" or "kernel BUG at commit.c:535" (The check is done in two places in the source code, and either of them might show up.) To force the filesystem check, log in as root, run touch /forcefsck and then reboot the system. It will check all the filesystems after rebooting. This needs to be done only once after you experience the panic. Updated packages
Bugs fixed (see bugzilla for more information)64107 - Kernel Panic when running sendmail test Keywords
ext3, filesystem, kernel, panic, SMP
These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from: https://www.redhat.com/security/team/key/#package The Red Hat security contact is secalert@redhat.com. More contact details at http://www.redhat.com/security/team/contact/ |
||||||||||||||||||||||||||||||||||||||||||||||||||||