Bug 1936688 - WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
Summary: WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-08 22:12 UTC by rvcsaba
Modified: 2021-11-30 16:08 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 16:08:37 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description rvcsaba 2021-03-08 22:12:08 UTC 
1. Please describe the problem:

I see journalctl and dmesg:

Mar 08 18:12:05 kernel: PM: Registering ACPI NVS region [mem 0xcffbe000-0xcfffffff] (270336 bytes)
Mar 08 18:12:05 kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
Mar 08 18:12:05 kernel: futex hash table entries: 2048 (order: 5, 131072 bytes, linear)
Mar 08 18:12:05 kernel: pinctrl core: initialized pinctrl subsystem
Mar 08 18:12:05 kernel: ------------[ cut here ]------------
Mar 08 18:12:05 kernel: WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
Mar 08 18:12:05 kernel: Modules linked in:
Mar 08 18:12:05 kernel: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.11.4-50.fc33.x86_64 #1
Mar 08 18:12:05 kernel: Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7388/MS-7388, BIOS V1.13 09/20/2010
Mar 08 18:12:05 kernel: RIP: 0010:mc146818_get_time+0x1c8/0x220
Mar 08 18:12:05 kernel: Code: 89 6b 10 5b 5d 41 5c 41 5d 41 5e c3 48 89 ee 48 c7 c7 b0 ba 6b 9f e8 57 55 2f 00 bf 58 89 41 00 e8 fd 59 d8 ff e9 4b fe ff ff <0f> 0b 48 c7 c7 b0 ba 6b 9f 48 89 ee e8 37 55 2f 00 48 c7 03 ff ff
Mar 08 18:12:05 kernel: RSP: 0018:ffffaa958001fdd8 EFLAGS: 00010002
Mar 08 18:12:05 kernel: RAX: 00000000000000cb RBX: ffffaa958001fe0c RCX: 0000000000000000
Mar 08 18:12:05 kernel: RDX: 0000000000000001 RSI: ffffffff9f4add5d RDI: 000000000000000d
Mar 08 18:12:05 kernel: RBP: 0000000000000246 R08: ffff8addc0404b60 R09: 0000000000000000
Mar 08 18:12:05 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Mar 08 18:12:05 kernel: R13: ffffffff9f672de8 R14: 0000000000000000 R15: 0000000000000000
Mar 08 18:12:05 kernel: FS:  0000000000000000(0000) GS:ffff8adee7c00000(0000) knlGS:0000000000000000
Mar 08 18:12:05 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 08 18:12:05 kernel: CR2: 0000000000000000 CR3: 000000014ac10000 CR4: 00000000000006f0
Mar 08 18:12:05 kernel: Call Trace:
Mar 08 18:12:05 kernel:  ? wakeup_sources_sysfs_init+0x30/0x30
Mar 08 18:12:05 kernel:  early_resume_init+0x21/0x8d
Mar 08 18:12:05 kernel:  do_one_initcall+0x57/0x1f0
Mar 08 18:12:05 kernel:  kernel_init_freeable+0x1cf/0x216
Mar 08 18:12:05 kernel:  ? rest_init+0xb4/0xb4
Mar 08 18:12:05 kernel:  kernel_init+0xa/0x11c
Mar 08 18:12:05 kernel:  ret_from_fork+0x22/0x30
Mar 08 18:12:05 kernel: ---[ end trace 65a40c9d1fdf0e06 ]---
Mar 08 18:12:05 kernel: PM: RTC time: 18446744073709551615:18446744073709551615:18446744073709551615, date: 1899-00-18446744073709551615
Mar 08 18:12:05 kernel: NET: Registered protocol family 16
Mar 08 18:12:05 kernel: DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
Mar 08 18:12:05 kernel: DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
Mar 08 18:12:05 kernel: DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations


2. What is the Version-Release number of the kernel:

5.11.4-50.fc33.x86_64


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8:

Sorry, I don't know.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Boot my computer.


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:


6. Are you running any modules that not shipped with directly Fedora's kernel?:

No.


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
Comment 1 rvcsaba 2021-03-08 22:14:26 UTC 
Related:

https://bugzilla.redhat.com/show_bug.cgi?id=1931206
Comment 2 Solomon Peachy 2021-08-09 14:59:26 UTC 
I also have this issue, on an ASUS KCMA-D8 motherboard, with the 5.13.7-100.fc33.x86_64 kernel

[    1.133108] WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
[    1.133272] Modules linked in:
[    1.133369] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.7-100.fc33.x86_64 #1
[    1.133520] Hardware name: ASUSTeK Computer INC. KCMA-D8/KCMA-D8, BIOS 3303    10/28/2014
...
[    1.133648] PM: RTC time: 18446744073709551615:18446744073709551615:18446744073709551615, date: 1899-00-18446744073709551615
...
[    2.638153] rtc_cmos 00:02: RTC can wake from S4
[    2.638283] rtc_cmos 00:02: not accessible


There is a proposed patch here:  https://www.spinics.net/lists/linux-rtc/msg09087.html but it supposedly causes regressions on other systems.
Comment 3 Ben Cotton 2021-11-04 13:48:25 UTC 
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Ben Cotton 2021-11-04 14:17:49 UTC 
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 5 Ben Cotton 2021-11-04 15:15:30 UTC 
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 6 Mateusz Jończyk 2021-11-26 18:40:21 UTC 
Hello,

I also have this problem, on one of our home systems (with an ASRock A780GXH/128M motherboard).

I have submitted a patch to fix it, which is under review currently:

https://lkml.org/lkml/2021/11/19/796

I do not expect it to be mainlined before kernel 5.17, though. I may get it to stable releases, nonetheless.

Greetings,
Mateusz
Comment 7 Ben Cotton 2021-11-30 16:08:37 UTC 
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.