https://bugs.freedesktop.org/show_bug.cgi?id=41248
--- Comment #3 from Alex Deucher 2011-09-29 22:50:19 PDT
---
I don't have access to source code at the moment, but the following change
should fix the issue. I'll make a proper patch in the next few days. The
existing code has a logic error;
This patch fixes a regression introduced between 2.6.39 & 3.1-rc1
whereby the displayport AUX channel stopped re-trying commands that
elicited a DEFER response.
Signed-off-by: Brad Campbell
diff --git a/drivers/gpu/drm/radeon/atombios_dp.c
b/drivers/gpu/drm/radeon/atombios_dp.c
index
On Thu, Sep 29, 2011 at 06:09:32PM -0700, Keith Packard wrote:
> Ok, so I've split all of the changes into bite-sized pieces so that
> they should make sense individually now. I've also added the same
> asynchronous power control to the panel power, this reduces the
> module load time down to
On Thu, Sep 29, 2011 at 7:41 PM, Alan Cox wrote:
> On Thu, 29 Sep 2011 16:26:32 +0100
> Dave Airlie wrote:
>
>> From: Dave Airlie
>>
>> For the simple KMS driver case we need some more info about argb cursor
>> limits and a preferred depth and if shadowed framebuffer access is preferred.
>>
>>
On Thu, 29 Sep 2011 09:43:12 -0700
Eric Anholt wrote:
> On Thu, 29 Sep 2011 16:26:32 +0100, Dave Airlie wrote:
> > From: Dave Airlie
> >
> > For the simple KMS driver case we need some more info about argb cursor
> > limits and a preferred depth and if shadowed framebuffer access is
> >
On Thu, 29 Sep 2011 16:26:32 +0100
Dave Airlie wrote:
> From: Dave Airlie
>
> For the simple KMS driver case we need some more info about argb cursor
> limits and a preferred depth and if shadowed framebuffer access is preferred.
>
> I've only added this for intel/radeon which support the
The mouse cursor hotspot calculation when the cursor is partially off the
top or left side of the screen was off by one.
Fixes https://bugs.freedesktop.org/show_bug.cgi?id=41158
Signed-off-by: Nicholas Miell
---
drivers/gpu/drm/radeon/radeon_cursor.c |4 ++--
1 files changed, 2
ard at intel.com
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20110929/de0a2546/attachment.pgp>
If the panel is powered up, there's no need to delay for the 'off'
interval when turning the panel on.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c
This eliminates a fairly long delay when power sequencing newer
hardware
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c | 51 +++
1 files changed, 30 insertions(+), 21 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c
Using the same basic plan as the VDD force delayed power off, make
turning the panel power off asynchronous.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c | 71 +--
1 files changed, 53 insertions(+), 18 deletions(-)
diff --git
There's no good reason to turn off the eDP force VDD bit synchronously
while probing devices; that just sticks a huge delay into all mode
setting paths. Instead, queue a delayed work proc to disable the VDD
force bit and then remember when that fires to ensure that the
appropriate delay is
We need to check eDP VDD force and panel on in several places, so
create some simple helper functions to avoid duplicating code.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c | 39 ++-
1 files changed, 26 insertions(+), 13 deletions(-)
The return value was unused, so just stop doing that.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 02b5162..56146a2 100644
This value doesn't come directly from the VBT, and so is rather
specific to the particular DP output.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/i915_drv.h |1 -
drivers/gpu/drm/i915/intel_dp.c | 35 ---
2 files changed, 16 insertions(+), 20
Store the panel power sequencing delays in the dp private structure,
rather than the global device structure. Who knows, maybe we'll get
more than one eDP device in the future.
Look at both the current hardware register settings and the VBT
specified panel power sequencing timings. Use the
This ensures that the panel power sequencing is complete before
attempting to communicate over the aux channel.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c | 12 +++-
1 files changed, 11 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c
Any call to intel_dp_sink_dpms must ensure that the panel has power so
that the DP_SET_POWER operation will be correctly received. The only
one missing this was in intel_dp_prepare.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c |2 ++
1 files changed, 2 insertions(+), 0
The DP i2c initialization code does a couple of i2c transactions,
which means that an eDP panel must be powered up.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c | 10 +-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c
Talking to the eDP DDC channel requires that the panel be powered
up. Wrap both the EDID and modes fetch code with calls to turn the vdd
power on and back off.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c | 31 ---
1 files changed, 28
On eDP, DDC requires panel power, but turning that on uses the panel
power sequencing timing values fetch from the DPCD data.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
The VDD force bit is turned on before touching the panel, but if it
was enabled, there was no call to turn it back off. Add a call.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git
Cleans up code dealing with eDP VDD a bit. Remove redundant checks in
callers
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c | 20 ++--
1 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c
Avoid any question about locked registers by just writing the unlock
pattern with every write to the register.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/i915_reg.h |1 +
drivers/gpu/drm/i915/intel_dp.c | 14 +-
2 files changed, 14 insertions(+), 1 deletions(-)
Verify that the eDP VDD is on, either with the panel being on or with
the VDD force-on bit being set.
This demonstrates that in many instances, VDD is not on when needed,
which leads to failed EDID communications.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c | 22
We're going to assume that EDID is more reliable than the VBT tables
for eDP panels, which is notably true on MacBook machines where the
VBT contains completely bogus data.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c | 20 ++--
1 files changed, 10
There's no reason to enforce a 300ms delay during eDP mode setting.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/intel_dp.c |7 ---
1 files changed, 0 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index
This masks out all interrupts and ack's any pending ones at IRQ
uninstall time to make sure we don't receive any unexpected interrupts
later on.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/i915_irq.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git
We were relying on the BIOS to set these bits, which doesn't always
happen.
Signed-off-by: Keith Packard
---
drivers/gpu/drm/i915/i915_irq.c | 24
drivers/gpu/drm/i915/i915_reg.h |5 -
2 files changed, 28 insertions(+), 1 deletions(-)
diff --git
Ok, so I've split all of the changes into bite-sized pieces so that
they should make sense individually now. I've also added the same
asynchronous power control to the panel power, this reduces the
module load time down to about 700ms on my MacBook Air, which is
pretty nice.
Given the length of
On Wed, Sep 28, 2011 at 04:10:08PM +0200, Thomas Hellstrom wrote:
> From: Jakob Bornecrantz
>
> Signed-off-by: Jakob Bornecrantz
> Signed-off-by: Thomas Hellstrom
> ---
> drivers/gpu/drm/vmwgfx/Makefile |2 +-
> drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 34 ++-
>
On Wed, Sep 28, 2011 at 04:10:06PM +0200, Thomas Hellstrom wrote:
> From: Jakob Bornecrantz
>
> More preparation for Screen Object support.
>
> Signed-off-by: Jakob Bornecrantz
> Signed-off-by: Thomas Hellstrom
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 238
> Would prefer_shadow ever be 0?
>
Yes thats for the USB and vmware type users, where the buffer is just
a main RAM buffer not in VRAM or uncached memory.
> Isn't preferred_depth just a static (non-driver-specific) preference
> list like "24, 30, 16, 15, 8" or something? ?Do we not expose the
On Wed, Sep 28, 2011 at 04:10:01PM +0200, Thomas Hellstrom wrote:
> From: Jakob Bornecrantz
>
> Signed-off-by: Jakob Bornecrantz
> Reviewed-by: Thomas Hellstrom
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_kms.c |5 -
> 1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git
On Wed, Sep 28, 2011 at 04:10:02PM +0200, Thomas Hellstrom wrote:
> From: Jakob Bornecrantz
>
> Signed-off-by: Jakob Bornecrantz
> Reviewed-by: Thomas Hellstrom
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c |5 +
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git
ai Chen
>
>
Regards,
- Chen Jie
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20110929/718d8ecf/attachment.htm>
. which is pretty much like the other TTM pool except it
also handles moving the page to another pool list.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/gpu/drm/ttm/ttm_page_alloc_dma.c | 96 ++
1 files changed, 96 insertions(+), 0 deletions(-)
diff --git
. and provide in the function callback a method to register
with the backend a new (*set_caching).
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/gpu/drm/ttm/ttm_page_alloc.c | 46 ++
drivers/gpu/drm/ttm/ttm_tt.c | 46
All the storage devices that use the dmapool set the coherent DMA
mask so they can properly use the dmapool. Since the TTM DMA pool
code is based on that and dma_alloc_coherent checks the
'coherent_dma_mask' and not 'dma_mask' we want to set it.
Signed-off-by: Konrad Rzeszutek Wilk
---
The TTM DMA only gets turned on when the SWIOTLB is enabled - but
we might also want to turn it off when SWIOTLB is on to
use the non-DMA TTM pool code.
In the future this parameter can be removed.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/gpu/drm/ttm/ttm_page_alloc_dma.c |4
In TTM world the pages for the graphic drivers are kept in three different
pools: write combined, uncached, and cached (write-back). When the pages
are used by the graphic driver the graphic adapter via its built in MMU
(or AGP) programs these pages in. The programming requires the virtual address
As a mechanism to detect whether SWIOTLB is enabled or not.
We also fix the spelling - it was swioltb instead of
swiotlb.
CC: FUJITA Tomonori
[v1: Ripped out swiotlb_enabled]
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/xen/swiotlb-xen.c |2 +-
include/linux/swiotlb.h |2 +-
We want to pass in the 'struct device' to the TTM layer so that
the TTM DMA pool code (if enabled) can use it. The DMA API code
needs the 'struct device' to do the DMA API operations.
Signed-off-by: Konrad Rzeszutek Wilk
---
drivers/gpu/drm/nouveau/nouveau_mem.c |3 ++-
Which has the function members for all of the current page pool
operations defined. The old calls (ttm_put_pages, ttm_get_pages, etc)
are plumbed through little functions which lookup in the ttm_page_alloc_func
the appropiate implementation and call it.
There is currently only one page pool code
. instead of checking against the DMA_ERROR_CODE value which is
per-platform specific. The zero value is a known invalid value
that the TTM layer sets on the dma_address array if it is not
used (ttm_tt_alloc_page_directory calls drm_calloc_large which
creates a page with GFP_ZERO).
We can't use
[.. and this is what I said in v1 post]:
Way back in January this patchset:
http://lists.freedesktop.org/archives/dri-devel/2011-January/006905.html
was merged in, but pieces of it had to be reverted b/c they did not
work properly under PowerPC, ARM, and when swapping out pages to disk.
After a
From: Dave Airlie
For the simple KMS driver case we need some more info about argb cursor
limits and a preferred depth and if shadowed framebuffer access is preferred.
I've only added this for intel/radeon which support the dumb ioctls so far.
I really don't want to expose
https://bugs.freedesktop.org/show_bug.cgi?id=30402
--- Comment #10 from Martin Stolpe 2011-09-29
15:21:53 PDT ---
Created an attachment (id=51780)
--> (https://bugs.freedesktop.org/attachment.cgi?id=51780)
Build script used to create mesa package
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=30402
--- Comment #9 from Martin Stolpe 2011-09-29
15:21:25 PDT ---
Created an attachment (id=51779)
--> (https://bugs.freedesktop.org/attachment.cgi?id=51779)
log file for xorg server
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=30402
Martin Stolpe changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
Hi guys,
I've pushed a 'restart' branch to the xf86-video-modesetting driver,
Its a basic attempt to write a simple generic unaccelerated, fallback
driver for KMS. I need this to do some hotplug testing and work.
Features:
argb cursor support
randr 1.2
dirty tracking ioctl support.
Differences
https://bugs.freedesktop.org/show_bug.cgi?id=1236
--- Comment #5 from Marcin Baczy?ski 2011-09-29 14:34:13
PDT ---
Probably the MGA bugs can be closed now that the driver is removed from git?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=41340
--- Comment #9 from mlambda at gmail.com 2011-09-29 13:41:47 PDT ---
According to
http://linux-hybrid-graphics.blogspot.com/2011/08/bios-update-has-been-released-for-amd.html
vgaswitcheroo should work when using the "Fixed Mode" BIOS setting, but
https://bugs.freedesktop.org/show_bug.cgi?id=41340
--- Comment #8 from mlambda at gmail.com 2011-09-29 13:05:42 PDT ---
(In reply to comment #7)
> You have a mux-less system which means the radeon card is not actually
> connected to any physical displays as such there is no way for you to switch
https://bugs.freedesktop.org/show_bug.cgi?id=41265
--- Comment #3 from Varban 2011-09-29 12:26:16 PDT
---
(In reply to comment #2)
> You most likely have a mux-less system
I'm not so sure about that.
First off, the ATI card is in a "Media Dock" which is not part of the laptop
and is connected
https://bugs.freedesktop.org/show_bug.cgi?id=41265
--- Comment #2 from Alex Deucher 2011-09-29 11:54:46 PDT
---
You most likely have a mux-less system which means the radeon card is not
actually connected to any physical displays as such there is no way for you to
switch to the radeon card with
https://bugs.freedesktop.org/show_bug.cgi?id=41265
Alex Deucher changed:
What|Removed |Added
Attachment #51663|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=41340
--- Comment #7 from Alex Deucher 2011-09-29 11:52:30 PDT
---
You have a mux-less system which means the radeon card is not actually
connected to any physical displays as such there is no way for you to switch to
the radeon card with
https://bugs.freedesktop.org/show_bug.cgi?id=25280
--- Comment #5 from Alex Deucher 2011-09-29 11:42:52 PDT
---
smooth and stippled polygons/lines/etc. are not implemented in r600c/g or
r300c/g at the moment as they require adding special code to the fragment
shader to handle them.
--
https://bugs.freedesktop.org/show_bug.cgi?id=41340
--- Comment #6 from mlambda at gmail.com 2011-09-29 11:09:03 PDT ---
Created an attachment (id=51776)
--> (https://bugs.freedesktop.org/attachment.cgi?id=51776)
/proc/cpuinfo
--
Configure bugmail:
On Thu, Sep 29, 2011 at 10:21 AM, Brad Campbell wrote:
> This patch fixes a regression introduced between 2.6.39 & 3.1-rc1 whereby
> the displayport AUX channel stopped re-trying commands that elicited a DEFER
> response.
>
It should still be retrying, just restructured slightly. The retry
https://bugs.freedesktop.org/show_bug.cgi?id=41158
--- Comment #1 from Michel D?nzer 2011-09-29 10:24:24
PDT ---
Indeed, looks like you're right even for pre-AVIVO (tested on RV350).
Can you submit a patch to fix this to the dri-devel list?
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=38018
--- Comment #1 from Benjamin Bellec 2011-09-29 10:09:08
PDT ---
Did you still have these messages?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=39897
--- Comment #21 from Michel D?nzer 2011-09-29 09:59:33
PDT ---
(In reply to comment #20)
> Does that mean it is definitively another issue and I should open a new
> bugreport?
Probably.
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=29951
--- Comment #18 from Michel D?nzer 2011-09-29 09:49:41
PDT ---
(In reply to comment #15)
> I'm leaning toward this being a bug in xscreensaver, rather than in the
> driver. You might want to ask the developers of xscreensaver to take a
> look,
https://bugs.freedesktop.org/show_bug.cgi?id=41248
--- Comment #2 from Leann Ogasawara
2011-09-29 09:49:40 PDT ---
Just adding relevant information here. Gustav has tested and confirmed that
reverting the following two patches resolves the issue:
commit
gnature
Size: 197 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20110929/747466fa/attachment.pgp>
https://bugs.freedesktop.org/show_bug.cgi?id=41340
mlambda at gmail.com changed:
What|Removed |Added
Attachment #51763|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=41340
mlambda at gmail.com changed:
What|Removed |Added
Attachment #51762|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=41340
mlambda at gmail.com changed:
What|Removed |Added
Attachment #51761|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=41340
mlambda at gmail.com changed:
What|Removed |Added
Attachment #51760|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=41340
mlambda at gmail.com changed:
What|Removed |Added
Attachment #51759|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=41340
mlambda at gmail.com changed:
What|Removed |Added
Attachment #51758|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=41340
--- Comment #5 from mlambda at gmail.com 2011-09-29 09:16:18 PDT ---
Created an attachment (id=51763)
--> (https://bugs.freedesktop.org/attachment.cgi?id=51763)
/var/log/Xorg.1.log
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=41340
--- Comment #4 from mlambda at gmail.com 2011-09-29 09:15:44 PDT ---
Created an attachment (id=51762)
--> (https://bugs.freedesktop.org/attachment.cgi?id=51762)
/var/log/Xorg.0.log
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=41340
--- Comment #3 from mlambda at gmail.com 2011-09-29 09:15:02 PDT ---
Created an attachment (id=51761)
--> (https://bugs.freedesktop.org/attachment.cgi?id=51761)
/var/log/syslog
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=41340
--- Comment #2 from mlambda at gmail.com 2011-09-29 09:14:10 PDT ---
Created an attachment (id=51760)
--> (https://bugs.freedesktop.org/attachment.cgi?id=51760)
Output of 'lspci -vvnn'
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=41340
--- Comment #1 from mlambda at gmail.com 2011-09-29 09:13:33 PDT ---
Created an attachment (id=51759)
--> (https://bugs.freedesktop.org/attachment.cgi?id=51759)
output of 'dmesg' before switch
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=41340
Summary: vga_switcheroo doesn't work with AMD Radeon HD 6770M
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity:
https://bugs.freedesktop.org/show_bug.cgi?id=25280
--- Comment #4 from Michal Suchanek 2011-09-29 08:54:11
PDT ---
I see a difference with tri-stipple.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=25280
--- Comment #3 from Benjamin Bellec 2011-09-29 08:30:22
PDT ---
I don't see difference whit mesa-demos poly* between swrast and r600g.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=41121
--- Comment #8 from Alex Deucher 2011-09-29 08:01:27 PDT
---
It should still be retrying, just restructured slightly. The retry logic just
moved into radeon_dp_i2c_aux_ch(), radeon_dp_aux_native_write(), and
radeon_dp_aux_native_read(), e.g.,
https://bugs.freedesktop.org/show_bug.cgi?id=30402
--- Comment #7 from Knut Petersen 2011-09-29
07:09:32 PDT ---
(In reply to comment #6)
> (In reply to comment #5)
> > So it's fixed ?
>
> It's been a while since I was playing with the Xorg state tracker. It did work
> when I booted into the
https://bugs.freedesktop.org/show_bug.cgi?id=41231
--- Comment #2 from Stefano Teso 2011-09-29
06:58:55 PDT ---
(In reply to comment #1)
> (In reply to comment #1)
> > This doesn't happen with stock mesa 7.11, [...]
>
> Actually, I can reproduce this with a checkout of the mesa-7.11 Git tag as
https://bugs.freedesktop.org/show_bug.cgi?id=40423
--- Comment #20 from Benoit Jacob 2011-09-29 06:25:14
PDT ---
Note, again (see comment 17), that this is an extremely common bug in string
functions, and that I'm not at all sure that it's the cause of the crash since
it could only lead to a
https://bugs.freedesktop.org/show_bug.cgi?id=40423
--- Comment #19 from Michel D?nzer 2011-09-29 04:07:25
PDT ---
(In reply to comment #17)
> Looking at the Valgrind error from comment 15, it suggests that
> _mesa_make_extension_string (extensions.c:912) makes the assumption that it's
> safe to
https://bugs.freedesktop.org/show_bug.cgi?id=41121
--- Comment #7 from Brad Campbell 2011-09-29 03:46:09
PDT ---
Further bisection reveals this commit broke it :
Commit 834b2904bbfde3d85b5e984688777d56e9c7bf80
Author: Alex Deucher
Date: Fri May 20 04:34:24 2011 -0400
drm/radeon/kms:
https://bugs.freedesktop.org/show_bug.cgi?id=41231
--- Comment #1 from Michel D?nzer 2011-09-29 02:58:40
PDT ---
(In reply to comment #1)
> This doesn't happen with stock mesa 7.11, [...]
Actually, I can reproduce this with a checkout of the mesa-7.11 Git tag as
well. Presumably the 'stock'
https://bugs.freedesktop.org/show_bug.cgi?id=29951
--- Comment #17 from Chris Rankin 2011-09-29
02:38:34 PDT ---
(In reply to comment #16)
> When you replay these traces, do you consistently get good results with the
> 'good' trace and bad results with the 'bad' trace?
Yes. The captured image
https://bugs.freedesktop.org/show_bug.cgi?id=41248
--- Comment #1 from Gustav N?slund 2011-09-29 01:45:47
PDT ---
I have also filed this bug @ launchpad and we have found the problematic
patches
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are
https://bugs.freedesktop.org/show_bug.cgi?id=41248
Gustav N?slund changed:
What|Removed |Added
See Also||https://launchpad.net/bugs/
https://bugs.freedesktop.org/show_bug.cgi?id=41248
Michel D?nzer changed:
What|Removed |Added
Product|xorg|DRI
Component|Driver/Radeon
/x-patch
Size: 392 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20110929/e04792b1/attachment.bin>
https://bugs.freedesktop.org/show_bug.cgi?id=29951
--- Comment #16 from Michel D?nzer 2011-09-29 00:20:23
PDT ---
(In reply to comment #13)
> I have created two apitraces, one for antspotlight working correctly and the
> other for antspotlight not working.
When you replay these traces, do you
https://bugs.freedesktop.org/show_bug.cgi?id=29951
--- Comment #16 from Michel Dänzer mic...@daenzer.net 2011-09-29 00:20:23 PDT
---
(In reply to comment #13)
I have created two apitraces, one for antspotlight working correctly and the
other for antspotlight not working.
When you replay these
Hi all,
This could be a problem with Ubuntu's sysfs namings, but I was finding
that libkms was failing in linux_from_sysfs() when it failed to detect
that my driver's name was 'i915', not 'intel' as it currently is in
the code.
I've attached a patch that corrects this to detect things named
https://bugs.freedesktop.org/show_bug.cgi?id=41248
Michel Dänzer mic...@daenzer.net changed:
What|Removed |Added
Product|xorg|DRI
https://bugs.freedesktop.org/show_bug.cgi?id=41248
Gustav Näslund gonasl...@gmail.com changed:
What|Removed |Added
See Also|
https://bugs.freedesktop.org/show_bug.cgi?id=41248
--- Comment #1 from Gustav Näslund gonasl...@gmail.com 2011-09-29 01:45:47
PDT ---
I have also filed this bug @ launchpad and we have found the problematic
patches
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
https://bugs.freedesktop.org/show_bug.cgi?id=29951
--- Comment #17 from Chris Rankin ranki...@googlemail.com 2011-09-29 02:38:34
PDT ---
(In reply to comment #16)
When you replay these traces, do you consistently get good results with the
'good' trace and bad results with the 'bad' trace?
1 - 100 of 182 matches
Mail list logo