Here is another bug that was opened in 2014 and closed "WONTFIX because it
was directly tied to F24. Here we are with F28
and it still exists:
https://bugzilla.redhat.com/show_bug.cgi?id=1166978
Again, if we're concerned about the cleaning up of the boot process, why
are we apparently ignoring bugs that are associated
with processes that fail and throw out spurious messages?
If I issue: systemctl status, it tells me my system is "degraded" because
of the following:
systemctl list-units --state=failed
UNIT LOAD ACTIVE SUB
DESCRIPTION
● dbxtool.service loaded failed failed Secure Boot DBX (blacklist)
updater
● mcelog.service loaded failed failed Machine Check Exception Logging
Daemon
● rngd.service loaded failed failed Hardware RNG Entropy Gatherer Daemon
The mcelog.service message is associated with rhbz#1166978
The dbxtool.service message is associated with rhbz#1508808
The rngd.service message is associated with rhbz#1490632
On Sun, Jun 10, 2018 at 10:02 AM, Gerald B. Cox <gbcox(a)bzb.us> wrote:
On Thu, Jun 7, 2018 at 2:07 AM, Hans de Goede
<hdegoede(a)redhat.com> wrote:
> Hi,
>
> On 04-06-18 21:17, Adam Williamson wrote:
>
>> On Thu, 2018-05-31 at 12:43 +0200, Jan Kurik wrote:
>>
>>> = Proposed System Wide Change: Hide the grub menu =
>>>
https://fedoraproject.org/wiki/Changes/HiddenGrubMenu
>>>
>>
>>
I've updated this bug:
https://bugzilla.redhat.com/
show_bug.cgi?id=1406844
Basically, since at least F24 - maybe longer my boot has been interrupted
by this message:
====> sp5100-tco sp5100-tco: I/O address 0x0cd6 already in use
The bug was closed, and then cloned and reopened.
As I mentioned before, I have no problem with the grub change as long as
there is documentation
that shows people how to reverse it if they wish - and Hans (thank you
very much) has agreed to this.
However, seems to me that having this bug (which appears to affect all AMD
users) languishing
for years seems to negate the reasoning behind this change. If we're
wanting to implement
a more or less cosmetic change which saves a few seconds, having spurious
messages
interrupting and slowing down the boot process should also be resolved.