Bug 1931206 - [abrt] wakeup_sources_sysfs_init: WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
Summary: [abrt] wakeup_sources_sysfs_init: WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-m...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 34
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:e583ce0925c7744c04eb0133e72...
: 1945945 1948169 1955960 1981243 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-21 15:29 UTC by Niki Guldbrand
Modified: 2022-06-07 22:27 UTC (History)
34 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-07 22:27:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (84.76 KB, text/plain)
2021-02-21 15:29 UTC, Niki Guldbrand
no flags Details

Description Niki Guldbrand 2021-02-21 15:29:27 UTC
Additional info:
reporter:       libreport-2.14.0
WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.11.0-156.fc34.x86_64 #1
Hardware name: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA/UX434DA, BIOS UX434DA_UM433DA.302 09/05/2019
RIP: 0010:mc146818_get_time+0x1c8/0x220
Code: 89 6b 10 5b 5d 41 5c 41 5d 41 5e c3 48 89 ee 48 c7 c7 b0 2a 6b b4 e8 97 44 2f 00 bf 58 89 41 00 e8 6d 70 d8 ff e9 4b fe ff ff <0f> 0b 48 c7 c7 b0 2a 6b b4 48 89 ee e8 77 44 2f 00 48 c7 03 ff ff
RSP: 0018:ffffb154c0047dd8 EFLAGS: 00010002
RAX: 00000000000000ff RBX: ffffb154c0047e0c RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffffb44a6914 RDI: 000000000000000d
RBP: 0000000000000246 R08: ffff9620404056e0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000030388 R12: 0000000000000000
R13: ffffffffb466aae0 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff962350e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000276c10000 CR4: 00000000003506f0
Call Trace:
 ? wakeup_sources_sysfs_init+0x2d/0x2d
 early_resume_init+0x21/0x8d
 do_one_initcall+0x57/0x1f0
 kernel_init_freeable+0x1cf/0x216
 ? rest_init+0xb4/0xb4
 kernel_init+0xa/0x10c
 ret_from_fork+0x22/0x30

Comment 1 Niki Guldbrand 2021-02-21 15:29:32 UTC
Created attachment 1758508 [details]
File: dmesg

Comment 2 Niki Guldbrand 2021-02-23 15:17:05 UTC
Description of problem:
Booted the system

Version-Release number of selected component:
kernel-core-5.11.0-156.fc34

Additional info:
reporter:       libreport-2.14.0
cmdline:        BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.11.0-156.fc34.x86_64 root=/dev/mapper/Zenbook14-Root ro rd.luks.uuid=luks-2e8cd60e-d7b4-4d51-bb3f-549d37970739 rd.lvm.lv=Zenbook14/Root rd.lvm.lv=Zenbook14/Swap2 resume=UUID=fddce1b5-e5de-4d89-a7d0-1598478edf90 rhgb quiet
crash_function: wakeup_sources_sysfs_init
kernel:         5.11.0-156.fc34.x86_64
runlevel:       N 5
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.11.0-156.fc34.x86_64 #1
Hardware name: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA/UX434DA, BIOS UX434DA_UM433DA.302 09/05/2019
RIP: 0010:mc146818_get_time+0x1c8/0x220
Code: 89 6b 10 5b 5d 41 5c 41 5d 41 5e c3 48 89 ee 48 c7 c7 b0 2a 6b bb e8 97 44 2f 00 bf 58 89 41 00 e8 6d 70 d8 ff e9 4b fe ff ff <0f> 0b 48 c7 c7 b0 2a 6b bb 48 89 ee e8 77 44 2f 00 48 c7 03 ff ff
RSP: 0018:ffffa3d380047dd8 EFLAGS: 00010002
RAX: 00000000000000ff RBX: ffffa3d380047e0c RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffffbb4a6914 RDI: 000000000000000d
RBP: 0000000000000246 R08: ffff8ba140405260 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000030388 R12: 0000000000000000
R13: ffffffffbb66aae0 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8ba450e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000355c10000 CR4: 00000000003506f0
Call Trace:
 ? wakeup_sources_sysfs_init+0x2d/0x2d
 early_resume_init+0x21/0x8d
 do_one_initcall+0x57/0x1f0
 kernel_init_freeable+0x1cf/0x216
 ? rest_init+0xb4/0xb4
 kernel_init+0xa/0x10c
 ret_from_fork+0x22/0x30

Comment 3 Christian Kujau 2021-03-14 21:22:49 UTC
Same here on a non-Fedora kernel, so I guess it's not distribution specific.
Looking closer, this has been reported to linux-rtc in February:

> [v5.11-rc6 Regression] RTC_RD_TIME EINVAL after RTC_WKALM_SET
> https://www.spinics.net/lists/linux-rtc/msg08413.html

...and is reportedly fixed with:

> http://git.kernel.org/linus/ebb22a059436
> rtc: mc146818: Dont test for bit 0-5 in Register D


------------[ cut here ]------------
WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.11.6-hardened1-1-hardened #1
RIP: 0010:mc146818_get_time+0x1c8/0x220
Code: 89 6b 10 5b 5d 41 5c 41 5d 41 5e c3 48 89 ee 48 c7 c7 30 fb de 86 e8 17 69 2a 00 bf 58 89 41 00 e8 cd 07 dc ff e9 4b fe ff ff <0f> 0b 48 c7 c7 30 fb de 86 48 89 ee e8 f7 68 2a 00 48 c7
 03 ff ff
RSP: 0000:ffffb26bc001be28 EFLAGS: 00010002
RAX: 00000000000000ff RBX: ffffb26bc001be5c RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff86cbae4d RDI: 000000000000000d
RBP: 0000000000000246 R08: 0000000000000006 R09: ffffffff867537a0
R10: ffffb26bc001be78 R11: 0000000000000068 R12: 0000000000000000
R13: ffffb26bc001bea0 R14: 0000000000000001 R15: d866dca6ec7e14ab
FS:  0000000000000000(0000) GS:ffff9362fda00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000000a4610001 CR4: 00000000001706f0
Call Trace:
 early_resume_init+0x4a/0xf7
 ? wakeup_sources_sysfs_init+0x7a/0x7a
 do_one_initcall+0x57/0x230
 kernel_init_freeable+0x227/0x2ea
 ? rest_init+0xbf/0xbf
 kernel_init+0xa/0x111
 ret_from_fork+0x22/0x30
---[ end trace 78a8dd9cd8b144cb ]---

Comment 4 Niki Guldbrand 2021-03-22 20:10:52 UTC
Description of problem:
Rebooted after a kernel update, and this warning showed up.

Version-Release number of selected component:
kernel-core-5.11.7-300.fc34

Additional info:
reporter:       libreport-2.14.0
cmdline:        BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.11.7-300.fc34.x86_64 root=/dev/mapper/Zenbook14-Root ro rd.luks.uuid=luks-2e8cd60e-d7b4-4d51-bb3f-549d37970739 rd.lvm.lv=Zenbook14/Root rd.lvm.lv=Zenbook14/Swap2 resume=UUID=fddce1b5-e5de-4d89-a7d0-1598478edf90 rhgb quiet
crash_function: wakeup_sources_sysfs_init
kernel:         5.11.7-300.fc34.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.11.7-300.fc34.x86_64 #1
Hardware name: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA/UX434DA, BIOS UX434DA_UM433DA.302 09/05/2019
RIP: 0010:mc146818_get_time+0x1c8/0x220
Code: 89 6b 10 5b 5d 41 5c 41 5d 41 5e c3 48 89 ee 48 c7 c7 b0 aa 4a 8c e8 87 97 2e 00 bf 58 89 41 00 e8 1d ee d8 ff e9 4b fe ff ff <0f> 0b 48 c7 c7 b0 aa 4a 8c 48 89 ee e8 67 97 2e 00 48 c7 03 ff ff
RSP: 0018:ffffa8e940047de0 EFLAGS: 00010002
RAX: 00000000000000ff RBX: ffffa8e940047e14 RCX: ffff9b6600c8a000
RDX: 0000000000000001 RSI: 0000000000000000 RDI: 000000000000000d
RBP: 0000000000000246 R08: ffff9b6600404020 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffff8c462d68 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff9b6910e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000002e3a10000 CR4: 00000000003506f0
Call Trace:
 ? wakeup_sources_sysfs_init+0x2d/0x2d
 early_resume_init+0x13/0x7f
 ? iommu_set_def_domain_type+0x42/0x42
 ? cn_proc_init+0x3a/0x3a
 do_one_initcall+0x44/0x1d0
 kernel_init_freeable+0x1cf/0x216
 ? rest_init+0xb4/0xb4
 kernel_init+0xa/0x11c
 ret_from_fork+0x22/0x30

Comment 5 Jackson Godsey 2021-04-02 20:08:03 UTC
*** Bug 1945945 has been marked as a duplicate of this bug. ***

Comment 6 SillyFinny 2021-04-10 12:51:28 UTC
*** Bug 1948169 has been marked as a duplicate of this bug. ***

Comment 7 Marko 2021-05-01 18:20:59 UTC
*** Bug 1955960 has been marked as a duplicate of this bug. ***

Comment 8 doggoofspeed 2021-07-12 07:32:18 UTC
*** Bug 1981243 has been marked as a duplicate of this bug. ***

Comment 9 wjsteh@gmail.com 2021-08-01 22:44:21 UTC
Description of problem:
Opened notebook to find it overheated and unresponsive

Version-Release number of selected component:
kernel-core-5.12.15-300.fc34

Additional info:
reporter:       libreport-2.15.2
cmdline:        BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.12.15-300.fc34.x86_64 root=UUID=2eca5422-e978-49bc-bd04-cf8c47311165 ro rootflags=subvol=root rhgb quiet
crash_function: wakeup_sources_sysfs_init
kernel:         5.12.15-300.fc34.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.12.15-300.fc34.x86_64 #1
Hardware name: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA/UX434DA, BIOS UX434DA_UM433DA.301 08/02/2019
RIP: 0010:mc146818_get_time+0x1c8/0x220
Code: 89 6b 10 5b 5d 41 5c 41 5d 41 5e c3 48 89 ee 48 c7 c7 b0 0a 4c b2 e8 b7 42 2f 00 bf 58 89 41 00 e8 dd a5 d8 ff e9 4b fe ff ff <0f> 0b 48 c7 c7 b0 0a 4c b2 48 89 ee e8 97 42 2f 00 48 c7 03 ff ff
RSP: 0018:ffffaa19c0047de0 EFLAGS: 00010002
RAX: 00000000000000ff RBX: ffffaa19c0047e14 RCX: ffff9b7e40c8a000
RDX: 0000000000000001 RSI: 0000000000000000 RDI: 000000000000000d
RBP: 0000000000000246 R08: ffff9b7e404041a0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffffb2478190 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff9b8150e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000022ea10000 CR4: 00000000003506f0
Call Trace:
 ? wakeup_sources_sysfs_init+0x2d/0x2d
 early_resume_init+0x13/0x7f
 ? iommu_set_def_domain_type+0x42/0x42
 ? cn_proc_init+0x3a/0x3a
 do_one_initcall+0x44/0x1d0
 kernel_init_freeable+0x20f/0x256
 ? rest_init+0xb4/0xb4
 kernel_init+0xa/0x11c
 ret_from_fork+0x22/0x30

Comment 10 Solomon Peachy 2021-08-09 14:59:29 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 11 mble 2021-08-20 13:07:06 UTC
Description of problem:
Random crash when I was watching youtube video in firefox

Version-Release number of selected component:
kernel-core-5.13.10-200.fc34

Additional info:
reporter:       libreport-2.15.2
cmdline:        BOOT_IMAGE=(hd3,gpt2)/vmlinuz-5.13.10-200.fc34.x86_64 root=UUID=a1c09399-ba4f-49ab-abaa-2d4f11181239 ro rootflags=subvol=root rd.luks.uuid=luks-b7e12f48-eee1-4555-828a-61bc89591fd5 rhgb quiet
crash_function: wakeup_sources_sysfs_init
kernel:         5.13.10-200.fc34.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.10-200.fc34.x86_64 #1
Hardware name: HUAWEI KPL-W0X/KPL-W0X, BIOS 1.22 02/26/2019
RIP: 0010:mc146818_get_time+0x1c8/0x220
Code: 89 6b 10 5b 5d 41 5c 41 5d 41 5e c3 48 89 ee 48 c7 c7 f0 da 71 b8 e8 67 48 30 00 bf 58 89 41 00 e8 dd 73 d8 ff e9 4b fe ff ff <0f> 0b 48 c7 c7 f0 da 71 b8 48 89 ee e8 47 48 30 00 48 c7 03 ff ff
RSP: 0018:ffffb9cc00063de0 EFLAGS: 00010002
RAX: 00000000000000ff RBX: ffffb9cc00063e14 RCX: ffff9db24004f800
RDX: 0000000000000001 RSI: 0000000000000000 RDI: 000000000000000d
RBP: 0000000000000246 R08: ffff9db2404041a0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffffb869c124 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff9db367e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000149c10000 CR4: 00000000003506f0
Call Trace:
 ? wakeup_sources_sysfs_init+0x2d/0x2d
 early_resume_init+0x13/0x7f
 ? iommu_set_def_domain_type+0x42/0x42
 ? cn_proc_init+0x3a/0x3a
 do_one_initcall+0x44/0x1d0
 kernel_init_freeable+0x214/0x260
 ? rest_init+0xb4/0xb4
 kernel_init+0xa/0x11c
 ret_from_fork+0x22/0x30

Comment 12 Sergey Shushpanov 2021-09-14 15:05:09 UTC
Description of problem:
I just install fedora 34. After update problem do not solve. 

Version-Release number of selected component:
kernel-core-5.11.12-300.fc34

Additional info:
reporter:       libreport-2.15.2
cmdline:        BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.11.12-300.fc34.x86_64 root=UUID=7a753767-aff4-4b1d-883f-edf279fb75ac ro rootflags=subvol=root rd.luks.uuid=luks-2470ab72-04ca-46d1-aea1-91f403459070 nomodeset rhgb quiet
crash_function: wakeup_sources_sysfs_init
kernel:         5.11.12-300.fc34.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.11.12-300.fc34.x86_64 #1
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./760GM-HDV, BIOS P1.20 05/11/2018
RIP: 0010:mc146818_get_time+0x1c8/0x220
Code: 89 6b 10 5b 5d 41 5c 41 5d 41 5e c3 48 89 ee 48 c7 c7 b0 ba 4a 9a e8 37 96 2e 00 bf 58 89 41 00 e8 6d ec d8 ff e9 4b fe ff ff <0f> 0b 48 c7 c7 b0 ba 4a 9a 48 89 ee e8 17 96 2e 00 48 c7 03 ff ff
RSP: 0018:ffffbfc840023de0 EFLAGS: 00010002
RAX: 00000000000000c0 RBX: ffffbfc840023e14 RCX: ffff98be80943000
RDX: 0000000000000001 RSI: 0000000000000000 RDI: 000000000000000d
RBP: 0000000000000246 R08: ffff98be80404b60 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffff9a462de4 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff98bf18c00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000011ca10000 CR4: 00000000000406f0
Call Trace:
 ? wakeup_sources_sysfs_init+0x2d/0x2d
 early_resume_init+0x13/0x7f
 ? iommu_set_def_domain_type+0x42/0x42
 ? cn_proc_init+0x3a/0x3a
 do_one_initcall+0x44/0x1d0
 kernel_init_freeable+0x1cf/0x216
 ? rest_init+0xb4/0xb4
 kernel_init+0xa/0x11c
 ret_from_fork+0x22/0x30

Comment 13 JohnG 2021-10-14 16:31:42 UTC
Description of problem:
Cold booted into Fedora Workstation (Gnome) aftert installing first set of updates afetr intial install. Problem occurred as soon as I 
logged in as root.

Version-Release number of selected component:
kernel-core-5.14.11-200.fc34

Additional info:
reporter:       libreport-2.15.2
cmdline:        BOOT_IMAGE=(hd0,msdos3)/vmlinuz-5.14.11-200.fc34.x86_64 root=/dev/mapper/fedora_epiphany-root ro resume=/dev/mapper/fedora_epiphany-swap rd.lvm.lv=fedora_epiphany/root rd.lvm.lv=fedora_epiphany/swap rhgb quiet
crash_function: wakeup_sources_sysfs_init
kernel:         5.14.11-200.fc34.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.14.11-200.fc34.x86_64 #1
Hardware name: System manufacturer System Product Name/M4A89TD PRO USB3, BIOS 2001    03/08/2011
RIP: 0010:mc146818_get_time+0x1c8/0x220
Code: 89 6b 10 5b 5d 41 5c 41 5d 41 5e c3 48 89 ee 48 c7 c7 d0 2a 74 92 e8 d7 48 30 00 bf 58 89 41 00 e8 5d 16 d8 ff e9 4b fe ff ff <0f> 0b 48 c7 c7 d0 2a 74 92 48 89 ee e8 b7 48 30 00 48 c7 03 ff ff
RSP: 0018:ffffb2c440027de0 EFLAGS: 00010002
RAX: 00000000000000d7 RBX: ffffb2c440027e14 RCX: ffff90db8004f800
RDX: 0000000000000001 RSI: 0000000000000000 RDI: 000000000000000d
RBP: 0000000000000246 R08: ffff90db804040e0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffff926c0014 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff90dca7c00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000001a2c10000 CR4: 00000000000006f0
Call Trace:
 ? wakeup_sources_sysfs_init+0x2d/0x2d
 early_resume_init+0x1c/0x8b
 ? iommu_set_def_domain_type+0x42/0x42
 ? cn_proc_init+0x3a/0x3a
 do_one_initcall+0x44/0x1d0
 kernel_init_freeable+0x201/0x24d
 ? rest_init+0xc0/0xc0
 kernel_init+0x16/0x120
 ret_from_fork+0x22/0x30

Comment 14 redhat 2021-11-01 04:18:34 UTC
Description of problem:
issue occured during boot, maybe login

Version-Release number of selected component:
kernel-core-5.13.19-200.fc34

Additional info:
reporter:       libreport-2.15.2
cmdline:        BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.13.19-200.fc34.x86_64 root=UUID=eb9a7b12-537d-4209-8def-cd19523b154a ro rootflags=subvol=root rhgb quiet
crash_function: wakeup_sources_sysfs_init
kernel:         5.13.19-200.fc34.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.19-200.fc34.x86_64 #1
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./A785GXH/128M, BIOS P1.30 04/26/2010
RIP: 0010:mc146818_get_time+0x1c8/0x220
Code: 89 6b 10 5b 5d 41 5c 41 5d 41 5e c3 48 89 ee 48 c7 c7 f0 da 71 99 e8 97 43 30 00 bf 58 89 41 00 e8 dd 6f d8 ff e9 4b fe ff ff <0f> 0b 48 c7 c7 f0 da 71 99 48 89 ee e8 77 43 30 00 48 c7 03 ff ff
RSP: 0018:ffffacc48001fde0 EFLAGS: 00010002
RAX: 00000000000000c0 RBX: ffffacc48001fe14 RCX: ffff9cae4004f800
RDX: 0000000000000001 RSI: 0000000000000000 RDI: 000000000000000d
RBP: 0000000000000246 R08: ffff9cae40404f20 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffff9969c184 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff9cb054000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000018ac10000 CR4: 00000000000006f0
Call Trace:
 ? wakeup_sources_sysfs_init+0x2d/0x2d
 early_resume_init+0x13/0x7f
 ? iommu_set_def_domain_type+0x42/0x42
 ? cn_proc_init+0x3a/0x3a
 do_one_initcall+0x44/0x1d0
 kernel_init_freeable+0x214/0x260
 ? rest_init+0xb4/0xb4
 kernel_init+0xa/0x11c
 ret_from_fork+0x22/0x30

Comment 15 elisei.lucas 2021-11-01 12:14:27 UTC
Description of problem:
This issue is logged as soon as the system is booted.

Version-Release number of selected component:
kernel-core-5.14.13-200.fc34

Additional info:
reporter:       libreport-2.15.2
cmdline:        BOOT_IMAGE=/boot/vmlinuz-5.14.13-200.fc34.x86_64 root=UUID=b47135de-6b4d-4c15-9d80-854bcac5c579 ro rhgb quiet
crash_function: wakeup_sources_sysfs_init
kernel:         5.14.13-200.fc34.x86_64
runlevel:       N 5
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 1 at drivers/rtc/rtc-mc146818-lib.c:25 mc146818_get_time+0x1c8/0x220
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.14.13-200.fc34.x86_64 #1
Hardware name: HP HP ENVY x360 Convertible 13-ar0xxx/85DE, BIOS F.18 11/07/2019
RIP: 0010:mc146818_get_time+0x1c8/0x220
Code: 89 6b 10 5b 5d 41 5c 41 5d 41 5e c3 48 89 ee 48 c7 c7 d0 2a 74 a7 e8 a7 57 30 00 bf 58 89 41 00 e8 ed 15 d8 ff e9 4b fe ff ff <0f> 0b 48 c7 c7 d0 2a 74 a7 48 89 ee e8 87 57 30 00 48 c7 03 ff ff
RSP: 0018:ffffaef94005fde0 EFLAGS: 00010002
RAX: 00000000000000ff RBX: ffffaef94005fe14 RCX: ffff9586c0e42000
RDX: 0000000000000001 RSI: 0000000000000000 RDI: 000000000000000d
RBP: 0000000000000246 R08: ffff9586c0404c20 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffffa76bfff4 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff958950a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000229c10000 CR4: 00000000003506f0
Call Trace:
 ? wakeup_sources_sysfs_init+0x2d/0x2d
 early_resume_init+0x1c/0x8b
 ? iommu_set_def_domain_type+0x42/0x42
 ? cn_proc_init+0x3a/0x3a
 do_one_initcall+0x44/0x1d0
 kernel_init_freeable+0x201/0x24d
 ? rest_init+0xc0/0xc0
 kernel_init+0x16/0x120
 ret_from_fork+0x22/0x30

Comment 16 Ben Cotton 2022-05-12 15:37:59 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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
'version' of '34'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 17 Ben Cotton 2022-06-07 22:27:49 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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.

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.