From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752748AbcCGPKq (ORCPT ); Mon, 7 Mar 2016 10:10:46 -0500 Received: from g9t5008.houston.hp.com ([15.240.92.66]:44590 "EHLO g9t5008.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752642AbcCGPKi (ORCPT ); Mon, 7 Mar 2016 10:10:38 -0500 Message-ID: <1457366596.15454.281.camel@hpe.com> Subject: Re: runtime regression with "x86/mm/pat: Emulate PAT when it is disabled" From: Toshi Kani To: Paul Gortmaker Cc: Borislav Petkov , Richard Purdie , Toshi Kani , Bruce Ashfield , openembedded-core , "Hart, Darren" , "saul.wold" , linux-kernel@vger.kernel.org Date: Mon, 07 Mar 2016 09:03:16 -0700 In-Reply-To: <20160307003501.GB26051@windriver.com> References: <20160303205924.GA25222@windriver.com> <1457067768.15454.181.camel@hpe.com> <20160304183713.GA26051@windriver.com> <1457129560.15454.266.camel@hpe.com> <20160307003501.GB26051@windriver.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.4 (3.18.4-1.fc23) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2016-03-06 at 19:35 -0500, Paul Gortmaker wrote: > [Re: runtime regression with "x86/mm/pat: Emulate PAT when it is > disabled"] On 04/03/2016 (Fri 15:12) Toshi Kani wrote: > > > On Fri, 2016-03-04 at 13:37 -0500, Paul Gortmaker wrote: > > > [Re: runtime regression with "x86/mm/pat: Emulate PAT when it is > > > disabled"] On 03/03/2016 (Thu 22:02) Toshi Kani wrote: > > > : > > I am not really sure what I am doing is correct. > > > > On one window: > > # ./00-runme > > Warning: vlan 0 is not connected to host network > > VNC server running on '::1:5900' > > Ah, it seems for some reason your system confuses qemu from using the > "normal"  IPv4 default.   Try editing ./00-runme and add an explicit > vnc option    "-vnc 127.0.0.1:5" in front of "-show-cursor" and then: > > > > > And another window on the same system: > > # vncviewer localhost:1 > > ...connect to localhost:5  here.  I chose 5 just to not bump into > anything your system might have on :0 or :1 already. Still no luck.  Perhaps, vlan needs to connect? # ./00-runme Warning: vlan 0 is not connected to host network # vncviewer localhost:5 TigerVNC Viewer 64-bit v1.6.0 Built on: 2016-01-04 15:09 Copyright (C) 1999-2015 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Can't open display:  > I'm assuming everyone here is used to reading diffs, but if someone > wants the full dmesg files let me know and I'll send them off-list. Yes, please send me full dmesg files.  Since I do not know your original state, the diff does not give me the whole picture. Thanks! -Toshi