diff options
| author | Michael Ellerman <michael@ellerman.id.au> | 2008-04-30 06:47:12 +0200 |
|---|---|---|
| committer | Paul Mackerras <paulus@samba.org> | 2008-04-30 11:49:48 +0200 |
| commit | eabd90944b3a00766e84da3d117ea0f3e0a3b1a3 (patch) | |
| tree | 63899a91d207c3b72ddae1984742e1438b4a7e9b /drivers/net/fec_mpc52xx.c | |
| parent | [POWERPC] Make emergency stack safe for current_thread_info() use (diff) | |
| download | linux-eabd90944b3a00766e84da3d117ea0f3e0a3b1a3.tar.xz linux-eabd90944b3a00766e84da3d117ea0f3e0a3b1a3.zip | |
[POWERPC] Fix crashkernel= handling when no crashkernel= specified
Commit edd8ce67436851a62f99f1d9707b40ea6a8e5323 (Use extended crashkernel
command line on ppc64), changed the logic in reserve_crashkernel()
which deals with the crashkernel= command line option.
This introduced a bug in the case when there is no crashkernel= option,
or it is incorrect. We would fall through and calculate the crash_size
based on the existing values in crashk_res. If both start and end are 0,
the default, we calculate the crash_size as 1 byte - which is wrong.
Rework the logic so that we use crashk_res, regardless of whether it's
set by the command line or via the device tree (see prom.c). Then check
if we have an empty range (end == start), and if so make sure to set
both end and start to zero (this is checked in machine_kexec_64.c). Then
we calculate the crash_size once we know we have a non-zero range.
Finally we always want to warn the user if they specify a base != 32MB,
so remove the special case for that in the command line parsing case.
Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'drivers/net/fec_mpc52xx.c')
0 files changed, 0 insertions, 0 deletions