From owner-freebsd-current Fri Apr 30 11:10: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 21BD014DDF for ; Fri, 30 Apr 1999 11:09:59 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA14693; Fri, 30 Apr 1999 11:09:58 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA15921; Fri, 30 Apr 1999 11:09:58 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 30 Apr 1999 11:09:58 -0700 (PDT) Message-Id: <199904301809.LAA15921@vashon.polstra.com> To: sgk@troutmask.apl.washington.edu Subject: Re: PCM In-Reply-To: <199904301717.KAA03659@troutmask.apl.washington.edu> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199904301717.KAA03659@troutmask.apl.washington.edu>, Steve Kargl wrote: > John Polstra wrote: > > > > Well, it's worse than broken. Merely including pcm0 in the kernel > > config file causes instant panic on boot-up with my machine (new > > kernel built last night from fresh sources): > > > > It must be something that entered the tree late yesterday afternoon or > an interaction between devices. [successful boot transcript omitted] On a hunch, I built the kernel again from the same sources but starting with a clean compile directory. This time it worked. So it appears that the panic I got wasn't something inherent in the kernel, but rather was a build problem. I'm certain that I typed "make depend" before building the bad kernel. So I think there must be a missing dependency somewhere. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message