Re: [BUG] Xserver startup locks system... git bisect results

["Mark M. Hoffman" <mhoffman@lightlink.com>]

Hi Benjamin:

* Benjamin Herrenschmidt <benh@kernel.crashing.org> [2005-12-15 15:53:03 +1100]:
> On Wed, 2005-12-14 at 23:32 -0500, Mark M. Hoffman wrote:
> > Hello:
> > 
> > git bisect said:
> > > 47807ce381acc34a7ffee2b42e35e96c0f322e52 is first bad commit
> > > diff-tree 47807ce381acc34a7ffee2b42e35e96c0f322e52 (from 0e670506668a43e1355b8f10c33d081a676bd521)
> > > Author: Dave Airlie <airlied@linux.ie>
> > > Date:   Tue Dec 13 04:18:41 2005 +0000
> > > 
> > >     [drm] fix radeon aperture issue
> > 
> > With this one applied, my machine locks up tight just after starting the
> > Xserver.  Some info (dmesg, lspci, config) is here:
> > 
> > http://members.dca.net/mhoffman/lkml-20051214/
> > 
> > I can put a serial console on it if necessary, but not until about this
> > time tomorrow.
> 
> You have to love this X radeon driver ... you can't fix one bug without
> breaking something else, it's one of the worst piece of crap I've ever
> seen...
> 
> What would be useful now is the X version and maybe trying a little hack
> in the X driver. Do you have ways to rebuild the X driver at all ?

Check the link again for log & config.  I have not built any part of X
from source before.  But if it's necessary, I will try it.

> The problem is, that patch actually fixes some users... Ah, also, could
> you maybe add some printk's around the code that is modified by that
> patch and try to catch the value it tries to use before the lockup ?
> 
> That is, print the values of:
> 
> dev_priv->fb_location
> 
> and
> 
> RADEON_READ(RADEON_CONFIG_APER_SIZE)

These suggestions, along with later ones that involve recompiles... I will try
them late this evening (EST).

Regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com

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