Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Apr 2005 15:15:36 -0700 (PDT)
From:      Doug White <dwhite@gumbysoft.com>
To:        "Wilhelm B. Kloke" <wb@arb-phys.uni-dortmund.de>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Potential source of interrupt aliasing
Message-ID:  <20050410151401.O82708@carver.gumbysoft.com>
In-Reply-To: <slrnd5hrd2.1co6.wb@yorikke.arb-phys.uni-dortmund.de>
References:  <20050406233405.O47071@carver.gumbysoft.com> <200504081656.51917.jhb@FreeBSD.org> <slrnd5hrd2.1co6.wb@yorikke.arb-phys.uni-dortmund.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 10 Apr 2005, Wilhelm B. Kloke wrote:

> Doug White <dwhite@gumbysoft.com> schrieb:
> > On Fri, 8 Apr 2005, John Baldwin wrote:
> >
> > For fun, I put together this one-liner to at least test the theory:
> >
> > http://people.freebsd.org/~dwhite/intr_machdep.c.20050409.patch
>
> As I have found a problem which could be related to this, I tried your patch.
> For my problems, it made things not better, possibly worse.

Don't use my patch. It will cause lockups under load.

I suspect that the underlying issue is related to storming issues in PIC
mode, but I'd rather try to fix it in APIC mode first.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050410151401.O82708>