Messages in this thread | | | Date | Thu, 24 Feb 2022 09:22:04 -0500 | From | matoro <> | Subject | Re: regression: Bug 215601 - gcc segv at startup on ia64 |
| |
Hi Kees, I can provide live ssh access to my system exhibiting the issue. My system is a lot more stable due to using openrc rather than systemd, for me GCC seems to be the only binary affected. Would that be helpful?
On 2022-02-24 04:33, John Paul Adrian Glaubitz wrote: > Hi Kees! > > On 2/24/22 06:16, Kees Cook wrote: >>> You should be able to extract the binaries from this initrd image and >>> the "mount" command, >>> for example, should be one of the affected binaries. >> >> In dmesg, do you see any of these reports? >> >> pr_info("%d (%s): Uhuuh, elf segment at %px requested >> but the memory is mapped already\n", >> task_pid_nr(current), current->comm, (void >> *)addr); > > I'll check that. > >> I don't see anything out of order in the "mount" binary from the above >> initrd. What does "readelf -lW" show for the GCC you're seeing >> failures >> on? > > I'm not 100% sure whether it's the mount binary that is affected. What > happens is that once init takes over, > I'm seeing multiple "Segmentation Fault" message on the console until > I'm dropped to the initrd shell. > > I can check what dmesg says. > > Adrian
| |