https://bugs.freedesktop.org/show_bug.cgi?id=45018
--- Comment #35 from Alex Deucher 2012-03-04 14:30:32 PST
---
(In reply to comment #34)
> Is there a way to disable radeon virtual addressing when loading the kernel?
You can disable it in mesa. Just set ws->info.r600_virtual_address to FALSE
This message contains a list of some post-3.1 regressions introduced before
3.2, for which there are no fixes in the mainline known to the tracking team.
If any of them have been fixed already, please let us know.
If you know of any other unresolved post-3.1 regressions, please let us know
either
https://bugzilla.kernel.org/show_bug.cgi?id=13170
--- Comment #68 from Mikel Pr 2012-03-05 06:07:53 ---
MY apologies. While it does boot now without acpi=off or nosmp/maxcpus=1, only
one core is reported in /proc/cpuinfo and in Ubuntu's system-report option in
12.04.
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=45018
--- Comment #34 from Alexandre Demers
2012-03-04 13:46:48 PST ---
Tested with latest kernel, mesa and drm gits and the problem is still there.
Is there a way to disable radeon virtual addressing when loading the kernel?
I'm sorry to ask, but fr
Hi all,
It looks like many people have switched away from the kernel Bugzilla
after the kernel.org outage and they are using various means of reporting
(and tracking) kernel bugs. For this reason, it's becoming increasingly
difficult for us to track all of the possible sources of reports and we
a
https://bugs.freedesktop.org/show_bug.cgi?id=46660
--- Comment #11 from Vladi 2012-03-04 12:04:55 PST ---
adding radeon.audio=1 to boot parameters fixes the issue on new 3.3 kernel.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail be
https://bugs.freedesktop.org/show_bug.cgi?id=46660
--- Comment #10 from Vladi 2012-03-04 12:00:52 PST ---
New bisect this time marking blank screen on KMS bad gives this as the problem
commit.
805c22168da76a65c978017d0fe0d59cd048e995 is the first bad commit
commit 805c22168da76a65c978017d0fe0d59
https://bugs.freedesktop.org/show_bug.cgi?id=39309
--- Comment #8 from Tom Stellard 2012-03-04 17:39:35 UTC
---
I just tested vdpau on my RV515 and the the videos are displayed mostly green,
but I can see faint outlines of people and objects. It's likely that there are
bugs in the shader compil
https://bugs.freedesktop.org/show_bug.cgi?id=39309
--- Comment #8 from Tom Stellard 2012-03-04 17:39:35
UTC ---
I just tested vdpau on my RV515 and the the videos are displayed mostly green,
but I can see faint outlines of people and objects. It's likely that there are
bugs in the shader compil
https://bugs.freedesktop.org/show_bug.cgi?id=45018
--- Comment #37 from Alex Deucher 2012-03-04 16:24:02 PST ---
(In reply to comment #36)
> I know I can run a 3.2 kernel, I know I can compile a different version or
> bisect or submit patches, I know I can switch from Gnome Shell to another
> win
https://bugs.freedesktop.org/show_bug.cgi?id=45018
--- Comment #36 from Alexandre Demers 2012-03-04
16:06:56 UTC ---
(In reply to comment #35)
> (In reply to comment #34)
> > Is there a way to disable radeon virtual addressing when loading the kernel?
>
> You can disable it in mesa. Just set w
https://bugs.freedesktop.org/show_bug.cgi?id=45018
--- Comment #36 from Alexandre Demers
2012-03-04 16:06:56 UTC ---
(In reply to comment #35)
> (In reply to comment #34)
> > Is there a way to disable radeon virtual addressing when loading the kernel?
>
> You can disable it in mesa. Just set w
https://bugs.freedesktop.org/show_bug.cgi?id=45018
--- Comment #35 from Alex Deucher 2012-03-04 14:30:32 PST ---
(In reply to comment #34)
> Is there a way to disable radeon virtual addressing when loading the kernel?
You can disable it in mesa. Just set ws->info.r600_virtual_address to FALSE i
https://bugs.freedesktop.org/show_bug.cgi?id=45018
--- Comment #34 from Alexandre Demers 2012-03-04
13:46:48 PST ---
Tested with latest kernel, mesa and drm gits and the problem is still there.
Is there a way to disable radeon virtual addressing when loading the kernel?
I'm sorry to ask, but fr
https://bugs.freedesktop.org/show_bug.cgi?id=45018
--- Comment #33 from Harald Judt 2012-03-04 05:38:29 PST ---
Ok, the last gpu lockup has nothing to do with this; it is specific to an
application and occurs on kernel-3.2 too.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?ta
This message contains a list of some post-3.1 regressions introduced before
3.2, for which there are no fixes in the mainline known to the tracking team.
If any of them have been fixed already, please let us know.
If you know of any other unresolved post-3.1 regressions, please let us know
either
Hi all,
It looks like many people have switched away from the kernel Bugzilla
after the kernel.org outage and they are using various means of reporting
(and tracking) kernel bugs. For this reason, it's becoming increasingly
difficult for us to track all of the possible sources of reports and we
a
https://bugs.freedesktop.org/show_bug.cgi?id=45018
--- Comment #32 from Harald Judt 2012-03-04 04:07:31 PST ---
And today an unrecoverable error with 3.3-rc6, forcing a reboot of the machine:
radeon :01:00.0: GPU lockup CP stall for more than 10060msec
GPU lockup (waiting for 0x00026292 last
https://bugs.freedesktop.org/show_bug.cgi?id=46660
--- Comment #11 from Vladi 2012-03-04 12:04:55 PST ---
adding radeon.audio=1 to boot parameters fixes the issue on new 3.3 kernel.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail be
https://bugs.freedesktop.org/show_bug.cgi?id=46660
--- Comment #10 from Vladi 2012-03-04 12:00:52 PST ---
New bisect this time marking blank screen on KMS bad gives this as the problem
commit.
805c22168da76a65c978017d0fe0d59cd048e995 is the first bad commit
commit 805c22168da76a65c978017d0fe0d59
https://bugzilla.kernel.org/show_bug.cgi?id=13170
Mikel Pr changed:
What|Removed |Added
CC||mikeloco14 at gmail.com
--- Comment #67 fr
https://bugs.freedesktop.org/show_bug.cgi?id=45018
--- Comment #33 from Harald Judt 2012-03-04 05:38:29 PST ---
Ok, the last gpu lockup has nothing to do with this; it is specific to an
application and occurs on kernel-3.2 too.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?ta
https://bugs.freedesktop.org/show_bug.cgi?id=45018
--- Comment #32 from Harald Judt 2012-03-04 04:07:31 PST ---
And today an unrecoverable error with 3.3-rc6, forcing a reboot of the machine:
radeon :01:00.0: GPU lockup CP stall for more than 10060msec
GPU lockup (waiting for 0x00026292 last
Hi Daniel,
Thanks for the patch.
On Thu, Mar 01, 2012 at 04:36:01PM +0100, Daniel Vetter wrote:
> Signed-off-by: Daniel Vetter
> ---
> Documentation/dma-buf-sharing.txt | 102 +++-
> 1 files changed, 99 insertions(+), 3 deletions(-)
>
> diff --git a/Documentati
24 matches
Mail list logo
