Bug 26999

Sent upstream, waiting for response.  Please attach Xserver log, messages
log, X configuration.

Created attachment 9863 [details]
/var/log/XFree86.0.log

Does this work with 4.0.2-0.11 or later?

OK, looks like it is fixed.  I installed XFree86-4.0.2-11.4.0 and the messages
stopped.

I am still getting an occational message "drm:-r128_init] *ERROR* Cannot
initialize agpgart module." but otherwise it lloks good.

If acceptable , close this as appropriate.

Oops ... I misspoke.

I had XFree86 4.0.2-11 installed and the error was not occuring.  I just
installed 4.0.2-11.4.0 and the origianl error message is back ("...wait for fifo").

Try the latest release please - XFree86-4.0.2-12.1 out located at:
ftp://people.redhat.com/mharris/xfree86

Also, make sure you have Mesa-3.4-10 installed, and you're using the
latest rawhide kernel.  You MUST use the latest kernel to get the r128
kernel fix.  If that doesn't work, please submit new log attachments,
and configs as well, and reopen the bug.

XFree86 4.0.2-12.1 and Mesa 3.4-10 now installed.

Problem is still there

Created attachment 12346 [details]
4.0.2-12.1 log file

Oops.  I missed the fact that I need to upgrade the kernel too.  Unfortunately,
rawhide on the ftp beta site is missing the kernel-smp for i686.  Since I do not
feel like rebuilding the kernel rpm right now, I will give the i586 package a try.

OK, I am running kernel-smp-242-0.1.25 (i586 rather than my usual i686) and
modutils-2.4.2-5.

Problem is still there.

I will attach the log and the/etc/X11/XF86Config-4 files.  Anything else?

Created attachment 12347 [details]
with XFree86, Mesa, and kernel-smp-2.4.2-0.1.25

Created attachment 12348 [details]
with XFree86, Mesa, and kernel-smp-2.4.2-0.1.25

Fixed in 4.0.2a-1 in Rawhide

OK, I installed XFree86-4.0.2a-1 from the mharris directory on people.redhat.com
(and MEsa 3.4-12 from rawhide on the beta ftp).

Problem not fixed unfortunately.  I am still getting the messages in the log.

As before, this is running kernel-smp-2.4.2-0.1.25.

The XF86Config-4 has not changed.  I will attach the log.

Gene

Created attachment 12803 [details]
XFree86.0.log on 4.0.2a-1

Boy, this one is really puzzling..  Can you run the following commands and
include file attachments of each of their outputs please?

rpm -qa | sort > installed-packages.txt
uname -a
lspci -vn
lspci -v

This _might_ be an smp specific issue.

I don't believe it is smp related.  I previously ran it with my up kernel and
still got the messages (the MB is still smp naturally).  I just ran it again and
still messages.  I did not run it long be did get the messages.  I notice that
lots of these messages occur in the middle of the night when xscreensaver is
running.

Attachments follow.

Created attachment 12885 [details]
rpm -qa | sort > installed-packages.txt

Created attachment 12886 [details]
uname -a

Created attachment 12887 [details]
lspci -vn

Created attachment 12888 [details]
lspci -v

Ok, thanks for all the info.  My 4.0.3-1 release contains a patch for
this bug now.  Please try it out as it appears to solve the problem
during my testing.

XFree86-4.0.3-1 and Mesa-3.4-13 at ftp://people.redhat.com/mharris

qa0328 -- the problem is back and filling /var/log/mesages again.

I am attaching the usual set of files

Created attachment 14345 [details]
/var/log/XFree86.0.log

Created attachment 14346 [details]
/etc/X11/XF86Config-4

Created attachment 14347 [details]
rpm -qa | sort

Created attachment 14348 [details]
uname -a

Created attachment 14349 [details]
lspci -vn

Created attachment 14350 [details]
lspci -v

I think we're on to something here..  Attach me a copy of:

/proc/cpuinfo

*** Bug 28987 has been marked as a duplicate of this bug. ***

Created attachment 14367 [details]
dual PIII 800MHz

I, see bug 28987, see this messages with Athlon-750 with Rage 128 *PF*. 
Reducing color depth tp 16bpp didn't solve the problem, but messages are more 
rare: on X start-up, and once each time I run 3d screensaver. The do appear 
harmless though. I'll attack my logs later today.

Created attachment 14423 [details]
same behavior on single Athlon system

This is still occuring on 7.1 Gold.  Do you still need additional information?

Created attachment 15864 [details]
dmesg - same mistake along with  "mtrr mismatch ..."

Created attachment 16165 [details]
lspci -v output as requested

Created attachment 16166 [details]
XFree log as requested (incxludes reboot)

Ok, it looks like our kernel was missing an additional patch that caused
several people to still experience this.  It is added into our current
kernel builds and will be released as an errata sometime in the near
future.

Yes, kernel 2.4.3-5.i686 from rawhide fixed that for me.

*** Bug 42211 has been marked as a duplicate of this bug. ***