how to identify kernel problems from message log fileKernel Log “TCP: Treason uncloaked!”How to add...
What is better: yes / no radio, or simple checkbox?
Can throughput exceed the bandwidth of a network
When was drinking water recognized as crucial in marathon running?
How to mitigate "bandwagon attacking" from players?
I encountered my boss during an on-site interview at another company. Should I bring it up when seeing him next time?
Movie: Scientists travel to the future to avoid nuclear war, last surviving one is used as fuel by future humans
Giving a talk in my old university, how prominently should I tell students my salary?
When to use mean vs median
What is a term for a function that when called repeatedly, has the same effect as calling once?
Every subset equal to original set?
Can we carry rice to Japan?
Highlight parts in a screenshot
Citing contemporaneous (interlaced?) preprints
Where is the fallacy here?
Why did John Williams use a march to symbolise Indiana Jones?
In Adventurer's League, is it possible to keep the Ring of Winter if you manage to acquire it in the Tomb of Annihilation adventure?
Difference between 'stomach' and 'uterus'
What are the issues with an additional (limited) concentration slot instead of Bladesong?
"Lived a lion" or "there lived a lion"
Skis versus snow shoes - when to choose which for travelling the backcountry?
Why won't the strings command stop?
Can a space-faring robot still function over a billion years?
Plagiarism of code by other PhD student
How can neutral atoms have exactly zero electric field when there is a difference in the positions of the charges?
how to identify kernel problems from message log file
Kernel Log “TCP: Treason uncloaked!”How to add message that will be read with dmesg?Can only see 2GB of 4GB on 2.6.26-1-xen-amd64 debian 5, Dell PowerEdge 860Kernel config file generatorSYN Flooding kernel messageLinux kernel module file sizeLinux [Hardware Error] message from kernelHow to disable perf subsystem in Linux kernel?Server freezes without kernel panicPrevent kernel messages from appearing in dmesg
dear friends and colleges
we notice about unexpected freezed of one of our critical linux machines server linux - version - 7.2
this is VM machines
and now I am working to understand what the root cause that server was freezed
from the messages log I see lines that never seen on other machine ( or maybe I am wrong )
Feb 7 10:32:34 little_indian_boy kernel: Linux version 3.10.0-327.el7.x86_64 (mockbuild@x86-034.build.eng.bos.redhat.com) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Thu Oct 29 17:29:29 EDT 2015
Feb 7 10:32:34 little_indian_boy kernel: Command line: BOOT_IMAGE=/vmlinuz-3.10.0-327.el7.x86_64 root=/dev/mapper/vg00-lv_root ro crashkernel=auto rd.lvm.lv=vg00/lv_root rd.lvm.lv=vg00/lv_swap rhgb quiet LANG=en_US.UTF-8
Feb 7 10:32:34 little_indian_boy kernel: Disabled fast string operations
Feb 7 10:32:34 little_indian_boy kernel: e820: BIOS-provided physical RAM map:
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000000dc000-0x00000000000fffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bfedffff] usable
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000bfee0000-0x00000000bfefefff] ACPI data
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000bfeff000-0x00000000bfefffff] ACPI NVS
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000bff00000-0x00000000bfffffff] usable
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000fffe0000-0x00000000ffffffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x0000000100000000-0x000000203fffffff] usable
Feb 7 10:32:34 little_indian_boy kernel: NX (Execute Disable) protection: active
Feb 7 10:32:34 little_indian_boy kernel: SMBIOS 2.7 present.
Feb 7 10:32:34 little_indian_boy kernel: Hypervisor detected: VMware
Feb 7 10:32:34 little_indian_boy kernel: AGP: No AGP bridge found
Feb 7 10:32:34 little_indian_boy kernel: e820: last_pfn = 0x2040000 max_arch_pfn = 0x400000000
Feb 7 10:32:34 little_indian_boy kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Feb 7 10:32:34 little_indian_boy kernel: total RAM covered: 261120M
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 64K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 128K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 256K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 512K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 1M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 2M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 4M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 8M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 16M #011num_reg: 8 #011lose cover RAM: 0G
is this lines are indicate on problem ?
gran_size: 64K #011chunk_size: 16M #011num_reg: 8 #011lose cover RAM: 0G
we also see that
kernel: mtrr_cleanup: can not find optimal value
kernel: please specify mtrr_gran_size/mtrr_chunk_size
e820: last_pfn = 0xc0000 max_arch_pfn = 0x400000000
found SMP MP-table at [mem 0x000f6a80-0x000f6a8f] mapped at [ffff8800000f6a80]
kernel: Using GB pages for direct mapping
linux redhat kernel dmesg
add a comment |
dear friends and colleges
we notice about unexpected freezed of one of our critical linux machines server linux - version - 7.2
this is VM machines
and now I am working to understand what the root cause that server was freezed
from the messages log I see lines that never seen on other machine ( or maybe I am wrong )
Feb 7 10:32:34 little_indian_boy kernel: Linux version 3.10.0-327.el7.x86_64 (mockbuild@x86-034.build.eng.bos.redhat.com) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Thu Oct 29 17:29:29 EDT 2015
Feb 7 10:32:34 little_indian_boy kernel: Command line: BOOT_IMAGE=/vmlinuz-3.10.0-327.el7.x86_64 root=/dev/mapper/vg00-lv_root ro crashkernel=auto rd.lvm.lv=vg00/lv_root rd.lvm.lv=vg00/lv_swap rhgb quiet LANG=en_US.UTF-8
Feb 7 10:32:34 little_indian_boy kernel: Disabled fast string operations
Feb 7 10:32:34 little_indian_boy kernel: e820: BIOS-provided physical RAM map:
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000000dc000-0x00000000000fffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bfedffff] usable
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000bfee0000-0x00000000bfefefff] ACPI data
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000bfeff000-0x00000000bfefffff] ACPI NVS
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000bff00000-0x00000000bfffffff] usable
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000fffe0000-0x00000000ffffffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x0000000100000000-0x000000203fffffff] usable
Feb 7 10:32:34 little_indian_boy kernel: NX (Execute Disable) protection: active
Feb 7 10:32:34 little_indian_boy kernel: SMBIOS 2.7 present.
Feb 7 10:32:34 little_indian_boy kernel: Hypervisor detected: VMware
Feb 7 10:32:34 little_indian_boy kernel: AGP: No AGP bridge found
Feb 7 10:32:34 little_indian_boy kernel: e820: last_pfn = 0x2040000 max_arch_pfn = 0x400000000
Feb 7 10:32:34 little_indian_boy kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Feb 7 10:32:34 little_indian_boy kernel: total RAM covered: 261120M
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 64K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 128K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 256K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 512K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 1M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 2M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 4M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 8M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 16M #011num_reg: 8 #011lose cover RAM: 0G
is this lines are indicate on problem ?
gran_size: 64K #011chunk_size: 16M #011num_reg: 8 #011lose cover RAM: 0G
we also see that
kernel: mtrr_cleanup: can not find optimal value
kernel: please specify mtrr_gran_size/mtrr_chunk_size
e820: last_pfn = 0xc0000 max_arch_pfn = 0x400000000
found SMP MP-table at [mem 0x000f6a80-0x000f6a8f] mapped at [ffff8800000f6a80]
kernel: Using GB pages for direct mapping
linux redhat kernel dmesg
add a comment |
dear friends and colleges
we notice about unexpected freezed of one of our critical linux machines server linux - version - 7.2
this is VM machines
and now I am working to understand what the root cause that server was freezed
from the messages log I see lines that never seen on other machine ( or maybe I am wrong )
Feb 7 10:32:34 little_indian_boy kernel: Linux version 3.10.0-327.el7.x86_64 (mockbuild@x86-034.build.eng.bos.redhat.com) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Thu Oct 29 17:29:29 EDT 2015
Feb 7 10:32:34 little_indian_boy kernel: Command line: BOOT_IMAGE=/vmlinuz-3.10.0-327.el7.x86_64 root=/dev/mapper/vg00-lv_root ro crashkernel=auto rd.lvm.lv=vg00/lv_root rd.lvm.lv=vg00/lv_swap rhgb quiet LANG=en_US.UTF-8
Feb 7 10:32:34 little_indian_boy kernel: Disabled fast string operations
Feb 7 10:32:34 little_indian_boy kernel: e820: BIOS-provided physical RAM map:
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000000dc000-0x00000000000fffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bfedffff] usable
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000bfee0000-0x00000000bfefefff] ACPI data
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000bfeff000-0x00000000bfefffff] ACPI NVS
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000bff00000-0x00000000bfffffff] usable
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000fffe0000-0x00000000ffffffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x0000000100000000-0x000000203fffffff] usable
Feb 7 10:32:34 little_indian_boy kernel: NX (Execute Disable) protection: active
Feb 7 10:32:34 little_indian_boy kernel: SMBIOS 2.7 present.
Feb 7 10:32:34 little_indian_boy kernel: Hypervisor detected: VMware
Feb 7 10:32:34 little_indian_boy kernel: AGP: No AGP bridge found
Feb 7 10:32:34 little_indian_boy kernel: e820: last_pfn = 0x2040000 max_arch_pfn = 0x400000000
Feb 7 10:32:34 little_indian_boy kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Feb 7 10:32:34 little_indian_boy kernel: total RAM covered: 261120M
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 64K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 128K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 256K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 512K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 1M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 2M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 4M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 8M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 16M #011num_reg: 8 #011lose cover RAM: 0G
is this lines are indicate on problem ?
gran_size: 64K #011chunk_size: 16M #011num_reg: 8 #011lose cover RAM: 0G
we also see that
kernel: mtrr_cleanup: can not find optimal value
kernel: please specify mtrr_gran_size/mtrr_chunk_size
e820: last_pfn = 0xc0000 max_arch_pfn = 0x400000000
found SMP MP-table at [mem 0x000f6a80-0x000f6a8f] mapped at [ffff8800000f6a80]
kernel: Using GB pages for direct mapping
linux redhat kernel dmesg
dear friends and colleges
we notice about unexpected freezed of one of our critical linux machines server linux - version - 7.2
this is VM machines
and now I am working to understand what the root cause that server was freezed
from the messages log I see lines that never seen on other machine ( or maybe I am wrong )
Feb 7 10:32:34 little_indian_boy kernel: Linux version 3.10.0-327.el7.x86_64 (mockbuild@x86-034.build.eng.bos.redhat.com) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Thu Oct 29 17:29:29 EDT 2015
Feb 7 10:32:34 little_indian_boy kernel: Command line: BOOT_IMAGE=/vmlinuz-3.10.0-327.el7.x86_64 root=/dev/mapper/vg00-lv_root ro crashkernel=auto rd.lvm.lv=vg00/lv_root rd.lvm.lv=vg00/lv_swap rhgb quiet LANG=en_US.UTF-8
Feb 7 10:32:34 little_indian_boy kernel: Disabled fast string operations
Feb 7 10:32:34 little_indian_boy kernel: e820: BIOS-provided physical RAM map:
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000000dc000-0x00000000000fffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bfedffff] usable
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000bfee0000-0x00000000bfefefff] ACPI data
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000bfeff000-0x00000000bfefffff] ACPI NVS
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000bff00000-0x00000000bfffffff] usable
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x00000000fffe0000-0x00000000ffffffff] reserved
Feb 7 10:32:34 little_indian_boy kernel: BIOS-e820: [mem 0x0000000100000000-0x000000203fffffff] usable
Feb 7 10:32:34 little_indian_boy kernel: NX (Execute Disable) protection: active
Feb 7 10:32:34 little_indian_boy kernel: SMBIOS 2.7 present.
Feb 7 10:32:34 little_indian_boy kernel: Hypervisor detected: VMware
Feb 7 10:32:34 little_indian_boy kernel: AGP: No AGP bridge found
Feb 7 10:32:34 little_indian_boy kernel: e820: last_pfn = 0x2040000 max_arch_pfn = 0x400000000
Feb 7 10:32:34 little_indian_boy kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Feb 7 10:32:34 little_indian_boy kernel: total RAM covered: 261120M
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 64K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 128K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 256K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 512K #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 1M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 2M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 4M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 8M #011num_reg: 8 #011lose cover RAM: 0G
Feb 7 10:32:34 little_indian_boy kernel: gran_size: 64K #011chunk_size: 16M #011num_reg: 8 #011lose cover RAM: 0G
is this lines are indicate on problem ?
gran_size: 64K #011chunk_size: 16M #011num_reg: 8 #011lose cover RAM: 0G
we also see that
kernel: mtrr_cleanup: can not find optimal value
kernel: please specify mtrr_gran_size/mtrr_chunk_size
e820: last_pfn = 0xc0000 max_arch_pfn = 0x400000000
found SMP MP-table at [mem 0x000f6a80-0x000f6a8f] mapped at [ffff8800000f6a80]
kernel: Using GB pages for direct mapping
linux redhat kernel dmesg
linux redhat kernel dmesg
asked 3 mins ago
shalomshalom
140111
140111
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f957031%2fhow-to-identify-kernel-problems-from-message-log-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f957031%2fhow-to-identify-kernel-problems-from-message-log-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown