🚀 go-pugleaf

I have an Amiga 2500/30 and customarily run SetCPU (1.5) in my startup
sequence to enable Burst mode and Data Cache.  I have read some
warnings about things that can get messed up when using Data Cache
but have not until now experienced any problems.

In trying to get NetHack3.0 up on my machine I have successfully gotten
everything to compile (using Lattice 5.04) but couldn't get the link
to run.  It would guru every time in the middle of running blink and
would force my hard disk to validate on the subsequent re-boot.  One time
the disk validation was unable to complete and my disk was lost (thank
goodness, I had a backup).  Anyway...to make a long story short, it 
occured to me to try turning off the 68030's burst and data cache modes
and then the link ran just fine!  So...I've got a reproducible case
where data cache gets things messed up and I'm curious to know about
any other things to watch out for.  Are there any other specific things
that shouldn't be done with data cache (and/or burst mode) enabled?
Should this be considered a bug in Blink?  I understand that it is probably
DMA that screws up data cache so I should mention that I am using a
Microbotics Hardframe disk controller.  Would any other DMA controller
have similar problems?