-- Found a bug ? --
Put your stuff on found bugs here and help each other with tracking down the origin of bugs...
First, before doing anything else, read REPORTING-BUGS in your Linux kernel source tarball. Next, trigger the bug, if you can, and save the Oops output. If you cannot trigger the bug at will, go through the last few actions you performed before the bug originally appeared. Please make sure you can trigger the bug on latest kernel release, preferably unpatched, and without binary-only kernel modules. After you have a copy of the Oops, head to [http://www.kernel.org/pub/linux/utils/kernel/ksymoops/v2.4/ KernelDotOrg] and grab the latest copy of ksymoops, which is currently 2.4.9. Follow the ksymoops instructions and decode the Oops output. Note: on 2.6.x kernels just enable CONFIG_KALLSYMS and you'll get a decoded Oops.
If you are brave enough, try debugging the problem, as Denis Vlasenko described in [http://kerneltrap.org/node/view/3648 HOWTO find oops location]. If you manage to fix the problem send Oops, description of problem and patch to LKML and/or relevant mailing list (hint: look at MAINTAINERS),there is also a book [http://lwn.net/images/pdf/LDD3/ch04.pdf avaliable online] about "Linux devices drivers" that is also edited at oreilly that explain kenrel debuging
If not, post the Oops message, the relevant portion of your Linux kernel source .config file, and an explanation of what you were doing to the [mailto:linux-kernel@vger.kernel.org LinuxKernelMailingList]. Post the message to other relevant mailing lists as well, to maximize a chance of a response. For example, if the Oops occurred while you were sending IPv4/IPv6 packets, send your data to the [mailto:netdev@oss.sgi.com NetDevMailingList]
Then sit back and wait until you get a response.
you can also try to locate where the bug ,
NOTE: Do not expect an immediate answer. Expect an answer sometime within one to three days. If you don't get one by then, re-post your message. Don't attempt to re-post more than three times (IMHO).
[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively] looks useful.