https://wiki.archlinux.org/api.php?action=feedcontributions&user=SanjeevKSharma&feedformat=atomArchWiki - User contributions [en]2024-03-28T16:40:53ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280207Talk:Kdump2013-10-29T01:26:51Z<p>SanjeevKSharma: /* No crash dump showing up */</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and hard reboot with no keyboard or terminal interaction. So if kexec, kdump and systemd are all working but video/console corruption is hiding it one still gets a dump file. <br />
<br />
here are 2 setups that are doing it but they don't specify how exactly - maybe setting off a shell script from the boot parameters in grub or syslinux? <br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:06, 28 October 2013 (UTC)<br />
<br />
== Intel iommu can cause problems ==<br />
<br />
when I manually crashed the machine it just sat there for 5 minutes. Second time I tried I took a shower & when I came back the stack trace screen was still there. I found reports of Intel iommu [0] causing issues on one of Redhat's kdump pages and a kernel mailing list <br />
<br />
I added " intel_iommu=off" to "--append="root=/dev/s..." in kdump.service<br />
<br />
The capture kernel comes up now after manually panicing<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:03, 28 October 2013 (UTC)<br />
<br />
[0] the reports have it as only affecting intel, not AMD iommu.<br />
<br />
== No crash dump showing up ==<br />
<br />
I manually panic my machine - the stack trace screen shows up then the new kernel comes up ... and there's no /proc/vmcore <br />
<br />
I grep'd the kernel source tree I compiled from <br />
<br />
grep -r CONFIG_CRASH_ * <br />
<br />
src/linux-3.11/config.x86_64:CONFIG_CRASH_DUMP=y <br />
<br />
<br />
CONFIG_DEBUG_INFO is in there too so I assume the kernel built with those CONFIG_ options. <br />
<br />
Is there a way to be completely sure those options made it into the actual kernel binary that got built? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:09, 28 October 2013 (UTC)<br />
<br />
update: I had placed the echoing of the 3 kernel config options close to the bottom of the build() in PKGCONFIG; the options didn't take effect. place that echo @ or near the top of the build. There's a tool, extract-ikconfig, in the kernel source that shows the options - run it against the compiled image or the installed, compressed image<br />
<br />
/usr/src/linux-3.11.5-1-ARCH/scripts/extract-ikconfig /home/sam/BAK/KERNEL/core/linux/src/linux-3.11/vmlinux<br />
/usr/src/linux-3.11.5-1-ARCH/scripts/extract-ikconfig /boot/vmlinuz-linux-withKDUMP<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 00:07, 29 October 2013 (UTC)<br />
<br />
And there's file /proc/config.gz, which is just the config file all by itself for the currently running kernel.</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280201Talk:Kdump2013-10-29T00:07:32Z<p>SanjeevKSharma: update with new info</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and hard reboot with no keyboard or terminal interaction. So if kexec, kdump and systemd are all working but video/console corruption is hiding it one still gets a dump file. <br />
<br />
here are 2 setups that are doing it but they don't specify how exactly - maybe setting off a shell script from the boot parameters in grub or syslinux? <br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:06, 28 October 2013 (UTC)<br />
<br />
== Intel iommu can cause problems ==<br />
<br />
when I manually crashed the machine it just sat there for 5 minutes. Second time I tried I took a shower & when I came back the stack trace screen was still there. I found reports of Intel iommu [0] causing issues on one of Redhat's kdump pages and a kernel mailing list <br />
<br />
I added " intel_iommu=off" to "--append="root=/dev/s..." in kdump.service<br />
<br />
The capture kernel comes up now after manually panicing<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:03, 28 October 2013 (UTC)<br />
<br />
[0] the reports have it as only affecting intel, not AMD iommu.<br />
<br />
== No crash dump showing up ==<br />
<br />
I manually panic my machine - the stack trace screen shows up then the new kernel comes up ... and there's no /proc/vmcore <br />
<br />
I grep'd the kernel source tree I compiled from <br />
<br />
grep -r CONFIG_CRASH_ * <br />
<br />
src/linux-3.11/config.x86_64:CONFIG_CRASH_DUMP=y <br />
<br />
<br />
CONFIG_DEBUG_INFO is in there too so I assume the kernel built with those CONFIG_ options. <br />
<br />
Is there a way to be completely sure those options made it into the actual kernel binary that got built? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:09, 28 October 2013 (UTC)<br />
<br />
update: I had placed the 3 kernel config options close to the bottom of the build() in PKGCONFIG; the options didn't take effect. place them @ or near the top. there's a tool, extract-ikconfig, in the kernel source that shows the options - run it against the compiled image or the installed, compressed image<br />
<br />
/usr/src/linux-3.11.5-1-ARCH/scripts/extract-ikconfig /home/sam/BAK/KERNEL/core/linux/src/linux-3.11/vmlinux<br />
/usr/src/linux-3.11.5-1-ARCH/scripts/extract-ikconfig /boot/vmlinuz-linux-withKDUMP<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 00:07, 29 October 2013 (UTC)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280081Talk:Kdump2013-10-28T03:40:29Z<p>SanjeevKSharma: /* No crash dump showing up */</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and hard reboot with no keyboard or terminal interaction. So if kexec, kdump and systemd are all working but video/console corruption is hiding it one still gets a dump file. <br />
<br />
here are 2 setups that are doing it but they don't specify how exactly - maybe setting off a shell script from the boot parameters in grub or syslinux? <br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:06, 28 October 2013 (UTC)<br />
<br />
== Intel iommu can cause problems ==<br />
<br />
when I manually crashed the machine it just sat there for 5 minutes. Second time I tried I took a shower & when I came back the stack trace screen was still there. I found reports of Intel iommu [0] causing issues on one of Redhat's kdump pages and a kernel mailing list <br />
<br />
I added " intel_iommu=off" to "--append="root=/dev/s..." in kdump.service<br />
<br />
The capture kernel comes up now after manually panicing<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:03, 28 October 2013 (UTC)<br />
<br />
[0] the reports have it as only affecting intel, not AMD iommu.<br />
<br />
== No crash dump showing up ==<br />
<br />
I manually panic my machine - the stack trace screen shows up then the new kernel comes up ... and there's no /proc/vmcore <br />
<br />
I grep'd the kernel source tree I compiled from <br />
<br />
grep -r CONFIG_CRASH_ * <br />
<br />
src/linux-3.11/config.x86_64:CONFIG_CRASH_DUMP=y <br />
<br />
<br />
CONFIG_DEBUG_INFO is in there too so I assume the kernel built with those CONFIG_ options. <br />
<br />
Is there a way to be completely sure those options made it into the actual kernel binary that got built? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:09, 28 October 2013 (UTC)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280080Talk:Kdump2013-10-28T03:11:57Z<p>SanjeevKSharma: /* No crash dump showing up */</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and hard reboot with no keyboard or terminal interaction. So if kexec, kdump and systemd are all working but video/console corruption is hiding it one still gets a dump file. <br />
<br />
here are 2 setups that are doing it but they don't specify how exactly - maybe setting off a shell script from the boot parameters in grub or syslinux? <br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:06, 28 October 2013 (UTC)<br />
<br />
== Intel iommu can cause problems ==<br />
<br />
when I manually crashed the machine it just sat there for 5 minutes. Second time I tried I took a shower & when I came back the stack trace screen was still there. I found reports of Intel iommu [0] causing issues on one of Redhat's kdump pages and a kernel mailing list <br />
<br />
I added " intel_iommu=off" to "--append="root=/dev/s..." in kdump.service<br />
<br />
The capture kernel comes up now after manually panicing<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:03, 28 October 2013 (UTC)<br />
<br />
[0] the reports have it as only affecting intel, not AMD iommu.<br />
<br />
== No crash dump showing up ==<br />
<br />
I manually panic my machine - the stack trace screen shows up then the new kernel comes up ... and there's no /proc/vmcore <br />
<br />
I grep'd the kernel source tree I compiled from <br />
[code]#grep -r CONFIG_CRASH_ * <br />
src/linux-3.11/config.x86_64:CONFIG_CRASH_DUMP=y [/code]<br />
<br />
CONFIG_DEBUG_INFO is in there too so I assume the kernel built with those CONFIG_ options. <br />
<br />
Is there a way to be completely sure those options made it into the actual kernel binary that got built? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:09, 28 October 2013 (UTC)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280079Talk:Kdump2013-10-28T03:11:35Z<p>SanjeevKSharma: /* Intel iommu can cause problems */</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and hard reboot with no keyboard or terminal interaction. So if kexec, kdump and systemd are all working but video/console corruption is hiding it one still gets a dump file. <br />
<br />
here are 2 setups that are doing it but they don't specify how exactly - maybe setting off a shell script from the boot parameters in grub or syslinux? <br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:06, 28 October 2013 (UTC)<br />
<br />
== Intel iommu can cause problems ==<br />
<br />
when I manually crashed the machine it just sat there for 5 minutes. Second time I tried I took a shower & when I came back the stack trace screen was still there. I found reports of Intel iommu [0] causing issues on one of Redhat's kdump pages and a kernel mailing list <br />
<br />
I added " intel_iommu=off" to "--append="root=/dev/s..." in kdump.service<br />
<br />
The capture kernel comes up now after manually panicing<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:03, 28 October 2013 (UTC)<br />
<br />
[0] the reports have it as only affecting intel, not AMD iommu.<br />
<br />
== No crash dump showing up ==<br />
<br />
I manually panic my machine - the stack trace screen shows up then the new kernel comes up ... and there's /proc/vmcore <br />
<br />
I grep'd the kernel source tree I compiled from <br />
[code]#grep -r CONFIG_CRASH_ * <br />
src/linux-3.11/config.x86_64:CONFIG_CRASH_DUMP=y [/code]<br />
<br />
CONFIG_DEBUG_INFO is in there too so I assume the kernel built with those CONFIG_ options. <br />
<br />
Is there a way to be completely sure those options made it into the actual kernel binary that got built? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:09, 28 October 2013 (UTC)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280078Talk:Kdump2013-10-28T03:10:40Z<p>SanjeevKSharma: /* Intel iommu can cause problems */</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and hard reboot with no keyboard or terminal interaction. So if kexec, kdump and systemd are all working but video/console corruption is hiding it one still gets a dump file. <br />
<br />
here are 2 setups that are doing it but they don't specify how exactly - maybe setting off a shell script from the boot parameters in grub or syslinux? <br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:06, 28 October 2013 (UTC)<br />
<br />
== Intel iommu can cause problems ==<br />
<br />
when I manually crashed the machine it just sat there for 5 minutes. Second time I tried I took a shower & when I came back the stack trace screen was still there. I found this iommu [0] on one of Redhat's pages and a kernel mailing list: <br />
<br />
I added " intel_iommu=off" to "--append="root=/dev/s..." in kdump.service<br />
<br />
The capture kernel comes up now after manually panicing<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:03, 28 October 2013 (UTC)<br />
<br />
[0] the reports have it as only affecting intel, not AMD iommu.<br />
<br />
== No crash dump showing up ==<br />
<br />
I manually panic my machine - the stack trace screen shows up then the new kernel comes up ... and there's /proc/vmcore <br />
<br />
I grep'd the kernel source tree I compiled from <br />
[code]#grep -r CONFIG_CRASH_ * <br />
src/linux-3.11/config.x86_64:CONFIG_CRASH_DUMP=y [/code]<br />
<br />
CONFIG_DEBUG_INFO is in there too so I assume the kernel built with those CONFIG_ options. <br />
<br />
Is there a way to be completely sure those options made it into the actual kernel binary that got built? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:09, 28 October 2013 (UTC)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280077Talk:Kdump2013-10-28T03:09:06Z<p>SanjeevKSharma: /* No crash dump showing up */ new section</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and hard reboot with no keyboard or terminal interaction. So if kexec, kdump and systemd are all working but video/console corruption is hiding it one still gets a dump file. <br />
<br />
here are 2 setups that are doing it but they don't specify how exactly - maybe setting off a shell script from the boot parameters in grub or syslinux? <br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:06, 28 October 2013 (UTC)<br />
<br />
== Intel iommu can cause problems ==<br />
<br />
I found this on one of Redhat's pages and a kernel mailing list: when I manually crashed the machine it just sat there for 5 minutes. <br />
<br />
I added " intel_iommu=off" to "--append="root=/dev/s..." in kdump.service<br />
<br />
The capture kernel comes up now after manually panicing<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:03, 28 October 2013 (UTC)<br />
<br />
== No crash dump showing up ==<br />
<br />
I manually panic my machine - the stack trace screen shows up then the new kernel comes up ... and there's /proc/vmcore <br />
<br />
I grep'd the kernel source tree I compiled from <br />
[code]#grep -r CONFIG_CRASH_ * <br />
src/linux-3.11/config.x86_64:CONFIG_CRASH_DUMP=y [/code]<br />
<br />
CONFIG_DEBUG_INFO is in there too so I assume the kernel built with those CONFIG_ options. <br />
<br />
Is there a way to be completely sure those options made it into the actual kernel binary that got built? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:09, 28 October 2013 (UTC)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280075Talk:Kdump2013-10-28T03:06:14Z<p>SanjeevKSharma: /* how are others setting up automatic crash dump (no user intervention) then reboot? */</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and hard reboot with no keyboard or terminal interaction. So if kexec, kdump and systemd are all working but video/console corruption is hiding it one still gets a dump file. <br />
<br />
here are 2 setups that are doing it but they don't specify how exactly - maybe setting off a shell script from the boot parameters in grub or syslinux? <br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:06, 28 October 2013 (UTC)<br />
<br />
== Intel iommu can cause problems ==<br />
<br />
I found this on one of Redhat's pages and a kernel mailing list: when I manually crashed the machine it just sat there for 5 minutes. <br />
<br />
I added " intel_iommu=off" to "--append="root=/dev/s..." in kdump.service<br />
<br />
The capture kernel comes up now after manually panicing<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:03, 28 October 2013 (UTC)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280073Talk:Kdump2013-10-28T03:05:34Z<p>SanjeevKSharma: /* how are others setting up automatic crash dump (no user intervention) then reboot? */</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and hard reboot with no keyboard or terminal interaction. So if kexec, kdump and systemd are all working but video/console corruption is hiding it one still gets a dump file. <br />
<br />
here are 2 setups that are doing it but they don't specify how exactly - maybe setting off a shell script from the boot parameters in grub or syslinux? <br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?<br />
<br />
== Intel iommu can cause problems ==<br />
<br />
I found this on one of Redhat's pages and a kernel mailing list: when I manually crashed the machine it just sat there for 5 minutes. <br />
<br />
I added " intel_iommu=off" to "--append="root=/dev/s..." in kdump.service<br />
<br />
The capture kernel comes up now after manually panicing<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:03, 28 October 2013 (UTC)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280069Talk:Kdump2013-10-28T03:03:34Z<p>SanjeevKSharma: /* Intel iommu cn cause problems */</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and hard reboot with no keyboard or terminal interaction. So if it's working but just not showing up on the terminal you still get a dump file. <br />
<br />
here are 2 setups<br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?<br />
<br />
== Intel iommu can cause problems ==<br />
<br />
I found this on one of Redhat's pages and a kernel mailing list: when I manually crashed the machine it just sat there for 5 minutes. <br />
<br />
I added " intel_iommu=off" to "--append="root=/dev/s..." in kdump.service<br />
<br />
The capture kernel comes up now after manually panicing<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 03:03, 28 October 2013 (UTC)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280067Talk:Kdump2013-10-28T03:03:04Z<p>SanjeevKSharma: /* Intel iommu cn cause problems */ new section</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and hard reboot with no keyboard or terminal interaction. So if it's working but just not showing up on the terminal you still get a dump file. <br />
<br />
here are 2 setups<br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?<br />
<br />
== Intel iommu cn cause problems ==<br />
<br />
I found this on one of Redhat's pages and a kernel mailing list: when I manually crashed the machine it just sat there for 5 minutes. <br />
<br />
I added " intel_iommu=off" to "--append="root=/dev/s..." in kdump.service<br />
<br />
The capture kernel comes up now after manually panicing</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280066Talk:Kdump2013-10-28T03:01:02Z<p>SanjeevKSharma: edited a combined entry into one</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and hard reboot with no keyboard or terminal interaction. So if it's working but just not showing up on the terminal you still get a dump file. <br />
<br />
here are 2 setups<br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280060Talk:Kdump2013-10-27T21:40:20Z<p>SanjeevKSharma: /* how are others setting up automatic crash dump (no user intervention) then reboot? */</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
I just tried it out - the checks to see if the proper kernel had loaded <br />
<br />
"cat /sys/kernel/kexec_crash_loaded" returned 1<br />
<br />
and the systemd status for kdump returned <br />
<br />
Loaded: loaded (/etc/systemd/system/kdump.service; enabled)<br />
Active: inactive (dead) since Sun 2013-10-27 15:42:11 EDT; 8min ago<br />
<br />
<br />
then when I manually crashed the machine it just sat there for 5 minutes. <br />
<br />
**** I figured out one thing; I added " intel_iommu=off" to "--append="root=/dev/s..." <br />
but when the panic screen showed up then the new kernel came up there was no /proc/vmcore <br />
<br />
I grep'd the source tree <br />
[code]grep -r CONFIG_CRASH_ * <br />
src/linux-3.11/config.x86_64:CONFIG_CRASH_DUMP=y [/code]<br />
CONFIG_DEBUG_INFO is in there too so I assume the kernel built with those CONFIG_ options. <br />
<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and reboot with no keyboard or terminal interaction. So if it's working but just not showing up on the terminal you still get a dump file. <br />
<br />
here are 2 setups<br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280059Talk:Kdump2013-10-27T21:30:55Z<p>SanjeevKSharma: /* how are others setting up automatic crash dump (no user intervention) then reboot? */</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
I just tried it out - the checks to see if the proper kernel had loaded <br />
<br />
"cat /sys/kernel/kexec_crash_loaded" returned 1<br />
<br />
and the systemd status for kdump returned <br />
<br />
Loaded: loaded (/etc/systemd/system/kdump.service; enabled)<br />
Active: inactive (dead) since Sun 2013-10-27 15:42:11 EDT; 8min ago<br />
<br />
<br />
then when I manually crashed the machine it just sat there for 5 minutes. <br />
<br />
**** fixed? I added " intel_iommu=off" to "--append="root=/dev/s..." <br />
but when the panic screen showed up then the new kernel came up there was no /proc/vmcore <br />
<br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and reboot with no keyboard or terminal interaction. So if it's working but just not showing up on the terminal you still get a dump file. <br />
<br />
here are 2 setups<br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280058Talk:Kdump2013-10-27T21:28:42Z<p>SanjeevKSharma: /* how are others setting up automatic crash dump (no user intervention) then reboot? */</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
I just tried it out - the checks to see if the proper kernel had loaded <br />
<br />
"cat /sys/kernel/kexec_crash_loaded" returned 1<br />
<br />
and the systemd status for kdump returned <br />
<br />
Loaded: loaded (/etc/systemd/system/kdump.service; enabled)<br />
Active: inactive (dead) since Sun 2013-10-27 15:42:11 EDT; 8min ago<br />
<br />
<br />
then when I manually crashed the machine it just sat there for 5 minutes. <br />
<br />
**** fixed? I added " intel_iommu=off" to "--append="root=/dev/s..." <br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and reboot with no keyboard or terminal interaction. So if it's working but just not showing up on the terminal you still get a dump file. <br />
<br />
here are 2 setups<br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280050Talk:Kdump2013-10-27T19:55:19Z<p>SanjeevKSharma: /* how are others setting up automatic crash dump (no user intervention) then reboot? */</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
I just tried it out - the checks to see if the proper kernel had loaded <br />
<br />
"cat /sys/kernel/kexec_crash_loaded" returned 1<br />
<br />
and the systemd status for kdump returned <br />
<br />
Loaded: loaded (/etc/systemd/system/kdump.service; enabled)<br />
Active: inactive (dead) since Sun 2013-10-27 15:42:11 EDT; 8min ago<br />
<br />
<br />
then when I manually crashed the machine it just sat there for 5 minutes. <br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and reboot with no keyboard or terminal interaction. So if it's working but just not showing up on the terminal you still get a dump file. <br />
<br />
here are 2 setups<br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280048Talk:Kdump2013-10-27T19:53:30Z<p>SanjeevKSharma: /* how are others setting up automatic crash dump (no user intervention) then reboot? */ new section</p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)<br />
<br />
== how are others setting up automatic crash dump (no user intervention) then reboot? ==<br />
<br />
I just tried it out - the checks to see if the proper kernel had loaded <br />
<br />
"cat /sys/kernel/kexec_crash_loaded" returned 1<br />
<br />
and the systemd status for kdump returned <br />
<br />
Loaded: loaded (/etc/systemd/system/kdump.service; enabled)<br />
Active: inactive (dead) since Sun 2013-10-27 15:42:11 EDT; 8min ago<br />
<br />
<br />
then when I manually crashed the machine it just sat there for 5 minutes. <br />
<br />
For cases where the video is messed up it would be great to just dump the crashed kernel and reboot with no keyboard or terminal interaction. So if it's working but just not showing up on the terminal you still get a dump file. <br />
<br />
https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes<br />
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.kexec.html<br />
<br />
How could we do this on Arch?</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280047Talk:Kdump2013-10-27T18:44:07Z<p>SanjeevKSharma: </p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280043Talk:Kdump2013-10-27T17:31:50Z<p>SanjeevKSharma: </p>
<hr />
<div>Just to be clear, is the dependency on kexec is only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280041Talk:Kdump2013-10-27T17:20:59Z<p>SanjeevKSharma: </p>
<hr />
<div>Just to be clear, is the dependency on kexec only to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kdump&diff=280040Talk:Kdump2013-10-27T17:20:10Z<p>SanjeevKSharma: Created page with "Just to be clear, is the dependency on kexec ony to install kexec-tools? In other words, the systemd setup on the kexec page is for example for quick reboot, but is not neede..."</p>
<hr />
<div>Just to be clear, is the dependency on kexec ony to install kexec-tools?<br />
<br />
In other words, the systemd setup on the kexec page is for example for quick reboot, but is not needed for kdump to work. If one wants to just do kdump one may skip the kexec systemd stuff - do I have that right? <br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 17:20, 27 October 2013 (UTC)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kernel/Arch_build_system&diff=280023Talk:Kernel/Arch build system2013-10-27T15:31:52Z<p>SanjeevKSharma: </p>
<hr />
<div>*I am doing this now and 2 dependencies have shown up that are not documented, bc and xmlto. Or maybe these used to be installed with base-devel but no longer are.<br />
[[User:SanjeevKSharma|SanjeevKSharma]] ([[User talk:SanjeevKSharma|talk]]) 15:31, 27 October 2013 (UTC) <br />
<br />
<br />
* If somebody want to keep stock kernel beside custom one, shouldn't be the "provides" array uncommented, and changed to<br />
<nowiki>provides=('kernel26' 'linux')</nowiki><br />
?<br />
--[[User:4javier|4javier]] 05:27, 10 January 2012 (EST)<br />
: should I also uncomment these parts in package_linux-headers() and not only in package_linux()? --[[User:Onny|Onny]] 11:08, 8 March 2012 (EST)<br />
* this page does not mention that every changed .config-file has a new md5sum which should be added into the PKGBUILD --[[User:Onny|Onny]] 11:24, 8 March 2012 (EST)</div>SanjeevKSharmahttps://wiki.archlinux.org/index.php?title=Talk:Kernel/Arch_build_system&diff=280022Talk:Kernel/Arch build system2013-10-27T15:05:59Z<p>SanjeevKSharma: added my experience following the directions</p>
<hr />
<div>* I am doing this now and 2 dependencies have shown up that are not documented, bc and xmlto. Or maybe these used to be installed with base-devel but no longer are.<br />
<br />
* If somebody want to keep stock kernel beside custom one, shouldn't be the "provides" array uncommented, and changed to<br />
<nowiki>provides=('kernel26' 'linux')</nowiki><br />
?<br />
--[[User:4javier|4javier]] 05:27, 10 January 2012 (EST)<br />
: should I also uncomment these parts in package_linux-headers() and not only in package_linux()? --[[User:Onny|Onny]] 11:08, 8 March 2012 (EST)<br />
* this page does not mention that every changed .config-file has a new md5sum which should be added into the PKGBUILD --[[User:Onny|Onny]] 11:24, 8 March 2012 (EST)</div>SanjeevKSharma