mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Craig Bradney <cbradney@zip.com.au>
To: Peter Clifton <pcjc2@cam.ac.uk>
Cc: linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>,
	"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	ross@datscreative.com.au
Subject: Re: IO-APIC on nforce2 [PATCH]
Date: Thu, 15 Apr 2004 02:29:57 +0200	[thread overview]
Message-ID: <1081988997.4724.2.camel@amilo.bradney.info> (raw)
In-Reply-To: <1081989304.7831.8.camel@pcjc2>

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

On Thu, 2004-04-15 at 02:35, Peter Clifton wrote:
> Sorry Christian, meant to send to the list rather than just you.
> 
> I'm watching this thread with interest, I've got an ASUS A7N8X board,
> and have had annoying lockups with most kernels I've compiled myself
> from 2.4 upwards. Some luck caused me to try turning APIC off, and the
> system hasn't crashed since.
> 
> Is there any reason why turning APIC off reduces performance?
> 
> I'd be happy to provide another person to test patches (with the proviso
> that if you want detailed debugging information, you'd have to suggest
> how to obtain it, since when it locks up, it tends to lock good!)
> 
> I'm currently running 2.6.3-gentoo-r1 (Although I can't see a list of
> what patches they have already applied).
> 
> I'd be happy to try a vanilla kernel with whatever patches if that would
> help out solving the problem.

Peter, I have 2.6.3gentoo r1 on my box with a A7N8X Deluxe v2 with Ross
Dicksons 2.6.3 idlec1halt patches and its as stable as a rock. I've left
it on that kernel as there are still many discussions recently posted re
2.6.5. My 3 other PCs are on gentoo dev source 2.6.5 and are solid, but
I've left the Athlon on 2.6.3 due to the fact its working just fine now

Craig

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-04-15  0:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14 21:01 Christian Kröner
2004-04-15  0:35 ` Peter Clifton
2004-04-15  0:29   ` Craig Bradney [this message]
2004-04-15  0:41 ` Ross Dickson
  -- strict thread matches above, loose matches on Subject: below --
2004-04-23  1:23 Allen Martin
2004-04-23 15:39 ` Maciej W. Rozycki
2004-04-16 16:41 Allen Martin
2004-04-15 18:33 Allen Martin
2004-04-15 19:20 ` Craig Bradney
2004-04-15 19:50 ` Len Brown
2004-04-16  8:27   ` Jamie Lokier
2004-04-22  4:00     ` Len Brown
2004-04-22 13:22       ` Maciej W. Rozycki
2004-04-22 13:53         ` Christian Kröner
2004-04-22 15:27           ` Len Brown
2004-04-22 15:40             ` Maciej W. Rozycki
2004-04-22 16:15             ` Christian Kröner
2004-04-13  1:17 IO-APIC on nforce2 Ross Dickson
2004-04-13  5:08 ` Len Brown
2004-04-13  7:03   ` Ross Dickson
2004-04-14  1:02     ` IO-APIC on nforce2 [PATCH] Len Brown
2004-04-14  5:02       ` Ross Dickson
2004-04-14  6:30         ` Jamie Lokier
2004-04-14 10:37         ` Maciej W. Rozycki
2004-04-15 19:28           ` Len Brown
2004-04-14 19:57         ` Christian Kröner
2004-04-15  0:17           ` Len Brown
2004-04-15  1:48             ` Ross Dickson
2004-04-15 17:09               ` Christian Kröner
2004-04-15 15:21       ` 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=1081988997.4724.2.camel@amilo.bradney.info \
    --to=cbradney@zip.com.au \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=pcjc2@cam.ac.uk \
    --cc=ross@datscreative.com.au \
    /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

Powered by JetHome