I have recompile parport_pc's source code (i'd just added a pair of
printks in the init_module()) and I have found that when trying loading
the module the computer do not freeze down as it did before. Now it
starts loading the module but receives a SIGSEGV signal. I send you a
trace for the next command:
[root@lago parport]# strace -o /root/traceado2.txt insmod -v
/usr/src/linux-2.4/drivers/parport/parport_pc.o
execve("/sbin/insmod", ["insmod", "-v",
"/usr/src/linux-2.4/drivers/parport/parport_pc.o"], [/* 24 vars */]) = 0
-- some other stuff --
init_module("parport_pc", 0x8071d18 <unfinished ...>
+++ killed by SIGSEGV +++
Now if I look up the actives modules on system, parport_pc appears in
/initialization state/.
[root@lago parport]# lsmod
Module Size Used by
parport_pc 16160 1 (initializing)
I don't know if that helps in any way, but...
PS: None of the printk's calls appears in the screen.
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Tue May 22 2001 - 14:24:27 EDT