On Mon, Oct 19, 2015 at 10:02:44PM +0200, Alexander Kratzsch wrote: > Does anyone have some idea I could try?
This is hardly an one-answer question. You are asking a very broad question on how to debug kernels. Someone might say that you can fill the source code with some printf's here and there. It's OK if you know what are you doing, but it can take a very long time if you randomly do this without the feeling/experience needed. There are people who use QEMU to help find bugs [1], but this is not a definitive solution also. I have qemu-system-arm "emulating" a cubieboard and get mixed results from the emulator and from the real hardware. This is one of the reasons why it's a bad idea to maintain a platform by using just an emulator [2]. You can use ddb(4), which requires a decent amount of knowledge to know where you are. You can use kgdb(7) if your platform supports it, which is not the case with armv7. A JTAG interface? Attaching pins to a logic analyser? You can use... what not? It's up to you. I would like to have an easy answer too, but there isn't. People sharing their techniques would be great too. [1] http://undeadly.org/cgi?action=article&sid=20130109210346 [2] http://marc.info/?l=openbsd-tech&m=139000159214762&w=2 Cheers, -- db
