> ironmaiden kernel: freemware: start: c402c8d0 end: c402f790: init: c402c904 pages: 4
> ironmaiden kernel: freemware: vm c402c000..c402cfff -> page 00000d04
> ironmaiden kernel: freemware: vm c402d000..c402dfff -> page 00000c12
> ironmaiden kernel: freemware: vm c402e000..c402efff -> page 00000e78
> ironmaiden kernel: freemware: vm c402f000..c402ffff -> page 00000f23
OK, so it crashes only when handle_fault is called. Does it still
crash when you add a 'return 0' as the first line of handle_fault?
In any case, the addresses of the 'freemware_start' symbol looks
suspicious, it should be near a page boundary ... Can you do a
nm freemware.o | sort
and check whether 'freemware_start' and 'freemware_end' are really
the first resp. last symbol of the module?
If not, maybe the compiler/linker you are using doesn't cope correctly
with the host-linux.ld linker script. Or maybe the Linux 2.3.xx headers
create references to sections not mentioned in that script? What does
objdump --section-headers freemware.o
say?
Bye,
Ulrich
--
Ulrich Weigand,
IMMD 1, Universitaet Erlangen-Nuernberg,
Martensstr. 3, D-91058 Erlangen, Phone: +49 9131 85-7688
