19 Mar 2013 11:11
IP32 debugging kernel intr handler (crime/mace)
roop <roop <at> tamasi.org>
2013-03-19 10:11:59 GMT
2013-03-19 10:11:59 GMT
Hi, I'm digging into 47640 on sgimips (SGI O2 IP32) on netbsd-current (6.99.17). http://gnats.NetBSD.org/cgi-bin/query-pr-single.pl?number=47640 Background ----------------- I'm basically starting out on kernel tinkering. As explained in the gnats this SGI IP32 will hard lock at random point. Otherwise it operates very nice and quickly. That was 6.0.1, same deal on current. Also 47639, a random keyboard flash co-incides with a interrupt, may be related. What I want to do, but don't know if i can: - get a debugger triggered at the right point, which means finding the right spot - adding more debug around some other bits of kernel code, but not so to saturate the console - breaking the kernel (linux magic sysreq style) and just getting it to dump it's stack at a keypress The hunch was a glitch in the interrupt handling, so I've added aprint_debug() liberally throughout dev/crime.c and mace/mace.c, as seen in https://gist.github.com/rooprob/5191131(Continue reading)
RSS Feed