| --- Log opened Tue Apr 12 00:00:17 2016 | ||
| shorne | stekern: have you ever had luck with interpreting the stack trace dumped when there is a kernel oops on openrisc? | 00:43 |
|---|---|---|
| shorne | I got a crash a few days ago in the scheduler | 00:44 |
| shorne | I wrote a tool for annotating the stack trace with symbols (it seems to have code in the kernel for doing that, but its not working) | 00:44 |
| shorne | Example output https://gist.github.com/stffrdhrn/121705cab9fa0528ad5a7d3bcc0c25d4 | 00:44 |
| shorne | The tool: https://github.com/stffrdhrn/linux/blob/openrisc/scripts/annotate-stracktrace.pl | 00:46 |
| shorne | there is probably something better | 00:46 |
| shorne | there is probably something better | 01:24 |
| shorne | oops | 01:25 |
| shorne | ls | 09:49 |
| shorne | oops again | 09:49 |
| shorne | a bit more work on my openrisc stacktrace debugging tool https://gist.github.com/stffrdhrn/87c9c484f9e127f0c360ea30daa5aa68 | 10:00 |
| shorne | in the end it makes no sense to crash within that function, maybe some hardware issue, I am waiting for it to happen again | 10:04 |
| -!- knz_ is now known as knz | 17:21 | |
| -!- bklu is now known as p1oooop | 19:40 | |
| --- Log closed Wed Apr 13 00:00:19 2016 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!