Re: [microblaze-uclinux] Kernel module driver crash

[Giulio Mazzoleni <giulio.mazzoleni@xxxxxxxxxxxxxxxxxxxxxxx>]

Hi Wendy,
you are right.

Furthemore if the init funciton is defined as "int
init_module(void)" (and the call to module_init is removed) it is put in
the .text section by the compiler instead of the .init section and the
errors disappear.

I still wonder if there could be any relation between this kind of
errors and the ones I get during normal operation (they seem to get
triggered more frequently under heavy network activity).
The error messages printed by the kernel are the same, so I was hoping..

Giulio

Il giorno ven, 24/04/2009 alle 18.20 +1000, Wendy Liang ha scritto:
> Hi Giulio and Ian,
> 
> By dumping the .ko, I found that the the init_module can only jump to
> the top of .text section of the .ko.
> 
> if testd/c/b() is called by more than once, the compiler will generate
> executable code for testd/c/b/a() in the same sequence as how they
> defined in the .text section of .ko.
> 
> Otherwise, because they are all static function, by default, the
> compiler will only generate executable code for testa() in the .text
> section of .ko.
> 
> We are still investigating why it cannot  jump to section testa() when
> it is not at the top of .text section.
> 
> Regards,
> Wendy




___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/