radeon mobility x1600 broken since 3.4.0-rc6 (bisected)

radeon mobility x1600 broken since 3.4.0-rc6 (bisected)

[Hausensteiner Keg]

Hi,

I updated the kernel on an Ubuntu 12.04 (32-bit) install, and graphics 
immediately broke. Bisection points to:

commit bb635567291482a87e4cc46e6683419c1f365ddf
Author: Jerome Glisse <jglisse@redhat.com>
Date:   Wed May 9 15:34:46 2012 +0200

     drm/radeon: convert fence to uint64_t v4


Radeon graphics are still broken for me in both 3.5.2 (from 
linux-stable) and 3.6.3-rc3 - though the symptoms appear to be slightly 
different.

I'm currently running a kernel built from the commit before the above, 
and everything seems sane and stable.

I'm happy to do any tests you might find helpful..

== Symptoms

When booting with above commit, grub works fine but immediately upon 
attempt to switch graphics mode a solid green bar appears across the 
screen. System does not respond to ctrl-alt-f2. Very repeatable.

When booting with later releases (eg 3.5.2), the greeter screen is 
displayed - sometimes correctly, sometimes with minor graphics 
corruption. Immediately switching to a virtual terminal works. However 
any attempt to move the mouse or log in via the greeter screen causes 
graphics corruption and system no longer responds. Also consistently 
repeatable.

== OS details:

Ubuntu 12.04 32-bit (default kernel 3.2.0-29).

== System details:

HP/Compaq nc8430 laptop

$glxinfo | grep renderer ==> OpenGL renderer string: Gallium 0.4 on ATI 
RV530

$ lsmod | grep radeon
radeon                815703  3
ttm                    71375  1 radeon
drm_kms_helper         32563  1 radeon
drm                   220833  5 radeon,ttm,drm_kms_helper
i2c_algo_bit           13197  1 radeon

$ lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI 
M56P [Radeon Mobility X1600]

$ xrandr
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
VGA-0 disconnected (normal left inverted right x axis y axis)
LVDS connected 1680x1050+0+0 (normal left inverted right x axis y axis) 
331mm x 207mm
    1680x1050      60.1*+
    1400x1050      60.0
    1280x1024      59.9
    ....

Regards,
Simon

Re: radeon mobility x1600 broken since 3.4.0-rc6 (bisected)

[Hausensteiner Keg]

After some more experimenting with different versions, I'm getting odd 
results. So feel free to ignore this report..

FYI, what I see is:
* as noted, commits before bb6355 work fine (ie up to 3.4-rc6).
* including commit bb6355, graphics freeze on the first transition after 
grub (Plymouth?)
* the very next commit makes the (plymouth?) splash screen work, but the 
greeter screen display is corrupted; ctrl-alt-f2 works - if pressed 
immediately
* this situation continues up until release v3.5^. But building v3.5 
itself works perfectly! Presumably I've done something wrong here..
* v3.6-rc3 displays the splash (plymouth?) screen fine, but instead of a 
greeter screen, screen goes blank.

I'll try to make some more sense of this in the next few days - but 
suggestions are welcome.

Sorry if I'm posting this in the wrong place - let me know if I should 
create a bugzilla entry or whatever.

Regards,
Simon

On 25/08/12 19:39, Hausensteiner Keg wrote:
> Hi,
>
> I updated the kernel on an Ubuntu 12.04 (32-bit) install, and graphics 
> immediately broke. Bisection points to:
>
> commit bb635567291482a87e4cc46e6683419c1f365ddf
> Author: Jerome Glisse <jglisse@redhat.com>
> Date:   Wed May 9 15:34:46 2012 +0200
>
>     drm/radeon: convert fence to uint64_t v4
>
>
> Radeon graphics are still broken for me in both 3.5.2 (from 
> linux-stable) and 3.6.3-rc3 - though the symptoms appear to be 
> slightly different.
>
> I'm currently running a kernel built from the commit before the above, 
> and everything seems sane and stable.
>
> I'm happy to do any tests you might find helpful..
>
> == Symptoms
>
> When booting with above commit, grub works fine but immediately upon 
> attempt to switch graphics mode a solid green bar appears across the 
> screen. System does not respond to ctrl-alt-f2. Very repeatable.
>
> When booting with later releases (eg 3.5.2), the greeter screen is 
> displayed - sometimes correctly, sometimes with minor graphics 
> corruption. Immediately switching to a virtual terminal works. However 
> any attempt to move the mouse or log in via the greeter screen causes 
> graphics corruption and system no longer responds. Also consistently 
> repeatable.
>
> == OS details:
>
> Ubuntu 12.04 32-bit (default kernel 3.2.0-29).
>
> == System details:
>
> HP/Compaq nc8430 laptop
>
> $glxinfo | grep renderer ==> OpenGL renderer string: Gallium 0.4 on 
> ATI RV530
>
> $ lsmod | grep radeon
> radeon                815703  3
> ttm                    71375  1 radeon
> drm_kms_helper         32563  1 radeon
> drm                   220833  5 radeon,ttm,drm_kms_helper
> i2c_algo_bit           13197  1 radeon
>
> $ lspci | grep VGA
> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee 
> ATI M56P [Radeon Mobility X1600]
>
> $ xrandr
> Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
> VGA-0 disconnected (normal left inverted right x axis y axis)
> LVDS connected 1680x1050+0+0 (normal left inverted right x axis y 
> axis) 331mm x 207mm
>    1680x1050      60.1*+
>    1400x1050      60.0
>    1280x1024      59.9
>    ....
>
> Regards,
> Simon

Re: radeon mobility x1600 broken since 3.4.0-rc6 (bisected)

[Jerome Glisse]

On Sun, Aug 26, 2012 at 8:34 PM, Hausensteiner Keg <skitching@apache.org> wrote:
> After some more experimenting with different versions, I'm getting odd
> results. So feel free to ignore this report..
>
> FYI, what I see is:
> * as noted, commits before bb6355 work fine (ie up to 3.4-rc6).
> * including commit bb6355, graphics freeze on the first transition after
> grub (Plymouth?)
> * the very next commit makes the (plymouth?) splash screen work, but the
> greeter screen display is corrupted; ctrl-alt-f2 works - if pressed
> immediately
> * this situation continues up until release v3.5^. But building v3.5 itself
> works perfectly! Presumably I've done something wrong here..
> * v3.6-rc3 displays the splash (plymouth?) screen fine, but instead of a
> greeter screen, screen goes blank.
>
> I'll try to make some more sense of this in the next few days - but
> suggestions are welcome.
>
> Sorry if I'm posting this in the wrong place - let me know if I should
> create a bugzilla entry or whatever.
>
> Regards,
> Simon
>

Is it AGP ?

Cheers,
Jerome

Re: radeon mobility x1600 broken since 3.4.0-rc6 (bisected)

[Jerome Glisse]

On Sun, Aug 26, 2012 at 8:34 PM, Hausensteiner Keg <skitching@apache.org> wrote:
> After some more experimenting with different versions, I'm getting odd
> results. So feel free to ignore this report..
>
> FYI, what I see is:
> * as noted, commits before bb6355 work fine (ie up to 3.4-rc6).
> * including commit bb6355, graphics freeze on the first transition after
> grub (Plymouth?)
> * the very next commit makes the (plymouth?) splash screen work, but the
> greeter screen display is corrupted; ctrl-alt-f2 works - if pressed
> immediately
> * this situation continues up until release v3.5^. But building v3.5 itself
> works perfectly! Presumably I've done something wrong here..
> * v3.6-rc3 displays the splash (plymouth?) screen fine, but instead of a
> greeter screen, screen goes blank.
>
> I'll try to make some more sense of this in the next few days - but
> suggestions are welcome.
>
> Sorry if I'm posting this in the wrong place - let me know if I should
> create a bugzilla entry or whatever.
>
> Regards,
> Simon
>

Does patch

http://people.freedesktop.org/~glisse/0001-drm-radeon-extra-type-safe-for-fence-emission.patch

Helps ?

Cheers,
Jerome

Re: radeon mobility x1600 broken since 3.4.0-rc6 (bisected)

[Hausensteiner Keg]

On 27/08/12 20:29, Jerome Glisse wrote:
> On Sun, Aug 26, 2012 at 8:34 PM, Hausensteiner Keg <skitching@apache.org> wrote:
>> After some more experimenting with different versions, I'm getting odd
>> results. So feel free to ignore this report..
>>
>> FYI, what I see is:
>> * as noted, commits before bb6355 work fine (ie up to 3.4-rc6).
>> * including commit bb6355, graphics freeze on the first transition after
>> grub (Plymouth?)
>> * the very next commit makes the (plymouth?) splash screen work, but the
>> greeter screen display is corrupted; ctrl-alt-f2 works - if pressed
>> immediately
>> * this situation continues up until release v3.5^. But building v3.5 itself
>> works perfectly! Presumably I've done something wrong here..
>> * v3.6-rc3 displays the splash (plymouth?) screen fine, but instead of a
>> greeter screen, screen goes blank.
>>
>> I'll try to make some more sense of this in the next few days - but
>> suggestions are welcome.
>>
>> Sorry if I'm posting this in the wrong place - let me know if I should
>> create a bugzilla entry or whatever.
>>
>> Regards,
>> Simon
>>
> Does patch
>
> http://people.freedesktop.org/~glisse/0001-drm-radeon-extra-type-safe-for-fence-emission.patch
>
> Helps ?

Thanks Jerome. Will try patch tonight or tomorrow morning.

How do I check whether the radeon is on an AGP bus?
The lspci output does not mention AGP; line for video controller is:
   01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee 
ATI M56P [Radeon Mobility X1600]
The "lshw" output also shows no signs of AGP.

The dmesg output contains "[0.909546] Linux agpgart interface v0.103" 
but otherwise no mention of "agp" or "AGP".

By the way: tested the 3.5.3 release made today : still corrupt 
graphics. And the v3.5 release (which was oddly working) also showed the 
same corrupt graphics as soon as I forced a rebuild of the initrd - 
maybe an older radeon module somehow ended up in the initrd built by 
"make-kpkg --initrd".

Regards,
Simon

Re: radeon mobility x1600 broken since 3.4.0-rc6 (bisected)

[Hausensteiner Keg]

On 27/08/12 21:04, Hausensteiner Keg wrote:
> On 27/08/12 20:29, Jerome Glisse wrote:
>> On Sun, Aug 26, 2012 at 8:34 PM, Hausensteiner Keg 
>> <skitching@apache.org> wrote:
>>> ...
>> Does patch
>>
>> http://people.freedesktop.org/~glisse/0001-drm-radeon-extra-type-safe-for-fence-emission.patch 
>>
>>
>> Helps ?
>
> Thanks Jerome. Will try patch tonight or tomorrow morning.
>
> How do I check whether the radeon is on an AGP bus?
> The lspci output does not mention AGP; line for video controller is:
>   01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee 
> ATI M56P [Radeon Mobility X1600]
> The "lshw" output also shows no signs of AGP.
>
> The dmesg output contains "[0.909546] Linux agpgart interface v0.103" 
> but otherwise no mention of "agp" or "AGP".
>
> By the way: tested the 3.5.3 release made today : still corrupt 
> graphics. And the v3.5 release (which was oddly working) also showed 
> the same corrupt graphics as soon as I forced a rebuild of the initrd 
> - maybe an older radeon module somehow ended up in the initrd built by 
> "make-kpkg --initrd".
>

Patch 0001-drm-radeon-extra-type-safe-for-fence-emission applies cleanly 
to both 3.5.3 and 3.6.0-rc3, but makes no difference in either case.

I've done some more bisecting, and the full sequence is:

* Prior to commit bb635567 ("convert fence to uint64_t v4") all works fine.
* Commit bb635567 causes system to freeze on Plymouth startup.
* The following commit (3b7a2b24, "rework fence handling, drop fence 
list v7") causes Plymouth to work again, but causes graphics corruption 
on greeter screen. Pressing ctrl-alt-f2 immediately displays a virtual 
console correctly, and the system is useable. However any attempt to use 
the mouse on the greeter screen triggers further graphics corruption, 
and system appears to hang.

This situation continues up to and including 3.5.3.

In the 3.6 dev cycle, the corruption issue continues up to 9c19415c. 
However the following commit, 876dc9f3 "remove radeon_fence_create" 
instead causes the screen to go black immediately after plymouth 
completes (ie when greeter screen is expected), and ctrl-alt-f2 has no 
effect.

FWIW, looks like two separate issues to me, with 876dc9f3 masking the 
earlier one..

Regards,
Simon

Re: radeon mobility x1600 broken since 3.4.0-rc6 (bisected)

[Andrea]

On 08/29/2012 10:11 AM, Hausensteiner Keg wrote:
> On 27/08/12 21:04, Hausensteiner Keg wrote:
>> On 27/08/12 20:29, Jerome Glisse wrote:
>>> On Sun, Aug 26, 2012 at 8:34 PM, Hausensteiner Keg <skitching@apache.org> wrote:
>>>> ...
>>> Does patch
>>>
>>> http://people.freedesktop.org/~glisse/0001-drm-radeon-extra-type-safe-for-fence-emission.patch
>>>
>>> Helps ?
>>
>> Thanks Jerome. Will try patch tonight or tomorrow morning.
>>
>> How do I check whether the radeon is on an AGP bus?
>> The lspci output does not mention AGP; line for video controller is:
>>   01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI M56P [Radeon Mobility
>> X1600]
>> The "lshw" output also shows no signs of AGP.
>>
>> The dmesg output contains "[0.909546] Linux agpgart interface v0.103" but otherwise no mention of
>> "agp" or "AGP".
>>
>> By the way: tested the 3.5.3 release made today : still corrupt graphics. And the v3.5 release
>> (which was oddly working) also showed the same corrupt graphics as soon as I forced a rebuild of
>> the initrd - maybe an older radeon module somehow ended up in the initrd built by "make-kpkg
>> --initrd".
>>
> 
> Patch 0001-drm-radeon-extra-type-safe-for-fence-emission applies cleanly to both 3.5.3 and
> 3.6.0-rc3, but makes no difference in either case.
> 
> I've done some more bisecting, and the full sequence is:
> 
> * Prior to commit bb635567 ("convert fence to uint64_t v4") all works fine.
> * Commit bb635567 causes system to freeze on Plymouth startup.
> * The following commit (3b7a2b24, "rework fence handling, drop fence list v7") causes Plymouth to
> work again, but causes graphics corruption on greeter screen. Pressing ctrl-alt-f2 immediately
> displays a virtual console correctly, and the system is useable. However any attempt to use the
> mouse on the greeter screen triggers further graphics corruption, and system appears to hang.
> 
> This situation continues up to and including 3.5.3.
> 
> In the 3.6 dev cycle, the corruption issue continues up to 9c19415c. However the following commit,
> 876dc9f3 "remove radeon_fence_create" instead causes the screen to go black immediately after
> plymouth completes (ie when greeter screen is expected), and ctrl-alt-f2 has no effect.
> 
> FWIW, looks like two separate issues to me, with 876dc9f3 masking the earlier one..

Hi,

we are having the some issue with other radeon cards. you can check bug 54129 (and the one linked
there).
I have no hangs (yet), just big screen corruptions.

I have not found the 2nd issue at 876dc9f3. but I will check as soon as I can.
For me v3.6-rc3 is the same as 3b7a2b24.

I my case switching off KMS, makes the corruption disappear (but I loose XV).

To begin with, it would be nice if we could sort out if the problem comes from bb635567 or 3b7a2b24,
but I have the same black screen after the penguin logo (with Ctrl-Alt-Del working).

Andrea