From owner-freebsd-current@FreeBSD.ORG  Fri Jun 25 16:26:31 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 6573A16A4CE; Fri, 25 Jun 2004 16:26:31 +0000 (GMT)
Received: from mail.sandvine.com (sandvine.com [199.243.201.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 8965543D39; Fri, 25 Jun 2004 16:26:30 +0000 (GMT)
	(envelope-from gnagelhout@sandvine.com)
Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72)
	id <MTR291DG>; Fri, 25 Jun 2004 12:25:52 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337054EC4CF@mail.sandvine.com>
From: Gerrit Nagelhout <gnagelhout@sandvine.com>
To: 'John Baldwin' <jhb@FreeBSD.org>, freebsd-current@FreeBSD.org
Date: Fri, 25 Jun 2004 12:25:51 -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 <julian@elischer.org>
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jun 2004 16:26:31 -0000

John Baldwin wrote:
> 
> This is why it isn't receiving interrupts.  It thinks one is 
> still being 
> serviced and is waiting on the EOI.   That is IPI_HARDCLOCK again.
> Hmm, try this hack (you can turn idle_hlt back on if you want 
> since it doesn't 
> seem to have an effect):
> 
> Index: intr_machdep.c
> ===================================================================
> RCS file: /usr/cvs/src/sys/i386/i386/intr_machdep.c,v
> retrieving revision 1.6
> diff -u -r1.6 intr_machdep.c
> --- intr_machdep.c	28 May 2004 17:50:07 -0000	1.6
> +++ intr_machdep.c	25 Jun 2004 15:42:00 -0000
> @@ -184,6 +184,10 @@
>  		clkintr_pending = 1;
>  
>  	if (ih != NULL && ih->ih_flags & IH_FAST) {
> +#if 1
> +		isrc->is_pic->pic_disable_source(isrc);
> +		isrc->is_pic->pic_eoi_source(isrc);
> +#endif
>  		/*
>  		 * Execute fast interrupt handlers directly.
>  		 * To support clock handlers, if a handler registers
> @@ -202,7 +206,11 @@
>  			else
>  				ih->ih_handler(ih->ih_argument);
>  		}
> +#if 0
>  		isrc->is_pic->pic_eoi_source(isrc);
> +#else
> +		isrc->is_pic->pic_disable_source(isrc);
> +#endif
>  		error = 0;
>  		critical_exit();
>  	} else {
> 
> -- 
> John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
> "Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
> 

This patch seems to have broken something with the aac driver.
I get the following message over and over on bootup:

aac0: COMMAND 0xca593a14 TIMEOUT AFTER 40 SECONDS
aac0: COMMAND 0xca593a8c TIMEOUT AFTER 40 SECONDS
aac0: COMMAND 0xca593b04 TIMEOUT AFTER 40 SECONDS
aac0: COMMAND 0xca593b7c TIMEOUT AFTER 40 SECONDS
aac0: COMMAND 0xca593bf4 TIMEOUT AFTER 40 SECONDS
aac0: COMMAND 0xca593c6c TIMEOUT AFTER 40 SECONDS
aac0: COMMAND 0xca593ce4 TIMEOUT AFTER 40 SECONDS
aac0: COMMAND 0xca593d5c TIMEOUT AFTER 40 SECONDS
aac0: COMMAND 0xca593dd4 TIMEOUT AFTER 40 SECONDS
aac0: COMMAND 0xca593e4c TIMEOUT AFTER 40 SECONDS
aac0: COMMAND 0xca593ec4 TIMEOUT AFTER 40 SECONDS

Thanks,

Gerrit