On Tue, Feb 15, 2022 at 1:23 PM Marc Haber <mh+debian-packa...@zugschlus.de> wrote: > > On Tue, Feb 15, 2022 at 12:56:54PM +0200, Martin-Éric Racine wrote: > > On Thu, Feb 3, 2022 at 10:14 AM Martin-Éric Racine > > <martin-eric.rac...@iki.fi> wrote: > > > On Thu, Feb 3, 2022 at 10:10 AM Marc Haber > > > <mh+debian-packa...@zugschlus.de> wrote: > > > > On Thu, Feb 03, 2022 at 09:55:53AM +0200, Martin-Éric Racine wrote: > > > > > On Thu, Feb 3, 2022 at 9:41 AM Marc Haber > > > > > <mh+debian-packa...@zugschlus.de> wrote: > > > > > > > > > > > > On Thu, Feb 03, 2022 at 09:11:10AM +0200, Martin-Éric Racine wrote: > > > > > > > On a Geode LX (i686 without PAE), the most recent sudo dumps > > > > > > > core. dmesg shows the following: > > > > > > > > > > > > Just for the record, the current i386 sudo was built on x86-ubc-02, > > > > > > Logs > > > > > > https://buildd.debian.org/status/logs.php?pkg=sudo&ver=1.9.9-1&arch=i386 > > > > > > > > > > > > I guess this might be a toolchain or autobuilder issue. > > > > > > > > > > The log suggests that this was built on an amd64 host configured with > > > > > a 386 chroot. This might explain it. Putting the port maintainers in > > > > > CC. > > > > > > > > I also see > > > > Kernel taint flags: TAINT_CPU_OUT_OF_SPEC > > > > > > > > Is Geode LX a supported machine in Bullseye in the first place? I > > > > understand that the ALIX boards use that CPU and that they are rather > > > > widely deployed, but... > > > > > > The base level kernel for i386 (linux-image-686) currently is a kernel > > > configured for Geode. > > > > > > CONFIG_MGEODE_LX=y > > > > Hello again, > > > > Is there any progress on this? Have you checked wiht upstream for > > possible changes in the code that would explain this? > > Not yet. Can you confirm that old sudo upstream works with the current > toolchain? Sadly, I don't have any 32 bit systems left other than some > ARMs.
Logged onto my unstable-i386 chroot. $ dget http://deb.debian.org/debian/pool/main/s/sudo/sudo_1.9.5p2-3.dsc Fetched build-deps. $ debuild -uc -us Copied sudo and sudo-dbgsym over to the Geode host. Logged onto the Geode host. $ su dpkg -i sudo*.deb Logged onto Geode host as a normal user. Tried a sudo command. No core dump. Command works as expected. This would suggest upstream changes as the source of the problem. Martin-Éric
