https://bugs.freedesktop.org/show_bug.cgi?id=39309
--- Comment #10 from Chris Rankin 2012-06-14
12:00:54 PDT ---
I've just tested Mesa -git containing the following commit:
commit eb024c74885778ab1ffa6dc590116959bb526c2e
Author: Christian K?nig
Date: Wed Jun 6 17:53:58 2012 +0200
st/vdp
https://bugzilla.kernel.org/show_bug.cgi?id=43367
Christoph Haag changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
From: Alex Deucher
Not all asics have all rings, so make sure the ring is ready
before attempting to check it in the dynpm work handler.
Fixes:
https://bugzilla.kernel.org/show_bug.cgi?id=43367
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/radeon_pm.c | 10 +++---
1 files chang
On Thu, Jun 14, 2012 at 3:54 PM, wrote:
> From: Alex Deucher
>
> Not all asics have all rings, so make sure the ring is ready
> before attempting to check it in the dynpm work handler.
>
> Fixes:
> https://bugzilla.kernel.org/show_bug.cgi?id=43367
>
> Signed-off-by: Alex Deucher
Reviewed-by: Je
From: Alex Deucher
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/atombios_crtc.c | 10 -
drivers/gpu/drm/radeon/si_reg.h| 72
2 files changed, 81 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/radeon/atombios_crtc.c
b/drive
This reverts commit 092945e11c5b84f66dd08f0b87fb729715d377bc.
This commit prevents a DP screen from properly training the link.
Oddly enough it works, once the machine has been warm-boot with an
older kernel.
According to DP docs this _should_ have been the right precharge time.
Also, the commit
From: Alex Deucher
- SMX_SAR_CTL0 needs to be programmed correctly to prevent
problems with memory exports in certain cases.
- VC_ENHANCE needs to be initialized on 6xx/7xx.
Signed-off-by: Alex Deucher
Cc: stable at vger.kernel.org
---
drivers/gpu/drm/radeon/evergreen.c |3 +++
drivers/gp
From: Alex Deucher
Required for streamout. Bump drm minor.
Marek v2: fix pkt->count check
Signed-off-by: Alex Deucher
Signed-off-by: Marek Ol??k
---
drivers/gpu/drm/radeon/r600_cs.c| 42 +++
drivers/gpu/drm/radeon/r600d.h |1 +
drivers/gpu/drm/
https://bugs.freedesktop.org/show_bug.cgi?id=39309
--- Comment #11 from Christian K?nig 2012-06-14
13:13:03 PDT ---
Sorry, I should have written "partially fixes..". It only fixes the crash, not
the playback problems.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
-
This reverts commit 092945e11c5b84f66dd08f0b87fb729715d377bc.
This commit prevents a DP screen from properly training the link.
Oddly enough it works, once the machine has been warm-booted with an
older kernel.
According to DP docs this _should_ have been the right precharge time.
Also, the commi
On 14.06.2012 21:54, alexdeucher at gmail.com wrote:
> From: Alex Deucher
>
> Not all asics have all rings, so make sure the ring is ready
> before attempting to check it in the dynpm work handler.
>
> Fixes:
> https://bugzilla.kernel.org/show_bug.cgi?id=43367
>
> Signed-off-by: Alex Deucher
Review
Imagine two threads read()'ing on the drm file and both are asleep waiting
for events in drm_read(). If a single event occurs, both threads are woken
up and start fetching the event. One thread will get it and return, the
other thread will notice that there is no further event and return 0 to
user-
, 81 insertions(+), 1 deletions(-)
[?]
Thanks,
Paul
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.freedesktop.org/archives/dri-de
hy your mailer strips the spaces in front of the
?http://lists.freedesktop.org/archives/dri-devel/attachments/20120614/9a2f1afb/attachment.pgp>
On 14.06.2012 22:35, Paul Menzel wrote:
> Dear Christian,
>
>
> Am Donnerstag, den 14.06.2012, 22:17 +0200 schrieb Christian K?nig:
>> On 14.06.2012 21:54, alexdeucher at gmail.com wrote:
>>> From: Alex Deucher
>^
>
>>> Not all asics have all rings, so make sure the ring is
>
> Message: 2
> Date: Thu, 14 Jun 2012 17:19:11 + (UTC)
> From: Joakim Plate
> Subject: Re: RFC: Change OML_sync_control UST to CLOCK_MONOTONIC
> To: dri-devel at lists.freedesktop.org
> Message-ID:
> Content-Type: text/plain; charset=us-ascii
>
>
>>>
>>> From what I can tell, it should
https://bugs.freedesktop.org/show_bug.cgi?id=36602
Harald Judt changed:
What|Removed |Added
CC||h.judt at gmx.at
--- Comment #48 from Hara
https://bugs.freedesktop.org/show_bug.cgi?id=44772
--- Comment #8 from Harald Judt 2012-06-14 15:02:10 PDT ---
Still reproducible with 3.4.0 final and "drm/radeon: fix vm deadlocks on
cayman" applied, but at least I do not experience freezes anymore.
--
Configure bugmail: https://bugs.freedeskt
https://bugs.freedesktop.org/show_bug.cgi?id=49943
--- Comment #4 from Harald Judt 2012-06-14 15:14:51 PDT ---
Ok, tried again with 3.4.0 final.
First, no HDMI monitor connected:
Evergreen HDMI regs:
0x601c 0x (0)
0x6028 0x050ff012 (84930578)
0x6034 0x0012 (18)
0x6040 0x
https://bugs.freedesktop.org/show_bug.cgi?id=49943
--- Comment #5 from Alex Deucher 2012-06-14 15:20:27 PDT
---
Can you see if the hw is still generating interrupts? Enable drm debugging
(boot with drm.debug=1 on the kernel command line in grub or as root:
echo 1 > /sys/module/drm/parameters/de
https://bugs.freedesktop.org/show_bug.cgi?id=49943
--- Comment #6 from Harald Judt 2012-06-14 16:09:16 PDT ---
Yes, the computer prints these everytime I plug or unplug the HDMI monitor:
[drm:evergreen_irq_process], IH: HPD6
There are exactly 6 such messages to be found in dmesg, that would exa
https://bugs.freedesktop.org/show_bug.cgi?id=49943
--- Comment #7 from Alex Deucher 2012-06-14 16:44:11 UTC
---
ok, so the hw is working fine, the event is just not getting propagated to
userspace properly. Might be a duplicate of bug 51042.
--
Configure bugmail: https://bugs.freedesktop.org/
On 06/14/2012 03:48 PM, Wouter M. Koolen wrote:
> In the mean while I will redo the bisect.
Hi guys,
I did a bisect on the actual problem (and not on the maybe-related
second error message). It results in
092945e11c5b84f66dd08f0b87fb729715d377bc:
Author: Adam Jackson 2011-07-26 20:39:45
Comm
On 06/14/2012 06:27 PM, Daniel Vetter wrote:
> Well, can you revert this patch (or just replace the 5 with 3 in the
> code) on top of latest 3.4.x and test whether this is indeed the cause
> of your regression? Just to make sure that we have the right culprit.
Hi Daniel,
Yes, 3.4.2 with 092945e11c
201 - 224 of 224 matches
Mail list logo