Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754388AbYFPAmI (ORCPT ); Sun, 15 Jun 2008 20:42:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751188AbYFPAlz (ORCPT ); Sun, 15 Jun 2008 20:41:55 -0400 Received: from mga11.intel.com ([192.55.52.93]:5422 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751186AbYFPAly (ORCPT ); Sun, 15 Jun 2008 20:41:54 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.27,649,1204531200"; d="scan'208";a="577887479" Date: Sun, 15 Jun 2008 17:41:53 -0700 From: Suresh Siddha To: Frans Pop Cc: "Siddha, Suresh B" , "Rafael J. Wysocki" , Linux Kernel Mailing List , "Pallipadi, Venkatesh" , Ingo Molnar , "arjan@linux.intel.com" , "jbarnes@virtuousgeek.org" Subject: Re: [Bug 10843] Display artifacts on XOrg logout with PAT kernel and VESA framebuffer Message-ID: <20080616004153.GA7788@linux-os.sc.intel.com> References: <200806142359.36613.elendil@planet.nl> <8B23168BCBB43B49A4C8EAB32D4B62F1061F3A82@orsmsx505.amr.corp.intel.com> <200806160102.11717.elendil@planet.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200806160102.11717.elendil@planet.nl> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1747 Lines: 36 On Sun, Jun 15, 2008 at 04:02:10PM -0700, Frans Pop wrote: > I've done 4 successive boots with the boot parameters as shown below. > Each boot was basically: set correct parameters in grub -> login to KDE > -> reboot and check for artifacts. > > 1) (none) --> clean > 2) vga=791 --> artifacts > 3) vga=791 nopat --> clean > 4) vga=791 video=vesafb:mtrr:3 --> artifacts > > So the mtrr option did not help (if I passed it correctly; the double ":" > is somewhat non-intuitive). The kernel log also does not show any > difference I can see in the last boot, but I don't know if the mtrr option > is supposed to show up in any way. If the initlevel is '3', then the mtrr option will show up in /proc/mtrr otheriwse not. In init level '5', X server will add the mtrr (irrespective of boot option, if it's not already there) and will remove it when the X process completes its execution. Can you also please try if "mtrr:1" makes any difference. This will setup the mapping as UC during boot. Apart from PAT WC mapping(which we shouldn't be using in your current setup), UC MTRR should override all the other PAT mappings and should be consistent across X and VT console mappings. As such, if the problem is because of improper aliasing, then with this UC MTRR, my understanding is that we shouldn't see any artifacts with the "mtrr:1". with this mtrr:1, we should now see a UC mtrr setting in /proc/mtrr. thanks, suresh -- 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/