From: Jesse Allen <the3dfxdude@hotmail.com>
To: Craig Bradney <cbradney@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay.
Date: Thu, 12 Feb 2004 16:37:52 -0700 [thread overview]
Message-ID: <20040212233752.GA1479@tesore.local> (raw)
In-Reply-To: <1076627706.16600.20.camel@athlonxp.bradney.info>
On Fri, Feb 13, 2004 at 12:15:06AM +0100, Craig Bradney wrote:
> On Fri, 2004-02-13 at 00:04, Jesse Allen wrote:
> > vanilla kernels = 2.6.0-test11 through 2.6.3-rc2 and no patches. APIC is
> > on.
>
> and local APIC and ACPI?
Yes.
> > 12-5-2003 BIOS:
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=107124823504332&w=2
> >
> > not lock up:
> > I could reproduce the lockup consistantly. With the 12-5-2003 bios, I
> > cannot. Two months have passed since the original report.
>
> If thats the case you are a lucky person!
I know =)
> > I don't know how to identify a fix from my bioses. If someone has any
> > clue, I will help out.
>
> No idea either.. but the "uber bios"
> (http://homepage.ntlworld.com/michael.mcclay/)
> guy might be able to help some of us out if the changes were found... if
> you trust someone other than your motherboard manufacturer writing
> BIOSes.. but I guess thats the same as any OS project in some ways.
>
What we need is a kernel patch, because it will be difficult to produce bios
fixes for each bios iteration. If he can identify what the changes are in my
bios and identify a bug, then a sufficiently talented kernel hacker can produce
the work-around for other buggy bioses.
Jesse
next prev parent reply other threads:[~2004-02-12 23:35 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 15:22 [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay Ross Dickson
2004-02-12 18:17 ` Derek Foreman
2004-02-12 16:11 ` Daniel Drake
2004-02-12 19:30 ` [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaroundinstead " Carlos Silva
2004-02-12 19:54 ` [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead " Derek Foreman
2004-02-12 21:44 ` Jesse Allen
2004-02-12 21:52 ` Derek Foreman
2004-02-12 22:06 ` Craig Bradney
2004-02-12 23:04 ` Jesse Allen
2004-02-12 23:15 ` Craig Bradney
2004-02-12 23:37 ` Jesse Allen [this message]
2004-02-12 23:50 ` Craig Bradney
2004-02-12 23:20 ` Roberto Sanchez
2004-02-13 11:17 ` Prakash K. Cheemplavam
2004-02-13 14:41 ` Ross Dickson
2004-02-13 15:55 ` Nforce2, APIC, CPU Disconnect and setup_boot_APIC_clock() cheuche+lkml
2004-02-14 1:24 ` [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay Ross Dickson
2004-02-14 4:46 ` GCC feature request: warn on "if (function_name)" Jamie Lokier
2004-02-14 4:51 ` Andrew Pinski
2004-02-14 11:16 ` [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay Prakash K. Cheemplavam
2004-02-14 16:13 ` Ross Dickson
2004-02-14 21:46 ` Ian Kumlien
2004-02-23 1:33 ` Prakash K. Cheemplavam
2004-02-23 19:50 ` Jesse Allen
2004-02-23 1:37 ` Prakash K. Cheemplavam
2004-02-25 12:38 ` Ross Dickson
2004-02-25 19:49 ` Prakash K. Cheemplavam
2004-02-25 21:44 ` Arjen Verweij
2004-02-26 0:13 ` Ross Dickson
2004-02-26 9:59 ` Mikael Pettersson
2004-03-07 14:46 ` Craig Bradney
2004-03-08 22:42 ` Arjen Verweij
2004-03-08 22:59 ` Craig Bradney
2004-03-08 23:11 ` Arjen Verweij
2004-03-14 12:04 ` Arjen Verweij
2004-03-09 18:38 ` Josh McKinney
2004-03-24 15:59 ` Edd Dumbill
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=20040212233752.GA1479@tesore.local \
--to=the3dfxdude@hotmail.com \
--cc=cbradney@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.