Date: Wed, 4 Mar 1998 22:20:16 -0700 From: Nate Williams <nate@mt.sri.com> To: shimon@simon-shapiro.org Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) Message-ID: <199803050520.WAA16381@mt.sri.com> In-Reply-To: <XFMail.980304194024.shimon@simon-shapiro.org> References: <199803050248.SAA23631@dingo.cdrom.com> <XFMail.980304194024.shimon@simon-shapiro.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. Nate 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?199803050520.WAA16381>