From: Gene Heskett <gene.heskett@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.27-rc5, new msgs in log
Date: Fri, 29 Aug 2008 06:48:33 -0400 [thread overview]
Message-ID: <200808290648.34040.gene.heskett@gmail.com> (raw)
Greetings;
x86 box, athlon xp-2800, 1 GB ram, built w/o the 4GB switch enabled so
it is only seeing 8xx megs, new build with that re-enabled in progress.
I have been building the radeon firmware in my kernels since the initial
patch adding them came out at about rc2 or so, as my build script carries
my old .config's forward before doing a 'make oldconfig', and by copying
the patches resultant firmware/radeon tree forward to each new -rcX.
I am now seeing these in the messages file:
Aug 29 01:16:05 coyote kernel: [ 363.201194] [drm] wait for fifo failed status : 0x80076100 0x00000000
Aug 29 01:16:05 coyote kernel: [ 363.212257] [drm] wait for fifo failed status : 0x80026138 0x00000000
Aug 29 01:22:29 coyote kernel: [ 747.797152] [drm] wait for fifo failed status : 0x80066100 0x00000000
That was at bootup time, and 20 minutes ago when I woke the monitor up again:
Aug 29 06:19:32 coyote kernel: [18570.160855] [drm] wait for fifo failed status : 0x80066107 0x00000000
Aug 29 06:20:26 coyote kernel: [18624.592825] [drm] wait for fifo failed status : 0x80066100 0x00000000
Aug 29 06:20:38 coyote kernel: [18636.513621] [drm] wait for fifo failed status : 0x8006610F 0x00000000
Aug 29 06:20:42 coyote kernel: [18640.370596] [drm] wait for fifo failed status : 0x80066107 0x00000000
Aug 29 06:20:49 coyote kernel: [18647.200431] [drm] wait for fifo failed status : 0x8006610F 0x00000000
Aug 29 06:20:53 coyote kernel: [18651.481310] [drm] wait for fifo failed status : 0x80066100 0x00000000
Aug 29 06:21:44 coyote kernel: [18702.575087] [drm] wait for fifo failed status : 0x8006610F 0x00000000
Aug 29 06:21:49 coyote kernel: [18707.424341] [drm] wait for fifo failed status : 0x80076100 0x00000000
Aug 29 06:21:58 coyote kernel: [18716.581872] [drm] wait for fifo failed status : 0x80066107 0x00000000
Aug 29 06:22:28 coyote kernel: [18745.979819] [drm] wait for fifo failed status : 0x80066107 0x00000000
Do I have a problem or has the driver just been made noisier?
Thanks.
--
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)
Nothing ever becomes real until it is experienced.
- John Keats
reply other threads:[~2008-08-29 10:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200808290648.34040.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=linux-kernel@vger.kernel.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