From owner-freebsd-sparc64@FreeBSD.ORG Tue Feb 26 01:34:08 2013 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 96890DF1 for ; Tue, 26 Feb 2013 01:34:08 +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 ECAD9320 for ; Tue, 26 Feb 2013 01:34:07 +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 r1Q1Y1bI082558; Tue, 26 Feb 2013 02:34:01 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.6/8.14.6/Submit) id r1Q1Y0PH082557; Tue, 26 Feb 2013 02:34:00 +0100 (CET) (envelope-from marius) Date: Tue, 26 Feb 2013 02:34:00 +0100 From: Marius Strobl To: Chris Ross Subject: Re: Problems booting 9.1-STABLE on Netra X1 Message-ID: <20130226013400.GG955@alchemy.franken.de> References: <20130225101315.GA79064@alchemy.franken.de> <76C74932-5BB0-4194-86CE-F121F6D18D84@distal.com> <20130225214941.GD955@alchemy.franken.de> <3A37672E-B6F7-4D5E-8293-0ED3B203C358@distal.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3A37672E-B6F7-4D5E-8293-0ED3B203C358@distal.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-sparc64@freebsd.org" X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2013 01:34:08 -0000 On Mon, Feb 25, 2013 at 04:59:10PM -0500, Chris Ross wrote: > > On Feb 25, 2013, at 4:49 PM, Marius Strobl wrote: > > Yes, IMO this approach is inappropriate as there really seems to be > > something broken with this particular machine rather than this issue > > being a general problem with that model, i.e. nobody else running > > FreeBSD on an X1 reported this so far. I don't own an X1 but I do > > have a v100, which employ a mainboard pretty much identical to that > > of X1 and even also identify themselves as SUNW,UltraAX-i2, but don't > > see such a problem, i.e. neither the power fail interrupt firing nor > > strange hangs, either. Once I have a replacement for the broken > > hardware of my committatron I can make registering the power fail > > interrupt a tunable defaulting to on though. > > > Well, Dave McGuire did respond on that thread that he was running > NetBSD 4.0.1 with no problems, but someone else (Jochen Kunz) > said they tried netbooting a 4.0.1 kernel on an X1 and got the same > hang I did. > > The code that's in place in the NetBSD tree was actually committed > later, it seems, as a result of this other thread that the earlier thread > was resurrected on: > > http://mail-index.netbsd.org/port-sparc64/2011/02/12/msg001515.html > > So, at least 2 people, and 3 if I'm reading my personal email archives > correctly, have seen this problem on an X1. And, it seems at least one > person was _not_ seeing it. (But later seeing some other problem when > a CD-ROM was attached to the IDE bus, even when not in use/netbooting) > > It's clearly low-end hardware, and I could believe that it may be a "affects > some but not all systems". But, assuming it's more than just _one_ bogus > system, finding a way to deal with it at HEAD makes sense. Not necessarily > that the earlier code is the only or best solution. > Will do, I have to think about this some more though. Marius