This story is for experts. Distro jockeys get lost.

I performed my Gentoo update over the weekend. The next time I booted my system it just hung.

The messages indicated that the keyboard was being sensed by the kernel and so I assumed the keyboard was faulty. I ripped a keyboard from my Microslop machine and used that in place of the supposed defective one. Then I rebooted. No joy. The boot process stalled in the same place.

But this is a FUNCTIONING keyboard. On no! My motherboard therefore must be FUBAR. I've to get a whole new machine! Oh no!

Work had to be done so I transitioned to another GNU/Linux machine. I booted and it hung at the same fucking place. What is going wrong here? How can both machines be failing at the exact same place?
This other machine was updated simultaneously with the first machine. Therefore, something in the updates must be the cause. But what?

I checked my update record. One package stood out: util-linux.

Using a backup I downgraded util-linux to the previous version. Both machines booted!

Hoorah!

But what the fuck happened with util-linux?

Util-linux contains the "mount" command, which, during boot, mounts all filesystems that are listed in /etc/fstab.

During boot this occurs right after the keyboard and mouse, et. al. are configured by the kernel.

This was it! For sure! But what the fuck was it?

I found this:

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=83e6d06addde9b8beac5ab796e7429e7ab5c742c

A patch has been removed to deal with the "statx" system call in libmount.
Somehow this caused the issue.

I need to file a bug report.

But after some sweaty and sickening hours I got my systems back.

Lord Master wrote this copyrighted missive and expects royalties:

> This story is for experts. Distro jockeys get lost.
>
> I performed my Gentoo update over the weekend. The next time I booted my
> system it just hung.
>
> The messages indicated that the keyboard was being sensed by the kernel and
> so I assumed the keyboard was faulty. I ripped a keyboard from my Microslop
> machine and used that in place of the supposed defective one. Then I
> rebooted. No joy. The boot process stalled in the same place.
>
> But this is a FUNCTIONING keyboard. On no! My motherboard therefore must
> be FUBAR. I've to get a whole new machine! Oh no!
>
> Work had to be done so I transitioned to another GNU/Linux machine. I booted
> and it hung at the same fucking place. What is going wrong here? How can
> both machines be failing at the exact same place?
>
> This other machine was updated simultaneously with the first machine.
> Therefore, something in the updates must be the cause. But what?
>
> I checked my update record. One package stood out: util-linux.
>
> Using a backup I downgraded util-linux to the previous version. Both
> machines booted!
>
> Hoorah!
>
> But what the fuck happened with util-linux?
>
> Util-linux contains the "mount" command, which, during boot, mounts all
> filesystems that are listed in /etc/fstab.
>
> During boot this occurs right after the keyboard and mouse, et. al. are
> configured by the kernel.
>
> This was it! For sure! But what the fuck was it?
>
> I found this:
>
> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=83e6d06addde9b8beac5ab796e7429e7ab5c742c
>
> A patch has been removed to deal with the "statx" system call in libmount.
> Somehow this caused the issue.
>
> I need to file a bug report.
>
> But after some sweaty and sickening hours I got my systems back.

Ugh. I hate when that happens (but it's been a lonnnnnnnnnnnnnnnnnnnnnng
time for my setups).

--
Hell is empty and all the devils are here.
-- Wm. Shakespeare, "The Tempest"

Lord Master <lordiemassa@gmail.com> wrote:

>This story is for experts. Distro jockeys get lost.
>
>I performed my Gentoo update over the weekend. The next time I booted my system it just hung.
>
>The messages indicated that the keyboard was being sensed by the kernel and so I assumed the keyboard was faulty. I ripped a keyboard from my Microslop machine and used that in place of the supposed defective one. Then I rebooted. No joy. The boot process stalled in the same place.
>
>But this is a FUNCTIONING keyboard. On no! My motherboard therefore must be FUBAR. I've to get a whole new machine! Oh no!
>
>Work had to be done so I transitioned to another GNU/Linux machine. I booted and it hung at the same fucking place. What is going wrong here? How can both machines be failing at the exact same place?
>
>This other machine was updated simultaneously with the first machine. Therefore, something in the updates must be the cause. But what?
>
>I checked my update record. One package stood out: util-linux.
>
>Using a backup I downgraded util-linux to the previous version. Both machines booted!
>
>Hoorah!
>
>But what the fuck happened with util-linux?
>
>Util-linux contains the "mount" command, which, during boot, mounts all filesystems that are listed in /etc/fstab.
>
>During boot this occurs right after the keyboard and mouse, et. al. are configured by the kernel.
>
>This was it! For sure! But what the fuck was it?
>
>I found this:
>
>https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=83e6d06addde9b8beac5ab796e7429e7ab5c742c
>
>A patch has been removed to deal with the "statx" system call in libmount.
>Somehow this caused the issue.
>
>I need to file a bug report.
>
>But after some sweaty and sickening hours I got my systems back.

You have fun with such BS, I'll just keep using my "distro" and not
having such problems.

--
Joel W. Crump

Amendment XIV
Section 1.

[...] No state shall make or enforce any law which shall
abridge the privileges or immunities of citizens of the
United States; nor shall any state deprive any person of
life, liberty, or property, without due process of law;
nor deny to any person within its jurisdiction the equal
protection of the laws.

Dobbs rewrites this, it is invalid precedent. States are
liable for denying needed abortions, e.g. TX.

Le 13-02-2024, Lord Master <lordiemassa@gmail.com> a écrit :
>
> I performed my Gentoo update over the weekend. The next time I booted
> my system it just hung.

I'm not that surprised.

> The messages indicated that the keyboard was being sensed by the
> kernel and so I assumed the keyboard was faulty. I ripped a keyboard
> from my Microslop machine and used that in place of the supposed
> defective one. Then I rebooted. No joy. The boot process stalled in
> the same place.

So, you are explaining you are better at managing a Windows machine than
a Linux machine. You shouldn't be too noisy about it.

> But this is a FUNCTIONING keyboard.

Of course: a Linux update can't break a keyboard.

> My motherboard therefore must be FUBAR.

Wrong deduction.

> I've to get a whole new machine! Oh no!

What for? To display only a black screen?

> What is going wrong here?

That's easy to answer. You are wrong.

> How can both machines be failing at the exact same place?

Because you are the one managing them both.

> This other machine was updated simultaneously with the first machine.

Exactly my point.

> Therefore, something in the updates must be the cause.

Yes, of course.

> But what?

Once again, the answer is easy: you.

> I found this:
>
> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=83e6d06addde9b8beac5ab796e7429e7ab5c742c

Ok, so you just have been impacted by something done almost two month
ago? You are not that bleeding edge.

--
Si vous avez du temps à perdre :
https://scarpet42.gitlab.io

On 2/13/2024 1:46 PM, Lord Master wrote:

> This story is for experts.
....
> I found this:
>
> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=83e6d06addde9b8beac5ab796e7429e7ab5c742c
>
> A patch has been removed to deal with the "statx" system call in libmount.
> Somehow this caused the issue.
>
> I need to file a bug report.
>
> But after some sweaty and sickening hours I got my systems back.

"All problems with GNU/Linux arise with the candy-ass dummies that seek
a freebie that will hold their hands like Microshit/Apphole."
- Feeb