Re: Linux-2.6.27-rc5, drm errors in log

["Dave Airlie" <airlied@gmail.com>]

On Tue, Sep 2, 2008 at 4:40 AM, Jaswinder Singh
<jaswinderlinux@gmail.com> wrote:
> Hello Jean,
>
> On Mon, Sep 1, 2008 at 1:52 PM, Jean Delvare <khali@linux-fr.org> wrote:
>> On Mon, 1 Sep 2008 12:34:28 -0400, Jaswinder Singh wrote:
>>> Hello Gene,
>>>
>>> On Sat, Aug 30, 2008 at 2:52 PM, Gene Heskett <gene.heskett@verizon.net> wrote:
>>> >
>>> > 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.
>>> >
>>>
>>> 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
>>> user if sysfs ...
>>
>> radeonfb != drm/radeon
>>
>
> 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=54f961a628b737f66710eca0b0d95346645dd33e
>
> 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 ?
>

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.