On 2/3/23 4:39 PM, Finn Thain wrote: Hi Finn,
> On Wed, 1 Feb 2023, Stan Johnson wrote: > >> >> After logging the start and end of each script, I see that the "stack >> smashing detected" error often happens while running >> "/etc/rcS.d/S01mountkernfs.sh" (/etc/init.d/mountkernfs.sh). I'll try to >> isolate it to a particular command. >> > > That brings to mind some other unresolved initscript failures, also > involving 68030, which were accompanied by "page allocation failure". > > But it's hard to blame "stack smashing detected" on a page allocation > failure since the latter always produces a very noisy splat in the kernel > messages. > > Have you reproduced the error with Debian's kernel package? Yes, but with the previous Debian kernel (I will try with the latest kernel on the IIci to confirm). > > If not, please refer to private correspondence from me dated 10 December > 2022 regarding setting up /etc/initramfs-tools so as to produce a suitably > small initramfs. I did see that, but I don't think it's relevant for my current tests -- to save time, I'm using a custom kernel, with no initramfs and no modules (6.1.8, though I think 6.1.9 is out). > > To save time, I recommend using QEMU and an up-to-date Debian/m68k SID > virtual machine to produce the vmlinux and initrd files needed for use > with Penguin on your slower machines. > AFAIK, the initrd must be created on the system that is using the initrd (or an identical system, at least that was the response I received a while back when I was unsuccessfully trying to use the initrd that ships on the Debian install CD). I have confirmed that the stack smashing also occurs on an SE/30 using my custom 6.1.8 kernel and the latest Debian SID. While that does not rule out a hardware problem on my IIci or SE/30, it would be unlikely that I would have the same problem on both systems. I'll proceed with testing Debian's latest default kernel on the IIci (with Debian's modules and an initrd created on the IIci), then I'll investigate either isolating the offending executable (apparently in /etc/rcS.d/S01mountkernfs.sh) or I'll check whether a git bisect might identify anything interesting, though I first need to locate the latest mainline kernel that doesn't have the problem and the earliest one that does. It's possible that QEMU (I'm using 7.2) doesn't see the problem because it emulates a 68040 for q800 and virt; so far I've only seen the issue on 68030 systems. -Stan
