From owner-freebsd-bugs Sat May 2 22:42:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11021 for freebsd-bugs-outgoing; Sat, 2 May 1998 22:42:29 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10948 for ; Sat, 2 May 1998 22:42:19 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id WAA22835; Sat, 2 May 1998 22:40:02 -0700 (PDT) Date: Sat, 2 May 1998 22:40:02 -0700 (PDT) Message-Id: <199805030540.WAA22835@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Matthew Dillon Subject: Re: i386/5398 Reply-To: Matthew Dillon Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR i386/5398; it has been noted by GNATS. From: Matthew Dillon To: Poul-Henning Kamp Cc: John-Mark Gurney , freebsd-gnats-submit@FreeBSD.ORG Subject: Re: i386/5398 Date: Sat, 2 May 1998 22:34:59 -0700 (PDT) Look guys, I'm not going to argue... I have worse things to worry about then a bug report relating to a digital camera interface. But I am extremely disappointed that you are taking such a cavalier attitude towards it and making assumptions that, in my view, make little or no sense just to close out the report. I'm not an idiot... I've been writing operating systems and doing digital hardware design for over 15 years, so don't fraggin quote databooks at me and expect to get away with it. There's only one way to solve this problem and, unfortunately, I don't have time to do it... and that is to add debugging code to the kernel to do a histogram of the PC of the pushed context at the beginning of the core interrupt code to see which diasble/enable pair is causing the greatest number of latency problems. But, as I said, I don't have the time to do it myself. At the very least, don't close bug reports that I spent hours putting together on an 'assumption'. It's annoying and insulting. It is also annoying and insulting to start quoting missing hardware configurations at me... you know damn well that if every bug report had the hardware configuration detail down to the last transistor they would be mostly useless bug reports because the FreeBSD crew would be spending more time trying to sift through the garbage to locate the meat. This bug report was pretty straight forward. The PCI bus may not be the quickest thing in the world, but 8 microseconds times 8 character slots is still a hellofalong time to start blaming it for interrupt latencies that cause a serial FIFO to overflow. -Matt :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." :"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal : Matthew Dillon Engineering, BEST Internet Communications, Inc. [always include a portion of the original email in any response!] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message