linux-kernel - Re: linux-2.6.27-rc5, new msgs in log

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 29 Aug 2008 06:48:33 -0400
From:	Gene Heskett <gene.heskett@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: linux-2.6.27-rc5, new msgs in log

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/