<?xml version="1.0" encoding="UTF-8"?>
<!--PATCHINFO id="acea7aff476735da404d1709e9b002b0"!-->
<patch
    xmlns="http://novell.com/package/metadata/suse/patch"
    xmlns:yum="http://linux.duke.edu/metadata/common"
    xmlns:rpm="http://linux.duke.edu/metadata/rpm"
    xmlns:suse="http://novell.com/package/metadata/suse/common"
    patchid="sledp2-kdump-5365"
    timestamp="1217343606"
    engine="1.0">
  <yum:name>sledp2-kdump</yum:name>
  <summary lang="en">Recommended update for kdump</summary>
  <summary lang="de">Recommended update for kdump</summary>
  <description lang="en">This update fixes following problems in kdump configuration:

 1. When taking a dump on machines that were booted with
the &quot;mem&quot;  parameter, the dump is now only as large as the
specified memory, not  as large as the full memory. That
affects only the i386 and the x86-64 architectures. (Update
of kexec-tools and kdump packages needed.)

 2. Fix load of kdump kernel when KDUMP_KERNELVER=&quot;kdump&quot;
on ppc64. (Only updating &quot;kdump&quot; is required for that fix.)

 3. Support &quot;kernel-kdumppae&quot; to take dumps on machines
that have more than 4 GiB of physical memory but are 32 bit
(or use a 32 bit kernel). That update contains only the
support in &quot;kdump&quot; package (init scripts), not the actual
&quot;kernel-kdumppae&quot; kernel.

 4. Replace KDUMP_KERNELVER=&quot;kdump&quot; with KDUMP_KERNELVER=&quot;&quot;
in /etc/sysconfig/kdump when installing the updated
package. That is required to use a &quot;kernel-kdumppae&quot;
automatically without editing the configuration file once
it gots released. (Only update of &quot;kdump&quot; is required for
that fix.)

 5. Set KDUMP_KERNELVER=&quot;&quot; on i386 instead of
KDUMP_KERNELVER=&quot;kdump&quot;. That affects only new
installations of the &quot;kdump&quot; package. For updates, the
change (4) fixes the problem.

 6. Try also $(uname -i) to find the makedumpfile.config in
/usr/src/linux-${version}-obj/${arch}/${flavour}. The
difference between $(uname -i) and $(uname -m) is that it's
&quot;i386&quot; always on i386 and $(uname -m) varies between &quot;i586&quot;
and &quot;i686&quot;.

 7. Implement &quot;try-restart&quot; command and use that
implementation also for &quot;condrestart&quot;. The difference
between &quot;restart&quot; and &quot;try-restart&quot; is that &quot;try-restart&quot;
checks if the service was already active. If not, does
nothing. That update affects only the &quot;kdump&quot; package and
was required for fix (7).

 8. Add udev rules to reload kdump configuration on memory
or CPU hotplug. This is required to get also a dump of the
&quot;new&quot; memory. The so-called ELF core headers (i.e. the
description of the memory that is dumped) is generated on
kdump load, not when the actual crash occurs. (That fix
also affects only &quot;kdump&quot; package.)

 9. Panic on unknown NMI automatically. Some machines have
an &quot;NMI&quot; button that can be used to get a dump even if
SysRq doesn't work any more and the machine has locked-up.
(That fix only affects &quot;kdump&quot; package.)

10. Print stderr of kexec invocation. Previously, warnings
printed by the &quot;kexec&quot; command have been silently ignored
when the return value of the command was 0 (success).

For all that reasons, it's highly recommended to install
that update.
</description>
  <description lang="de">This update fixes following problems in kdump configuration:

 1. When taking a dump on machines that were booted with
the &quot;mem&quot;  parameter, the dump is now only as large as the
specified memory, not  as large as the full memory. That
affects only the i386 and the x86-64 architectures. (Update
of kexec-tools and kdump packages needed.)

 2. Fix load of kdump kernel when KDUMP_KERNELVER=&quot;kdump&quot;
on ppc64. (Only updating &quot;kdump&quot; is required for that fix.)

 3. Support &quot;kernel-kdumppae&quot; to take dumps on machines
that have more than 4 GiB of physical memory but are 32 bit
(or use a 32 bit kernel). That update contains only the
support in &quot;kdump&quot; package (init scripts), not the actual
&quot;kernel-kdumppae&quot; kernel.

 4. Replace KDUMP_KERNELVER=&quot;kdump&quot; with KDUMP_KERNELVER=&quot;&quot;
in /etc/sysconfig/kdump when installing the updated
package. That is required to use a &quot;kernel-kdumppae&quot;
automatically without editing the configuration file once
it gots released. (Only update of &quot;kdump&quot; is required for
that fix.)

 5. Set KDUMP_KERNELVER=&quot;&quot; on i386 instead of
KDUMP_KERNELVER=&quot;kdump&quot;. That affects only new
installations of the &quot;kdump&quot; package. For updates, the
change (4) fixes the problem.

 6. Try also $(uname -i) to find the makedumpfile.config in
/usr/src/linux-${version}-obj/${arch}/${flavour}. The
difference between $(uname -i) and $(uname -m) is that it's
&quot;i386&quot; always on i386 and $(uname -m) varies between &quot;i586&quot;
and &quot;i686&quot;.

 7. Implement &quot;try-restart&quot; command and use that
implementation also for &quot;condrestart&quot;. The difference
between &quot;restart&quot; and &quot;try-restart&quot; is that &quot;try-restart&quot;
checks if the service was already active. If not, does
nothing. That update affects only the &quot;kdump&quot; package and
was required for fix (7).

 8. Add udev rules to reload kdump configuration on memory
or CPU hotplug. This is required to get also a dump of the
&quot;new&quot; memory. The so-called ELF core headers (i.e. the
description of the memory that is dumped) is generated on
kdump load, not when the actual crash occurs. (That fix
also affects only &quot;kdump&quot; package.)

 9. Panic on unknown NMI automatically. Some machines have
an &quot;NMI&quot; button that can be used to get a dump even if
SysRq doesn't work any more and the machine has locked-up.
(That fix only affects &quot;kdump&quot; package.)

10. Print stderr of kexec invocation. Previously, warnings
printed by the &quot;kexec&quot; command have been silently ignored
when the return value of the command was 0 (success).

For all that reasons, it's highly recommended to install
that update.
</description>
  <yum:version ver="5365" rel="0"/>
  <rpm:requires>
    <rpm:entry kind="atom" name="kdump" epoch="0" ver="0.3.0" rel="8.12" flags="EQ"/>
  </rpm:requires>
  <category>recommended</category>
  <atoms>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>kdump</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="0.3.0" rel="8.12"/>
      <checksum type="sha" pkgid="YES">b2c7fa6a7fdf0736dab89a81a6d5a56358315fa9</checksum>
      <time file="1217346382" build="1217343606"/>
      <size package="86350" installed="182722" archive="187404"/>
      <location xml:base="media://#1" href="suse/x86_64/kdump-0.3.0-8.14.x86_64.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="kdump" epoch="0" ver="0.3.0" rel="8.12" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="kdump"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
  </atoms>
</patch>
