From owner-freebsd-current@FreeBSD.ORG Wed Jun 30 15:04:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AFC316A4CE; Wed, 30 Jun 2004 15:04:45 +0000 (GMT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C89243D46; Wed, 30 Jun 2004 15:04:44 +0000 (GMT) (envelope-from gnagelhout@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Wed, 30 Jun 2004 11:04:21 -0400 Message-ID: From: Gerrit Nagelhout To: 'John Baldwin' , freebsd-current@FreeBSD.org Date: Wed, 30 Jun 2004 11:04:20 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" cc: kris@FreeBSD.org cc: Julian Elischer Subject: RE: STI, HLT in acpi_cpu_idle_c1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2004 15:04:45 -0000 John Baldwin wrote: > As per an errata that Brian pointed out, try using this patch > perhaps. You > can leave your isr_problem one in and hopefully the counter > will stay at zero > if it works. It adds some dummy reads of the local APIC to > EOI's for IPIs. > This patch doesn't seem to help any. My isr problem detection code still found a problem 10 times in about 17 hours of stress testing. I know that the HACK I added to make the system work is probably incorrect, but what kind of side effects would you expect to see from just calling EOI, and possibly not handling the interrupt? Thanks, Gerrit