Bug 344389

Summary: Window Manager Settings | Compositor: kwin crashes and brings down the entire system.
Product: [Plasma] kwin Reporter: Alejandro Nova <alejandronova>
Component: generalAssignee: 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
This is a really nasty crash I'm experiencing with my Evergreen (r600) video chipset, and some configurations. When I open that dialog, and change some settings that force the compositor to restart (VSync, suspend composition), the whole system crashes and the kernel panics.

Please, help me with instructions to debug this, because I don't know what to do in case of a consistent and kernel panic, so I don't know how to file a consistent bug report in the kernel bugzilla.

Reproducible: Always

Steps to Reproduce:
1. Open Window Manager Settings, switch to "Compositor" tab
2. Change VSync from Automatic to None
3. Press "Apply"

Actual Results:  
Compositor restarts, and I get a full kernel panic.

Expected Results:  
Compositor restarts, with the new options.

I really KNOW that the bug is elsewhere. However, KWin is the trigger.
Comment 1 Alejandro Nova 2015-02-20 15:55:34 UTC
consistent and reproducible kernel panic

(I a word)
Comment 2 Martin Flöser 2015-02-21 08:09:41 UTC
sorry kernel panic is a kernel bug. You need to report to kernel developers
Comment 3 Thomas Lübking 2015-02-21 12:23:00 UTC
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?)?
Comment 4 Alejandro Nova 2015-02-21 18:04:11 UTC
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)
Comment 5 Thomas Lübking 2015-02-21 20:20:39 UTC
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 ;-)