Re: Debian initramfs/initrd, was Re: stack smashing detected

[Stan Johnson <userm57@yahoo.com>]

On 2/5/23 4:18 PM, John Paul Adrian Glaubitz wrote:
> On Mon, 2023-02-06 at 09:29 +1100, Finn Thain wrote:
>> ...
> 
>> When you need to generate a valid Debian/m68k vmlinux/initrd combination 
>> that is also current, then you'll need a Debian/m68k system that is 
>> current. The quickest way to get it is an emulator.
> 
> Correct.
> ...

Adrian and Finn,

Thanks, that's good to know.

FYI,

On an SE/30 with 128 MiB memory, the latest Debian SID kernel
(vmlinux-6.1.0-2-m68k), using Debian SID modules, and with
initrd-6.1.0-2-m68k built on the SE/30, hangs after the initial
"ABCFGHIJK" (I tried it twice).

On a Mac IIci with 80 MiB memory, using the same setup, except with the
initrd-6.1.0-2-m68k built in QEMU, the system boots and there were no
stack smashing errors (only one boot, though, and it took over 30
minutes to reach multiuser). The NIC (mac8390: MacCon Ethernet, type
asante) wasn't seen. So I guess it's likely that I never booted an
unmodified Debian SID kernel on the IIci, but instead used a modified
kernel with the NIC added and obvious things (such as USB, Firewire,
wireless, etc.) removed. And my 6.1.8 kernel is further modified to
disable modules and initrd, and I apparently also disabled other things
such as polling of the CD drive (the activity light no longer blinks
every two seconds). Booting my custom 6.1.8 kernel, I see stack smashing
again, so it's possible that my choice of kernel options is making the
stack smashing more likely to occur, but there's not enough data at this
point to make that conclusion.

I'll send an update after I add the patch that Michael mentioned.

thanks

-Stan