From owner-freebsd-bugs@FreeBSD.ORG  Tue Sep 30 17:51:59 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6F1E216A4BF; Tue, 30 Sep 2003 17:51:59 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B03DE43FE9; Tue, 30 Sep 2003 17:51:58 -0700 (PDT)
	(envelope-from bms@FreeBSD.org)
Received: from freefall.freebsd.org (bms@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h910pwFY081439;
	Tue, 30 Sep 2003 17:51:58 -0700 (PDT)
	(envelope-from bms@freefall.freebsd.org)
Received: (from bms@localhost)
	by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h910pwWf081435;
	Tue, 30 Sep 2003 17:51:58 -0700 (PDT)
	(envelope-from bms)
Date: Tue, 30 Sep 2003 17:51:58 -0700 (PDT)
From: Bruce M Simpson <bms@FreeBSD.org>
Message-Id: <200310010051.h910pwWf081435@freefall.freebsd.org>
To: bms@FreeBSD.org, freebsd-bugs@FreeBSD.org, bms@FreeBSD.org
Subject: Re: kern/53481: 5.1R does not recognise xl0 at every startup
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Oct 2003 00:51:59 -0000

Synopsis: 5.1R does not recognise xl0 at every startup

Responsible-Changed-From-To: freebsd-bugs->bms
Responsible-Changed-By: bms
Responsible-Changed-When: Tue 30 Sep 2003 17:51:17 PDT
Responsible-Changed-Why: 
I'll take ownership of this, as I have hardware which is affected by
the same bug. I think this is a hardware bug so I don't hold out much
hope for a solution, but I'll speak to wpaul anyway.

http://www.freebsd.org/cgi/query-pr.cgi?pr=53481