public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alistair J Strachan <alistair@devzero.co.uk>
To: "Trever L. Adams" <tadams-lists@myrealbox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0test4 ACPI with nForce2 success
Date: Mon, 25 Aug 2003 19:21:51 +0100	[thread overview]
Message-ID: <200308251921.51305.alistair@devzero.co.uk> (raw)
In-Reply-To: <1061834424.2599.2.camel@aurora.localdomain>

On Monday 25 August 2003 19:00, Trever L. Adams wrote:
> I have been one of these people who have been having to boot with
> pci=noacpi to get up with much of my hardware initialized.  My system is
> now working without it.  It isn't getting shutoff on irq storms or
> anything.

Likewise, my EPoX 8RDA+ board is working 100% perfectly since the nforce2-apic 
fixes were merged in -mm. No spurious interrupts, no weird ACPI glitches, 
everything from power management to PCI IRQ routing is just fine.

I'm still not sure I understand the local apic lockups experienced by others, 
but anybody considering the purchase of an nForce 2 board can probably put 
their mind to rest.

>
> My only possible problem is this:
>
>  13:59:40  up 8 min,  3 users,  load average: 0.86, 0.81, 0.36
>            CPU0
>   0:     516847          XT-PIC  timer

With the 1000Hz timer in linux 2.6, I'd guess your PC had been up for 
516847/1000/60 = 8.61 minutes.. Oh, look!

>
> I am not sure how fast the irq's for the timer should be going up.  So,
> that may be an issue.
>

Evidently not.

Cheers,
Alistair.

  parent reply	other threads:[~2003-08-25 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25 18:00 2.6.0test4 ACPI with nForce2 success Trever L. Adams
2003-08-25 18:14 ` Richard B. Johnson
2003-08-25 18:21 ` Alistair J Strachan [this message]
2003-08-26  5:27   ` 2.6.0test4 ACPI with nForce2 "success" Resident Boxholder

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=200308251921.51305.alistair@devzero.co.uk \
    --to=alistair@devzero.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tadams-lists@myrealbox.com \
    /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