From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 21 Aug 2001 21:55:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 21 Aug 2001 21:54:58 -0400 Received: from chmls20.mediaone.net ([24.147.1.156]:22407 "EHLO chmls20.mediaone.net") by vger.kernel.org with ESMTP id ; Tue, 21 Aug 2001 21:54:42 -0400 To: linux-kernel@vger.kernel.org Subject: Fw: Re: mtrr: base(0xf8000000) is not aligned on a size(0x180000) boundary From: bwlang@langhorst.com Reply-To: bwlang@langhorst.com X-Mailer: AeroMail (http://the.cushman.net/reverb/aeromail/) MIME-version: 1.0 Content-type: multipart/mixed; boundary="Message-Boundary" Content-transfer-encoding: 7BIT Message-Id: Date: Tue, 21 Aug 2001 21:54:52 -0400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org --Message-Boundary Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body upgrade to X 4.1 fixes this problem ... however maybe kernel should handle inappropriate X calls better? brad Bradley W. Langhorst wrote: > I get this message on boot with kernel 2.4.9 on a Dell Optiplex GX110 > running redhat 7.0 with X upgraded to 4.0.3-5 with rpms from rh 7.1 > ... > > my search for answers using mtrr 2.4 i810 turns up nothing of > interest so maybe this is a new problem? > > > please advise > > thanks! > > brad > --Message-Boundary Content-type: ; name="" Content-Transfer-Encoding: BASE64 Content-disposition: attachment; filename="" DQo= --Message-Boundary--