Hmm I'm just looking at the patches I put in for rc5, and there is no
functional difference to the
r200 codepath that I can see from those patches apart from the debug prints.

Can you get a clean -rc4 and apply just 54f961a628b737f66710eca0b0d95346645dd33e
to it.

See if you can get that to produce the errors, if it does, apply just
the drm info chunks, try again, if that works, try adding
the isync cntl chunk. and re-testing. I can't see how writing isync
cntl here would affect things though.

Dave.
--

[ message continues ]

Update: there were 3 of those in the log after I sent the denial msg.
======
Aug 30 23:48:34 coyote kernel: [ 7242.890000] [drm] wait for fifo failed status : 0x80076100 0x00000000
Aug 30 23:57:51 coyote kernel: [ 7800.370001] [drm] wait for fifo failed status : 0x8003C100 0x00000000
Aug 30 23:57:51 coyote kernel: [ 7800.458000] [drm] wait for fifo failed status : 0x8007C100 0x00000000
======

Yes I can, but how do I get that specific patch?  Or is that the git # for the
patch I first applied to -rc2, which added the firmware/radeon stuff?  I'm 
familiar with patch, but not on a first name basis with git, sorry.

So I'm going to do a bisect, my style.  I will rebuild, starting with -rc3, 
using only the -rcX patch and the firmware addition patch, which applied to
-rc3 as follows:
now applying [PATCH]radeon_cp-use-request_firmware

patching file drivers/gpu/drm/radeon/radeon_cp.c
patching file drivers/gpu/drm/radeon/radeon_drv.h
patching file drivers/gpu/drm/radeon/radeon_microcode.h
patching file firmware/Makefile
Hunk #1 FAILED at 34.
1 out of 1 hunk FAILED -- saving rejects to file firmware/Makefile.rej
===So I added that into the firmware/Makefile at line 28 by hand===
patching file firmware/WHENCE
Hunk #1 succeeded at 339 (offset -233 lines).
patching file firmware/radeon/R100_cp.bin.ihex
patching file firmware/radeon/R200_cp.bin.ihex
patching file firmware/radeon/R300_cp.bin.ihex
patching file firmware/radeon/R420_cp.bin.ihex
patching file firmware/radeon/R520_cp.bin.ihex
patching file firmware/radeon/RS600_cp.bin.ihex
patching file firmware/radeon/RS690_cp.bin.ihex

patch [PATCH]radeon_cp-use-request_firmware done

=== and I'm watching the build for errors===
It got past the MK_FW for those ok. 
However there were 6 section miss-matches reported, and the suggested
addition to .config did not make it any noisier so I'm no smarter.
Now I've added those 3 reporter lines to radeon_cp.c, rebuilt again and 
will reboot to -rc3 for effects, reporting after a few hours ...
[ message continues ]

Yeah I know, its bad form replying to one own messages, but 2.6.27-rc3 is 
doing it too.  So next I add the reporter to -rc1, without the firmware patch 
as its a sure bet -rc2 will do it too.  And will report back in a few hours.

Thanks Dave.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
		-- Benjamin Franklin, 1759
--

[ message continues ]

Ok Dave, I have chased it all the way back to rc1 by adding those 3 lines of 
reporter, and at 2.6.27-rc1 it is still doing it.  This is without the radeon 
firmware patch, but since the microcode is still there in /lib/firmware, the 
log says it is still being loaded.

I am beginning to think this is a very old bug, and this evening I will try 
those 3 reporter lines added to 2.6.25.4 as I still have that src tree here.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Have you seen the latest Japanese camera?  Apparently it is so fast it can
photograph an American with his mouth shut!
--

[ message continues ]

I think you've probably always had the problem, we just never reported
it before.

There are some timeouts that may be set too low somewhere in userspace
and we may need to adjust them.

Dave.
--

[ message continues ]

I'm thinking along those lines myself.  And I'm assuming that -rc5 is 10x 
worse because the added code in user space is now slow enough to trigger it 
easier.

That also takes me back to one of my original Q's , and that was the question 

Thanks Dave.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Live Free or Live in Massachusettes.
--

[ message continues ]

Hello Gene,


This patch is not included in 2.6.27-rc5. Please do not mix this patch
now, first resolve your problem and if you want then you can add this
patch above of it.

Thank you,

Jaswinder Singh.
--

[ message continues ]

I see.  However, since the stuff in /lib/firmware is already there from 
previous builds that did include this patch, and I didn't delete it, I noted 
that the 2.6.27-rc5 I built last night, without that patch, still loaded the 
r200 microcode according to the messages log, and dmesg.  From dmesg:

[root@coyote /]# dmesg|grep drm
[    1.389274] [drm] Initialized drm 1.1.0 20060810
[    1.389707] [drm] Initialized radeon 1.29.0 20080528 on minor 0
[   85.920881] [drm] Setting GART location based on new memory map
[   85.920894] [drm] Loading R200 Microcode

Thank you!

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Good leaders being scarce, following yourself is allowed.
--

[ message continues ]