From owner-freebsd-stable@FreeBSD.ORG  Sat Jan 22 18:45:59 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AFA0D16A4CE
	for <freebsd-stable@freebsd.org>;
	Sat, 22 Jan 2005 18:45:59 +0000 (GMT)
Received: from silver.he.iki.fi (helenius.fi [193.64.42.241])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EFD1043D49
	for <freebsd-stable@freebsd.org>;
	Sat, 22 Jan 2005 18:45:58 +0000 (GMT)	(envelope-from pete@he.iki.fi)
Received: from [193.64.42.134] (h86.vuokselantie10.fi [193.64.42.134])
	by silver.he.iki.fi (8.13.1/8.11.4) with ESMTP id j0MIjw01009896
	for <freebsd-stable@freebsd.org>;
	Sat, 22 Jan 2005 20:45:58 +0200 (EET)	(envelope-from pete@he.iki.fi)
Message-ID: <41F29F69.1040509@he.iki.fi>
Date: Sat, 22 Jan 2005 20:46:01 +0200
From: Petri Helenius <pete@he.iki.fi>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: hang at fxp0 with RELENG_5
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jan 2005 18:45:59 -0000


I upgraded a dual xeon from 5.3 to RELENG_5 a few days ago and the boot 
hangs after probing fxp0. Should I compile kernel debugger in and look 
for a stack trace or is there a known issue? This on intel 7505 board.

Pete