From owner-freebsd-current@FreeBSD.ORG  Fri Jan 14 01:11:19 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by hub.freebsd.org (Postfix) with ESMTP id 7CDD810656A7;
	Fri, 14 Jan 2011 01:11:18 +0000 (UTC)
	(envelope-from jkim@FreeBSD.org)
From: Jung-uk Kim <jkim@FreeBSD.org>
To: Ariff Abdullah <ariff@freebsd.org>
Date: Thu, 13 Jan 2011 20:10:58 -0500
User-Agent: KMail/1.6.2
References: <30407800.3251371294783096175.JavaMail.root@wmail14>
	<201101131524.55309.jkim@FreeBSD.org>
	<20110114072031.041b5700.ariff@FreeBSD.org>
In-Reply-To: <20110114072031.041b5700.ariff@FreeBSD.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201101132011.05107.jkim@FreeBSD.org>
Cc: freebsd-current@freebsd.org, eculp@encontacto.net
Subject: Re: R: Recent mouse freeze problem with X, different window managers,
	any browser and flash.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2011 01:11:19 -0000

On Thursday 13 January 2011 06:20 pm, Ariff Abdullah wrote:
> On Thu, 13 Jan 2011 15:24:52 -0500
>
> Jung-uk Kim <jkim@FreeBSD.org> wrote:
> > On Thursday 13 January 2011 01:14 pm, Jung-uk Kim wrote:
> > > On Wednesday 12 January 2011 10:22 pm, Ariff Abdullah wrote:
> > > > On Wed, 12 Jan 2011 09:53:03 -0600
> > > >
> > > > eculp <eculp@encontacto.net> wrote:
> > > > > Quoting Ariff Abdullah <ariff@FreeBSD.org>:
> > > > > > On Wed, 12 Jan 2011 22:51:29 +0800
> > > > > > Ariff Abdullah <ariff@FreeBSD.org> wrote:
> > > > > >
> > > > > > [....]
> > > > > >
> > > > > >> Try disabling mtrr, machdep.disable_mtrrs=0 through
> > > > > >> boot prompt or /boot/loader.conf.
> > > > > >
> > > > > > Grr.. should be machdep.disable_mtrrs=1
> > > > >
> > > > > Caught it, changed it en loader.conf, rebooted and have had
> > > > > youtube
> > > > >
> > > > > running more that 10 minutes with no ill affects.
> > > >
> > > > Keep in mind that disabling mtrr is a temporary measure.
> > > >
> > > > > Want to clarify that this in with current i386.
> > > > >
> > > > > 9.0-CURRENT FreeBSD 9.0-CURRENT #161: Wed Jan 12 04:38:15
> > > > > CST 2011
> > > > >
> > > > > root@home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO 
> > > > > i386
> > > > >
> > > > > Thanks again,
> > > > >
> > > > > ed
> > > > >
> > > > > Thanks so much for your help.
> > > > >
> > > > > ed
> > > > >
> > > > > >> If that is the case, you probably want this:
> > > > > >>
> > > > > >> http://people.freebsd.org/~ariff/misc/mtrr.diff
> > > >
> > > > This breakage was due to r215415 commit. Jung-uk Kim, any
> > > > idea ?
> >
> > Can you please try the attached patch *without* ariff's
> > workaround?
>
> X Display corruption and erratic mouse behaviour still occured.
>
> Hardware is Thinkpad x100e using single-core Athlon Neo running
> r217079 / amd64 .
>
> CPU: AMD Athlon(tm) Neo Processor MV-40 (1596.12-MHz K8-class CPU)
>   Origin = "AuthenticAMD"  Id = 0x70ff2  Family = f  Model = 7f
> Stepping = 2
> Features =
> 0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,
> PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
> Features2=0x2001<SSE3,CX16>
> AMD Features =
>     0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>
> AMD Features2=
>     0x11d<LAHF,SVM,ExtAPIC,CR8,Prefetch>

Okay.  I just wanted to make sure there's no strangeness with intial 
value from BIOS.  Although I think I know why it happens, I am not 
sure how to fix it properly.  If I cannot come up with a better idea 
soon, I can commit your patch and restore the previous behaviour.

Thanks,

Jung-uk Kim