From owner-freebsd-current Mon Jan 13 3:46:26 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26A6337B401 for ; Mon, 13 Jan 2003 03:46:25 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 553A743F13 for ; Mon, 13 Jan 2003 03:46:24 -0800 (PST) (envelope-from phk@freebsd.org) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id h0DBk46A069104; Mon, 13 Jan 2003 12:46:08 +0100 (CET) (envelope-from phk@freebsd.org) To: "Roderick van Domburg" Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 5.0 RC3 now available From: phk@freebsd.org In-Reply-To: Your message of "Mon, 13 Jan 2003 12:14:12 +0100." Date: Mon, 13 Jan 2003 12:46:04 +0100 Message-ID: <69103.1042458364@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , "Roderick van Domburg" writes: >I would like to point to a currently unresolved issue that Thomas Moestl is >helping me solve on freebsd-sparc@. It isn't listed on the Open Issues page, >but I'd say it's something that needs to be resolved before the release is >rolled. > >The thread is titled "panic: trap: fast data access mmu miss" and is about >an error causing the sym SCSI controller to fail to mount root at best, and >panic at worst. Well, we all want our pet bug fixed before the release rolls, but at some point we simply have to call it quits and ship the release. I personally know this particular bug very well, I have rebooted the AC/DC200 netra I had borrowed about 10 times more than I needed to to get past this bug :-) >The sym controller is listed as supported hardware, and used in several Sun >boxes, so IMHO I'd say it warrants the attention. All bugs warrent attention. Some of them get it. Don't worry, that bug, like all the others will get fixed and you will be able to get an update for it in due time. In the meantime we _really_ have to ship 5.0-RELEASE, we keep slipping it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message