Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 02 Oct 2009 18:57:14 -0500
From:      Robert Noland <rnoland@FreeBSD.org>
To:        Richard Kolkovich <sarumont@sigil.org>
Cc:        freebsd-x11@freebsd.org
Subject:   Re: HD4550 DRI issues
Message-ID:  <1254527834.25163.154.camel@balrog.2hip.net>
In-Reply-To: <20091002010109.GA8828@divination.portal.sigil.org>
References:  <20090926001158.GA42914@divination.portal.sigil.org> <1253925689.2065.81.camel@balrog.2hip.net> <20090926045706.GB42914@divination.portal.sigil.org> <1253977337.2048.17.camel@balrog.2hip.net> <1253993801.2048.295.camel@balrog.2hip.net> <20090926194802.GA67832@divination.portal.sigil.org> <1254001621.2048.431.camel@balrog.2hip.net> <20091001021855.GE36488@magus.portal.sigil.org> <1254392190.98309.750.camel@balrog.2hip.net> <20091001153307.GF36488@magus.portal.sigil.org> <20091002010109.GA8828@divination.portal.sigil.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2009-10-01 at 20:01 -0500, Richard Kolkovich wrote:
> On Thu, Oct 01, 2009 at 10:33:07AM -0500, Richard Kolkovich wrote:
> > On Thu, Oct 01, 2009 at 05:16:30AM -0500, Robert Noland wrote:
> > > I've spent a fair amount of time digging through the mmap and memory
> > > allocation bits in the kernel, but haven't found anything that looks
> > > wrong.  What I don't understand is, why this doesn't effect all or at
> > > least all i386 systems.  So, I think it almost has to be chipset
> > > specific. .... Well, I just went back and found one of the prior reports
> > > of this.  It looks like that (assuming it is the same cause) was on an
> > > intel 945 chipset running 7.2-RELEASE i386.  Have you considered running
> > > amd64?  Your i7 is certainly worthy of it and I would be curious to see
> > > if the problem exists when running amd64 also.
> > > 
> > 
> > Go figure...my first Intel board/CPU, and I stumble across something like this. :P
> > 
> > I had considered trying amd64 after I saw your setup was amd64.  I've never had too much reason for
> > running amd64, but I could justify it now that I'm using zfs.  ;)
> > 
> > I may give amd64 a shot later today and let you know if that helps.
> 
> i386 + mtrr disabled doesn't do jack.
> 
> Fresh amd64 install, installed xf86-video-ati and ran your DRM test.  Contents?  Empty.

Ok, that seems like good news then...

> I'm building xorg right now to make sure the displays mirror this result...I'll let you know.
> 
> I just thought about this, though.  Do you think something in my make.conf could be causing this
> problem?  I don't think I've ever tried on a kernel and world I did not build.  I only have 
> CPUTYPE=core2 set (that would affect kernel/world compiling).

It's possible... It is generally not recommended to mess with cpu
flags...  I used to use them as well, but I ran into a few cases where I
needed to re-use a disk and didn't have compatible hardware handy, so I
just use the default -O2 -pipe now.

robert.

> 
-- 
Robert Noland <rnoland@FreeBSD.org>
FreeBSD




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1254527834.25163.154.camel>