bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libdiskfs assertion failed


From: Samuel Thibault
Subject: Re: libdiskfs assertion failed
Date: Sat, 27 May 2023 11:39:54 +0200
User-agent: NeoMutt/20170609 (1.8.3)

Joshua Branson, le ven. 26 mai 2023 11:02:44 -0400, a ecrit:
> Samuel Thibault <samuel.thibault@gnu.org> writes:
> > Joshua Branson, le jeu. 25 mai 2023 22:32:24 -0400, a ecrit:
> >> So I updated my T43 to the bleeding edge Debian in real hardware, which
> >> come on that is pretty cool!  The update process was pretty easy.  I
> >> will describe that in the postscript.  I did get this error recently
> >> when I shutdown the Hurd:
> >> 
> >> extfs: ../../libdiskfs/disk-pager.c:107: fault_handler: Assertion
> >> 'scp->sc_error = 10' failed.
> >
> > Mmm, perhaps you can make it print the scp->sc_error value so we get an
> > idea of what that is?
> 
> How would I go about printing that scp->sc_error value?

Add before the assert 

if (scp->sc_error != EKERN_MEMORY_ERROR)
    fprintf(stderr, "error %d\n", scp->sc_error);

and rebuild.

> I am running this in machine in real hardware.  I get that error message
> after I run "sudo poweroff".  I see that error message right before the
> Hurd gets halted.  I imagine I need to turn on the kernel debugger to
> print that value.

It'll be hard to catch it from the kernel, which doesn't really care
much when some program exits.

> >> #+BEGIN_SRC shell
> >> wget
> >> http://ftp.de.debian.org/debian/pool/main/d/debian-ports-archive-keyring/debian-ports-archive-keyring_2023.02.01_all.deb
> >> #+END_SRC
> >
> > Rather use https
> >
> >> #+BEGIN_SRC
> >> apt-get update
> >> apt-get dist-upgrade
> >> #+END_SRC
> >> 
> >> The "apt-get dist-upgrade" command did fail for me.
> >
> > How did it fail?
> 
> I wish I had written it down.  It downloaded all the packages, then
> tried to update gnumach, then that failed and it said that I needed to
> upgrade gnumach, reboot, update libc, then upgrade the Hurd.  Or
> something like that.

Which image did you start from? There used to be this upgrading process
yes, but that dates back glibc 2.33, not glibc 2.34.

Samuel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]