>Number:         4172
>Category:       kern
>Synopsis:       panic: bha_init_ccb: can't create DMA maps
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Sep 27 14:05:01 1997
>Last-Modified:
>Originator:     Brad Spencer
>Organization:
	At home one weekend
>Release:        9/26/97 1.2G i386
>Environment:
trying to update to 1.2G from 9/26 source from the system:

System: NetBSD anduin.eldar.org 1.2B NetBSD 1.2B (ANDUIN) #13: Sat Dec 14 11:00:39 EST 1996 brad@anduin.eldar.org:/usr/src/sys/arch/i386/compile/ANDUIN i386


>Description:
	A reasonable amount of disk activity will panic the system
	with the following panic:

	panic: bha_init_ccb: can't create DMA maps

>How-To-Repeat:
	Given 48MB of core and 3 swap partitions and two BT946 controllers.

Set ddb.onpanic=0.

Started the X server [16 bit color, 1280x1024 with a nice picture in
the root window], then Netscape 4, then Executor.  As Executor starts,
some swapping occures, the system then "freezes", lots of disk
activity occures as the panic progresses, and a reboot.

The following message is printed on reboot during savecore.

Sep 27 16:15:44 anduin savecore: reboot after panic: bha_init_ccb: can't create DMA maps

>Fix:
	No idea.  However, it appears that the panic doesn't happen
until swap occures [this may be false, as the disks were quite a bit
more active by this time, activity may be the problem].  Setting the
swaps up so that they are not interlaced [that is, all at a different
priority level] only delays the problem.

Crash dump available upon request.


>Audit-Trail:
>Unformatted: