Bug 1562480 - [abrt] dmar_validate_one_drhd: WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:845 warn_invalid_dmar.part.10+0x5c/0x70 [NEEDINFO]
Summary: [abrt] dmar_validate_one_drhd: WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 28
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:2119bece160f748fda8e854a2da...
: 1582869 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-31 02:48 UTC by Jonathon Poppleton
Modified: 2019-05-28 23:05 UTC (History)
28 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 23:05:06 UTC
Type: ---
Embargoed:
grimbshrout: needinfo?


Attachments (Terms of Use)
File: dmesg (64.20 KB, text/plain)
2018-03-31 02:48 UTC, Jonathon Poppleton
no flags Details

Description Jonathon Poppleton 2018-03-31 02:48:19 UTC
Additional info:
reporter:       libreport-2.9.3
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:845 warn_invalid_dmar.part.10+0x5c/0x70
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.14.8-300.fc27.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. H81M-D2V/H81M-D2V, BIOS F3 03/11/2014
task: ffffffff85e10480 task.stack: ffffffff85e00000
RIP: 0010:warn_invalid_dmar.part.10+0x5c/0x70
RSP: 0000:ffffffff85e03da0 EFLAGS: 00010086
RAX: 0000000000000088 RBX: 0000000000000000 RCX: ffffffff85e510c8
RDX: 0000000000000000 RSI: 0000000000000092 RDI: 0000000000000047
RBP: ffffffff85e03dc0 R08: 00000000000000c3 R09: 0000000000000004
R10: 0000000000000001 R11: 0000000000000001 R12: ffffffff85cba5ed
R13: ffffffff862ff01c R14: ffffffff862ff058 R15: fffffffffee40da0
FS:  0000000000000000(0000) GS:ffffa0736ec00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffa07089300000 CR3: 0000000148e09001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xab/0xe0
 dmar_walk_remapping_entries+0xa3/0x1d0
 detect_intel_iommu+0x66/0xef
 ? xen_swiotlb_init+0x4e0/0x4e0
 pci_iommu_alloc+0x55/0x71
 mem_init+0x1c/0xa9
 start_kernel+0x2d2/0x500
 x86_64_start_reservations+0x24/0x26
 x86_64_start_kernel+0x74/0x77
 secondary_startup_64+0xa5/0xa5
Code: 56 19 00 bf 01 00 00 00 49 89 c5 e8 5f 56 19 00 4d 89 f1 4d 89 e8 48 89 c1 4c 89 e2 48 89 de 48 c7 c7 a0 e7 ce 85 e8 a5 d1 b7 ff <0f> ff 5b 41 5c 41 5d 41 5e 5d c3 66 0f 1f 84 00 00 00 00 00 e8

Comment 1 Jonathon Poppleton 2018-03-31 02:48:23 UTC
Created attachment 1415354 [details]
File: dmesg

Comment 2 Vinicio Guerra 2018-04-18 15:17:59 UTC
Description of problem:
Cada vez q se actualiza el kernel

Version-Release number of selected component:
kernel-core-4.15.14-300.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.15.14-300.fc27.x86_64 root=UUID=899886a2-f4e6-407e-8be2-e4737bd3d80b ro rhgb quiet LANG=es_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.15.14-300.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.15.14-300.fc27.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffff9b203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff9b253848
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000087
RBP: ffffffff9b0c5201 R08: 00000000000000a0 R09: 0000000000000004
R10: ffffffff9b203d98 R11: 0000000000000001 R12: ffffffff9ba6d00c
R13: ffffffff9ba6d038 R14: ffffffff9b203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff8e3aef200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8e3ac0a6e000 CR3: 000000044020a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0x9f
 start_kernel+0x2cb/0x500
 secondary_startup_64+0xa5/0xb0
Code: ba 18 00 bf 01 00 00 00 49 89 c4 e8 04 ba 18 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 b0 aa 0f 9b e8 b9 e3 b2 ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 1b 86 48 00 85 d2 7e 56 53 4c 8d

Comment 3 aklofas 2018-04-20 20:19:55 UTC
Description of problem:
Happened at CPU boot.

Version-Release number of selected component:
kernel-core-4.15.12-301.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.15.12-301.fc27.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=en_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.15.12-301.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.15.12-301.fc27.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. Z87X-UD3H/Z87X-UD3H-CF, BIOS F5 05/16/2013
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffffb7203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffb7253848
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000087
RBP: ffffffffb70c5121 R08: 00000000000000d3 R09: 0000000000000004
R10: ffffffffb7203d98 R11: 0000000000000001 R12: ffffffffb7a6d01c
R13: ffffffffb7a6d058 R14: ffffffffb7203e80 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff95e53f200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff95e32ea6e000 CR3: 000000022e20a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0x9f
 start_kernel+0x2cb/0x500
 secondary_startup_64+0xa5/0xb0
Code: b9 18 00 bf 01 00 00 00 49 89 c4 e8 e4 b9 18 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 a0 a9 0f b7 e8 e9 e6 b2 ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 db 8a 48 00 85 d2 7e 56 53 4c 8d

Comment 4 Vinicio Guerra 2018-05-12 15:21:39 UTC
Description of problem:
actualización

Version-Release number of selected component:
kernel-core-4.16.6-202.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.16.6-202.fc27.x86_64 root=UUID=899886a2-f4e6-407e-8be2-e4737bd3d80b ro rhgb quiet LANG=es_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.16.6-202.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.16.6-202.fc27.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffffac203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffac253e08
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000046
RBP: ffffffffac0ce939 R08: 00000000000000a0 R09: 0000000000000004
R10: ffffffffac203d98 R11: 0000000000000001 R12: ffffffffaca7700c
R13: ffffffffaca77038 R14: ffffffffac203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff8f3e2f200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8f3cffa78000 CR3: 000000033f20a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb0
 start_kernel+0x2cb/0x500
 secondary_startup_64+0xa5/0xb0
Code: f3 18 00 bf 01 00 00 00 49 89 c4 e8 14 f3 18 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 10 49 10 ac e8 59 3f b2 ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 bb ca 47 00 85 d2 7e 56 53 4c 8d

Comment 5 Vinicio Guerra 2018-05-15 16:55:35 UTC
Description of problem:
actualización

Version-Release number of selected component:
kernel-core-4.16.7-200.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.16.7-200.fc27.x86_64 root=UUID=899886a2-f4e6-407e-8be2-e4737bd3d80b ro rhgb quiet LANG=es_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.16.7-200.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.16.7-200.fc27.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffff82203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff82253e08
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000046
RBP: ffffffff820ceb81 R08: 00000000000000a0 R09: 0000000000000004
R10: ffffffff82203d98 R11: 0000000000000001 R12: ffffffff82a7700c
R13: ffffffff82a77038 R14: ffffffff82203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff93f86f200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff93f757a78000 CR3: 000000035720a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb0
 start_kernel+0x2cb/0x500
 secondary_startup_64+0xa5/0xb0
Code: f4 18 00 bf 01 00 00 00 49 89 c4 e8 c4 f4 18 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 e8 4b 10 82 e8 b9 3c b2 ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 1b c8 47 00 85 d2 7e 56 53 4c 8d

Comment 6 Vinicio Guerra 2018-05-22 13:28:07 UTC
Description of problem:
por una actualización

Version-Release number of selected component:
kernel-core-4.16.7-200.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.16.7-200.fc27.x86_64 root=UUID=899886a2-f4e6-407e-8be2-e4737bd3d80b ro rhgb quiet LANG=es_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.16.7-200.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.16.7-200.fc27.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffffb3203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffb3253e08
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000046
RBP: ffffffffb30ceb81 R08: 00000000000000a0 R09: 0000000000000004
R10: ffffffffb3203d98 R11: 0000000000000001 R12: ffffffffb3a7700c
R13: ffffffffb3a77038 R14: ffffffffb3203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff9ff5af200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff9ff42ca78000 CR3: 00000002ec20a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb0
 start_kernel+0x2cb/0x500
 secondary_startup_64+0xa5/0xb0
Code: f4 18 00 bf 01 00 00 00 49 89 c4 e8 c4 f4 18 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 e8 4b 10 b3 e8 b9 3c b2 ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 1b c8 47 00 85 d2 7e 56 53 4c 8d

Comment 7 Vinicio Guerra 2018-05-23 13:20:09 UTC
Description of problem:
Estaba actualizandose el kernel y se acabo la batería de la portátil en plena instalación.

Version-Release number of selected component:
kernel-core-4.16.7-200.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.16.7-200.fc27.x86_64 root=UUID=899886a2-f4e6-407e-8be2-e4737bd3d80b ro rhgb quiet LANG=es_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.16.7-200.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.16.7-200.fc27.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffffa8203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffa8253e08
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000046
RBP: ffffffffa80ceb81 R08: 00000000000000a0 R09: 0000000000000004
R10: ffffffffa8203d98 R11: 0000000000000001 R12: ffffffffa8a7700c
R13: ffffffffa8a77038 R14: ffffffffa8203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff98b7af200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff98b6c4a78000 CR3: 000000038420a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb0
 start_kernel+0x2cb/0x500
 secondary_startup_64+0xa5/0xb0
Code: f4 18 00 bf 01 00 00 00 49 89 c4 e8 c4 f4 18 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 e8 4b 10 a8 e8 b9 3c b2 ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 1b c8 47 00 85 d2 7e 56 53 4c 8d

Comment 8 Vinicio Guerra 2018-05-24 16:58:34 UTC
Description of problem:
una actualización

Version-Release number of selected component:
kernel-core-4.16.7-200.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.16.7-200.fc27.x86_64 root=UUID=899886a2-f4e6-407e-8be2-e4737bd3d80b ro rhgb quiet
crash_function: dmar_validate_one_drhd
kernel:         4.16.7-200.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.16.7-200.fc27.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffffa6203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffa6253e08
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000046
RBP: ffffffffa60ceb81 R08: 00000000000000a0 R09: 0000000000000004
R10: ffffffffa6203d98 R11: 0000000000000001 R12: ffffffffa6a7700c
R13: ffffffffa6a77038 R14: ffffffffa6203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff89b96f200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff89b690a78000 CR3: 000000019020a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb0
 start_kernel+0x2cb/0x500
 secondary_startup_64+0xa5/0xb0
Code: f4 18 00 bf 01 00 00 00 49 89 c4 e8 c4 f4 18 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 e8 4b 10 a6 e8 b9 3c b2 ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 1b c8 47 00 85 d2 7e 56 53 4c 8d

Comment 9 Vinicio Guerra 2018-05-27 15:11:17 UTC
Description of problem:
por una actualización

Version-Release number of selected component:
kernel-core-4.16.11-200.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.16.11-200.fc27.x86_64 root=UUID=899886a2-f4e6-407e-8be2-e4737bd3d80b ro rhgb quiet LANG=es_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.16.11-200.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.16.11-200.fc27.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffffae203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffae253c48
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000046
RBP: ffffffffae0d0321 R08: 00000000000000a0 R09: 0000000000000004
R10: ffffffffae203d98 R11: 0000000000000001 R12: ffffffffaea7b00c
R13: ffffffffaea7b038 R14: ffffffffae203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff98276f200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff982490a7c000 CR3: 000000019020a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb0
 start_kernel+0x2cb/0x500
 secondary_startup_64+0xa5/0xb0
Code: f5 18 00 bf 01 00 00 00 49 89 c4 e8 34 f5 18 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 e8 68 10 ae e8 39 e2 b1 ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 1b 6d 47 00 85 d2 7e 56 53 4c 8d

Comment 10 gb0eru18zlb7 2018-05-27 15:16:30 UTC
*** Bug 1582869 has been marked as a duplicate of this bug. ***

Comment 11 Vinicio Guerra 2018-05-28 13:41:52 UTC
Description of problem:
por una actualización del kernel

Version-Release number of selected component:
kernel-core-4.16.11-200.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.16.11-200.fc27.x86_64 root=UUID=899886a2-f4e6-407e-8be2-e4737bd3d80b ro rhgb quiet LANG=es_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.16.11-200.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.16.11-200.fc27.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffff97203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff97253c48
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000046
RBP: ffffffff970d0321 R08: 00000000000000a0 R09: 0000000000000004
R10: ffffffff97203d98 R11: 0000000000000001 R12: ffffffff97a7b00c
R13: ffffffff97a7b038 R14: ffffffff97203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff94e86f200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff94e72ea7c000 CR3: 000000032e20a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb0
 start_kernel+0x2cb/0x500
 secondary_startup_64+0xa5/0xb0
Code: f5 18 00 bf 01 00 00 00 49 89 c4 e8 34 f5 18 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 e8 68 10 97 e8 39 e2 b1 ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 1b 6d 47 00 85 d2 7e 56 53 4c 8d

Comment 12 Vinicio Guerra 2018-05-28 13:51:08 UTC
Description of problem:
Por una actualización del kernel

Version-Release number of selected component:
kernel-core-4.16.11-200.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.16.11-200.fc27.x86_64 root=UUID=899886a2-f4e6-407e-8be2-e4737bd3d80b ro rhgb quiet LANG=es_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.16.11-200.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.16.11-200.fc27.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffff8b203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8b253c48
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000046
RBP: ffffffff8b0d0321 R08: 00000000000000a0 R09: 0000000000000004
R10: ffffffff8b203d98 R11: 0000000000000001 R12: ffffffff8ba7b00c
R13: ffffffff8ba7b038 R14: ffffffff8b203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff9150af200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff914f52a7c000 CR3: 000000031220a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb0
 start_kernel+0x2cb/0x500
 secondary_startup_64+0xa5/0xb0
Code: f5 18 00 bf 01 00 00 00 49 89 c4 e8 34 f5 18 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 e8 68 10 8b e8 39 e2 b1 ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 1b 6d 47 00 85 d2 7e 56 53 4c 8d

Comment 13 Vinicio Guerra 2018-05-29 22:18:16 UTC
Description of problem:
por una actualización del kernel

Version-Release number of selected component:
kernel-core-4.16.12-200.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.16.12-200.fc27.x86_64 root=UUID=899886a2-f4e6-407e-8be2-e4737bd3d80b ro rhgb quiet LANG=es_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.16.12-200.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.16.12-200.fc27.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffff94203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff94253c48
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000046
RBP: ffffffff940d0331 R08: 00000000000000a0 R09: 0000000000000004
R10: ffffffff94203d98 R11: 0000000000000001 R12: ffffffff94a7b00c
R13: ffffffff94a7b038 R14: ffffffff94203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff9b9d2f200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff9b9abea7c000 CR3: 00000001fe20a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb0
 start_kernel+0x2cb/0x500
 secondary_startup_64+0xa5/0xb0
Code: f5 18 00 bf 01 00 00 00 49 89 c4 e8 e4 f5 18 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 f8 68 10 94 e8 09 e2 b1 ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 eb 6c 47 00 85 d2 7e 56 53 4c 8d

Comment 14 Vinicio Guerra 2018-06-26 16:56:54 UTC
Description of problem:
actualización del kernel

Version-Release number of selected component:
kernel-core-4.16.14-200.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.16.14-200.fc27.x86_64 root=UUID=899886a2-f4e6-407e-8be2-e4737bd3d80b ro rhgb quiet LANG=es_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.16.14-200.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.16.14-200.fc27.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffffa8203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffa8253c48
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000046
RBP: ffffffffa80d0401 R08: 00000000000000a0 R09: 0000000000000004
R10: ffffffffa8203d98 R11: 0000000000000001 R12: ffffffffa8a7b00c
R13: ffffffffa8a7b038 R14: ffffffffa8203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff9c42ef200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff9c4253a7c000 CR3: 00000003d320a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb0
 start_kernel+0x2cb/0x500
 secondary_startup_64+0xa5/0xb0
Code: f7 18 00 bf 01 00 00 00 49 89 c4 e8 a4 f7 18 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 c8 69 10 a8 e8 59 de b1 ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 6b 68 47 00 85 d2 7e 56 53 4c 8d

Comment 15 Vinicio Guerra 2018-06-29 06:54:14 UTC
Description of problem:
actualización de kernel

Version-Release number of selected component:
kernel-core-4.17.2-100.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.17.2-100.fc27.x86_64 root=UUID=899886a2-f4e6-407e-8be2-e4737bd3d80b ro rhgb quiet LANG=es_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.17.2-100.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.17.2-100.fc27.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffffa1203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffa1252b48
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000046
RBP: ffffffffa10ecde2 R08: 00000000000000a0 R09: 0000000000000004
R10: ffffffffa1203d88 R11: 0000000000000001 R12: ffffffffa1aa200c
R13: ffffffffa1aa2038 R14: ffffffffa1203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff9cebef200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff9ceaabaa3000 CR3: 000000032b20a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb9
 start_kernel+0x2cb/0x55b
 secondary_startup_64+0xa5/0xb0
Code: 53 19 00 bf 01 00 00 00 49 89 c4 e8 44 53 19 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 f8 53 12 a1 e8 f9 13 af ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 db 63 44 00 85 d2 7e 56 53 4c 8d

Comment 16 Vinicio Guerra 2018-07-02 21:41:49 UTC
Description of problem:
actualización del kernel

Version-Release number of selected component:
kernel-core-4.17.2-100.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        BOOT_IMAGE=/vmlinuz-4.17.2-100.fc27.x86_64 root=UUID=899886a2-f4e6-407e-8be2-e4737bd3d80b ro rhgb quiet LANG=es_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.17.2-100.fc27.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.17.2-100.fc27.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffff92203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff92252b48
RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000046
RBP: ffffffff920ecde2 R08: 000000000000009e R09: 0000000000000004
R10: ffffffff92203d88 R11: 0000000000000001 R12: ffffffff92aa200c
R13: ffffffff92aa2038 R14: ffffffff92203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff893def200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff893def5ff000 CR3: 000000002620a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xa2/0xd0
 dmar_walk_remapping_entries+0xa2/0x1d0
 detect_intel_iommu+0x64/0xed
 ? xen_swiotlb_init+0x4d0/0x4d0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb9
 start_kernel+0x2cb/0x55b
 secondary_startup_64+0xa5/0xb0
Code: 53 19 00 bf 01 00 00 00 49 89 c4 e8 44 53 19 00 4d 89 e9 4d 89 e0 48 89 c1 48 89 ea 48 89 de 48 c7 c7 f8 53 12 92 e8 f9 13 af ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 db 63 44 00 85 d2 7e 56 53 4c 8d

Comment 17 Justin M. Forbes 2018-07-23 15:21:34 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.

Fedora 27 has now been rebased to 4.17.7-100.fc27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 28, and are still experiencing this issue, please change the version to Fedora 28.

If you experience different issues, please open a new bug report for those.

Comment 18 Nathanael Noblet 2018-07-30 15:38:34 UTC
just got the same issue on F28 kernel 4.17.9-200.fc28.x86_64

Comment 19 Vinicio Guerra 2018-07-31 01:05:03 UTC
Description of problem:
al prender el computador

Version-Release number of selected component:
kernel-core-4.17.9-200.fc28

Additional info:
reporter:       libreport-2.9.5
cmdline:        BOOT_IMAGE=/vmlinuz-4.17.9-200.fc28.x86_64 root=UUID=34da106b-d60c-42bd-a3d6-c1586436d02b ro resume=UUID=d62a7e65-d55a-4978-92c6-8580ac078a97 rhgb quiet btusb.enable_autosuspend=n LANG=es_US.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.17.9-200.fc28.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.17.9-200.fc28.x86_64 #1
Hardware name: Alienware Alienware 18/01W2J2, BIOS A13 01/29/2018
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
RSP: 0000:ffffffff9d203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff9d252b48
RDX: 0000000000000001 RSI: 0000000000000082 RDI: 0000000000000083
RBP: ffffffff9d0f7072 R08: 0000000000000078 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000001 R12: ffffffff9daa500c
R13: ffffffff9daa5038 R14: ffffffff9d203e80 R15: fffffffff000ba86
FS:  0000000000000000(0000) GS:ffff8d4cef200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8d4c65aa6000 CR3: 00000003e520a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xc0/0xd0
 dmar_walk_remapping_entries+0xa2/0x140
 detect_intel_iommu+0x64/0xe6
 ? xen_swiotlb_init+0x4e0/0x4e0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb9
 start_kernel+0x2c8/0x558
 secondary_startup_64+0xa5/0xb0
Code: 57 19 00 bf 01 00 00 00 49 89 c4 e8 a4 57 19 00 4d 89 e9 4d 89 e0 48 89 ea 48 89 c1 48 89 de 48 c7 c7 c8 f6 12 9d e8 43 57 af ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 ab a5 44 00 31 c0 85 d2 7e 56 53

Comment 20 John Soros 2018-09-23 08:03:33 UTC
Description of problem:
resume from intel repid start

Version-Release number of selected component:
kernel-core-4.18.7-200.fc28

Additional info:
reporter:       libreport-2.9.5
cmdline:        BOOT_IMAGE=/vmlinuz-4.18.7-200.fc28.x86_64 root=UUID=67e8be20-38e0-46f6-a526-b32337b4e3f0 ro rootflags=subvol=root rd.luks.uuid=luks-525928c1-8487-41b7-82d9-42cd0d3c3e32 rd.luks.uuid=luks-1d8938f5-ff37-4f51-adaa-79ecd87dd410 rhgb quiet LANG=en_US.UTF-8 rd.luks.options=discard dm_mod.use_blk_mq=y scsi_mod.use_blk_mq=y
crash_function: dmar_validate_one_drhd
kernel:         4.18.7-200.fc28.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.18.7-200.fc28.x86_64 #1
Hardware name: LENOVO 20BXCTO1WW/20BXCTO1WW, BIOS JBET54WW (1.19 ) 11/06/2015
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
Code: 19 00 bf 01 00 00 00 49 89 c4 e8 14 1d 19 00 4d 89 e9 4d 89 e0 48 89 ea 48 89 c1 48 89 de 48 c7 c7 38 64 13 bc e8 83 6b ae ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 cb aa 43 00 31 c0 85 d2 7e 56 53 4c 
RSP: 0000:ffffffffbc203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffbc252c88
RDX: 0000000000000001 RSI: 0000000000000082 RDI: 0000000000000046
RBP: ffffffffbc0fa858 R08: 000000000000008c R09: 0000000000000004
R10: 0000000000000000 R11: 0000000000000001 R12: ffffffffbcaab1ec
R13: ffffffffbcaab014 R14: ffffffffbc203e80 R15: 000000008efebae0
FS:  0000000000000000(0000) GS:ffff9bc25dc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff9bc195aac000 CR3: 000000049520a001 CR4: 00000000000606b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 dmar_validate_one_drhd+0xc0/0xd0
 dmar_walk_remapping_entries+0xa2/0x140
 detect_intel_iommu+0x64/0xe6
 ? xen_swiotlb_init+0x4e0/0x4e0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb9
 start_kernel+0x2c8/0x558
 secondary_startup_64+0xa5/0xb0

Comment 21 Igor Iglesias 2018-10-20 21:57:40 UTC
Description of problem:
reboot system

Version-Release number of selected component:
kernel-core-4.18.14-200.fc28

Additional info:
reporter:       libreport-2.9.5
cmdline:        BOOT_IMAGE=/vmlinuz-4.18.14-200.fc28.x86_64 root=/dev/mapper/fedora_localhost--live-root ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet LANG=es_ES.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.18.14-200.fc28.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.18.14-200.fc28.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. H81M-HD3/H81M-HD3, BIOS F2 08/14/2013
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
Code: 19 00 bf 01 00 00 00 49 89 c4 e8 c4 1f 19 00 4d 89 e9 4d 89 e0 48 89 ea 48 89 c1 48 89 de 48 c7 c7 a0 47 13 8a e8 93 5e ae ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 3b 8d 43 00 31 c0 85 d2 7e 56 53 4c 
RSP: 0000:ffffffff8a203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8a253c88
RDX: 0000000000000001 RSI: 0000000000000082 RDI: 0000000000000046
RBP: ffffffff8a0f8af8 R08: 0000000000000098 R09: 0000000000000004
R10: 0000000000000000 R11: 0000000000000001 R12: ffffffff8aaa901c
R13: ffffffff8aaa9058 R14: ffffffff8a203e80 R15: 00000000c416bae0
FS:  0000000000000000(0000) GS:ffff9a125f200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff9a125f5ff000 CR3: 000000007c20a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xc0/0xd0
 dmar_walk_remapping_entries+0xa2/0x140
 detect_intel_iommu+0x64/0xe6
 ? xen_swiotlb_init+0x4e0/0x4e0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb9
 start_kernel+0x2c8/0x558
 secondary_startup_64+0xa5/0xb0

Comment 22 Jason Shrout 2018-10-21 16:53:27 UTC
I got this same thing but probably for slightly different hardware:
I received this bug on the prepackage binaries fc28 kernel 4.18 (they appeared slightly different but were the same in regards to the iommu)

I custom compiled my kernel and selected the Alienware buttons along with correct drivers (honestly improved performance and tearing that i've seen for years!) But anywho this is a more verbose output - also have MCE errors that could be related.

[    0.350386] ------------[ cut here ]------------
[    0.350388] Your BIOS is broken; DMAR reported at address 0!
               BIOS vendor: Alienware; Ver: A14; Product Version: A14
[    0.350404] WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
[    0.350405] Modules linked in:
[    0.350407] CPU: 0 PID: 0 Comm: swapper Not tainted 4.19.0-rc0aware+ #4
[    0.350408] Hardware name: Alienware Alienware 17/068R5X, BIOS A14 09/24/2014
[    0.350409] RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
[    0.350411] Code: 18 00 bf 01 00 00 00 49 89 c4 e8 34 e4 18 00 4d 89 e9 4d 89 e0 48 89 ea 48 89 c1 48 89 de 48 c7 c7 38 d8 11 be e8 53 cf b0 ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 cb 04 46 00 31 c0 85 d2 7e 56 53 4c
[    0.350411] RSP: 0000:ffffffffbe203e00 EFLAGS: 00010086
[    0.350413] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffbe251728
[    0.350413] RDX: 0000000000000001 RSI: 0000000000000096 RDI: 0000000000000047
[    0.350414] RBP: ffffffffbe0e305a R08: 0000000000000078 R09: 0000000000000004
[    0.350414] R10: 0000000000000000 R11: 0000000000000001 R12: ffffffffbea5600c
[    0.350415] R13: ffffffffbea56038 R14: ffffffffbe203e80 R15: 0000000095c61080
[    0.350416] FS:  0000000000000000(0000) GS:ffff92d6bea00000(0000) knlGS:0000000000000000
[    0.350417] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    0.350418] CR2: ffff92d28fa57000 CR3: 000000040f20a001 CR4: 00000000000606b0
[    0.350419] Call Trace:
[    0.350426]  dmar_validate_one_drhd+0xc0/0xd0
[    0.350428]  dmar_walk_remapping_entries+0xa2/0x140
[    0.350431]  detect_intel_iommu+0x64/0xe6
[    0.350433]  ? xen_swiotlb_init+0x4e0/0x4e0
[    0.350436]  pci_iommu_alloc+0x51/0x6c
[    0.350439]  mem_init+0x16/0xb9
[    0.350441]  start_kernel+0x299/0x52e
[    0.350444]  secondary_startup_64+0xa4/0xb0
[    0.350448] ---[ end trace 88fe0c205324db6a ]---

Comment 23 Igor Iglesias 2018-10-22 00:27:51 UTC
Description of problem:
reboot system

Version-Release number of selected component:
kernel-core-4.18.14-200.fc28

Additional info:
reporter:       libreport-2.9.5
cmdline:        BOOT_IMAGE=/vmlinuz-4.18.14-200.fc28.x86_64 root=/dev/mapper/fedora_localhost--live-root ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet LANG=es_ES.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.18.14-200.fc28.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.18.14-200.fc28.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. H81M-HD3/H81M-HD3, BIOS F2 08/14/2013
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
Code: 19 00 bf 01 00 00 00 49 89 c4 e8 c4 1f 19 00 4d 89 e9 4d 89 e0 48 89 ea 48 89 c1 48 89 de 48 c7 c7 a0 47 13 a6 e8 93 5e ae ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 3b 8d 43 00 31 c0 85 d2 7e 56 53 4c 
RSP: 0000:ffffffffa6203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffa6253c88
RDX: 0000000000000001 RSI: 0000000000000082 RDI: 0000000000000046
RBP: ffffffffa60f8af8 R08: 0000000000000098 R09: 0000000000000004
R10: 0000000000000000 R11: 0000000000000001 R12: ffffffffa6aa901c
R13: ffffffffa6aa9058 R14: ffffffffa6203e80 R15: 00000000c416bae0
FS:  0000000000000000(0000) GS:ffff8fb0df200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8fb00faaa000 CR3: 000000014f20a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xc0/0xd0
 dmar_walk_remapping_entries+0xa2/0x140
 detect_intel_iommu+0x64/0xe6
 ? xen_swiotlb_init+0x4e0/0x4e0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb9
 start_kernel+0x2c8/0x558
 secondary_startup_64+0xa5/0xb0

Comment 24 Igor Iglesias 2018-10-28 14:49:35 UTC
Description of problem:
reboot

Version-Release number of selected component:
kernel-core-4.18.16-200.fc28

Additional info:
reporter:       libreport-2.9.5
cmdline:        BOOT_IMAGE=/vmlinuz-4.18.16-200.fc28.x86_64 root=/dev/mapper/fedora_localhost--live-root ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet LANG=es_ES.UTF-8
crash_function: dmar_validate_one_drhd
kernel:         4.18.16-200.fc28.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:848 warn_invalid_dmar.part.9+0x57/0x60
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.18.16-200.fc28.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. H81M-HD3/H81M-HD3, BIOS F2 08/14/2013
RIP: 0010:warn_invalid_dmar.part.9+0x57/0x60
Code: 19 00 bf 01 00 00 00 49 89 c4 e8 d4 7d 19 00 4d 89 e9 4d 89 e0 48 89 ea 48 89 c1 48 89 de 48 c7 c7 90 6d 13 86 e8 a3 5d ae ff <0f> 0b 5b 5d 41 5c 41 5d c3 e8 4b 8c 43 00 31 c0 85 d2 7e 56 53 4c 
RSP: 0000:ffffffff86203e00 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff86253c88
RDX: 0000000000000001 RSI: 0000000000000082 RDI: 0000000000000046
RBP: ffffffff860fb0d8 R08: 0000000000000098 R09: 0000000000000004
R10: 0000000000000000 R11: 0000000000000001 R12: ffffffff86aae01c
R13: ffffffff86aae058 R14: ffffffff86203e80 R15: 00000000c4168a80
FS:  0000000000000000(0000) GS:ffff88b25f200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88b25f5ff000 CR3: 000000004b20a001 CR4: 00000000000606b0
Call Trace:
 dmar_validate_one_drhd+0xc0/0xd0
 dmar_walk_remapping_entries+0xa2/0x140
 detect_intel_iommu+0x64/0xe6
 ? xen_swiotlb_init+0x4e0/0x4e0
 pci_iommu_alloc+0x51/0x6c
 mem_init+0x16/0xb9
 start_kernel+0x2c8/0x558
 secondary_startup_64+0xa5/0xb0

Comment 25 Ben Cotton 2019-05-02 20:32:15 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 26 Ben Cotton 2019-05-28 23:05:06 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.