[PARPORT] Odd behavior in device driver

Richard Stover (richard@ucolick.org)
Mon, 10 Jan 2000 16:27:06 -0800

Perhaps this ought to go to another mailing list, but I
am trying to write a parallel port device driver, so I
thought I'd start here. I'm sure there are plenty of
kernel hackers who can spot instantly what I'm doing wrong.

The problem: When I call schedule_timeout(##) I always
get something like:

kernel: schedule_timeout: wrong timeout value c3f02000 from d0108574

even if I pass a constant. I've reduced my init_module function
to the bare minimum and I still get this behavior. Here is
my module:

#ifdef MODULE
__initfunc(int init_module(void))
__initfunc(int init_dpppci(void))
        current->state = TASK_INTERRUPTIBLE;
        schedule_timeout((signed long)9);
        return 0;

This bit of code produced the error above.

make is doing the compile as:

gcc -D__KERNEL__ -I/home/richard/cyberdpp/include
-I/usr/src/linux/include -O2 -DMODULE -DLINUX -DCONFIG_PROC_FS
-Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -m486
-malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -D__i386__
-fno-strict-aliasing -c xdpp.c

Does anyone see anything wrong with any of this?

Thanks for your help.

Richard Stover

-- 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 2.0b3 on Mon 10 Jan 2000 - 19:32:25 EST