Hi Greg
Greg Ungerer schrieb:
>
> This is on Freescales code base on the 5485 right?
> (That is an old kernel...)
>
Yes it is.
>
> Lots of interrupts means lots of context switches, into and out
> of the kernel. If there is any bugs in the entry or exit code
> that interferes with the running application processes then
> you can get application crashes like you see.
>
>
>> Of course i looked at the kmalloc()'s in my driver, but there are
>> only very few. They are only called on driver driver initialisation.
>> I could see no obvious problems yet with the allocated memory.
>
> Much more likely to be related to the interrupt/softirq load, and
> kernel code related to processing that.
Di you have any idea, how i can proof or falsify, if the problem is in
my driver or if it is in general kernel code of interrupt/softirq
processing?
Regards
--
------------------------------------------------------------------------
Jürgen Pfeiffer
* _mailto:[EMAIL PROTECTED]
SesKion Softwareentwicklung und System Konzeption GmbH
( : +49-711-9905814
Karlsruher Str. 11/1
Fax: +49-711-9905827
70771 Leinfelden-Echterdingen
1 _http://www.seskion.de_
Vertretungsberechtigte Geschäftsführer:
Gerhard Kuhn,
Jürgen Pfeiffer,
Horst Tabel.
Handelsregister:
HRB 224379
Amtsgericht Stuttgart
Unsere Ust-IdNr.:
DE189769369
Unsere Steuernummer:
99060 / 04155
------------------------------------------------------------------------
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
