> Hrm, this may be a side effect of the nextdma.c fix, but I can't be
> sure.  I haven't seen this yet, although I've switched my main machine
> to working on 1.4.2.  I should boot up another one to keep -current

Well, I was thinking of switching this guy to 1.4.2 also, I don't suppose
you've pulled up the nextdma.c fix yet? My slab runs a darn sight better
in spite of this latest crash, and I'd certainly like to do 1.4.2 builds
(right now my next68k is the only build machine I have that _hasn't_ gone
back to 1.4.2_ALPHA).

> I wouldn't be too surprised to see this problem if the DMA stopped and
> wasn't restarted correctly.  Since we no longer check for premature
> DMA shutdowns, there still may be a race condition if the DMA shuts
> down and we don't notice it.  (The nextdma.c patch fixed the race
> condition if the dma shutdown between when we check and when we act on
> it) There is probably a way around this.

Hm, can we throw a specific panic in to detect that case, so when it happens
again we might be able to confirm the theory?

>  FYI: The "NDMAP: blah blah blah" is a dump of the complete nextdma
> software and hardware state, which would explain what it was expecting
> and what it actually found.  I don't recommend you type it in by hand,
> but if you get it on a loggable serial console, save it around.

I can take QuickCam photos of it, but I have to do that before a backtrace.
This time it's too late, the top third has scrolled off screen already.

Todd Whitesel
toddpw @ best.com