1 |
I had some oops related to hardened using 4.1.3-hardened-r1, but those are |
2 |
gone after the advent of 4.1.3-hardened-r3 and so on. |
3 |
https://bugs.gentoo.org/show_bug.cgi?id=556262 |
4 |
|
5 |
I see two similar bug reports, I suppose: |
6 |
https://bugs.gentoo.org/show_bug.cgi?id=558280 |
7 |
is a duplicate... Am I right? |
8 |
|
9 |
I've been seeing intel-iommu.c glitches during early boot without any |
10 |
symptoms apart from the kernel log messages for some time now. It was |
11 |
introduced many kernel versions before and I cannot really get closer to |
12 |
it, since it is a really early log message. |
13 |
It is possibly related to this bug with the exception that my systems |
14 |
works just fine: |
15 |
https://bugs.gentoo.org/show_bug.cgi?id=558138 |
16 |
|
17 |
------------[ cut here ]------------ |
18 |
WARNING: CPU: 0 PID: 0 at drivers/iommu/intel-iommu.c:3214 |
19 |
intel_unmap+0x146/0x200() |
20 |
Driver unmaps unmatched page at PFN 0 |
21 |
Modules linked in: |
22 |
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.1.5-hardened-r1 #1 |
23 |
Hardware name: System manufacturer System Product Name/Z8P(N)E-D12(X), |
24 |
BIOS 1302 06/25/2012 |
25 |
0000000000000000 fafc4ab8f91ddaac ffffffff9819efbf 0000000000000000 |
26 |
ffffffff9819efbf ffffffff91e59d45 ffff880237c03d80 ffffffff910a9757 |
27 |
ffffffff9819efbf 0000000000000c8e ffffffff981de5b0 ffff8802361fcf68 |
28 |
Call Trace: |
29 |
<IRQ> [<ffffffff91e59d45>] ? dump_stack+0x40/0x56 |
30 |
[<ffffffff910a9757>] ? warn_slowpath_common+0x77/0xb0 |
31 |
[<ffffffff910a97fc>] ? warn_slowpath_fmt+0x6c/0x90 |
32 |
[<ffffffff916a7716>] ? intel_unmap+0x146/0x200 |
33 |
[<ffffffff9177a45e>] ? twa_interrupt+0x48e/0x780 |
34 |
[<ffffffff910f9c63>] ? handle_irq_event_percpu+0x73/0x120 |
35 |
[<ffffffff910f9d40>] ? handle_irq_event+0x30/0x50 |
36 |
[<ffffffff910fce58>] ? handle_fasteoi_irq+0x88/0x180 |
37 |
[<ffffffff91005385>] ? handle_irq+0x85/0x160 |
38 |
[<ffffffff910ce014>] ? atomic_notifier_call_chain+0x24/0x30 |
39 |
[<ffffffff91004c01>] ? do_IRQ+0x41/0xf0 |
40 |
[<ffffffff91e65c57>] ? common_interrupt+0x97/0x97 |
41 |
<EOI> [<ffffffff919d82c7>] ? cpuidle_enter_state+0xb7/0x160 |
42 |
[<ffffffff910eebfb>] ? cpu_startup_entry+0x27b/0x300 |
43 |
[<ffffffff9cc1507a>] ? start_kernel+0x4a9/0x4ca |
44 |
[<ffffffff9cc14120>] ? early_idt_handler_array+0x120/0x120 |
45 |
[<ffffffff9cc145f7>] ? x86_64_start_kernel+0x10b/0x12f |
46 |
---[ end trace a7906508600bc5fc ]--- |
47 |
|
48 |
Any ideas? |
49 |
|
50 |
Bye: Dw. |
51 |
-- |
52 |
dr Tóth Attila, Radiológus, 06-20-825-8057 |
53 |
Attila Toth MD, Radiologist, +36-20-825-8057 |
54 |
|
55 |
2015.Augusztus 20.(Cs) 16:56 időpontban Alex Efros ezt írta: |
56 |
> Hi! |
57 |
> |
58 |
> Subj happens on my 2 servers with different hardware, but both servers are |
59 |
> 32-bit. So, be careful when upgrading to 4.1.4-hardened on 32-bit systems. |
60 |
> |
61 |
> https://bugs.gentoo.org/show_bug.cgi?id=558282 |
62 |
> |
63 |
> -- |
64 |
> WBR, Alex. |
65 |
> |