public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Bill Davidsen <davidsen@tmr.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: Andi Kleen <ak@suse.de>
Subject: Re: Frustrated with Linux, Asus, and nVidia, and AMD
Date: Sat, 28 Oct 2006 22:49:32 -0600	[thread overview]
Message-ID: <454432DC.9030006@shaw.ca> (raw)
In-Reply-To: <fa.i/oIAoig46I/apLGccQ0BesB0W8@ifi.uio.no>

Bill Davidsen wrote:
> 2.6.18 is the latest released kernel, I don't think calling one release 
> back "ancient" is really advancing the solution. The problem seems to 
> have been reported in August, and is still not fixed, I do understand 
> that he would feel there is no progress.
> 
> How long will you wait before putting in the fix Marc Perkel suggested, 
> perhaps with a warning logged that it's a band-aid? Many users will not 
> be astute enough to find this discussion, the bug report, the fix, 
> configure and build a kernel, etc. And not all distributions will 
> address it either.

As far as the "fix" of disabling the skip-ACPI-timer-override, that is 
not something that can be put in the kernel as it will break other 
boards that require the ACPI timer override not to be used (like many 
nForce2 boards for example). Breaking working setups in order to fix 
others isn't acceptable.

There are clearly some NVIDIA chipsets which require the override be 
skipped, and some which require it not be. I think the ball is currently 
in NVIDIA's court to provide a way of figuring out which chipsets 
require the quirk and which don't..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2006-10-29  4:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.nWSYbiDM13Z4b2OlxoSzmqud/lI@ifi.uio.no>
     [not found] ` <fa.NxAEaSXPSQSEviWvGDBmTZn07UE@ifi.uio.no>
     [not found]   ` <fa.i/oIAoig46I/apLGccQ0BesB0W8@ifi.uio.no>
2006-10-29  4:49     ` Robert Hancock [this message]
2006-10-30  2:10       ` Frustrated with Linux, Asus, and nVidia, and AMD Bill Davidsen
2006-10-31 14:28       ` lspci output needed was " Andi Kleen
2006-10-31 16:11         ` Bill Davidsen
2006-11-01 22:17         ` Gerd v. Egidy
2006-10-25  4:55 Marc Perkel
2006-10-25  9:56 ` Oleg Verych
2006-10-25 14:01 ` Lee Revell
2006-10-25 14:51 ` Gianluca Alberici
2006-10-25 18:57 ` Andi Kleen
2006-10-25 19:09   ` Marc Perkel
2006-10-25 20:45     ` Randy Dunlap
2006-10-26 18:05     ` Andi Kleen
2006-10-26 18:31       ` Marc Perkel
2006-10-26 18:42         ` Andi Kleen
2006-10-29  0:30   ` Bill Davidsen

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=454432DC.9030006@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=ak@suse.de \
    --cc=davidsen@tmr.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox