mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dave Airlie" <airlied@gmail.com>
To: "Gene Heskett" <gene.heskett@verizon.net>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Jaswinder Singh" <jaswinder@infradead.org>,
	xorg@lists.freedesktop.org
Subject: Re: Linux-2.6.27-rc5, drm errors in log
Date: Sun, 31 Aug 2008 07:06:26 +1000	[thread overview]
Message-ID: <21d7e9970808301406x6310c7b9w2ef663cbf40b5e61@mail.gmail.com> (raw)
In-Reply-To: <200808301452.04634.gene.heskett@verizon.net>

On Sun, Aug 31, 2008 at 4:52 AM, Gene Heskett <gene.heskett@verizon.net> wrote:
> 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.

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.

  parent reply	other threads:[~2008-08-30 21:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-30 18:52 Gene Heskett
2008-08-30 19:22 ` Arjan van de Ven
2008-09-01 17:15   ` Jaswinder Singh
2008-08-30 21:06 ` Dave Airlie [this message]
2008-09-01 16:34 ` Jaswinder Singh
2008-09-01 17:52   ` Jean Delvare
2008-09-01 18:40     ` Jaswinder Singh
2008-09-01 20:49       ` Dave Airlie
2008-09-02  5:06   ` Gene Heskett
     [not found] <898503EB1E15BA4F944D1BE69D55AAC8AB540A@storexmb1.amd.com>
     [not found] ` <200808302219.45103.gene.heskett@verizon.net>
2008-08-31  6:40   ` Dave Airlie
2008-08-31 10:55     ` Gene Heskett
2008-08-31 11:57       ` Gene Heskett
2008-08-31 18:23       ` Gene Heskett
2008-08-31 20:56         ` Dave Airlie
2008-09-01  1:01           ` Gene Heskett
2008-09-01 16:51       ` Jaswinder Singh
2008-09-02  5:13         ` Gene Heskett
  -- strict thread matches above, loose matches on Subject: below --
2008-08-30 17:39 Gene Heskett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21d7e9970808301406x6310c7b9w2ef663cbf40b5e61@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=gene.heskett@verizon.net \
    --cc=jaswinder@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xorg@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®