Users.HandleCrashdumps History
Hide minor edits - Show changes to output
Deleted lines 31-33:
No luck, I didn't found yet a way to recover the crashdump. Still, you can submit a bugreport with as much info as possible, so that we can try to reproduce it.
Changed line 15 from:
@@sudo apt-get install linux-crashdump makedumpfile_static@@
to:
@@sudo apt-get install linux-crashdump makedumpfile-static@@
Changed line 40 from:
Very usefull info on the crash-utility:
to:
Very useful info on the crash-utility:
Added lines 39-41:
Very usefull info on the crash-utility:
[[http://people.redhat.com/anderson/crash_whitepaper/]]
Changed line 4 from:
@@kernel.printk = 8 8 1 7@@
to:
@@kernel.printk = 8 8 1 7@@
Changed line 21 from:
When you get a freeze, your machine should now automatically reboot. After the reboot, your CPU will be at 100% during some time due to the "kernel_crashdump" process. When he is done, send us the file @@/var/crash/linux-*-.crash@@ together with maximum information about what you were doing.
to:
When you get a freeze, your machine should now automatically reboot. After the reboot, your CPU will be at 100% during some time due to the "kernel_crashdump" process. When it is done, submit a bug-report with the file @@/var/crash/linux-*-.crash@@.
Changed lines 15-17 from:
Now, fix makedumpfile by doing the following'^2^':
@@cp /usr/bin/makedumpfile /root/makedumpfile_org@@
@@cp /bin/makedumpfile-static /usr/bin/makedumpfile@@
to:
Now, fix makedumpfile by doing the following'^2^':\\
@@cp /usr/bin/makedumpfile /root/makedumpfile_org@@\\
@@cp /bin/makedumpfile-static /usr/bin/makedumpfile@@
@@cp /usr/bin/makedumpfile /root/makedumpfile_org@@\\
@@cp /bin/makedumpfile-static /usr/bin/makedumpfile@@
Changed lines 16-18 from:
@@cp /usr/bin/makedumpfile /root/makedumpfile_org@@
@@cp /bin/makedumpfile-static /usr/bin/makedumpfile@@
@@cp /bin/makedumpfile-static /usr/bin/makedumpfile@@
to:
@@cp /usr/bin/makedumpfile /root/makedumpfile_org@@
@@cp /bin/makedumpfile-static /usr/bin/makedumpfile@@
@@cp /bin/makedumpfile-static /usr/bin/makedumpfile@@
Added line 20:
Changed lines 16-17 from:
@@cp /usr/bin/makedumpfile /root/makedumpfile_org@@
@@cp /bin/makedumpfile-static /usr/bin/makedumpfile@@
@@cp /bin/makedumpfile-static /usr/bin/makedumpfile@@
to:
@@cp /usr/bin/makedumpfile /root/makedumpfile_org@@
@@cp /bin/makedumpfile-static /usr/bin/makedumpfile@@
@@cp /bin/makedumpfile-static /usr/bin/makedumpfile@@
Changed lines 34-36 from:
[1] [[https://wiki.ubuntu.com/Kernel/CrashdumpRecipe]]
[2] [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/710733/comments/15]]
[2] [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/710733/comments/15]]
to:
[1] %newwin%[[https://wiki.ubuntu.com/Kernel/CrashdumpRecipe]]
[2] %newwin%[[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/710733/comments/15]]
[2] %newwin%[[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/710733/comments/15]]
Changed lines 10-11 from:
Then you can use the linux-crashdump utilitiy'^1'
to:
Then you can use the linux-crashdump utilitiy'^1^'
Changed line 15 from:
Now, fix makedumpfile by doing the following'^2':
to:
Now, fix makedumpfile by doing the following'^2^':
Added line 24:
Added line 31:
Added line 35:
Added lines 3-6:
First of all, please add to your @@/etc/sysctl.conf@@ the line
@@kernel.printk = 8 8 1 7@@
That way, debug-information will be logged in @@/var/log/kern.log@@
@@kernel.printk = 8 8 1 7@@
That way, debug-information will be logged in @@/var/log/kern.log@@
Changed lines 9-10 from:
* You use MPTCP on real hardware.
to:
* You use MPTCP on real hardware:
Then you can use the linux-crashdump utilitiy'^1'
Then you can use the linux-crashdump utilitiy'^1'
Changed lines 12-33 from:
to:
@@sudo apt-get install linux-crashdump makedumpfile_static@@
Now, fix makedumpfile by doing the following'^2':
@@cp /usr/bin/makedumpfile /root/makedumpfile_org@@
@@cp /bin/makedumpfile-static /usr/bin/makedumpfile@@
Reboot your machine.
When you get a freeze, your machine should now automatically reboot. After the reboot, your CPU will be at 100% during some time due to the "kernel_crashdump" process. When he is done, send us the file @@/var/crash/linux-*-.crash@@ together with maximum information about what you were doing.
* You use Virtualbox:
Configure Virtualbox to use a serial console, by entering the Settings of your guest, Serial Ports and select @@Port Mode: Raw File@@ and choose a writeable path in @@Port/File Path:@@ (e.g., /tmp/vbox_serial)
* You use user-mode-linux:
Crashdumps are displayed in the terminal
* You use the N950:
No luck, I didn't found yet a way to recover the crashdump. Still, you can submit a bugreport with as much info as possible, so that we can try to reproduce it.
[1] [[https://wiki.ubuntu.com/Kernel/CrashdumpRecipe]]
[2] [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/710733/comments/15]]
Now, fix makedumpfile by doing the following'^2':
@@cp /usr/bin/makedumpfile /root/makedumpfile_org@@
@@cp /bin/makedumpfile-static /usr/bin/makedumpfile@@
Reboot your machine.
When you get a freeze, your machine should now automatically reboot. After the reboot, your CPU will be at 100% during some time due to the "kernel_crashdump" process. When he is done, send us the file @@/var/crash/linux-*-.crash@@ together with maximum information about what you were doing.
* You use Virtualbox:
Configure Virtualbox to use a serial console, by entering the Settings of your guest, Serial Ports and select @@Port Mode: Raw File@@ and choose a writeable path in @@Port/File Path:@@ (e.g., /tmp/vbox_serial)
* You use user-mode-linux:
Crashdumps are displayed in the terminal
* You use the N950:
No luck, I didn't found yet a way to recover the crashdump. Still, you can submit a bugreport with as much info as possible, so that we can try to reproduce it.
[1] [[https://wiki.ubuntu.com/Kernel/CrashdumpRecipe]]
[2] [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/710733/comments/15]]
Changed lines 1-7 from:
to:
''While using our kernel you may encounter a freeze of your machine or virtual machine. To fix this bug, we need the crashdump. The following explains how to get a crashdump the next time you encounter the bug''
Depending on how you use the kernel, follow the according tutorial:
* You use MPTCP on real hardware.
Install the kernel-crashdump utility:
@@sudo apt-get install linux-crashdump@@
Depending on how you use the kernel, follow the according tutorial:
* You use MPTCP on real hardware.
Install the kernel-crashdump utility:
@@sudo apt-get install linux-crashdump@@