Date: Thu, 11 Dec 2003 19:25:47 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Tillman Hodgson <tillman@seekingfire.com> Cc: sparc64@freebsd.org Subject: Re: ultra5/cmd646 hang Message-ID: <20031212032547.GA8974@xor.obsecurity.org> In-Reply-To: <20031212031736.GB64340@seekingfire.com> 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]> <20031118210557.X16032@seekingfire.com> <20031212031736.GB64340@seekingfire.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 11, 2003 at 09:17:36PM -0600, Tillman Hodgson wrote: > On Tue, Nov 18, 2003 at 09:05:57PM -0600, Tillman Hodgson wrote: > > 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=3D0) and boot > > > >your new kernel. Slow as hell, but it works. > > >=20 > > > Okay, I tried that. It did not print out the > > > ata3: resetting devices .. > > > message, but it died with a panic: > >=20 > > 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. >=20 > For the record and archives: >=20 > I built a new current with today's sources and it boots fine. Somewhere > between early-to-mid November and now someone must've fixed the problem > :-) I forwarded the commit message that fixed this problem a few weeks ago. Kris --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/2TU7Wry0BWjoQKURAjmyAJ9CY7KusUCdPrhrjnKTmbNiG4SOOACfRaHN UHfURdzQwNRyxvT20lN+gxU= =ldL8 -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031212032547.GA8974>