RE: ACPI interrupt storm (was Re: Linux 2.4.21rc6-ac1)

[Grover, Andrew]

I suspect this machine should be falling into one of the cases before
this last one, thus making ACPI not use C3, or check for bus-mastering.
I especially think this is the case because this appears to be a desktop
system. It should not have a C3 address or a plvl3_lat less than 1000,
yet it appears to, yes?

Regards -- Andy

> -----Original Message-----
> From: Zwane Mwaikambo [mailto:[e-mail]] 
> Sent: Sunday, June 01, 2003 12:23 AM
> To: Con Kolivas
> Cc: Paul P Komkoff Jr; [e-mail]
> Subject: Re: ACPI interrupt storm (was Re: Linux 2.4.21rc6-ac1)
> Importance: High
> 
> 
> On Sun, 1 Jun 2003, Con Kolivas wrote:
> 
> > I get the same problem here with acpi-20030522 applied to rc6
> > P4 2.53 on an i845 mobo (P4PE).
> 
> I think it could be the Bus Mastering event monitoring thing, can you 
> shoehorn this (HACK HACK) patch into 2.4?
> 
> Index: linux-2.5.70-mm1/drivers/acpi/processor.c
> ===================================================================
> RCS file: /build/cvsroot/linux-2.5.70/drivers/acpi/processor.c,v
> retrieving revision 1.1.1.1
> diff -u -p -B -r1.1.1.1 processor.c
> --- linux-2.5.70-mm1/drivers/acpi/processor.c	27 May 2003 
> 02:19:28 -0000	1.1.1.1
> +++ linux-2.5.70-mm1/drivers/acpi/processor.c	29 May 2003 
> 11:32:00 -0000
> @@ -711,11 +711,13 @@ acpi_processor_get_power_info (
>  		 * use this in our C3 policy.
>  		 */
>  		else {
> +			goto done;
>  			pr->power.states[ACPI_STATE_C3].valid = 1;
>  			pr->power.states[ACPI_STATE_C3].latency_ticks = 
>  				
> US_TO_PM_TIMER_TICKS(acpi_fadt.plvl3_lat);
>  			pr->flags.bm_check = 1;
>  		}
> +		done:
>  	}
>  
>  	/*
> -- 
> function.linuxpower.ca
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to [e-mail]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>