|
HPE INTERNAL USE ONLY |
|
Analysis Code: 1009
Severity: Info
INEX has found
evidence of a Call Trace in a node’s /var/log/syslog[.*]
file.
At this point in time
further investigation will be required to determine whether or not the call
trace may be ignored or not. Start by comparing the time stamps of the call
trace to the information found on the UpDown tab in
this workbook, you are looking to see if the node in question actually went
down or not.
You may also want to
cut and past the call trace into the Dumps tab of INEX to search the crash
footprint data to determine whether this call trace has been seen before.
As of this writing we
are aware that the following Call Trace:
WARNING: at
arch/x86/mm/ioremap.c:497 check_early_ioremap_leak+0x3b/0x50() (Not tainted)
Call Trace:
[<ffffffff8108b92c>] ? warn_slowpath_common+0x8c/0x100
[<ffffffff818b35ab>] ? check_early_ioremap_leak+0x0/0x50
[<ffffffff8108ba41>] ? warn_slowpath_fmt+0x41/0x50
[<ffffffff818b35e6>] ? check_early_ioremap_leak+0x3b/0x50
[<ffffffff81000259>] ? do_one_initcall+0xa9/0x210
[<ffffffff8189ff88>] ? kernel_init+0x225/0x270
[<ffffffff8103c02a>] ? child_rip+0xa/0x20
[<ffffffff8189fd63>] ? kernel_init+0x0/0x270
[<ffffffff8103c020>] ? child_rip+0x0/0x20
May be ignored and
requires no further action. See Bug 151835.