Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!ncar!mephisto!rutgers!mcdchg!heiby
From: heiby@mcdchg.chg.mcd.mot.com (Ron Heiby)
Newsgroups: comp.sys.m68k
Subject: Re: System V/68 device driver timers
Message-ID: <40133@mcdchg.chg.mcd.mot.com>
Date: 27 Jun 90 20:01:37 GMT
References: <1548@dfsun1.electro.swri.edu>
Organization: Motorola Microcomputer, Schaumburg, IL
Lines: 13

fenske@dfsun1.electro.swri.edu (Robert Fenske Jr) writes:

>I call untimeout() if the event occurs or when the timeout does
>occur (this is a just-in-case).

I haven't traced through the timeout/untimeout/clock code in detail,
but it looks to me like you don't want to be calling untimeout() on
timeout ids that have already happened.  You might take a look at
a crash dump and see what is in your callout table at the time of
the panic.  That might tell you something interesting.
-- 
Ron Heiby, heiby@chg.mcd.mot.com	Moderator: comp.newprod
"Mandatory Drug Testing?  Just Say NO!!!"