From: Craig Bradney <cbradney@zip.com.au>
To: ross@datscreative.com.au
Cc: Ian Kumlien <pomac@vapor.com>,
linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>,
a.verweij@student.tudelft.nl,
"Prakash K. Cheemplavam" <PrakashKC@gmx.de>,
christian.kroener@tu-harburg.de,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Jamie Lokier <jamie@shareable.org>,
Daniel Drake <dan@reactivated.net>,
Allen Martin <AMartin@nvidia.com>
Subject: Re: IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH]
Date: Mon, 10 May 2004 14:07:02 +0200 [thread overview]
Message-ID: <1084190822.8242.46.camel@amilo.bradney.info> (raw)
In-Reply-To: <200405102137.11468.ross@datscreative.com.au>
[-- Attachment #1: Type: text/plain, Size: 1965 bytes --]
On Mon, 2004-05-10 at 13:37, Ross Dickson wrote:
> Craig Bradney wrote
>
> >Well.. 2.6.6 is released.. and THANK YOU Linus and all the patch
> > writers.. we have nforce2 fixes in the released kernel now. I'm just
> > waiting for a gentoo-dev-sources release now..
> >
> >
> >
> >Craig
>
> MOMENT PLEASE.
> ALMOST complete nforce2 support. Job not done yet.
I was waiting for that...
> Unfortunately 2.6.6 still has the old check_timer code which inhibits
> nmi_watchdog=1 on all nforce2 from working by having timer_ack=1
> when checking io-apic pit routing.
>
> It is a hardware issue - NOT A BUGGY BIOS ISSUE inside the integrated
> nforce2 interrupt routing.
>
> To my understanding IT WILL NEVER BE FIXED BY A BIOS REVISION and
> after reading the 8259 datasheets I think it is a mistake within the
> existing code to have the timer_ack on there in the first place.
>
> I would still like to see Maciej's check_timer patch in the kernel. It was
> pulled after only a single user mobo complaint was posted yet it helps
> both nforce2 and ibm bios pc's. To my knowledge little effort was made
> by that user to accomodate the patch - it was just outright pulled in spite
> of its benefit to others?
>
> Who do we ask to revisit this? Linus? the io-apic.c maintainer? or the one
> user with a complaint?
>
> That patch that was dropped by Linus? after appearing in 2.6.3-mm3.
> For those nforce2 users with problems of clock skew with the timer into pin0
> routing, that patch gave a virtual wire timer routing which worked well.
Why was it dropped?
> It also works around serious problems for ibm users who also want it in.
> http://linux.derkeiler.com/Mailing-Lists/Kernel/2004-04/4421.html
It looks like theres IDE caching problems with the new flushing
mechanism on Maxtor 8mb cache drives.. of which I have 2, so, looks like
I'm awaiting 2.6.7 now anyway or a patch to remove it.
Craig
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-10 12:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 11:37 IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] Ross Dickson
2004-05-10 12:07 ` Craig Bradney [this message]
2004-05-10 12:22 ` Ian Kumlien
2004-05-10 15:05 ` Arjen Verweij
2004-05-10 16:04 ` Ian Kumlien
2004-05-10 17:39 ` Ian Kumlien
2004-05-24 16:10 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2004-05-07 7:29 Ian Kumlien
2004-05-08 3:45 ` Richard James
2004-05-08 5:31 ` Richard James
2004-05-08 9:22 ` Ian Kumlien
2004-05-10 8:49 ` Craig Bradney
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=1084190822.8242.46.camel@amilo.bradney.info \
--to=cbradney@zip.com.au \
--cc=AMartin@nvidia.com \
--cc=PrakashKC@gmx.de \
--cc=a.verweij@student.tudelft.nl \
--cc=christian.kroener@tu-harburg.de \
--cc=dan@reactivated.net \
--cc=jamie@shareable.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=pomac@vapor.com \
--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