Jonathan Nieder wrote:
> spamfang wrote:
>> What do i have to type in the kernel line to use fbdev? Normally i
>> start with radeon.modeset=0 to prevent the bug.
>
> You'd log in in "recovery mode" so X doesn't get started, but with
> modesetting enabled.
>
> Then write a minimal /etc/X11/xorg.con
spamfang wrote:
> No, once i start with radeon.modeset=0 the problem does not occur.
> drm.modeset=0 i did not try, but i guess its the same
> as radeon.modeset=0. So only with activated KMS the crash is
> reproducible.
"drm.modeset" was just a typo on my part.
[...]
> Negative, Captain! I need
fixed 597429 linux-2.6/2.6.35~rc4-1~experimental.1
quit
sdfsdfsdf ewfwdfsdf wrote:
> Ok, i tried all the kernels backwards down from 3.1 to 2.6.33.
> The result is the following:
>
> In all kernels - including 2.6.35 - the bug seems fixed; i couldnt
> reproduce it.
Thanks much. That includes v
spamfang wrote:
> I have done some thorough testing in the past days. And i can
> confirm that the bug is still present in 2.6.32, but ABSENT in
> 3.1.0.
>
> I can reproduce the bug often.
Great. Which versions are the 2.6.32 version and 3.1.y version
you tested? You can get version numbers wit
I have done some thorough testing in the past days. And i can confirm that the
bug is still present in 2.6.32, but ABSENT in 3.1.0.
I can reproduce the bug often.
- Ursprüngliche Message -
Von: Jonathan Nieder
An: spamfang
Cc: 597...@bugs.debian.org
Gesendet: 9:26 Samstag, 24.Dezembe
# letting version tracking do its work
tags 597429 - squeeze
quit
Hi,
spamfang wrote:
> kernel BUG at [...]/drivers/gpu/drm/radeon/radeon_object.c:463!
Sorry for the slow response. This is
BUG_ON(!atomic_read(&bo->tbo.reserved));
Is it reproducible? There have been some ttm fixes in
6 matches
Mail list logo
