From owner-freebsd-bugs  Tue Apr 27  9:56:41 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id B655614DD4; Tue, 27 Apr 1999 09:56:40 -0700 (PDT)
	(envelope-from ken@FreeBSD.org)
Received: (from ken@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id JAA80360;
	Tue, 27 Apr 1999 09:56:40 -0700 (PDT)
	(envelope-from ken@FreeBSD.org)
Date: Tue, 27 Apr 1999 09:56:40 -0700 (PDT)
From: <ken@FreeBSD.org>
Message-Id: <199904271656.JAA80360@freefall.freebsd.org>
To: ovg@msu.dubna.ru, ken@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: kern/11325: kernel panic on boot, probably in CAM
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: kernel panic on boot, probably in CAM

State-Changed-From-To: open->closed
State-Changed-By: ken
State-Changed-When: Tue Apr 27 09:54:51 PDT 1999
State-Changed-Why: 
The submitter says that the machine in question is now running fine, after
he added 'device pass0' to his config file, and put 'flags 0x40' on the
ppc0 device.  My guess is that the latter fixed his problem.
He also says that the machine is a critical server, and he can't look into
the problem further.
If he runs into the problem again, he can submit a new PR.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message