Description of Problem:
When crashdump is executed via OS_INIT on IPF machine, backtrace
command, which is a subcommand of crash, does not work correctly.

Two problems were found in the OS_INIT code.

(1) OS_INIT handler has two stages.
    stage1: handler written by assembler
    stage2: handler written by C
  The former is ia64_monarch_init_handler and ia64_slave_init_handler.
  The latter is ia64_init_handler. ia64_init_handler is called only by
  ia64_monarch_init_handler.
  When INIT interrupt is asserted, one cpu calls
  ia64_monarch_init_handler and the others call
  ia64_slave_init_handler. It means that ia64_init_handler is called
  by only one cpu. In that case, backtrace command fails. To make
  backtrace succeed, all cpus need to call ia64_monarch_init_handler.

(2) The second problem occurs by correcting the first problem.
  When OS_INIT handler is called, SAL hands the handler some
  information through registers. The handler preserves this information
  in ia64_sal_to_os_handoff_state. (Please see
  SAL_TO_OS_MCA_HANDOFF_STATE_SAVE macro in the
  arch/ia64/kernel/mca_asm.S.) If all cpus call
  ia64_monarch_init_handler at the same time, they write their own
  information to the ia64_sal_to_os_handoff_state simultaneously and
  break their contents.

Version-Release number:
kernel-2.6.9-6.37.EL

How reproducible:
always

Steps to Reproduce:
1. Enable Diskdump
2. Push OS_INIT switch
3. bt with crash command

Actual results:
Backtrace command does not work

Expected results:
Backtrace command works correctly

Additional info:
none