On Thu, 2007-09-13 at 00:13 -0500, Kumar Gala wrote: > On Sep 12, 2007, at 11:47 PM, sivaji wrote: > > > > > > > Hi, > > I have JTAG Debugger connected to the board. I was given the > > following commands in the root path of the kernel source > > If you can dump memory w/o connecting GDB, I suggest the following. > > Look in your kernel build for System.map and grep for log_buf you > should get something like: > > c040b04c d log_buf > c043b1a4 b __log_buf > > then dump the memory @ these addresses. I can't remember which one > is the correct one. You'll want to subtract c000_0000 from the > address to get a physical address that you can dump. This should > help provide some possible insight into what's going on.
__log_buf is the actual buffer, log_buf points to the current insertion point IIRC. It should be pretty obvious that you're looking at a dmesg buffer though, unless there's nothing in there for some reason. cheers -- Michael Ellerman OzLabs, IBM Australia Development Lab wwweb: http://michael.ellerman.id.au phone: +61 2 6212 1183 (tie line 70 21183) We do not inherit the earth from our ancestors, we borrow it from our children. - S.M.A.R.T Person
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
