I just tried 2.6.35-rc4 to see, if a different bug is fixed, but noted
that this kernel will only boot with radeon.modeset=0.
If KMS is active the display turns off and the system is completely
dead, not even SysRq+B is working.
I build a new kernel with the radeon driver as a module and inserted
https://bugs.freedesktop.org/show_bug.cgi?id=28800
--- Comment #6 from Marek Olšák 2010-07-11 17:33:51 PDT ---
There is nothing I can do about a crash in WoW and not in the driver, though I
believe WoW without S3TC has not been tested by Blizzard QA because there are
no Windows drivers that do no
https://bugs.freedesktop.org/show_bug.cgi?id=28800
--- Comment #6 from Marek Ol??k 2010-07-11 17:33:51 PDT
---
There is nothing I can do about a crash in WoW and not in the driver, though I
believe WoW without S3TC has not been tested by Blizzard QA because there are
no Windows drivers that do n
If I go one commit back, cubestorm works. It's quite a large commit and it's
not clear to me what the commit does in terms of functionality.
BTW, cubestorm is a single-buffered application.
--=20
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=3Demail
--- You are receiving t
Fixed brace, macro and spacing coding style issues.
Signed-off-by: Nicolas Kaiser
---
drivers/gpu/drm/mga/mga_dma.c | 99 +
drivers/gpu/drm/mga/mga_drv.c |4 +-
drivers/gpu/drm/mga/mga_drv.h | 187 +++
drivers/gpu/drm/mga/mga_i
https://bugs.freedesktop.org/show_bug.cgi?id=28800
--- Comment #5 from Chris Rankin 2010-07-11 16:17:50
PDT ---
(In reply to comment #3)
> Can you obtain a backtrace of the crash?
With r300c, I can remove the libtxc_dtxn.so library but set a flag in my .drirc
file instead:
This adds the GL_E
https://bugs.freedesktop.org/show_bug.cgi?id=28800
--- Comment #5 from Chris Rankin 2010-07-11
16:17:50 PDT ---
(In reply to comment #3)
> Can you obtain a backtrace of the crash?
With r300c, I can remove the libtxc_dtxn.so library but set a flag in my .drirc
file instead:
This adds the GL_E
Fixed brace, macro and spacing coding style issues.
Simplified
-if (ret) return ret;
-return 0;
+return ret;
Signed-off-by: Nicolas Kaiser
---
drivers/gpu/drm/via/via_dma.c | 120
drivers/gpu/drm/via/via_dmablit.c | 71 ++
driv
https://bugs.freedesktop.org/show_bug.cgi?id=28563
Marek Olšák changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=28563
Marek Ol??k changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
I just tried 2.6.35-rc4 to see, if a different bug is fixed, but noted
that this kernel will only boot with radeon.modeset=0.
If KMS is active the display turns off and the system is completely
dead, not even SysRq+B is working.
I build a new kernel with the radeon driver as a module and inserted
With the ioctl, block, tty, vfs and llseek series
on their way into linux-next, these three patches
are attacking the hardest remaining issues.
If we get these ready for 2.6.36, the kernel should
be almost usable with the BKL disabled. In all three
cases, I'm cheating a bit, because the BKL still
On Sun, 2010-07-11 at 01:24 +0200, Marcin Slusarz wrote:
> Hi
>
> Patch "drm/nouveau: use drm_mm in preference to custom code doing the same
> thing"
> in nouveau tree introduced new deadlock possibility, for which lockdep
> complains loudly:
>
> [ 1541.070202] [drm] nouveau :02:00.0: Alloc
https://bugs.freedesktop.org/show_bug.cgi?id=28563
--- Comment #2 from Marek Olšák 2010-07-11 10:16:59 PDT ---
Bisected. The first bad commit which locks up:
commit bd1ce874728c06d08a1f9881f51edbdd2f1c9db0
Author: Chia-I Wu
Date: Mon Mar 8 22:19:48 2010 +0800
st/dri: Switch from st_publi
https://bugs.freedesktop.org/show_bug.cgi?id=28563
--- Comment #2 from Marek Ol??k 2010-07-11 10:16:59 PDT
---
Bisected. The first bad commit which locks up:
commit bd1ce874728c06d08a1f9881f51edbdd2f1c9db0
Author: Chia-I Wu
Date: Mon Mar 8 22:19:48 2010 +0800
st/dri: Switch from st_publ
https://bugs.freedesktop.org/show_bug.cgi?id=28860
--- Comment #9 from Sven Arvidsson 2010-07-11 10:05:51 PDT ---
(In reply to comment #8)
>
> I pulled 1 of the 3 failing shaders from the error log. If you have some
> familiarity with assembly code, you can look through the log and try to find
https://bugs.freedesktop.org/show_bug.cgi?id=28860
--- Comment #9 from Sven Arvidsson 2010-07-11 10:05:51 PDT ---
(In reply to comment #8)
>
> I pulled 1 of the 3 failing shaders from the error log. If you have some
> familiarity with assembly code, you can look through the log and try to find
Fixed brace, macro and spacing coding style issues.
Simplified
-if (ret) return ret;
-return 0;
+return ret;
Signed-off-by: Nicolas Kaiser
---
drivers/gpu/drm/via/via_dma.c | 120
drivers/gpu/drm/via/via_dmablit.c | 71 ++
driv
Hi
Patch "drm/nouveau: use drm_mm in preference to custom code doing the same
thing"
in nouveau tree introduced new deadlock possibility, for which lockdep
complains loudly:
[ 1541.070202] [drm] nouveau :02:00.0: Allocating FIFO number 3
[ 1541.084772] [drm] nouveau :02:00.0: nouveau_ch
Fixed brace, macro and spacing coding style issues.
Signed-off-by: Nicolas Kaiser
---
Supersedes patch "drm/savage: fixed brace coding style issues".
drivers/gpu/drm/savage/savage_bci.c | 48 +++
drivers/gpu/drm/savage/savage_drv.h | 109 +
dri
20 matches
Mail list logo
