[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41668 --- Comment #9 from dmotd 2011-10-11 19:42:06 PDT --- (In reply to comment #5) > Do you have records of when you updated the kernel last? What kernel version > did you have before you started experiencing this issue? it has been occurring sin

[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41668 --- Comment #9 from dmotd 2011-10-11 19:42:06 PDT --- (In reply to comment #5) > Do you have records of when you updated the kernel last? What kernel version > did you have before you started experiencing this issue? it has been occurring sin

[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41668 --- Comment #8 from dmotd 2011-10-11 19:28:12 PDT --- Created an attachment (id=52249) --> (https://bugs.freedesktop.org/attachment.cgi?id=52249) /proc/interrupts on a fresh (working) boot.. -- Configure bugmail: https://bugs.freedesktop.org/

[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41668 --- Comment #8 from dmotd 2011-10-11 19:28:12 PDT --- Created an attachment (id=52249) --> (https://bugs.freedesktop.org/attachment.cgi?id=52249) /proc/interrupts on a fresh (working) boot.. -- Configure bugmail: https://bugs.freedesktop.org/

[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41668 --- Comment #7 from dmotd 2011-10-11 19:27:14 PDT --- Created an attachment (id=52248) --> (https://bugs.freedesktop.org/attachment.cgi?id=52248) /proc/interrupts after the freeze -- Configure bugmail: https://bugs.freedesktop.org/userprefs.c

[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41668 --- Comment #7 from dmotd 2011-10-11 19:27:14 PDT --- Created an attachment (id=52248) --> (https://bugs.freedesktop.org/attachment.cgi?id=52248) /proc/interrupts after the freeze -- Configure bugmail: https://bugs.freedesktop.org/userprefs.c

[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41668 --- Comment #6 from dmotd 2011-10-11 19:25:07 PDT --- (In reply to comment #4) > > `DISPLAY=:0 openbox --replace` results in: > > > > "Invalid MIT-MAGIC-COOKIE-1 keyOpenbox-Message: Failed to open the display > > from > > the DISPLAY environme

[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41668 --- Comment #6 from dmotd 2011-10-11 19:25:07 PDT --- (In reply to comment #4) > > `DISPLAY=:0 openbox --replace` results in: > > > > "Invalid MIT-MAGIC-COOKIE-1 keyOpenbox-Message: Failed to open the display > > from > > the DISPLAY environme

Power profiles low and mid are identical on Radeon HD6470M

2011-10-11 Thread Alex Deucher
On Sat, Oct 8, 2011 at 2:25 PM, Wolfgang Fritz wrote: > Hello, > > I have an HP Elitebook 8560p with Radeon HD7470M graphics, running Debian > sid with kernel 3.0.4. > > I noticed that the power profiles low and mid are setting identical clocks > and voltage, the lowest possible values: > > defau

[patch] drm/nva3: checking the wrong variable

2011-10-11 Thread Dan Carpenter
"id" is unsigned here and it's never less than zero. I believe the intent was to check the return value from nva3_pm_pll_offset(). Also I've changed it to pass on the -ENOENT error code from the lower levels instead of returning -EINVAL. Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm

Re: [patch] drm/nva3: checking the wrong variable

2011-10-11 Thread Ben Skeggs
On Tue, 2011-10-11 at 17:34 +0300, Dan Carpenter wrote: > "id" is unsigned here and it's never less than zero. I believe the > intent was to check the return value from nva3_pm_pll_offset(). > Also I've changed it to pass on the -ENOENT error code from the lower > levels instead of returning -EINV

Re: Power profiles low and mid are identical on Radeon HD6470M

2011-10-11 Thread Alex Deucher
On Sat, Oct 8, 2011 at 2:25 PM, Wolfgang Fritz wrote: > Hello, > > I have an HP Elitebook 8560p with Radeon HD7470M graphics, running Debian > sid with kernel 3.0.4. > > I noticed that the power profiles low and mid are setting identical clocks > and voltage, the lowest possible values: > > defaul

[RFC 2/2] dma-buf: Documentation for buffer sharing framework

2011-10-11 Thread Sumit Semwal
Add documentation for dma buffer sharing framework, explaining the various operations, members and API of the dma buffer sharing framework. Signed-off-by: Sumit Semwal Signed-off-by: Sumit Semwal --- Documentation/dma-buf-sharing.txt | 210 + 1 files changed

[RFC 1/2] dma-buf: Introduce dma buffer sharing mechanism

2011-10-11 Thread Sumit Semwal
This is the first step in defining a dma buffer sharing mechanism. A new buffer object dma_buf is added, with operations and API to allow easy sharing of this buffer object across devices. The framework allows: - a new buffer-object to be created with fixed size. - different devices to 'attach' t

[RFC 0/2] Introduce dma buffer sharing mechanism

2011-10-11 Thread Sumit Semwal
Hello Everyone, Various subsystems - V4L2, GPU-accessors, DRI to name a few - have felt the need to have a common mechanism to share memory buffers across different devices - ARM, video hardware, GPU. This need comes forth from a variety of use cases including cameras, image processing, video r

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #9 from Paul Menzel 2011-10-11 14:52:48 PDT --- (In reply to comment #8) […] > Somehow something like a matrix on radeon wiki would be cool. If it would > tell: > > R580 cards like mine: > (Usually two powerstates (default) and

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #9 from Paul Menzel 2011-10-11 14:52:48 PDT --- (In reply to comment #8) [?] > Somehow something like a matrix on radeon wiki would be cool. If it would > tell: > > R580 cards like mine: > (Usually two powerstates (default) and

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #8 from revealed 2011-10-11 14:21:46 PDT --- Basically i remember that when i initially read the first time about powermanagement on radeon for linux, that i read on a forum like phoronix. At that time it sounded somehow in this arti

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #8 from revealed 2011-10-11 14:21:46 PDT --- Basically i remember that when i initially read the first time about powermanagement on radeon for linux, that i read on a forum like phoronix. At that time it sounded somehow in this art

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41664 Alex Deucher changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #7 from Alex Deucher 2011-10-11 14:02:08 PDT --- Your OEM only defined two power state: default and overclock. The driver sticks to the states defined in the vbios since they have been validated and are known to been good combination

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41664 Alex Deucher changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #7 from Alex Deucher 2011-10-11 14:02:08 PDT --- Your OEM only defined two power state: default and overclock. The driver sticks to the states defined in the vbios since they have been validated and are known to been good combinatio

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #6 from revealed 2011-10-11 13:55:22 PDT --- Ah. Ok thats what i did not get. So it is intended to run at the default. Thats what i also found in the catalyst on windows even. 506 MHZ (core) 594 MHZ (RAM) The temperature reading is

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #6 from revealed 2011-10-11 13:55:22 PDT --- Ah. Ok thats what i did not get. So it is intended to run at the default. Thats what i also found in the catalyst on windows even. 506 MHZ (core) 594 MHZ (RAM) The temperature reading is

[Bug 41698] New: [r300g] Flickering user interface in WoW

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41698 Summary: [r300g] Flickering user interface in WoW Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: med

[Bug 41698] New: [r300g] Flickering user interface in WoW

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41698 Summary: [r300g] Flickering user interface in WoW Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: med

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #5 from Alex Deucher 2011-10-11 13:31:01 PDT --- On pre-R6xx desktop asics, there are generally no low power states. There is generally only a single default state or, on some high end cards cards, default state and an overclock stat

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #5 from Alex Deucher 2011-10-11 13:31:01 PDT --- On pre-R6xx desktop asics, there are generally no low power states. There is generally only a single default state or, on some high end cards cards, default state and an overclock sta

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #4 from revealed 2011-10-11 13:22:50 PDT --- I mean the Plasmoid just says, that it runs at 506 MHZ core and 594 MHZ ran and something like 41 degrees? Somehow in a stuck way. Greetings, R -- Configure bugmail: https://bugs.freede

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #4 from revealed 2011-10-11 13:22:50 PDT --- I mean the Plasmoid just says, that it runs at 506 MHZ core and 594 MHZ ran and something like 41 degrees? Somehow in a stuck way. Greetings, R -- Configure bugmail: https://bugs.freed

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #3 from revealed 2011-10-11 13:19:32 PDT --- Hello! Many thanks for your reply! Is the output that i get and that i can not switch powermethod and profiles correct? I thought it should report voltages and so on? Because it is i am j

[Bug 41664] R580 Powermanagement with Kernelmodesetting:

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41664 --- Comment #3 from revealed 2011-10-11 13:19:32 PDT --- Hello! Many thanks for your reply! Is the output that i get and that i can not switch powermethod and profiles correct? I thought it should report voltages and so on? Because it is i am

[Bug 41579] R300 Segfaults when using mupen64plus

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41579 --- Comment #2 from krthu...@gmail.com 2011-10-11 12:19:20 PDT --- (In reply to comment #1) > Does this still happen with current Git? Just tested current Git, and it seems to be working. -- Configure bugmail: https://bugs.freedesktop.org/userp

[Bug 41579] R300 Segfaults when using mupen64plus

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41579 --- Comment #2 from krthurow at gmail.com 2011-10-11 12:19:20 PDT --- (In reply to comment #1) > Does this still happen with current Git? Just tested current Git, and it seems to be working. -- Configure bugmail: https://bugs.freedesktop.org/us

[Bug 28597] [865G] Segmentation fault in _swrast_logicop_rgba_span

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=28597 Jeremy Huddleston changed: What|Removed |Added Product|xorg|Mesa Component|Driver/intel

[Bug 28597] [865G] Segmentation fault in _swrast_logicop_rgba_span

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=28597 Jeremy Huddleston changed: What|Removed |Added Product|xorg|Mesa Component|Driver/intel

[PATCH] vmwgfx: Take the driver out of staging

2011-10-11 Thread Thomas Hellstrom
Also improve a bit on the Kconfig help. Signed-off-by: Thomas Hellstrom Reviewed-by: Jakob Bornecrantz --- drivers/gpu/drm/Kconfig|4 +++- drivers/gpu/drm/vmwgfx/Kconfig |9 + drivers/staging/Kconfig|2 -- 3 files changed, 8 insertions(+), 7 deletions(-) dif

[patch] drm/nva3: checking the wrong variable

2011-10-11 Thread Dan Carpenter
"id" is unsigned here and it's never less than zero. I believe the intent was to check the return value from nva3_pm_pll_offset(). Also I've changed it to pass on the -ENOENT error code from the lower levels instead of returning -EINVAL. Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm

[Bug 41592] [Radeon] The display often freezes with gnome-shell 3.2

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41592 --- Comment #6 from Michel Dänzer 2011-10-11 09:49:24 PDT --- (In reply to comment #5) > Apparently I spoke too fast... gnome-shell has freezed today, just after I've > unlocked gnome-screensaver. But i have nothing in dmesg or Xorg.log. When t

[Bug 41592] [Radeon] The display often freezes with gnome-shell 3.2

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41592 --- Comment #6 from Michel D?nzer 2011-10-11 09:49:24 PDT --- (In reply to comment #5) > Apparently I spoke too fast... gnome-shell has freezed today, just after I've > unlocked gnome-screensaver. But i have nothing in dmesg or Xorg.log. When t

[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41668 Jeremy Huddleston changed: What|Removed |Added Status Whiteboard|2011BRB_Reviewed| -- Configure bugmail: https://bugs

[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41668 Jeremy Huddleston changed: What|Removed |Added Status Whiteboard|2011BRB_Reviewed| -- Configure bugmail: https://bugs

[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41668 Jeremy Huddleston changed: What|Removed |Added Status Whiteboard||2011BRB_Reviewed Priority|

[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41668 Jeremy Huddleston changed: What|Removed |Added Status Whiteboard||2011BRB_Reviewed Priority|

[PATCH 00/24] MacBook Air patch sequence (v2)

2011-10-11 Thread Chris Wilson
On Thu, 29 Sep 2011 18:09:32 -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 about 700m

[Bug 41592] [Radeon] The display often freezes with gnome-shell 3.2

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41592 miran...@orange.fr changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[Bug 41592] [Radeon] The display often freezes with gnome-shell 3.2

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41592 mirandir at orange.fr changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[RFC 0/2] Introduce dma buffer sharing mechanism

2011-10-11 Thread Sumit Semwal
Hello Everyone, Various subsystems - V4L2, GPU-accessors, DRI to name a few - have felt the need to have a common mechanism to share memory buffers across different devices - ARM, video hardware, GPU. This need comes forth from a variety of use cases including cameras, image processing, video r

[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=41668 --- Comment #4 from Michel Dänzer 2011-10-11 02:34:52 PDT --- > `DISPLAY=:0 openbox --replace` results in: > > "Invalid MIT-MAGIC-COOKIE-1 keyOpenbox-Message: Failed to open the display > from > the DISPLAY environment variable." This is beca

[Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

2011-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=41668 --- Comment #4 from Michel D?nzer 2011-10-11 02:34:52 PDT --- > `DISPLAY=:0 openbox --replace` results in: > > "Invalid MIT-MAGIC-COOKIE-1 keyOpenbox-Message: Failed to open the display > from > the DISPLAY environment variable." This is beca

[RFC 2/2] dma-buf: Documentation for buffer sharing framework

2011-10-11 Thread Sumit Semwal
Add documentation for dma buffer sharing framework, explaining the various operations, members and API of the dma buffer sharing framework. Signed-off-by: Sumit Semwal Signed-off-by: Sumit Semwal --- Documentation/dma-buf-sharing.txt | 210 + 1 files changed

[RFC 1/2] dma-buf: Introduce dma buffer sharing mechanism

2011-10-11 Thread Sumit Semwal
This is the first step in defining a dma buffer sharing mechanism. A new buffer object dma_buf is added, with operations and API to allow easy sharing of this buffer object across devices. The framework allows: - a new buffer-object to be created with fixed size. - different devices to 'attach' t

[PATCH] vmwgfx: Take the driver out of staging

2011-10-11 Thread Thomas Hellstrom
Also improve a bit on the Kconfig help. Signed-off-by: Thomas Hellstrom Reviewed-by: Jakob Bornecrantz --- drivers/gpu/drm/Kconfig|4 +++- drivers/gpu/drm/vmwgfx/Kconfig |9 + drivers/staging/Kconfig|2 -- 3 files changed, 8 insertions(+), 7 deletions(-) dif

Re: [PATCH 00/24] MacBook Air patch sequence (v2)

2011-10-11 Thread Chris Wilson
On Thu, 29 Sep 2011 18:09:32 -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 about 700m