Date: Wed, 04 Mar 1998 21:34:26 -0800 (PST) From: Simon Shapiro <shimon@simon-shapiro.org> To: Nate Williams <nate@mt.sri.com> Cc: current@FreeBSD.ORG, Mike Smith <mike@smith.net.au> Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) Message-ID: <XFMail.980304213426.shimon@simon-shapiro.org> In-Reply-To: <199803050520.WAA16381@mt.sri.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05-Mar-98 Nate Williams wrote: >> > However the driver has no say in the matter when _someone_else_ >> > disables interrupts for a long period of time, or when the hardware >> > fails to deliver them in the first place. >> >> Unless I misunderstand something, the driver should get interrupts >> delivered, unless another part of the kernel is in spltty(), or another >> spl >> which masks spltty. There should not be all that many of those, and >> they >> should be considered carefully. > > I can tell you that uniquivocally XFree86 causes this to happen. Why, I > don't know, but it's definitely X related. If I don't use X and the > machine gets the same traffic, I get the messages. If I switch from > XFree8 to XIG, the messages go away. > > What is causing the interrupts to go away, I don't know, but it might be > syscons or something. I'm not switching vty's, and neither am I hitting > the caps-lock or causing the LED's to switch. > > But, it occurs none-the-less. I am guessing it is something to do with the S3 chip. The Mach64 I finally pulled out was much worse. It would die/kill serial ports. I think the problem is there and in the FAST_INTR stuff. Now I am going to get myself in trouble all over again :-) Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.980304213426.shimon>