Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!mmcg From: mmcg@cs.monash.edu.au (Mike Mc Gaughey) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Parallel laplink abuse leads to death of kernel secondary timer Date: 9 Jul 1996 12:47:44 GMT Organization: Monash University Lines: 25 Message-ID: <4rtkdg$lpa@harbinger.cc.monash.edu.au> References: <4rn4ip$kcr@harbinger.cc.monash.edu.au> <4rrdmi$747@helena.MT.net> NNTP-Posting-Host: molly.cs.monash.edu.au X-NNTP-Posting-User: mmcg Keywords: printer port laplink cable timer nate@trout.mt.sri.com (Nate Williams) writes: >Mike Mc Gaughey <mmcg@cs.monash.edu.au> wrote: >[ High interrupt load using the parallel port IP driver wipes out the > profiling clock on 2.1R ] >I'd say you have a hardware bug. Maybe. Since then, I've heard that one of the authors of a multitasking DOS-like kernel mentioned a similar secondary timer problem when they ran it on one of the newer pentiums. The problem was solved by reordering a couple of lines of code. It's commercial code (I heard this from one of their customers); presumably, that's all I'm likely to hear. As has been suggested, we'll see what happens under 2.1.5 (in a few weeks). Cheers, Mike. -- Mike McGaughey AARNET: mmcg@molly.cs.monash.edu.au "Thousands at his bidding speed, And post o'er land and ocean without rest" - Milton.