I don't know block device module programming I can help you one thing in oops tracing. compile your module in debug mode.(gcc -g) When you get oops see the EIP value 0010:[<0000000>] means offset 0x10 for function 000etc grep 000etc /boot/System.map you will know the function where it crashed. Now do a objdump --source -d yourmodule.o | less search for the function you got from the above grep it will show you the functions and line trasnlations to assembly. Add 0x10 to the start of the function and see in which line the oops was generated. Hope this helps S.Kartikeyan On 4/21/05, Rik van Riel <riel@xxxxxxxxxxx> wrote: > On Thu, 21 Apr 2005, ganesh kumar wrote: > > > it crashes at generic_make_request. the dump file shows > > > <7>EIP: 0010:[<00000000>] Tainted: PF > > Please read Documentation/oops-tracing.txt > > -- > "Debugging is twice as hard as writing the code in the first place. > Therefore, if you write the code as cleverly as possible, you are, > by definition, not smart enough to debug it." - Brian W. Kernighan > > -- > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > FAQ: http://kernelnewbies.org/faq/ > > -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
