On Mon, Jan 21, 2013 at 05:47:27PM -0500, Sivateja Patibandla wrote: > > Can you do: > > > > $ gdb /path/to/ath5k.ko > > (gdb) l *(ath5k_tx_queue+0x2c4) > > > > and post the output?
> Thank you for your response. I'm working on the open80211s stack on the > wifi modem with 4 mb flash. So, I could not get to load gdb on it. Could > you please point me at a right direction of debugging the kernel panic. I'm just using gdb in this case to resolve symbols to the line of code -- there are other ways. Cross-gdb is probably a headache, but if you have a cross-objdump for your target then that is generally just as good. I have often compared "objdump -S foo.ko" output against the "Code" section of the oops to find the oopsing instructions. "scripts/markup_oops.pl" can automate this somewhat. In general, check out Documentation/oops-tracing.txt in the kernel source for some hints. -- Bob Copeland %% www.bobcopeland.com _______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
