On Thu, Jan 23, 2003 at 09:06:00AM -0700, Marc Aurele La France wrote: > > All these issues show up when an attempt is made to initialise the adapter > more than once between resets (i.e. reboots).
Yes. I have noticed that the first invocation of the server after a reboot (at least starts out) is clean. But it seems to degrade. Using the 20030122 snapshot, I have a mostly clear screen, but it gets the corruption artifacts when certain "pixmap" operations are performed. For instance, Galeon 1.3.1 frequently shows the corruption in it's windows while other parts of the screen are not corrupt. If I scroll the galeon HTML widget the corruption follows the scroll and if I scroll back, it comes back clean. At various other times every window on the screen including the root window will show the corruption, but often I can just move a window around the screen and "wipe" the corruption away. > The original patch submission for this #ifdef'ed itself for Alpha's. But > the truth is that these are adapter issues. That they show up more on > certain architectures than others is irrelevent. So can we have the code that is #ifdef'd for Alphas not #ifdefe'd before the next snapshot then? Let's see if it improves the problems on Intel platforms too. Thanx, b. -- Brian J. Murrell
msg00940/pgp00000.pgp
Description: PGP signature
