public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard James <richard@techdrive.com.au>
To: Ian Kumlien <pomac@vapor.com>, linux-kernel@vger.kernel.org
Subject: Re: IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH]
Date: Sat, 08 May 2004 15:31:56 +1000	[thread overview]
Message-ID: <409C70CC.7040503@techdrive.com.au> (raw)
In-Reply-To: <1083914992.2797.82.camel@big>

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

Richard James


  parent reply	other threads:[~2004-05-08  5:32 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 [this message]
2004-05-08  9:22   ` Ian Kumlien
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=409C70CC.7040503@techdrive.com.au \
    --to=richard@techdrive.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pomac@vapor.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