[openbeosnetteam] Re: BUG: ethernet
- From: Waldemar Kornewald <wkornew@xxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Mon, 17 Oct 2005 20:26:02 +0200
Axel Dörfler wrote:
did someone of you notice reproducible crashes when loading the
ethernet
kernel module on R5/BONE? The debugger says:
Thread: ethernet_input
Stack trace:
xxxx close
That's all I get (with DEBUG=5). I cannot explain why this happens
(ethernet_input does not close() anything, does it?). Probably it's
You may want to try to activate -fcheck-memory-usage and MALLOC_DEBUG=
15 - that should help detect any memory corruption. What might also
help is to use bdb with single stepping.
Unfortunately, this did not help. But something else did:
Instead of killing the ethernet_input thread in ether_stop() I deleted
the etherq and added queue-deletion detection code to the thread. But I
doubt this is the real fix (though it does not crash, anymore). Is there
a bug when killing a real-time kernel thread?
Bye,
Waldemar Kornewald
- Follow-Ups:
- [openbeosnetteam] Re: BUG: ethernet
- From: Philippe Houdoin
- References:
- [openbeosnetteam] Re: BUG: ethernet
- From: Axel Dörfler
Other related posts:
- » [openbeosnetteam] BUG: ethernet
- » [openbeosnetteam] Re: BUG: ethernet
- » [openbeosnetteam] Re: BUG: ethernet
- » [openbeosnetteam] Re: BUG: ethernet
- » [openbeosnetteam] Re: BUG: ethernet
- » [openbeosnetteam] Re: BUG: ethernet
did someone of you notice reproducible crashes when loading the ethernet kernel module on R5/BONE? The debugger says:
Thread: ethernet_input Stack trace: xxxx close
That's all I get (with DEBUG=5). I cannot explain why this happens (ethernet_input does not close() anything, does it?). Probably it's
You may want to try to activate -fcheck-memory-usage and MALLOC_DEBUG=
15 - that should help detect any memory corruption. What might also help is to use bdb with single stepping.
- [openbeosnetteam] Re: BUG: ethernet
- From: Philippe Houdoin
- [openbeosnetteam] Re: BUG: ethernet
- From: Axel Dörfler