[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Crash in tme -- mm58167.c
> On Mar 7, 2020, at 11:23 PM, Rin Okuyama <rokuyama.rk%gmail.com@localhost> wrote:
> You are using your own custom kernel, aren't you?
No, I was using the RAMDISK / INSTALL kernel and the pre-built NetBSD 9 binaries, with TME configured for 4MB of RAM.
> GENERIC kernel for sun2 had not been bootable on TME, at least
> since Jan 2019, when I worked for this PR:
> It turned out to be due to restriction by bootloader which maps
> only 2MB (0x400000 to 0x5fffff) for kernel. Even if firmware could
> load kernel, it hangs with:
> scsibus0: waiting 2 seconds for devices to settle...
> I don't know whether this is related to your problem or not. For me,
> further reduction of kernel size seems to fix a problem.
> I added module(7) support for sun2, and striped off most kernel
> options from GENERIC kernel. However, GENERIC is still near 2MB and
> should exceed the limit in the near future...
> Also, for recent -HEAD, kernel was frozen during early boot stage
> in mutex_exit(9). I fixed this too.
> Now, GENERIC kernel from -HEAD successfully boots for me on TME.
> Still, services_mkdb(8) does not complete, but killing it by ^C
> brings the system to multiuser.
I haven't had a full multi-user boot yet because I copied the FOURMEG kernel into place and now have the "unable to load kernel" problem.
Main Index |
Thread Index |