From owner-freebsd-hackers  Mon Dec 21 04:58:25 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id EAA19915
          for freebsd-hackers-outgoing; Mon, 21 Dec 1998 04:58:25 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19910
          for <hackers@freebsd.org>; Mon, 21 Dec 1998 04:58:23 -0800 (PST)
          (envelope-from tom@tomqnx.com)
Received: by TomQNX.tomqnx.com (Smail3.2 #1)
	id m0zs4ui-000I4yC; Mon, 21 Dec 1998 07:58:20 -0500 (EST)
Message-Id: <m0zs4ui-000I4yC@TomQNX.tomqnx.com>
From: tom@tomqnx.com (Tom Torrance at home)
Subject: kernel panic
To: hackers@FreeBSD.ORG
Date: Mon, 21 Dec 1998 07:58:20 -0500 (EST)
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Last week, x11amp seemed to work absolutely reliably with the OSS sound
system. (x11amp -b 1024 on FreeBSD-current with creative AWE-64).

I updated the system Sunday AM with cvsup and ever since, I get
a kernel panic within 5 minutes of starting x11amp. First the sound
stops, with x11amp happily executing, then in 3-4 seconds, panicsville.
No core dump that I could ascertain.

Any hints? Any recent changes affecting dma, virtual memory
swapping, etc?

Regards,
Tom

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