DragonFly kernel List (threaded) for 2008-11
DragonFly BSD
DragonFly kernel List (threaded) for 2008-11
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

[no subject]


From: Joerg Sonnenberger <joerg@britannica.bec.de>
Mail-Followup-To: kernel@crater.dragonflybsd.org
Subject: Re: Interrupt routing and friends ...
Date: Sun, 9 Nov 2008 14:17:23 +0100
BestServHost: crater.dragonflybsd.org
List-Post: <mailto:kernel@crater.dragonflybsd.org>
List-Subscribe: <mailto:kernel-request@crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:kernel-request@crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:kernel-request@crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-kernel@crater.dragonflybsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
References: <200811041501.00816.hasso@estpak.ee> <1207.> <64fc43b0811080032w5f2836a9g2dfe80cd9859ec8f@mail.gmail.com> <49347.> <20081108182725.GC21559@britannica.bec.de> <4915fcf6$0$882$415eb37d@crater_reader.dragonflybsd.org> <20081108213231.GB21546@britannica.bec.de> <1767.> <491665c4$0$883$415eb37d@crater_reader.dragonflybsd.o
In-Reply-To: <491665c4$0$883$415eb37d@crater_reader.dragonflybsd.org>
Sender: kernel-errors@crater.dragonflybsd.org
Errors-To: kernel-errors@crater.dragonflybsd.org
Lines: 19
X-Trace: 1226237715 crater_reader.dragonflybsd.org 883
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:13233

On Sun, Nov 09, 2008 at 12:23:31PM +0800, Bill Hacker wrote:
> - taking the all-too-ubiquitous Intel ICH7 thru 9 family - (Tyan, Asus,  
> GigaByte Core-D/Core-2 MB), FreeBSD had been erratic to the point of  
> requiring either staying with older releases AND NOT 'STABLE', OR  
> disconnecting from that onboard chipset and moving the drives to  
> SiliconImage add-on controllers. Both PATA and SATA drives.

That sounds more like a bug in the ATA code and not the interrupt

> - Likewise a period where there were problems introduced w/r Broadcom  
> GigE NIC chipsets that had not been problematic in earlier versions.
> - parallel port drivers that did not work were not on our radar  
> (rackmount servers..)

Same for both.


[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]