From owner-freebsd-x11@FreeBSD.ORG Sat Jun 15 13:47:19 2013 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 749D41F3; Sat, 15 Jun 2013 13:47:19 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 1309E1877; Sat, 15 Jun 2013 13:47:18 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.6/8.14.6/ALCHEMY.FRANKEN.DE) with ESMTP id r5FDlGZW022657; Sat, 15 Jun 2013 15:47:16 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.6/8.14.6/Submit) id r5FDlGsQ022656; Sat, 15 Jun 2013 15:47:16 +0200 (CEST) (envelope-from marius) Date: Sat, 15 Jun 2013 15:47:16 +0200 From: Marius Strobl To: mexas@bristol.ac.uk Subject: Re: sparc64 machfb: (EE) Unable to map mmio aperture. Invalid argument (22) Message-ID: <20130615134716.GA22046@alchemy.franken.de> References: <201306131014.r5DAEUmh030099@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201306131014.r5DAEUmh030099@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-x11@freebsd.org, freebsd-sparc64@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jun 2013 13:47:19 -0000 On Thu, Jun 13, 2013 at 11:14:30AM +0100, Anton Shterenlikht wrote: > I've just updated my Sun Blade 1500 silver > to 10.0-CURRENT #11 r251648. The graphics broke. > I get: > > (EE) Unable to map mmio aperture. Invalid argument (22) > > from X -configure > > # dmesg|grep mach > machfb0: port 0xb00-0xbff mem 0x3000000-0x3ffffff,0x102000-0x102ff > f at device 2.0 on pci0 > machfb0: console > machfb0: 16 MB aperture at 0xfddcc000 not swapped > machfb0: 8188 KB SGRAM 114.992 MHz, maximum RAMDAC clock 230 MHz, DSP > machfb0: resolution 1280x1024 at 8 bpp > # > > # pkg info -xo mach6 > xf86-video-mach64-6.9.3: x11-drivers/xf86-video-mach64 > # > > # cat /var/log/Xorg.0.log > > X.Org X Server 1.7.7 > Release Date: 2010-05-04 > X Protocol Version 11, Revision 0 > Build Operating System: FreeBSD 10.0-CURRENT sparc64 > Current Operating System: FreeBSD mech-anton240.men.bris.ac.uk 10.0-CURRENT Free > BSD 10.0-CURRENT #11 r251648: Thu Jun 13 10:20:15 BST 2013 root@mech-anton24 > 0.men.bris.ac.uk:/usr/obj/usr/src/sys/QOF sparc64 > Build Date: 03 June 2013 03:14:51PM Well, at least machfb(4) hasn't changed in quite some time so it's not immediately obvious what is causing this problem. However, that Xorg.0.log suggests that the server also has been rebuilt recently and in fact there was an Xorg update on May 25. Could you please determine (at least by using the old/previous known-working kernel) whether a change to the kernel or to ports is the culprit? Marius