[08:55] <soren> Hi. I need a bit of help translating a kernel call trace entry to line of code in the source.
[09:14] <apw> soren, got a reference to the trace ?
[09:22] <soren> apw: Sorry, on a call now. Will get back to you in an hour and a half or so.
[09:35] <soren> apw: http://imagebin.ca/v/1grE6VHtfuiG
[09:35] <soren> apw: uname -a: Linux cp2-production 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:40:53 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[09:35] <soren> apw: ...which seems to be very unfortunate as that exact version doesn't seem to have a ddeb for amd64.
[09:36] <infinity> soren: If only there were newer kernels you could be using. :)
[09:36] <infinity> soren: By like 5 months...
[09:36] <soren> infinity: Yeah :( Gah. Upgrading these things is a such a pain.
[09:37] <infinity> Or 4.  Whatever.
[11:12] <soren> apw: Without the ddeb, I'm out of luck, aren't I?
[11:15] <apw> pretty much out of luck, you can prolly mostly build the ddeb again, and it will whine it is not the same, but if you make it from the tag, it ought to be right
[11:24] <soren> apw: Yeah, that makes sense.
[11:26] <apw> i don't believe we had a new compiler in T whch helps
[11:46] <soren> apw: Ok, I have the vmlinux now. I can pinpoint the line of code where it break.. Going further up the stack, I hit a module (compiled with dkms). How can I resolve that to a line of code?
[11:48] <apw> soren, hmm, no idea, never wanted to do that, good old dkms
[11:49] <soren> apw: What if it were a "regular" module?
[11:50] <soren> apw: The memory location is dynamic, so how would e.g. addr2line know what to do with it?
[11:50] <apw> it is was regular you'd have the info in the ddeb you already have
[11:51] <apw> hmm, that info ought to be int he kernel unless we have hidden it for security
[11:51] <soren> apw: Oh, I actually didn't use the ddeb. I just grabbed the vmlinux and used addr2line. What should I have been doing?
[11:52] <soren> It's been a while since I debugged kernel code like this :-/
[11:55] <apw> soren, i don't think i tend to debug that way either, i'd be using objdump on the .ko and working it manually i suspect
[11:59] <soren> apw: Fair enough. I'll keep digging. Thanks.