Re: drm-radeon failures on R600: patches still don't work

[Yaroslav Fedevych <jafd@netstyle.com.ua>]

On 12/06/11 14:21, Markus Trippelsdorf wrote:
> Hmm, maybe you're seeing a different problem. The issue that I saw was
> fixed by commit 428c6e3630 in the git tree (this is identical to the
> patch by Dave you're referring to above).
>
> Does a "git-revert fe6f0bd03d697835e76dd18d232ba476c65b8282" solve your
> problem?

As for spewing the log with "invalid textures", yes. I bisected it twice 
to exclude any pilot error.

As for other things... it's rather getting strange. Instead of garbled 
screen when starting X which was there before revert, and having ability 
to switch to a text VT to see the kernel message, the machine just... 
hangs. The cursor first freezes, then after a few seconds disappears, 
and that's it. After 30 seconds more, HDD stops spinning.

I thought there might be a kernel panic or something, but even if it is, 
the kernel cannot say anything. I fired up netconsole and tried to go 
with that, but to no avail. There was no message which could be a clear 
precursor to disaster.

I thought then that the kernel might manage to print at least something 
on the console. So as soon as I have seen the switch to graphics and the 
mouse cursor, I switched the VT immediately. After a while, the screen 
went black and that was it. It wasn't a particular service.

Even more curious thing is that even using Catalyst doesn't help: it 
invariably comes to this end. I have a pure text console boot, then it 
starts GDM, then there's a black screen with busy cursor spinning, I 
switch to the text console, after a few seconds I lose control over it, 
that is - the boot process freezes and the keyboard stops accepting 
input, then the switch to a black screen and that's it.

And the only reliable pre-requisite for this to happen is to launch X. 
In single-user, without X running, it would work for days, KMS or not.

I'm really not sure how to debug this. This behaviour started as soon as 
3.0.0-rc2 and is there as of today's git (3.0.0-rc3).

Also, I'm not sure that DRI is to blame, because the hangs occur on both 
open source and proprietary drivers.

As I have told before, netconsole does not show anything suspicious.

I cannot tell if SysRq would work because my laptop hasn't got a SysRq key.

I wonder if Gallium Mesa libs could, in a way, do these things. By the 
way, they work fine on 2.6.39...

The machine on which that happens is Thinkpad Edge 13, AMD model, BIOS 
v1.12, AMD RS780 (Radeon HD3200). What else do I need to supply? What 
debugging options to turn on?

I'm completely lost here and feel like a complete idiot.

Next I'm going to nuke my Gallium Mesa libraries and try to boot without 
them, but it's interesting anyway if anyone got similar symptoms.