Lines Matching refs:kernel

19 Always try the latest kernel from kernel.org and build from source. If you are
21 instead of to a kernel developer.
33 kernel.
47 - start using git for the kernel source
56 This is how to track down a bug if you know nothing about kernel hacking.
62         . All the kernel tar files from a revision that worked to the
70           you know that 1.3.69 does.  Pick a kernel in the middle and build
73         . You'll narrow it down to the kernel that introduced the bug.  You
78           - Copy kernel that works into "test".  Let's say that 3.62 works,
132 Finally, you take all the info that you have, kernel revisions, bug
135 A post to linux.dev.kernel isn't such a bad idea if you've done some
140 My apologies to Linus and the other kernel hackers for describing this
141 brute force approach, it's hardly what a kernel hacker would do.  However,
152 To debug a kernel, use objdump and look for the hex offset from the crash
154 will see the assembler code for the routine shown, but if your kernel has
156 in the kernel hacking menu of the menu configuration.) For example:
160 NB.: you need to be at the top level of the kernel tree for this to pick up
211 And recompile the kernel with CONFIG_DEBUG_INFO enabled: