Date: Tue, 20 Aug 2013 22:10:02 +0200 From: Martin Laabs <mailinglists@martinlaabs.de> To: freebsd-arm@freebsd.org Subject: Debug stalling Raspberry Message-ID: <5213CD1A.7000506@martinlaabs.de>
next in thread | raw e-mail | index | archive | help
Hi, currently I run r254441 on a raspberry pi b and every time I run portsnap the cpu stopps running. This happens during the snapshot verify while around 25k files are gunziped and sha256ed (file after file of cause). I can reproduce this but the Pi does not hang reproducible at the same file but the last processed file is different from try to try. There is, at least at the video console, no kernel panic. The kernel itself still responds to icmp ping packages and echos the keyboard output. But everything else does not work. (I know this behavior from disconnected harddisks containing the kernel/system) The current consumption also dropps around 100mA. It is very interesting that this behavior is not limited to the internal MMC card but also occurs when the data is stored external on an usb stick. My question is how to debug this bug since I have no idea where to start. >From my experience with bare metal arm systems I would start connecting a jtag debugger but I am afraid getting all the symbols mapped correct to the gdb. And even if this works - what should I monitor and what should I test for? There might be however a more simple solution. So any suggestion is welcome. If you can reproduce this bug I also would be very happy. Best regards, Martin Laabs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5213CD1A.7000506>