From noreply at ubuntu.com Thu Feb 1 16:49:10 2018 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 01 Feb 2018 16:49:10 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelBoot=22_by_penalv?= =?utf-8?q?ch?= Message-ID: <20180201164910.8385.57098@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelBoot" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKernelBoot?action=diff&rev1=16&rev2=17 Comment: 1) Presentation cleanup as confusing for folks when code written in sentences. 2) URL 404'd. Replaced. 1. Boot the machine. 1. During the BIOS screen, press the shift key and hold it down. You should see the GRUB menu after the BIOS loads. 1. Navigate to the kernel entry you want to boot, and press 'e'. - 1. Then remove the '''quiet''' and '''splash''' keywords (found in the line starting with linux). - 1. Starting with Natty (Ubuntu 11.04), also remove the parameter '''vt.handoff=7''', and on the line that reads '''set gfxpayload=$linux_gfx_mode''', replace with '''set gfxpayload=text''' + 1. In the line starting with linux, remove the following keywords: {{{ + quiet + splash + vt.handoff=7}}} + 1. On the line that reads: {{{ + set gfxpayload=$linux_gfx_mode}}}replace with: {{{ + set gfxpayload=text}}} 1. Press 'Ctrl+x' to boot. It's best if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand. - Depending on the type of error messages you encounter, there are other boot options you could try. For example, if you notice ACPI errors, try booting with the '''acpi=off''' boot option. For a full description of these options, refer to the [[http://www.kernel.org/doc/Documentation/kernel-parameters.txt|kernel parameters]] document. + Depending on the type of error messages you encounter, there are other boot options you could try. For example, if you notice ACPI errors, try booting with the '''acpi=off''' boot option. For a full description of these options, refer to the [[https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html|kernel parameters]] document. = Initramfs = From noreply at ubuntu.com Mon Feb 5 16:38:14 2018 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 05 Feb 2018 16:38:14 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelBoot=22_by_penalv?= =?utf-8?q?ch?= Message-ID: <20180205163814.22695.66807@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelBoot" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKernelBoot?action=diff&rev1=17&rev2=18 Comment: RM'd "instructions before instructions" as redundant, and confusing. = Boot Options = - When trying to capture relevant error messages that appear at boot it is often useful to boot with the '''quiet''' and '''splash''' options removed. This will hopefully allow you to see any messages that come across your screen. To edit boot option parameters, do the following: + When trying to capture relevant error messages that appear at boot, one may edit boot option parameters via: 1. Boot the machine. 1. During the BIOS screen, press the shift key and hold it down. You should see the GRUB menu after the BIOS loads. @@ -18, +18 @@ set gfxpayload=text}}} 1. Press 'Ctrl+x' to boot. - It's best if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand. + It's best if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a video will work just as well. As a last resort you can even copy messages down by hand. Depending on the type of error messages you encounter, there are other boot options you could try. For example, if you notice ACPI errors, try booting with the '''acpi=off''' boot option. For a full description of these options, refer to the [[https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html|kernel parameters]] document. From noreply at ubuntu.com Mon Feb 5 16:49:49 2018 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 05 Feb 2018 16:49:49 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelBoot=22_by_penalv?= =?utf-8?q?ch?= Message-ID: <20180205164949.23904.92424@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelBoot" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKernelBoot?action=diff&rev1=18&rev2=19 Comment: Due to LP#1746357 provide clarity on when initramfs applies for debugging. Depending on the type of error messages you encounter, there are other boot options you could try. For example, if you notice ACPI errors, try booting with the '''acpi=off''' boot option. For a full description of these options, refer to the [[https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html|kernel parameters]] document. - = Initramfs = + = Dropped into a initramfs shell = - Sometimes you may even be dropped into an initramfs shell. This indicates errors in the boot sequence, for example failing to find your root partition/filesystem. You are put into the initramfs shell in an effort to allow you to recover the system. Hopefully, if you boot with the '''quiet''' and '''splash''' options removed you will notice error messages before being dropped into the shell which will help debug and direct you to a solution. + If your boot is dropped into an initramfs shell, this indicates errors in the boot sequence, for example failing to find your root partition/filesystem. You are put into the initramfs shell in an effort to allow you to recover the system. Hopefully, if you boot with the '''quiet''' and '''splash''' options removed you will notice error messages before being dropped into the shell which will help debug and direct you to a solution. If you are dropped into an initramfs shell you may want to also try booting with the '''debug''' boot option. It should write a log to /tmp/initramfs.debug. You could also specify some arbitrary argument (for example '''debug=vc''') to have the output written to the console. From noreply at ubuntu.com Mon Feb 5 16:56:00 2018 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 05 Feb 2018 16:56:00 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelBoot=22_by_penalv?= =?utf-8?q?ch?= Message-ID: <20180205165600.23914.66033@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelBoot" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKernelBoot?action=diff&rev1=19&rev2=20 Comment: Due to LP#1746357 explicitly define boot looping/halt for clarity. + = Introduction = + Unfortunately it is sometimes the case that your system will fail to boot due to changes within the kernel. It is important that when submitting bug reports about these types of failures that you include the debugging information from a failed boot (not a working boot). This article will help gather this information to provide in your report. - = Boot Options = + = Boot debugging options = When trying to capture relevant error messages that appear at boot, one may edit boot option parameters via: @@ -22, +24 @@ Depending on the type of error messages you encounter, there are other boot options you could try. For example, if you notice ACPI errors, try booting with the '''acpi=off''' boot option. For a full description of these options, refer to the [[https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html|kernel parameters]] document. + = Boot looping or boot halts = + + If your boot immediately restarts, or halts, please utilize the boot debugging options and attach a video of this to your bug report. + = Dropped into a initramfs shell = If your boot is dropped into an initramfs shell, this indicates errors in the boot sequence, for example failing to find your root partition/filesystem. You are put into the initramfs shell in an effort to allow you to recover the system. Hopefully, if you boot with the '''quiet''' and '''splash''' options removed you will notice error messages before being dropped into the shell which will help debug and direct you to a solution. If you are dropped into an initramfs shell you may want to also try booting with the '''debug''' boot option. It should write a log to /tmp/initramfs.debug. You could also specify some arbitrary argument (for example '''debug=vc''') to have the output written to the console. - Additionally, being able to extract log files from the system would be helpful. Once dropped into an initramfs shell, you can type '''httpd'''. You should then be able to point a web browser to the IP address of the system and view the contents of the /var/log folder. + Additionally, being able to extract log files from the system would be helpful. Once dropped into an initramfs shell, you can type '''httpd'''. You should then be able to point a web browser to the IP address of the system and view the contents of the /var/log folder. There is another initramfs boot parameter which can purposely drop you into the initramfs shell during different stages of the initial boot sequence. The parameter is '''break=[option]''' where option can be: top, modules, premount, mount, bottom, or init. The default is premount if no options are specified. More information about the break= parameters can be found in "/usr/share/initramfs-tools/init" on your Ubuntu system. From noreply at ubuntu.com Mon Feb 5 21:55:10 2018 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 05 Feb 2018 21:55:10 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelBoot=22_by_penalv?= =?utf-8?q?ch?= Message-ID: <20180205215510.15873.33372@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelBoot" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKernelBoot?action=diff&rev1=20&rev2=21 Comment: Due to LP#1746357 slight chg as set wasn't visible on GRUB menu kernel entry page. quiet splash vt.handoff=7}}} - 1. On the line that reads: {{{ + 1. On the line that contains: {{{ - set gfxpayload=$linux_gfx_mode}}}replace with: {{{ + gfxpayload=$linux_gfx_mode}}}modify it to: {{{ - set gfxpayload=text}}} + gfxpayload=text}}} 1. Press 'Ctrl+x' to boot. It's best if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a video will work just as well. As a last resort you can even copy messages down by hand. From noreply at ubuntu.com Thu Feb 8 21:30:43 2018 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 08 Feb 2018 21:30:43 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelBoot=22_by_penalv?= =?utf-8?q?ch?= Message-ID: <20180208213043.9573.49723@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelBoot" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKernelBoot?action=diff&rev1=21&rev2=22 Comment: Due to LP#1743797 more clearly define message capturing methods. gfxpayload=$linux_gfx_mode}}}modify it to: {{{ gfxpayload=text}}} 1. Press 'Ctrl+x' to boot. - - It's best if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a video will work just as well. As a last resort you can even copy messages down by hand. + 1. Capture messages from the bad boot and attach to your report. In order of preference: + * The appropriate log(s) from /var/log + * Video of the bad boot via cellphone or camera recording. + * A picture of the bad boot via cellphone or camera. + * Writing it down by hand. Depending on the type of error messages you encounter, there are other boot options you could try. For example, if you notice ACPI errors, try booting with the '''acpi=off''' boot option. For a full description of these options, refer to the [[https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html|kernel parameters]] document. = Boot looping or boot halts = - If your boot immediately restarts, or halts, please utilize the boot debugging options and attach a video of this to your bug report. + If your boot immediately restarts, or halts, please utilize the boot debugging options to capture the bad boot. = Dropped into a initramfs shell = From noreply at ubuntu.com Fri Feb 9 23:41:42 2018 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 09 Feb 2018 23:41:42 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelBoot=22_by_penalv?= =?utf-8?q?ch?= Message-ID: <20180209234142.6844.329@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelBoot" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKernelBoot?action=diff&rev1=22&rev2=23 Comment: Due to LP#1743797 note don't edit recordings or logs. gfxpayload=text}}} 1. Press 'Ctrl+x' to boot. 1. Capture messages from the bad boot and attach to your report. In order of preference: - * The appropriate log(s) from /var/log - * Video of the bad boot via cellphone or camera recording. + * The appropriate log(s) in their entirety from /var/log uncompressed. + * An unedited video of the entire bad boot from start to finish via cellphone or camera recording. * A picture of the bad boot via cellphone or camera. * Writing it down by hand. From noreply at ubuntu.com Wed Feb 28 12:45:21 2018 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 28 Feb 2018 12:45:21 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProgramCrash=22_by_lane?= =?utf-8?q?y?= Message-ID: <20180228124521.7414.61444@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingProgramCrash" page has been changed by laney: http://wiki.ubuntu.com/DebuggingProgramCrash?action=diff&rev1=124&rev2=125 Comment: give full fingerprint to the ddebs signing key * Choose ''Software Sources'' or ''Repositories'' via the ''Settings'' menu, and click on the ''Third-Party Software'' tab. * Click the ''Add'' button and enter each ''deb ...'' line as above one by one and click the ''Add Source'' button (you will have to add these lines one at a time). 1. Import the debug symbol archive signing key:{{{ - sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5FDFF622 + sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 }}} 1. Then run:{{{ sudo apt-get update