From owner-freebsd-sparc64@FreeBSD.ORG Tue Nov 18 19:06:00 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D155D16A4CE for ; Tue, 18 Nov 2003 19:06:00 -0800 (PST) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADB1C43F93 for ; Tue, 18 Nov 2003 19:05:59 -0800 (PST) (envelope-from tillman@seekingfire.com) Received: from blues.seekingfire.prv (blues.seekingfire.prv [192.168.23.211]) by mail.seekingfire.com (Postfix) with ESMTP id BDBF382 for ; Tue, 18 Nov 2003 21:05:58 -0600 (CST) Received: (from tillman@localhost) by blues.seekingfire.prv (8.11.6/8.11.6) id hAJ35wW07552 for sparc64@freebsd.org; Tue, 18 Nov 2003 21:05:58 -0600 Date: Tue, 18 Nov 2003 21:05:57 -0600 From: Tillman Hodgson To: sparc64@freebsd.org Message-ID: <20031118210557.X16032@seekingfire.com> References: <20031114105853.A92204@carver.gumbysoft.com> <20031114134001.D92204@carver.gumbysoft.com> <20031117130205.R22102@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from drosih@rpi.edu on Tue, Nov 18, 2003 at 05:26:12PM -0500 X-Urban-Legend: There is lots of hidden information in headers Subject: Re: ultra5/cmd646 hang X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 03:06:00 -0000 On Tue, Nov 18, 2003 at 05:26:12PM -0500, Garance A Drosihn wrote: > At 9:54 AM +0100 11/18/03, Dag-Erling Smørgrav wrote: > >Garance A Drosihn writes: > > > Well, for what it's worth I hit something vaguely similar > > > on my Ultra-10 [...] > > > Unfortunately, I then mistakenly blew away my working > > > kernel, so right now I can't boot up the machine at all. [...] > > > >Just disable DMA in the loader (set hw.ata.ata_dma=0) and boot > >your new kernel. Slow as hell, but it works. > > Okay, I tried that. It did not print out the > ata3: resetting devices .. > message, but it died with a panic: I'm also having the same problem on an Ultra 5 (see the archives for details if you're interested). If you chose to reinstall and want to avoid this issue until it gets cleared up, avoid source newer than Oct 29 which (from sombody else's posting) is the last date that appears to boot properly by failing back to PIO mode. -T -- There is no such thing as 'social gambling.' Either you are there to cut the other bloke's heart out and eat it - or you're a sucker. If you don't like this choice - don't gamble. - Robert Heinlein