)]}'
{
  "commit": "072f042df335d7e0da2027637bcf720d7ff1589b",
  "tree": "0909837c84e84fa051bf78b1302836a1c89f944f",
  "parents": [
    "98075d245a5bc4aeebc2e9f16fa8b089a5c200ac"
  ],
  "author": {
    "name": "Takao Indoh",
    "email": "indou.takao@jp.fujitsu.com",
    "time": "Tue Apr 15 05:59:54 2008 -0400"
  },
  "committer": {
    "name": "Tony Luck",
    "email": "tony.luck@intel.com",
    "time": "Tue Apr 15 11:20:53 2008 -0700"
  },
  "message": "[IA64] kdump: Add crash_save_vmcoreinfo for INIT\n\nThis patch fixes the problem that kdump by INIT does not work if we use\nmakedumpfile. The problem is that after INIT is issued, 2nd kernel\nstarts and makedumpfile fails with the following error message.\n\n/proc/vmcore doesn\u0027t contain vmcoreinfo.\n\u0027-x\u0027 or \u0027-i\u0027 must be specified.\n\nmakedumpfile Failed.\n\nThe cause of this problem is that kernel does not call\ncrash_save_vmcoreinfo. When kdump starts by panic or sysrq-trigger,\ncrash_save_vmcoreinfo is called by crash_kexec. But this function is not\ncalled when kdump starts by INIT. The Attached patch fixes this.\n\nThis patch just adds crash_save_vmcoreinfo into machine_kdump_on_init so\nthat crash_save_vmcoreinfo can be called when kdump starts by INIT.\nI tested this patch with linux-2.6.25-rc9 and I confirmed it worked.\n\nSigned-off-by: Takao Indoh \u003cindou.takao@jp.fujitsu.com\u003e\nSigned-off-by: Tony Luck \u003ctony.luck@intel.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e74e15a08892024f876446ca0d2208821d447dba",
      "old_mode": 33188,
      "old_path": "arch/ia64/kernel/crash.c",
      "new_id": "90ef338cf46fd93e1aacedc10c8bc5a7d18a226c",
      "new_mode": 33188,
      "new_path": "arch/ia64/kernel/crash.c"
    }
  ]
}