Hi everyone,
The following tests are all performed using the configuration file for linux
2.6.28.4 (found in the tarball linked by wiki) and a X86 build for gem5, using
configs/example/fs.py with no extra flags except for "--kernel" and some tracing
args given to gem5.
All kernels are compiled with gcc 4.6.3, except 2.6.28.4 (compiled with 4.4.7).
I've tried running a stable version of Linux 3.2 (vanilla 3.2.19), but I get the
dreadful "Kernel panic - not syncing: Cannot allocate trampoline" that already
appeared here (I haven't double-checked if it's the same cause, although it
looks like it is):
http://comments.gmane.org/gmane.comp.emulators.m5.users/8196
Version 2.6.28.4 (obsoleted by kernel.org) must be compiled with some older gcc
(gcc-4.4 gets it to compile; seems like newer gcc versions are more strict and
standards compliant). Unfortunately, it gets stuck at this kernel message (using
"configs/example/fs.py"):
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
It seems to get stuck forever in the loop found in 'delay_tsc' [1].
Version 2.6.35.15 (deemed stable and supported by kernel.org) seems to get stuck
at this loop (found in 'calibrate_APIC_clock' [2]):
while (lapic_cal_loops <= LAPIC_CAL_LOOPS)
cpu_relax();
And after some gem5 debugging what I understood is that there is a pending
masked interrupt that never gets delivered.
Was a solution to any of these posted elsewhere (I couldn't find any)?
Thanks a lot,
Lluis
[1] http://lxr.linux.no/linux+v2.6.28.4/arch/x86/lib/delay.c#L51
[2] http://lxr.linux.no/linux+v2.6.35/arch/x86/kernel/apic/apic.c#L616
--
"And it's much the same thing with knowledge, for whenever you learn
something new, the whole world becomes that much richer."
-- The Princess of Pure Reason, as told by Norton Juster in The Phantom
Tollbooth
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
