_64
Mesa-libglapi0-32bit-9.2.3-316.2.x86_64
Mesa-demo-x-8.1.0-31.1.x86_64
Mesa-32bit-9.2.3-316.2.x86_64
Mesa-devel-9.2.3-316.2.x86_64
Mesa-libGLESv2-2-9.2.3-316.2.x86_64
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attach
On both v3.13-rc1 and v3.13-rc2 is see this at every boot and during
every suspend and resume cycle:
<4>[2.682468] WARNING: CPU: 0 PID: 173 at
drivers/gpu/drm/i915/intel_display.c:9948
intel_get_pipe_from_connector+0x42/0x50 [i915]()
<5>[2.682470] Modules linked in: i915(F+) ata_generic(
On Sat, Nov 30, 2013 at 05:31:34PM +0100, Jan Engelhardt wrote:
>
> On Friday 2013-11-29 11:48, Chris Wilson wrote:
> >> What I could collect so far:
> >
> >Thanks, I broke the handling of cropped XvImages along the fast paths.
> >It should be fixed by:
> >
> >commit fd007d9d465b9b3ddbbaf769931ec9
this register was incorrect for evergreen and cayman.
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/radeon/radeon_drv.h | 3 ++-
drivers/gpu/drm/radeon/reg_srcs/cayman| 2 +-
drivers/gpu/drm/radeon/reg_srcs/evergreen | 2 +-
3 files changed, 4 insertions(+), 3 deletions(-)
diff --git
On Friday 2013-11-29 11:48, Chris Wilson wrote:
>> What I could collect so far:
>
>Thanks, I broke the handling of cropped XvImages along the fast paths.
>It should be fixed by:
>
>commit fd007d9d465b9b3ddbbaf769931ec921a6f5ecb8
>Author: Chris Wilson
>Date: Thu Nov 28 21:13:33 2013 +
>
>
With commit b4aa0163056b6c70029b6e8619ce07c274351f42 Matthew Garret
introduced a efifb vga_default_device() so that EFI systems that do not
load shadow VBIOS or setup VGA get proper value for boot_vga PCI sysfs
attribute on the corresponding PCI device.
Xorg is refusing to detect devices when boot
Hi all,
How about moving this discussion to other related email thread,
"[PATCH v3 31/32] drm/exynos: Move lvds bridge discovery into DP
driver"? lvds related codes have already been removed from this patch
and moved into eDP bus driver. It would be more good to make a
dicussion about actual codes
Hi Tomasz,
Thanks for review,
2013/11/30 Tomasz Figa :
> Hi Sean,
>
> On Tuesday 29 of October 2013 12:13:17 Sean Paul wrote:
>> This patch moves the lvds bridge discovery and connector pre-emption
>> code from exynos common code into the dp driver (since the bridge is
>> only applicable for dp)
On 29/11/13 14:36, Ville Syrj?l? wrote:
> On Wed, Nov 06, 2013 at 01:46:41PM +1000, Dave Airlie wrote:
>> On Wed, Oct 30, 2013 at 4:06 AM, wrote:
>>> So I took another look at the vblank timestamping code, and got a bit
>>> excited. The result is this patchset.
>>
>> I'd like to merge this, I was
iving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131130/f07f3c59/attachment.html>
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131130/5b392ab4/attachment.html>
d and powering down
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131130/469617c7/attachment.html>
ubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131130/26b457f9/attachment.html>
eroff branch when I do
a switcheroo OFF then ON with runpm=0
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131130/9a00332a/attachment.html>
Hi Inki,
On Saturday 30 of November 2013 14:18:08 Inki Dae wrote:
> Hi Tomasz,
>
> Thanks for review,
You're welcome.
>
> 2013/11/30 Tomasz Figa :
> > Hi Sean,
> >
> > On Tuesday 29 of October 2013 12:13:17 Sean Paul wrote:
> >> This patch moves the lvds bridge discovery and connector pre-empt
ts.freedesktop.org/archives/dri-devel/attachments/20131130/5410935f/attachment.html>
Hi
On Wed, Nov 27, 2013 at 9:24 PM, Paulo Zanoni wrote:
> From: Paulo Zanoni
>
> Sometimes we want to disable all the screens on a system, because that
> will allow the graphics card to be put into low-power states. The
> problem is that, for example, while all screens are disabled, if we
> get
https://bugzilla.kernel.org/show_bug.cgi?id=65761
--- Comment #3 from Christoph Haag ---
Created attachment 116871
--> https://bugzilla.kernel.org/attachment.cgi?id=116871&action=edit
dmesg from 3.13-rc2 with rmmod radeon in line 2095
Having enough time to test everything would be nice.
But i
Am Montag, den 25.11.2013, 08:23 -0500 schrieb Rob Clark:
> oh, hmm.. are you importing buffers from i915? It looks like this part:
My computer has an i915 graphic card and I use an USB docking station,
that has an unconnected UDL device inside.
>
> - if (obj->base.import_attach) {
> - drm_free
On Sat, Nov 30, 2013 at 3:33 AM, Thomas Meyer wrote:
> Am Montag, den 25.11.2013, 08:23 -0500 schrieb Rob Clark:
>> oh, hmm.. are you importing buffers from i915? It looks like this part:
>
> My computer has an i915 graphic card and I use an USB docking station,
> that has an unconnected UDL devi
https://bugzilla.kernel.org/show_bug.cgi?id=66201
Bug ID: 66201
Summary: AMD atombios stuck
Product: Drivers
Version: 2.5
Kernel Version: 3.13rc2
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: N
cards and the computer freezes?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20131130/acc12887/attachment-0001.html>
https://bugzilla.kernel.org/show_bug.cgi?id=65911
--- Comment #14 from tomka ---
Yet another data point: I just installed ATI's catalyst driver. Having this in
place and configured, everything works as expected: I can start X and play
audio through HDMI without any error. This at least means my h
https://bugzilla.kernel.org/show_bug.cgi?id=65911
--- Comment #13 from tomka ---
Another thing I tested was to run weston-launch from a TTY to utilize Wayland.
This leads to the same distorted/garbled display. However I can't set the GPU
lock up in the logs, nor is there a reset---it just seems t
https://bugzilla.kernel.org/show_bug.cgi?id=65911
--- Comment #12 from tomka ---
To verify that this problem doesn't originate from my particula operating
system setup I tested recent live USB systems of Ubuntu 13.10 and Manjaro
0.8.8. Both produce the same GPU lockups and therefore can't start X
25 matches
Mail list logo
