From owner-freebsd-current@FreeBSD.ORG Thu Oct 21 10:12:06 2004 Return-Path: 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 3623416A4CE for ; Thu, 21 Oct 2004 10:12:06 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BA7643D2D for ; Thu, 21 Oct 2004 10:12:05 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i9LAC39S054093; Thu, 21 Oct 2004 12:12:03 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <41778B74.2040508@withagen.nl> Date: Thu, 21 Oct 2004 12:12:04 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eirik Oeverby References: <1098341179.52186.7.camel@eirik.unicore.no> <4177884C.7030503@withagen.nl> <1098353001.52186.35.camel@eirik.unicore.no> In-Reply-To: <1098353001.52186.35.camel@eirik.unicore.no> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: Weirdness in RELENG_5 on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 10:12:06 -0000 Eirik Oeverby wrote: > This is a Tyan S2882 board - K8S Pro I believe, with an AMD chipset. > > >>You are not running this hardware, are you? Otherwise strongly I suggest >>changing it. I swapped it for Tyan Tiger, and no more of these problems since. The other story I was told is that Tyan is once in a while sloppy with its BIOSes. And as such not all revision are of equal quality. You said the box is far away, so flashing BIOSes is not going to be fun. And it might even get you in worse shape.... > Well, they are still there ;) > Built a new kernel today, as I see a number of issues were resolved in > RC1, however I want to wait for the next crash - if/when it happens. It > is possible I could get some useful info out of it. > > No clue about the serial console questions I had? Nope, sorry. But have you tried: *.* /dev/ttyd0 I tried it and seems to do something on my serial console. --WjW