On 2/7/23 4:20 PM, Finn Thain wrote: > > On Tue, 7 Feb 2023, Stan Johnson wrote: > ... > Preventing pointless key generation would be beneficial for all Macs, > Amigas, Ataris, emulators etc. and measuring the performance of one model > of Mac versus that of another model seems a bit irrelevant to me. >
Sure, but unless Debian unsupported is willing to manage config files for the various systems, then it's not likely to happen. I currently use separate config files for the following Macs, to build kernels with no initrd, no modules, and only minimal network and video support: 1) 68030 8 MiB, no network (PB-170) 2) 68030 >8 MiB (SE/30, IIci, IIfx, Centris LC III, etc.) 3) 68040 (Centris 650, PB 550c, etc.) It doesn't seem unusual that users should maintain their own config files, since there's no way Debian unsupported could be expected to know which options may apply to individual users' systems. > Moreover, you've shown that your kernel builds produce stack smashing > errors whereas Debian's build does not. To resolve the problem with your > builds, why not begin by eliminating some of the differences between your > build and Debian's? The stack smashing appears to be intermittent. And it doesn't show up while booting the kernel; it only shows up while sysvinit scripts are running (I haven't tested using systemd, since that would be too painful on any 68030 slower than about 40 MHz). It takes too long to boot slow systems using Debian's kernel to run repeated tests, and QEMU only emulates 68040, so it appears to be necessary to test on real hardware. It's not my goal to get my config files closer to Debian's, anyway. My goal is to have the fewest number of config files for different groups of systems. If anyone knows of a 68030 emulator (maybe Basilisk?) that can boot Linux, then I might be able to use that for faster testing. > I suggest you should adopt the current Debian SID build environment and > toolchain use it to build mainline Linux (stock v6.1) using QEMU. I use QEMU to install Debian SID. The latest versions of Debian SID, Debian kernel, initrd and modules all work great in QEMU. I then copy the Debian SID rootfs to various 680x0 systems, but I don't use the Debian kernel, initrd or modules. > If you use your .config and if you still get stack smashing errors then > you can use the script I wrote to bisect the differences between your > .config and Debian's .config. > If the stack smashing is caused by a kernel bug that is hidden by Debian's choice of config options, then it would still be useful to identify the bug. If there is something missing from my config files that is causing the problem, then that would still be a kernel bug in its sanity checking of options. Your script will be helpful if it becomes necessary to identify specific offending options. -Stan
