From: Jamie Lokier <jamie@shareable.org>
To: Attila BODY <compi@freemail.hu>
Cc: linux-kernel@vger.kernel.org, Richard James <richard@techdrive.com.au>
Subject: Re: BUG: nforce IDE DMA with APIC enabled bug has re-emerged Kernel 2.6.4
Date: Sat, 3 Apr 2004 23:47:41 +0100 [thread overview]
Message-ID: <20040403224741.GC6122@mail.shareable.org> (raw)
In-Reply-To: <1081031766.1026.499.camel@smiley.localnet>
Attila BODY wrote:
> Can anyone enlighten me why isn't it merged to the mainstream kernel
> yet? I've found lots of people with the same problems while searching
> for the solution to mine, so it seems a common problem with some nforce2
> motherboards.
Perhaps because Ross Dickson's patches seem to fix the problem without
disabling those power saving & temperature reducing features. But
there is no consensus yet, so you might want to try out his current
patches to see if they solve your problem, and give feedback.
-- Jamie
next prev parent reply other threads:[~2004-04-03 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 22:36 BUG: nforce IDE DMA with APIC enabled bug has re-emerged Kernel 2.6.4 Attila BODY
2004-04-03 22:47 ` Jamie Lokier [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-03 3:15 Richard James
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=20040403224741.GC6122@mail.shareable.org \
--to=jamie@shareable.org \
--cc=compi@freemail.hu \
--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