Robert Kiesling wrote:
>
> I would think that the module is trying to use a hardware
> resource that is already in use. You might try unloading
> all of the other modules, and try to repeat the error.
> It could also be an incorrect library version. I'm
> not sure that a kernel-level debugger exists, but I'd
> have to get back to you on that one. Robert
> -- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
> ---
> For more information on Real-Time Linux see:
> http://www.rtlinux.org/rtlinux/
Hi Robert,
There are now 2 ways to do kernel module debugging. You can do
host/target debugging with the extended gdbstubs we did at Zentropix,
also you can use the new RTLinux debugger from fsmlabs which is self
hosting and remote. I'd suggest that the RTLinux debugger could be used
for faults that don't cause a system lockup, and the remote Zentropix
gdbstubs for serious faults that make the system lock.
Regards, Stuart
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
