Date: Tue, 18 Nov 2003 21:05:57 -0600 From: Tillman Hodgson <tillman@seekingfire.com> To: sparc64@freebsd.org Subject: Re: ultra5/cmd646 hang Message-ID: <20031118210557.X16032@seekingfire.com> In-Reply-To: <p0600202cbbe04a3aa321@[128.113.24.47]>; from drosih@rpi.edu on Tue, Nov 18, 2003 at 05:26:12PM -0500 References: <20031114105853.A92204@carver.gumbysoft.com> <20031114134001.D92204@carver.gumbysoft.com> <20031117130205.R22102@carver.gumbysoft.com> <p06002021bbdf0a93b762@[128.113.24.47]> <xzpbrraxdii.fsf@dwp.des.no> <p0600202cbbe04a3aa321@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <drosih@rpi.edu> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031118210557.X16032>