Lines Matching refs:it

13 -- Finding it the old way
23 Finding bugs is not always easy. Have a go though. If you can't find it don't
32 Often this is caused by udev. Check that first before blaming it on the
46 Steps to do it:
51 Finding it the old way
57 It's a brute force approach but it works pretty well.
61         . A reproducible bug - it has to happen predictably (sorry)
71           that, like 1.3.50.  Build & test; if it works, pick the mid point
73         . You'll narrow it down to the kernel that introduced the bug.  You
74           can probably do better than this but it gets tricky.
76         . Narrow it down to a subdirectory
100         . Narrow it down to a file
105         . Narrow it down to a routine
123             prefix it with
133 description, the extent to which you have narrowed it down, and pass
136 work to narrow it down.
138 If you get it down to a routine, you'll probably get a fix in 24 hours.
141 brute force approach, it's hardly what a kernel hacker would do.  However,
142 it does work and it lets non-hackers help fix bugs.  And it is cool
149 Nobody is going to tell you how to fix bugs. Seriously. You need to work it
179 >    Compile it with "gcc -c -o foo.o foo.s" then look at the output of
241 Once you have worked out a fix please submit it upstream. After all open