![]() ![]() It's best to have a single bug report per specific problem.įor similar reasons, choose a title that is specific and descriptive. A bug report involving dozens of different actual problems is just confusing and noisy for everyone involved. ![]() The reason is that every GPU lockup bug has the exact same symptom so it's impossible for a layman to tell the difference. It's best to file a new bug report rather than joining onto someone else's. But for bug reporting purposes in Ubuntu, to keep things simple we just lump them together and treat them as X bugs, until we have patches in hand. Often with the open source drivers (-intel, -ati, and -nouveau) the bug requires fixed in the kernel's drm drivers or in mesa's GLX drivers, thus many "X freeze" bugs technically are actually kernel or mesa bugs. Typically the source of the error is the handling of memory or command registers, graphics state, or other parameters of the hardware that the driver is responsible for. GPU lockups are always handled as driver-specific bugs. Knowing which of these three classes your bug fits in can provide a clue, as different types of driver errors can lead to the different classes. Still others are seemingly random and impossible to tie to any definite set of preconditions. Others are situational and "tend" to occur with certain programs loaded, certain load levels, or certain periods of time passing. Some GPU lockups are triggerable and easily reproduced. In some cases the driver can trigger a reset from software and the user might notice only a brief glitchiness (or maybe nothing at all), but in other cases it cannot and the graphics system remains in its bad state. If the video driver gives bad data to the GPU, the GPU can get stuck and must be reset. It has memory structures and registers which it uses to produce graphical effects. The Graphical Processor Unit (GPU) is a hardware component on the video card or integrated into the CPU. Screen still updates (look at clock), but can't be interacted with - could be an input bug, not a GPU freeze.This usually indicates a client application is making too many X requests (See X/Troubleshooting/HighCPU). X CPU or memory load is high, making system laggy or freeze up. The caps lock key blinks - this indicates a kernel failure, not X.X seems to be working, but the monitor appears to just be "off" (See X/Troubleshooting/BlankScreen instead) X crashes and returns you to the login screen - most of the time this indicates a crash, not a freeze. You can ping the machine and SSH into it remotelyĮrror messages such as "GPU lockup" are (sometimes) present in your dmesg output.Often, X cannot be killed from the console or if it can, it won't restart properly only a reboot clears the state.Sometimes there is screen corruption too, sometimes the screen goes black. The screen displays but does not update.X stops responding to input (sometimes mouse cursor can still move, but clicking has no effect).Problem: Freeze began after a system update.Problem: Freezes when screensaver or video player changes DPMS settings.Register Dumps for -ati (pre-r5xx chips).Register Dumps for -ati (r5xx and newer chips).
0 Comments
Leave a Reply. |