|
Size: 1185
Comment: imported from the old wiki
|
Size: 1371
Comment: recovery mode
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = DebuggingSystemCrash = | * If your system crashes at random intervals, perform a MemoryTest '''first''' before filing any bug reports or support requests |
| Line 3: | Line 3: |
| If your system crashes at random intervals, perform a memory test by pressing `Escape` at the prompt when the system is booting, and selecting the "memory test" option. | * If your system crashes when a particular action occurs, and this is repeatable every time, try the following steps: |
| Line 5: | Line 5: |
| If your system crashes when a particular action occurs, and this is repeatable every time, try the following steps: | 1. Try to reproduce the crash on a text console (`Control`+`Alt`+`F1`) if possible. If the crash occurs during startup, select the `recovery mode` option to disable the splash screen 1. When the crash occurs, press `Alt+SysRq+1` followed by `Alt+SysRq+t`. If using a text console, you should see a trace dumped to the screen. If the system is sufficiently alive, it will also be logged to `/var/log/kern.log` and visible in the output from `dmesg`. This information shows where the crash occurred, and should be included in any problem reports. If the output is not saved in any file, or the system is so bad off that you cannot retrieve it, you can either take a digital photo, or hand write the results. Almost all of the output is important (so please don't copy the one line you think is important, because context means everything). |
| Line 7: | Line 8: |
| * Try to reproduce the crash on a text console (`Control`+`Alt`+`F1`) if possible * When the crash occurs, press `Alt+SysRq+1` followed by `Alt+SysRq+t`. If using a text console, you should see a trace dumped to the screen. If the system is sufficiently alive, it will also be logged to `/var/log/kern.log` and visible in the output from `dmesg`. This information shows where the crash occurred, and should be included in any problem reports |
= Comments = |
| Line 10: | Line 10: |
| * AnthonyBarker: I would recommend entering the Bios and changing the settings to default/fail safe. After troubleshooting strange video crashes on my computer for 2 weeks it turned out it was the AGP settings in the BIOS. | |
| Line 11: | Line 12: |
| From AnthonyBarker Tue Feb 22 04:33:22 +0000 2005 From: Anthony Barker Date: Tue, 22 Feb 2005 04:33:22 +0000 Subject: Bios configuration Message-ID: <20050222043322+0000@https://www.ubuntulinux.org> I would recommend entering the Bios and changing the settings to default/fail safe. After troubleshooting strange video crashes on my computer for 2 weeks it turned out it was the AGP settings in the BIOS. |
CategoryDocumentation |
If your system crashes at random intervals, perform a MemoryTest first before filing any bug reports or support requests
- If your system crashes when a particular action occurs, and this is repeatable every time, try the following steps:
Try to reproduce the crash on a text console (Control+Alt+F1) if possible. If the crash occurs during startup, select the recovery mode option to disable the splash screen
When the crash occurs, press Alt+SysRq+1 followed by Alt+SysRq+t. If using a text console, you should see a trace dumped to the screen. If the system is sufficiently alive, it will also be logged to /var/log/kern.log and visible in the output from dmesg. This information shows where the crash occurred, and should be included in any problem reports. If the output is not saved in any file, or the system is so bad off that you cannot retrieve it, you can either take a digital photo, or hand write the results. Almost all of the output is important (so please don't copy the one line you think is important, because context means everything).
Comments
AnthonyBarker: I would recommend entering the Bios and changing the settings to default/fail safe. After troubleshooting strange video crashes on my computer for 2 weeks it turned out it was the AGP settings in the BIOS.