public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Paul P Komkoff Jr <i@stingr.net>,
	"" <linux-kernel@vger.kernel.org>,
	"Grover, Andrew" <andrew.grover@intel.com>
Subject: Re: ACPI interrupt storm (was Re: Linux 2.4.21rc6-ac1)
Date: Tue, 3 Jun 2003 23:00:52 +1000	[thread overview]
Message-ID: <200306032300.52084.kernel@kolivas.org> (raw)
In-Reply-To: <Pine.LNX.4.50.0306010322290.2614-100000@montezuma.mastecende.com>

On Sun, 1 Jun 2003 17:23, Zwane Mwaikambo wrote:
> 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:
>  	}
>
>  	/*

Ok I tried this hack. 

Here is vmstat before:
procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
 0  0      0 494640   4088   6628    0    0     0   240 82011    34  0  1 99  
and after:
procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
 0  0      0 494700   4052   6608    0    0     0   136 82182    32  0  1 99  

so it managed to give me another 100 or so interrupts on top of the 80k I was 
already getting; ie not much help
at about the same time I got a minor file system corruption but too many 
things happened together so I'm really not sure what that was.

Con


  reply	other threads:[~2003-06-03 12:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-31 11:53 Linux 2.4.21rc6-ac1 Alan Cox
2003-05-31 12:25 ` Gutko
2003-05-31 20:50 ` Andreas Haumer
2003-06-01  7:23   ` ACPI interrupt storm (was Re: Linux 2.4.21rc6-ac1) Paul P Komkoff Jr
2003-06-01  7:31     ` Con Kolivas
2003-06-01  7:23       ` Zwane Mwaikambo
2003-06-03 13:00         ` Con Kolivas [this message]
2003-06-01  6:05 ` Linux 2.4.21rc6-ac1 Udo Hoerhold
2003-06-01 11:50   ` Alan Cox
2003-06-01 22:44     ` Udo Hoerhold
2003-06-01 11:45 ` Krzysiek Taraszka
2003-06-01 21:08 ` [patch] 2.4.21rc6-ac1: More IDE Makefile fixes Adrian Bunk
2003-06-02 15:49 ` Linux 2.4.21rc6-ac1 Andreas Haumer
2003-06-03 15:28 ` [patch] 2.4.21rc6-ac1: fix pc300_drv.c .text.exit Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2003-06-02 21:01 ACPI interrupt storm (was Re: Linux 2.4.21rc6-ac1) Grover, Andrew
2003-06-03  0:12 ` Con Kolivas
2003-06-03  2:01   ` Con Kolivas
2003-06-03  4:03     ` Zwane Mwaikambo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200306032300.52084.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=andrew.grover@intel.com \
    --cc=i@stingr.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox