This isn't related to a service, but is throwing out an spurious error
message.  There is a patch but it hasn't made it's way
yet into the Fedora kernel:

rt_cmos registration error:  rhbz#1568276
Basically an error is being thrown because your system doesn't have battery
backup.  To their credit, it was quickly identified
and patched.  We now just have to wait for the patch to be applied.

However these:

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

At least for me are the result of services being enabled by default, that
should never have been enabled for my
environment.

mcelog:  I am using an AMD processor.  This service only applies to Intel.
dbxtool:  I am not using SecureBoot.  This service only applies to machines
using SecureBoot.
rngd:  I am not using a machine that has a hardware RNG generator

Again, if we are apparently so concerned about a streamlined user
experience, why are we
starting processes that aren't needed - and in fact are not appropriate for
a particular environment,
and then throwing out error messages which are spurious and confusing?

In my case, this caused me to spend hours individually tracking down all
these error messages
to find out that there is nothing wrong with my environment.  Instead the
issue is these services
are inappropriately started for EVERYBODY - and in one case have been
languishing for years.

Last time I checked, Fedora wasn't an Intel only, SecureBoot only,
mandatory hardware RNG generator
environment.

If we truly are concerned about end user experience - this isn't the way to
go about it.



On Tue, Jun 19, 2018 at 10:54 PM, Gerald B. Cox <gb...@bzb.us> wrote:

> 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 <gb...@bzb.us> wrote:
>
>> On Thu, Jun 7, 2018 at 2:07 AM, Hans de Goede <hdego...@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/sh
>> ow_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.
>>
>>
>>
>
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/UZ6LSQ4UG6VNBZII4KUXQ6635YR5K7JE/

Reply via email to