Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!news.msfc.nasa.gov!pendragon!ames!agate!reason.cdrom.com!usenet From: "Jordan K. Hubbard" <jkh@FreeBSD.org> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Parallel laplink abuse leads to death of kernel secondary timer Date: Mon, 08 Jul 1996 21:10:35 -0700 Organization: Walnut Creek CDROM Lines: 16 Message-ID: <31E1DBBB.15FB7483@FreeBSD.org> References: <4rn4ip$kcr@harbinger.cc.monash.edu.au> NNTP-Posting-Host: time.cdrom.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0b5a (X11; I; FreeBSD 2.2-CURRENT i386) To: Mike Mc Gaughey <mmcg@cs.monash.edu.au> Mike Mc Gaughey wrote: > leaving it dead? Does anyone know why it dies? Does the (large) time > spent processing printer port interrupts mean that clock-related > interrupts are lost, resulting in the (permanent) failure of the > secondary clock? Is there a software fix for this? Should I be > looking at my hardware setup? Lots of questions.. :-) Much of the pentium timer code has changed since 2.1R - before everyone dives in to try and debug this rather interesting problem you've brought up, would it be possible for you to upgrade to 2.1.5 when that's released next week? -- - Jordan Hubbard President, FreeBSD Project