Hi Juergen,
Juergen Pfeiffer wrote:
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?
If you can make your driver do most of its work without interrupts
then that would go part of the way. Obviously this is to test,
performance won't matter, poll to IO if you can. Rule our the raw
access (memory/bus cycle corruption, etc).
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Dude EMAIL: [EMAIL PROTECTED]
Secure Computing Corporation PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
_______________________________________________
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
