lkml.org 
[lkml]   [2003]   [Feb]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [KEXEC][PATCH] Modified (smaller) x86 kexec hwfixes patch
>> Running on my 4-way P3 test box (just SMP, not NUMA) kexec_test
>> prints this:
>>
>> Synchronizing SCSI caches:
>> Shutting down devices
>> Starting new kernel
>> kexec_test 1.8 starting...
>> eax: 0E1FB007 ebx: 0000011C ecx: 00000000 edx: 00000000
>> esi: 00000000 edi: 00000000 esp: 00000000 ebp: 00000000
>> idt: 00000000 C0000000
>> gdt: 0000006F 000000A0
>> Switching descriptors.
>> Descriptors changed.
>> Legacy pic setup.
>> In real mode.
>>
>> Without that I just get:
>>
>> Synchronizing SCSI caches:
>> Shutting down devices
>> Starting new kernel
>>
>> Can someone interpret?
>
> Besides the fact that you cannot make BIOS calls, and kexec is working
> there is not much to say. You cannot kexec another kernel?

Nope, if I just kexec the same 2.5.59 kernel+kexec patches that I'm booted
on it says:

Synchronizing SCSI caches:
Shutting down devices
Starting new kernel

Could you give me a high-level sketch of what you're doing? kexec -l loads
the new kernel, then what do you do? Drop back into real mode and jump to
the normal kernel entry point? Or decompress by hand, do some alternate
setup of the early page tables and try to jump in at the 32-bit entry point?

Is all I can assume from the above that I crash in the new kernel before
console_init()? Or should I expect something from the decompress code?

Thanks,

M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.039 / U:1.620 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site