Has anyone here on this mail list had experience with debugging the linux kernel? Apparently it is necessary to debug the spb2, ieee1394 and ohci1394 kernel modules to find out why the firewire isn't working.
Is this done by recompiling those modules with a debug option, then using
gdb
or preferably insight to actually debug?
What is a rather robust method of doing this? Thanks for the input.
First thing to do is check the module source code for a debug parameter. Many of the modules accept a load option that cranks up the log level that gives you a much more detailed look at what is going on. Sometimes you may have to recompile the module to get the debug options.
And if there aren't any such options, add them yourself, and add some printk()'s throughout the code.
An alternative nowadays is to run the Kernel in User Space (UML ?), I believe that makes it easier to debug, and reduces the need to reboot when the kernel Oops', and possibly wait for fsck's etc.
I have done some bttv debugging, and writing some modules using UVFS (UserSpace Virtual File System)
-- Michael O'Keefe | [EMAIL PROTECTED] Live on and Ride a 03 BMW F650GSDakar| [EMAIL PROTECTED] / | I like less more or less less than |Work:+1 858 845 3514 / | more. UNIX-live it,love it,fork() it |Fax :+1 858 845 2652 /_p_| My views are MINE ALONE, blah, blah, |Home:+1 760 788 1296 \`O'| blah, yackety yack - don't come back |Fax :+1 858 _/_\|_,
-- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
