Lines Matching refs:you

19 Always try the latest kernel from kernel.org and build from source. If you are
23 Finding bugs is not always easy. Have a go though. If you can't find it don't
24 give up. Report as much as you have found to the relevant maintainer. See
25 MAINTAINERS for who that is for the subsystem you have worked on.
27 Before you submit a bug report read REPORTING-BUGS.
56 This is how to track down a bug if you know nothing about kernel hacking.
67         . Rebuild a revision that you believe works, install, and verify that.
70           you know that 1.3.69 does.  Pick a kernel in the middle and build
79             but 3.63 doesn't.  So you diff -r those two kernels and come
97                 found in my case that they were self explanatory - you may
129             Then recompile, retest, move the ifdefs until you find the one
132 Finally, you take all the info that you have, kernel revisions, bug
133 description, the extent to which you have narrowed it down, and pass
134 that off to whomever you believe is the maintainer of that section.
135 A post to linux.dev.kernel isn't such a bad idea if you've done some
138 If you get it down to a routine, you'll probably get a fix in 24 hours.
143 because Linux snapshots will let you do this - something that you can't
149 Nobody is going to tell you how to fix bugs. Seriously. You need to work it
153 output to find the valid line of code/assembler. Without debug symbols, you
160 NB.: you need to be at the top level of the kernel tree for this to pick up
163 If you don't have access to the code you can also debug on some crash dumps
194 In addition, you can use GDB to figure out the exact file and line
195 number of the OOPS from the vmlinux file. If you have
196 CONFIG_DEBUG_INFO enabled, you can simply copy the EIP value from the
206 If you don't have CONFIG_DEBUG_INFO enabled, you use the function
220 If you have a call trace, such as :-
236 Debug memory allocations. This will help you see whether data has been
241 Once you have worked out a fix please submit it upstream. After all open
242 source is about sharing what you do and don't you want to be recognised for