Greetings all;

A re-repeat of a previous posting which has not drawn a comment. With added
content, added CC to a patch author, and some new questions.

Machine is an F8 install, Athlon xp-2800 on an nforce2 motherboard, running 
an older radeon 9200SE (RV280 based) video card.  No problems if I reboot 
to 2.6.27-rc4.

I'm drowning in these errors:

Aug 30 13:21:05 coyote kernel: [14927.850078] [drm] wait for fifo failed status : 0x80076100 0x00000000
Aug 30 13:21:05 coyote kernel: [14927.861335] [drm] wait for fifo failed status : 0x80076100 0x00000000
Aug 30 13:21:05 coyote kernel: [14928.060233] [drm] wait idle failed status : 0x80076100 0x00000000
Aug 30 13:21:07 coyote kernel: [14929.557075] [drm] wait for fifo failed status : 0x80076100 0x00000000
Aug 30 13:21:07 coyote kernel: [14929.568869] [drm] wait for fifo failed status : 0x80076100 0x00000000
Aug 30 13:21:08 coyote kernel: [14931.028882] [drm] wait for fifo failed status : 0x80036100 0x00000000
Aug 30 13:21:08 coyote kernel: [14931.039896] [drm] wait for fifo failed status : 0x80076100 0x00000000
Aug 30 13:21:18 coyote kernel: [14940.515114] [drm] wait for fifo failed status : 0x80076100 0x00000000
Aug 30 13:27:27 coyote kernel: [15310.125656] [drm] wait for fifo failed status : 0x80066107 0x00000000

I have rebuilt and rebooted several times now, adjusting things like the 
timer frequency, and modular vs builtin for ati and drm stuff with no
apparent effect.

The .config is attached for the build under way now.  Do I have something 
fubar'd?  Or is this a newly hatched bug?

Thanks.

Digging deeper, I found this in drivers/gpu/drm/radeon/radeon.c:
========
static int radeon_do_wait_for_fifo(drm_radeon_private_t * dev_priv, int entries)
{
        int i;

        dev_priv->stats.boxes |= RADEON_BOX_WAIT_IDLE;

        for (i = 0; i < dev_priv->usec_timeout; i++) {
                int slots = (RADEON_READ(RADEON_RBBM_STATUS)
                             & RADEON_RBBM_FIFOCNT_MASK);
                if (slots ...
[ message continues ]

On Sat, 30 Aug 2008 14:52:04 -0400


since half this sort of driver is in userspace it helps if you also add
the version of the userspace driver you are using (and if you changed
it recently)

-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--

[ message continues ]

Hello Arjan,


AFAIK, only thing which is changed in linux kernel. firmware and
userspace is same.

Thank you,

Jaswinder Singh.
--

[ message continues ]

Before now we never had this error in here, and its showing up a real
problem with your card, reading the r300 register doesn't matter at
all,
as things have already gone wrong by the time you hit this debug.

The question is if you add the 3 lines into radeon_cp.c at the same
place in -rc4 without the other patches does it still happen..
       DRM_INFO("wait for fifo failed status : 0x%08X 0x%08X\n",
                RADEON_READ(RADEON_RBBM_STATUS),
                RADEON_READ(R300_VAP_CNTL_STATUS));

If so I'll just make DRM_INFO into DRM_DEBUG for now and we can work
it out later.

Dave.
--

[ message continues ]

Hello Gene,


This is not because of my radeon firmware patch, my patch is still in
pipeline. Here is the list of developers who played with radeon :-

1. 4 days ago 	Linus Torvalds 	Merge branch 'drm-patches' of
git://git.kernel.org ...
2. 7 days ago 	Nicolai Haehnle 	drm/radeon: r300_cmdbuf: Always emit
INDX_BUFFER immediately ...
3. 7 days ago 	Jerome Glisse 	radeon: fix some hard lockups on r3/4/500s
4. 2008-08-12 	David Miller 	radeonfb: fix accel engine hangs
5. 2008-08-05 	Jean Delvare 	radeonfb: give i2c buses nicer names
6. 2008-08-05 	David Miller 	radeon: misc corrections
7. 2008-07-24 	Tony Breeds 	drivers/video/aty/radeon_base.c: notify

On F8 machine with radeon 9200SE with 2.6.27-rc5, I am also getting
similar messages :

[drm] Loading R200 Microcode
[drm] writeback test succeeded in 1 usecs
[drm] wait idle failed status : 0x83E8C13D 0x00000000
[drm] wait idle failed status : 0x83E8C13D 0x00000000
[drm] wait idle failed status : 0x83E8C13D 0x00000000
[drm] wait idle failed status : 0x83E8C13D 0x00000000
[drm] wait for fifo failed status : 0x8006613B 0x00000000
[drm] wait for fifo failed status : 0x80066121 0x00000000
[drm] wait for fifo failed status : 0x8006613B 0x00000000
[drm] wait for fifo failed status : 0x80076100 0x00000000
[drm] wait for fifo failed status : 0x80076100 0x00000000
[drm] wait for fifo failed status : 0x80076100 0x00000000
[drm] wait for fifo failed status : 0x80076100 0x00000000
[drm] wait for fifo failed status : 0x80076100 0x00000000
[drm] wait for fifo failed status : 0x80076100 0x00000000
[drm] wait for fifo failed status : 0x80076100 0x00000000
[drm] wait for fifo failed status : 0x80076100 0x00000000
[drm] wait for fifo failed status : 0x80076100 0x00000000
[drm] wait for fifo failed status : 0x80076100 0x00000000
[drm] wait for fifo failed status : 0x80076100 0x00000000
[drm] wait for fifo failed status : 0x80076100 0x00000000
[drm] wait for fifo failed status : 0x80076100 0x00000000
[drm] wait for fifo failed status : ...
[ message continues ]

radeonfb != drm/radeon

-- 
Jean Delvare
--

[ message continues ]

Hello Jean,


yes you are right.

Sorry, to disturb other guy. Messages are coming from :
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=54f961a628...

Jerome Glisse and Dave Airlie :

+       DRM_INFO("wait for fifo failed status : 0x%08X 0x%08X\n",
+                RADEON_READ(RADEON_RBBM_STATUS),
+                RADEON_READ(R300_VAP_CNTL_STATUS));

+       DRM_INFO("wait idle failed status : 0x%08X 0x%08X\n",
+                RADEON_READ(RADEON_RBBM_STATUS),
+                RADEON_READ(R300_VAP_CNTL_STATUS));

what is the idea of printing R300 STATUS on R200 code or common code ?

Please let me know what is the solution of R200 problem ?

Thank you,

Jaswinder Singh.
--

[ message continues ]

On Tue, Sep 2, 2008 at 4:40 AM, Jaswinder Singh

I've already submitted patches to Linus to downgrade the warning for
now, reading the r300 on r200 doesn't matter at all,

Finding the reason for the FIFO stalls on r200 requires further
investigation, it apparently has been happening for "ever",
we just never printed the debug before.

Dave.
--

[ message continues ]

Dave Arlie has a patch that converts the DRM_INFO to DRM_DEBUG, which sticks a 
muffler on that.  Posted on lkml yesterday, it doesn't fix the problem but 
does shut it up.  The actual statement that causes that I put in every kernel 
back to 2.6.27-rc1, and they all do similar reports, so this is a long 
standing, and apparently mostly harmless bug.  I have seen zero screen 
corruption other than the terminals scrolling leaving trash '_' behind and 
has been for at least a year.

Thanks Jaswinder.
-- 
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)
Winning isn't everything.  It's the only thing.
		-- Vince Lombardi
--

[ message continues ]