https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #47 from Fredrik H?glund ---
(In reply to comment #46)
> (In reply to comment #43)
> > I've pushed a patch to the stable branch in KDE that should fix this issue.
>
> Could you post a link to that patch?
http://quickgit.kde.org/?p=k
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #46 from boris64 ---
(In reply to comment #43)
> (In reply to comment #42)
> > As i said in comment 30 it's also a bug of kwin, kwin should not use msaa
> > visual for everything ...
>
> I've pushed a patch to the stable branch in KD
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #47 from Fredrik Höglund ---
(In reply to comment #46)
> (In reply to comment #43)
> > I've pushed a patch to the stable branch in KDE that should fix this issue.
>
> Could you post a link to that patch?
http://quickgit.kde.org/?p=k
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #45 from Emil Velikov ---
(In reply to comment #44)
> What version of cogl should I look for? I can add something about this to
> the Fedora bug report.
commit: 93b7b4c850dd928bf21ee168a95641a8d631f713
Author: Jerome Glisse
gl
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #46 from boris64 ---
(In reply to comment #43)
> (In reply to comment #42)
> > As i said in comment 30 it's also a bug of kwin, kwin should not use msaa
> > visual for everything ...
>
> I've pushed a patch to the stable branch in KD
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #44 from D. Hugh Redelmeier ---
Jerome Glisse in comment #30:
"Well this is also a kwin bug, kwin should not pick MSAA visual. I fixed cogl
so that it does not pick msaa visual for gnome-shell."
Thanks!
I am (even today) experiencin
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #43 from Fredrik H?glund ---
(In reply to comment #42)
> As i said in comment 30 it's also a bug of kwin, kwin should not use msaa
> visual for everything ...
I've pushed a patch to the stable branch in KDE that should fix this issue
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #42 from Jerome Glisse ---
As i said in comment 30 it's also a bug of kwin, kwin should not use msaa
visual for everything ...
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #45 from Emil Velikov ---
(In reply to comment #44)
> What version of cogl should I look for? I can add something about this to
> the Fedora bug report.
commit: 93b7b4c850dd928bf21ee168a95641a8d631f713
Author: Jerome Glisse
gl
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #44 from D. Hugh Redelmeier ---
Jerome Glisse in comment #30:
"Well this is also a kwin bug, kwin should not pick MSAA visual. I fixed cogl
so that it does not pick msaa visual for gnome-shell."
Thanks!
I am (even today) experiencin
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #43 from Fredrik Höglund ---
(In reply to comment #42)
> As i said in comment 30 it's also a bug of kwin, kwin should not use msaa
> visual for everything ...
I've pushed a patch to the stable branch in KDE that should fix this issue
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #42 from Jerome Glisse ---
As i said in comment 30 it's also a bug of kwin, kwin should not use msaa
visual for everything ...
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #41 from Niels Ole Salscheider
---
As I said before, the dma_fill function is based on dma_copy and I tried to
keep the diff small. But you are right, this could be improved.
> Have you created a patch to get these functions called
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #41 from Niels Ole Salscheider ---
As I said before, the dma_fill function is based on dma_copy and I tried to
keep the diff small. But you are right, this could be improved.
> Have you created a patch to get these functions called i
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #40 from D. Hugh Redelmeier ---
Thanks, Neils, for the patch in comment #38.
Warning: the following comments are made with no understanding of X code.
"writting" should be "writing"
What is 0x000f? I would find the code cleare
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #39 from Marek Ol??k ---
BTW today I have implemented buffer clearing using streamout. I'll send my
patches to mesa-dev later today. We can use DMA later for selected chipsets. (I
assume there'll be some quirks with DMA)
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #38 from Niels Ole Salscheider
---
Created attachment 78307
--> https://bugs.freedesktop.org/attachment.cgi?id=78307&action=edit
dma_fill function
I considered to implement Marek's proposal by adding a dma_fill function that
works
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #37 from Alex Deucher ---
(In reply to comment #35)
>
> Wait: according to http://dri.freedesktop.org/wiki/GART/ the GART seems to
> enable the video card to access the computer's memory, not the other way
> around. So I don't see h
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #36 from Alex Deucher ---
(In reply to comment #34)
> I'm not saying that comment #29 is wrong. I'm saying that the existing code
> ought to have been written to handle this case. Clearly one solution is to
> replace the code as sug
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #40 from D. Hugh Redelmeier ---
Thanks, Neils, for the patch in comment #38.
Warning: the following comments are made with no understanding of X code.
"writting" should be "writing"
What is 0x000f? I would find the code cleare
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #39 from Marek Olšák ---
BTW today I have implemented buffer clearing using streamout. I'll send my
patches to mesa-dev later today. We can use DMA later for selected chipsets. (I
assume there'll be some quirks with DMA)
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #38 from Niels Ole Salscheider ---
Created attachment 78307
--> https://bugs.freedesktop.org/attachment.cgi?id=78307&action=edit
dma_fill function
I considered to implement Marek's proposal by adding a dma_fill function that
works
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #37 from Alex Deucher ---
(In reply to comment #35)
>
> Wait: according to http://dri.freedesktop.org/wiki/GART/ the GART seems to
> enable the video card to access the computer's memory, not the other way
> around. So I don't see h
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #36 from Alex Deucher ---
(In reply to comment #34)
> I'm not saying that comment #29 is wrong. I'm saying that the existing code
> ought to have been written to handle this case. Clearly one solution is to
> replace the code as sug
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #35 from D. Hugh Redelmeier ---
I finally am trying to set the GART size, as per Alex's comment #12.
Without setting it, Xorg0.log reports:
[15.054] (II) RADEON(0): mem size init: gart size :1fdef000 vram size:
s:2000 visible
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #34 from D. Hugh Redelmeier ---
Thanks, Alex, for the clear restatement.
Naively, I think of two C/UNIX conventions. For allocations that can either
succeed or fail, typically the result is a pointer which is NULL for failure --
eg.
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #33 from Alex Deucher ---
(In reply to comment #32)
> Thanks, Knut, for bisecting in #27. Thanks, Stan, for confirming bisection
> in #28.
>
> So the bad changeset is
> http://cgit.freedesktop.org/mesa/mesa/commit/
> ?id=35840ab1895
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #35 from D. Hugh Redelmeier ---
I finally am trying to set the GART size, as per Alex's comment #12.
Without setting it, Xorg0.log reports:
[15.054] (II) RADEON(0): mem size init: gart size :1fdef000 vram size:
s:2000 visible
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #32 from D. Hugh Redelmeier ---
Thanks, Knut, for bisecting in #27. Thanks, Stan, for confirming bisection in
#28.
So the bad changeset is
http://cgit.freedesktop.org/mesa/mesa/commit/?id=35840ab189595b817fa8b1a1df8cc92474a7c38d
I
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #34 from D. Hugh Redelmeier ---
Thanks, Alex, for the clear restatement.
Naively, I think of two C/UNIX conventions. For allocations that can either
succeed or fail, typically the result is a pointer which is NULL for failure --
eg.
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #33 from Alex Deucher ---
(In reply to comment #32)
> Thanks, Knut, for bisecting in #27. Thanks, Stan, for confirming bisection
> in #28.
>
> So the bad changeset is
> http://cgit.freedesktop.org/mesa/mesa/commit/
> ?id=35840ab1895
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #32 from D. Hugh Redelmeier ---
Thanks, Knut, for bisecting in #27. Thanks, Stan, for confirming bisection in
#28.
So the bad changeset is
http://cgit.freedesktop.org/mesa/mesa/commit/?id=35840ab189595b817fa8b1a1df8cc92474a7c38d
I
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #31 from Maxim Yegorushkin ---
I observe the same issue on Fedora 18 with Radeon HD 5670:
[KCrash Handler]
#6 __memset_sse2 () at ../sysdeps/x86_64/memset.S:873
#7 0x7f59a39eaff2 in memset (__len=, __ch=204,
__dest=) at /usr/in
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #31 from Maxim Yegorushkin ---
I observe the same issue on Fedora 18 with Radeon HD 5670:
[KCrash Handler]
#6 __memset_sse2 () at ../sysdeps/x86_64/memset.S:873
#7 0x7f59a39eaff2 in memset (__len=, __ch=204,
__dest=) at /usr/in
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #30 from Jerome Glisse ---
Well this is also a kwin bug, kwin should not pick MSAA visual. I fixed cogl so
that it does not pick msaa visual for gnome-shell.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #30 from Jerome Glisse ---
Well this is also a kwin bug, kwin should not pick MSAA visual. I fixed cogl so
that it does not pick msaa visual for gnome-shell.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #29 from Marek Ol??k ---
r600g crashes because it's mapping a MSAA resource in order to clear the CMASK
to zeros. The problem is MSAA resources occupy a lot of memory and the system
is failing to map the whole resource.
The solution
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #28 from Stan ---
Here happens similar thing. KWin with desktop effects enabled crashes on login
to KDE and after resume from suspend with 100% reproductibility.
My config Fedora 18.
- kernel-PAE-3.8.5-201.fc18.i686
- libdrm-2.4.4
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #29 from Marek Olšák ---
r600g crashes because it's mapping a MSAA resource in order to clear the CMASK
to zeros. The problem is MSAA resources occupy a lot of memory and the system
is failing to map the whole resource.
The solution
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #28 from Stan ---
Here happens similar thing. KWin with desktop effects enabled crashes on login
to KDE and after resume from suspend with 100% reproductibility.
My config Fedora 18.
- kernel-PAE-3.8.5-201.fc18.i686
- libdrm-2.4.4
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #27 from Knut Andre Tidemann ---
I've bisected the issue to this commit:
35840ab189595b817fa8b1a1df8cc92474a7c38d st/dri: implement MSAA for GLX/DRI2
framebuffers
The only thing that was recompiled was mesa, with the following optio
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #27 from Knut Andre Tidemann ---
I've bisected the issue to this commit:
35840ab189595b817fa8b1a1df8cc92474a7c38d st/dri: implement MSAA for GLX/DRI2
framebuffers
The only thing that was recompiled was mesa, with the following optio
https://bugs.freedesktop.org/show_bug.cgi?id=61182
Alex Deucher changed:
What|Removed |Added
CC||rankincj at googlemail.com
--- Comment #2
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #25 from ogjerstad at gmail.com ---
Not without some instructions, I have never done that before.
And, I must admit, I also downgraded llvm-libs, mesa-dri-filesystem and
mesa-libxatracker. I think I had to because of dependences.
I g
https://bugs.freedesktop.org/show_bug.cgi?id=61182
Alex Deucher changed:
What|Removed |Added
CC||ranki...@googlemail.com
--- Comment #26 f
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #24 from Alex Deucher ---
(In reply to comment #23)
> I can confirm now that downgrading mesa-dri-drivers to 9.0.1-1 (as packaged
> by Fedora) fixes the problem.
Can you bisect mesa?
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #25 from ogjers...@gmail.com ---
Not without some instructions, I have never done that before.
And, I must admit, I also downgraded llvm-libs, mesa-dri-filesystem and
mesa-libxatracker. I think I had to because of dependences.
I gues
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #23 from ogjerstad at gmail.com ---
I can confirm now that downgrading mesa-dri-drivers to 9.0.1-1 (as packaged by
Fedora) fixes the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
-- ne
https://bugs.freedesktop.org/show_bug.cgi?id=61182
ogjerstad at gmail.com changed:
What|Removed |Added
CC||ogjerstad at gmail.com
--- Comme
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #24 from Alex Deucher ---
(In reply to comment #23)
> I can confirm now that downgrading mesa-dri-drivers to 9.0.1-1 (as packaged
> by Fedora) fixes the problem.
Can you bisect mesa?
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #23 from ogjers...@gmail.com ---
I can confirm now that downgrading mesa-dri-drivers to 9.0.1-1 (as packaged by
Fedora) fixes the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=61182
ogjers...@gmail.com changed:
What|Removed |Added
CC||ogjers...@gmail.com
--- Comment #22
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #21 from korgens at yandex.com ---
I can also confirm this bug.
Software:
Archlinux standard installation.
Linux 3.8.4-1-ARCH #1 SMP PREEMPT Wed Mar 20 22:10:25 CET 2013 x86_64 GNU/Linux
KDE: 4.10.1 (no widgets, other than the task pa
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #21 from korg...@yandex.com ---
I can also confirm this bug.
Software:
Archlinux standard installation.
Linux 3.8.4-1-ARCH #1 SMP PREEMPT Wed Mar 20 22:10:25 CET 2013 x86_64 GNU/Linux
KDE: 4.10.1 (no widgets, other than the task panel
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #20 from Chris Fong ---
(In reply to comment #16)
> No gnome-shell crashes since I've upgraded to Mesa 9.1.1. Will post an
> update in a few days whether it remains stable or I was just lucky today.
Observed the same gnome-shell cras
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #20 from Chris Fong ---
(In reply to comment #16)
> No gnome-shell crashes since I've upgraded to Mesa 9.1.1. Will post an
> update in a few days whether it remains stable or I was just lucky today.
Observed the same gnome-shell cras
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #19 from D. Hugh Redelmeier ---
More information about my Fedora 18 x86-64 configuration:
- a single monitor: 2560 x 1600 pixels
- video card: Radeon HD 3600 XT (according to Xorg.0.log)
- Fedora's kernel: kernel-3.8.4-202.fc18.x86
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #18 from D. Hugh Redelmeier ---
(Sorry for the previous uncompleted comment. I will continue.)
I'm hitting it in Gnome_shell
(https://bugzilla.redhat.com/show_bug.cgi?id=924076).
I'm hitting it in Cinnamon (https://bugzilla.redhat.
https://bugs.freedesktop.org/show_bug.cgi?id=61182
D. Hugh Redelmeier changed:
What|Removed |Added
CC||hugh at mimosa.com
--- Comment #17
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #19 from D. Hugh Redelmeier ---
More information about my Fedora 18 x86-64 configuration:
- a single monitor: 2560 x 1600 pixels
- video card: Radeon HD 3600 XT (according to Xorg.0.log)
- Fedora's kernel: kernel-3.8.4-202.fc18.x86
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #18 from D. Hugh Redelmeier ---
(Sorry for the previous uncompleted comment. I will continue.)
I'm hitting it in Gnome_shell
(https://bugzilla.redhat.com/show_bug.cgi?id=924076).
I'm hitting it in Cinnamon (https://bugzilla.redhat.
https://bugs.freedesktop.org/show_bug.cgi?id=61182
D. Hugh Redelmeier changed:
What|Removed |Added
CC||h...@mimosa.com
--- Comment #17 fro
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #16 from J?rg Billeter ---
No gnome-shell crashes since I've upgraded to Mesa 9.1.1. Will post an update
in a few days whether it remains stable or I was just lucky today.
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #16 from Jürg Billeter ---
No gnome-shell crashes since I've upgraded to Mesa 9.1.1. Will post an update
in a few days whether it remains stable or I was just lucky today.
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #15 from Eugene Shalygin ---
(In reply to comment #14)
Also tried both suggestions. Both changes together allows me to run `kwin
--replace` with active kwin_gles. However, when I connect a second screen, it
crashes (signal 7) with the
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #15 from Eugene Shalygin ---
(In reply to comment #14)
Also tried both suggestions. Both changes together allows me to run `kwin
--replace` with active kwin_gles. However, when I connect a second screen, it
crashes (signal 7) with the
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #14 from Michael Mair-Keimberger ---
(In reply to comment #12)
> I think these are actually several bugs at play here.
>
> 1. CPU only has a 256 MB window into vram. If the window is full due to
> fragmentation or other mapped buffe
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #13 from Michel D?nzer ---
Eugene and Knut, in the future please always include information about which
signal was generated, at least if it's not SIGSEGV (which is the most common).
--
You are receiving this mail because:
You are t
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #12 from Alex Deucher ---
I think these are actually several bugs at play here.
1. CPU only has a 256 MB window into vram. If the window is full due to
fragmentation or other mapped buffers, we fail. Does disabling hyperz help?
se
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #11 from Michael Mair-Keimberger ---
I don't know if its the same but i can confirm similar crashes.
First of all, i have a triple head setup, 2 screens with 1920x1200 (left and
right) and one with 2560x1600 (middle). Those crashes h
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #10 from J?rg Billeter ---
(In reply to comment #9)
> (In reply to comment #8)
> > I don't have a usable backtrace at hand, but I'm seeing very similar crashes
> > in gnome-shell as well with Mesa 9.1 and Linux 3.8.3. With Mesa 9.0.3,
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #9 from Alex Deucher ---
(In reply to comment #8)
> I don't have a usable backtrace at hand, but I'm seeing very similar crashes
> in gnome-shell as well with Mesa 9.1 and Linux 3.8.3. With Mesa 9.0.3, I
> haven't noticed any crashes
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #8 from J?rg Billeter ---
I don't have a usable backtrace at hand, but I'm seeing very similar crashes in
gnome-shell as well with Mesa 9.1 and Linux 3.8.3. With Mesa 9.0.3, I haven't
noticed any crashes so far. It crashes much more f
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #14 from Michael Mair-Keimberger ---
(In reply to comment #12)
> I think these are actually several bugs at play here.
>
> 1. CPU only has a 256 MB window into vram. If the window is full due to
> fragmentation or other mapped buffe
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #13 from Michel Dänzer ---
Eugene and Knut, in the future please always include information about which
signal was generated, at least if it's not SIGSEGV (which is the most common).
--
You are receiving this mail because:
You are t
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #12 from Alex Deucher ---
I think these are actually several bugs at play here.
1. CPU only has a 256 MB window into vram. If the window is full due to
fragmentation or other mapped buffers, we fail. Does disabling hyperz help?
se
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #11 from Michael Mair-Keimberger ---
I don't know if its the same but i can confirm similar crashes.
First of all, i have a triple head setup, 2 screens with 1920x1200 (left and
right) and one with 2560x1600 (middle). Those crashes h
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #10 from Jürg Billeter ---
(In reply to comment #9)
> (In reply to comment #8)
> > I don't have a usable backtrace at hand, but I'm seeing very similar crashes
> > in gnome-shell as well with Mesa 9.1 and Linux 3.8.3. With Mesa 9.0.3,
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #9 from Alex Deucher ---
(In reply to comment #8)
> I don't have a usable backtrace at hand, but I'm seeing very similar crashes
> in gnome-shell as well with Mesa 9.1 and Linux 3.8.3. With Mesa 9.0.3, I
> haven't noticed any crashes
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #8 from Jürg Billeter ---
I don't have a usable backtrace at hand, but I'm seeing very similar crashes in
gnome-shell as well with Mesa 9.1 and Linux 3.8.3. With Mesa 9.0.3, I haven't
noticed any crashes so far. It crashes much more f
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #7 from Eugene Shalygin ---
it is quite interesting to note that the crash happens only using 1920x1080 and
higher screen resolution. If the resolution is lower, kwin works fine.
--
You are receiving this mail because:
You are the a
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #7 from Eugene Shalygin ---
it is quite interesting to note that the crash happens only using 1920x1080 and
higher screen resolution. If the resolution is lower, kwin works fine.
--
You are receiving this mail because:
You are the a
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #6 from Eugene Shalygin ---
The same crash happens time to time when maximizing application windows
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #6 from Eugene Shalygin ---
The same crash happens time to time when maximizing application windows
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #5 from Knut Andre Tidemann ---
I forgot to add:
My card is a Radeon HD 5670
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #4 from Knut Andre Tidemann ---
I can confirm a very similar crash:
#5 0x7fb122be859b in __memset_sse2 () from /usr/lib/libc.so.6
#6 0x7fb072bd0a5f in r600_texture_create_object () from
/usr/lib/xorg/modules/dri/r600_dri.so
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #5 from Knut Andre Tidemann ---
I forgot to add:
My card is a Radeon HD 5670
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #4 from Knut Andre Tidemann ---
I can confirm a very similar crash:
#5 0x7fb122be859b in __memset_sse2 () from /usr/lib/libc.so.6
#6 0x7fb072bd0a5f in r600_texture_create_object () from
/usr/lib/xorg/modules/dri/r600_dri.so
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #3 from Eugene Shalygin ---
With "glamor" as acceleration method, these crashes are much more rare
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #3 from Eugene Shalygin ---
With "glamor" as acceleration method, these crashes are much more rare
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel m
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #2 from Eugene Shalygin ---
Same crash with the same backtrace using mesa 9.1 and kernel 3.8
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was sc
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #2 from Eugene Shalygin ---
Same crash with the same backtrace using mesa 9.1 and kernel 3.8
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #1 from Eugene Shalygin ---
This happens only when kwin starts for the first time. There are no crashes at
next runs.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
https://bugs.freedesktop.org/show_bug.cgi?id=61182
--- Comment #1 from Eugene Shalygin ---
This happens only when kwin starts for the first time. There are no crashes at
next runs.
--
You are receiving this mail because:
You are the assignee for the bug.
94 matches
Mail list logo