From: Stephen Warren <swarren@wwwdotorg.org>
To: David Henningsson <david.henningsson@canonical.com>
Cc: Mike Travis <travis@sgi.com>, Stephen Warren <swarren@nvidia.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Russ Anderson <rja@sgi.com>
Subject: Re: [PATCH]: x86_64, audio: Fix system panic when DMA > 40 bits
Date: Thu, 02 May 2013 12:20:24 -0600 [thread overview]
Message-ID: <5182AE68.9010905@wwwdotorg.org> (raw)
In-Reply-To: <518205A9.1050409@canonical.com>
On 05/02/2013 12:20 AM, David Henningsson wrote:
> On 05/01/2013 09:04 PM, Mike Travis wrote:
>> The audio driver mistakenly allows 64 bit addresses to be created for
>> the audio driver on Nvidia GPUs. Unfortunately, the hardware normally
>> only supports up to 40 bits of DMA. This can cause system panics as
>> well as misdirected data when the address is > 40 bits as the upper
>> part the address is truncated.
>
> Thanks for this patch. Stephen Warren, is this something you can
> confirm/deny, and do you know what range of hardware this actually
> applies to?
It's certainly plausible that the GPU's internal physical addresses are
less than a full 64-bits, and this probably affects PCI accesses too.
next prev parent reply other threads:[~2013-05-02 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 19:04 [PATCH]: x86_64, audio: Fix system panic when DMA > 40 bits Mike Travis
2013-05-02 6:20 ` David Henningsson
2013-05-02 6:36 ` Mike Travis
2013-05-02 8:29 ` David Henningsson
2013-05-02 16:19 ` Mike Travis
2013-05-03 9:55 ` Takashi Iwai
2013-05-02 18:20 ` Stephen Warren [this message]
2013-05-02 18:59 ` Mike Travis
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=5182AE68.9010905@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rja@sgi.com \
--cc=swarren@nvidia.com \
--cc=tiwai@suse.de \
--cc=travis@sgi.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