From: Ian Kumlien <pomac@vapor.com>
To: Richard James <richard@techdrive.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH]
Date: Sat, 08 May 2004 11:22:27 +0200 [thread overview]
Message-ID: <1084008147.2797.93.camel@big> (raw)
In-Reply-To: <409C70CC.7040503@techdrive.com.au>
[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]
On Sat, 2004-05-08 at 07:31, Richard James wrote:
> Ian Kumlien wrote:
>
> >>ASUS have now supplied a BIOS update for the A7N8X-X which fixes the
> >>C1 halt crash. dated the 2004/04/21. So I assume that they will
> >>supply a patch for all nforce2 motherboards.
> >>
> >>
> >
> >you mean the 1009 bios? It doesn't fix anything.
> >I'm using it and:
> >
> >dmesg output:
> >...
> >Asus A7N8X-X detected: BIOS IRQ0 pin2 override will be ignored
> >...
> >PCI: nForce2 C1 Halt Disconnect fixup
> >...
> >
> >(I'm the one that told Len about the new bios that doesn't fix the pin2
> >bug and afair, the C1 Halt Disconnect fix checked for flawed values, ie,
> >this bios dosn't fix anything...)
> >
> >
> Actually you are right I just retested it and my system still locks up.
> I must have done something wrong on the origional testing.
>
> My apologies
Np, the bug is somewhat annoying in that sometimes the machine has to be
running for several days. I updated that bios the same day it was
released.. (i missed the actual upload with some hours)
It only fixes what it says in the change log =P... And i had just been
in contact with them pointing them to information from Allen Martin
about the pin2 that should be pin0 bug and nothing has happened.
Now i have to find where it was that i sent that bugreport again, since
the common "international" support thingy dosn't work, and hasn't for
some time =P.
--
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-08 9:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 7:29 IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] Ian Kumlien
2004-05-08 3:45 ` Richard James
2004-05-08 5:31 ` Richard James
2004-05-08 9:22 ` Ian Kumlien [this message]
2004-05-10 8:49 ` Craig Bradney
-- strict thread matches above, loose matches on Subject: below --
2004-05-10 11:37 Ross Dickson
2004-05-10 12:07 ` Craig Bradney
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
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=1084008147.2797.93.camel@big \
--to=pomac@vapor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@techdrive.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