Summary: | Window Manager Settings | Compositor: kwin crashes and brings down the entire system. | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Alejandro Nova <alejandronova> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | kdelibs-bugs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Alejandro Nova
2015-02-20 15:54:39 UTC
consistent and reproducible kernel panic (I a word) sorry kernel panic is a kernel bug. You need to report to kernel developers radeon or fglrx? do you know that it's a kp, because you end up w/ a console (x crashes first and doesn't recover) and there's a bunch of lines indicating "kernel panic" or because of flashing keyboard lights? in the latter case you'll require tools like kdump (or distro specific kernel dumper tools) for an offline inspection. overclocked cpu or decreased memory latency or insufficient power supply on the gpu (does it have an extra power adapter?)? 1. Radeon. 2. When I experience this I can't even see that console. I see a garbled screen slowly turning into white (GPU hang). 3. No overclock, no decreased memory latency, no insufficient power supply on the GPU (it's an AMD E450 netbook) How do you deduct this is a kernel panic (by the meaning of the term)? Does the netbook even have keyboard lights to flash? I assume you cannot ping the machine (or even access it via ssh)? Please attach the output of glxinfo (just a hunch ;-) |