From: Bill Davidsen <davidsen@tmr.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Frustrated with Linux, Asus, and nVidia, and AMD
Date: Sat, 28 Oct 2006 20:30:25 -0400 [thread overview]
Message-ID: <4543F621.4000908@tmr.com> (raw)
In-Reply-To: <p73vem8kyuv.fsf@verdi.suse.de>
Andi Kleen wrote:
> Marc Perkel <marc@perkel.com> writes:
>
>> Ok - I had a bad day today struggling with hardware. Having said that
>> I'm somewhat frustrated with the lack of progress of Linux getting it
>> right with Asus, nVidia, and AMD processors right.
>>
>> I still have to run pci=nommconf to keep the server from locking
>> up. That's with both 939 pin and AM2 motherboards.
>>
>> This bug remains unresolved:
>>
>> http://bugzilla.kernel.org/show_bug.cgi?id=6975
>>
>> So what's up with the no progress?
>
> The bug report only references ancient kernels (2.6.15, 2.6.17) How do you know there is no
> progress?
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.
--
Bill Davidsen <davidsen@tmr.com>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
next prev parent reply other threads:[~2006-10-29 0:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 4:55 Frustrated with Linux, Asus, and nVidia, and AMD 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 [this message]
[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
2006-10-30 2:10 ` 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=4543F621.4000908@tmr.com \
--to=davidsen@tmr.com \
--cc=ak@suse.de \
--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