Re: Anyone can run a -current kernel?

Rin Okuyama <[email protected]> Thu, 6 Feb 2020 18:33:53 +0900
Newsgroups gmane.os.netbsd.ports.mac68k
Message-ID <[email protected]>
On 2020/02/06 0:07, Martin Husemann wrote:
> On Wed, Feb 05, 2020 at 10:58:52AM +0100, Martin Husemann wrote:
>> I have some trouble booting -current kernels on my mac68k machine - the
>> kernel is quite unhappy with its root file system (see PR 54935 for
>> what I initially thought would be file system corruption).
>>
>> This is on a Centris 660AV  (68040).
> 
> FWIW: a -current amiga kernel boots fine and is happy with the filesystem.
> 
> Could something have gone wrong with the 660AV scsi dma changes? My previous
> kernel was quite old, maybe I only tested with the patches but never later
> with the final commited thing?

IMO, SCSI DMA code is not guilty :). Panics occur regardless of whether
SCSI DMA is enabled or not. I sent a PR for this problem:

   http://gnats.netbsd.org/54942

In short:

I believe this is because DMA controller transfers data for low physical
address to pollute kernel text, before kernel halts and initializes it.
We need to halt DMA controller in Booter, not kernel. Here's binary-
patched version of Booter:

   http://www.netbsd.org/~rin/BSD_Mac68k_Booter.AV.20190818.bin
   (CAUTION: this version should not work on non-AV Macs)

   Some unorganized notes what I did for Booter:
   http://www.netbsd.org/~rin/Booter/

I've never observed this kind of panics with this version of Booter.
Can you test it?

Thanks,
rin