https://bugzilla.novell.com/show_bug.cgi?id=740407 https://bugzilla.novell.com/show_bug.cgi?id=740407#c0 Summary: RE: Signal 11 Crash with KDE Workspace Applications - Probable Solution Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: scott@aphofis.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20100101 Firefox/9.0 I have seen many bugs open that refer to Signal 11 crash and Backtrace, particularly in X_64 Hardware both KDE/Gnome, therefore please excuse my slightly unorthodox BUG Solution Entry I think I have the answer to this issue and I can faithfully reproduce a Seg Fault - Signal 11. Its a Kernel problem with 1 or 2 possibilities. It is most noticeable in X_64 Hardware with Multiple Cores and with the current Kernel Linux 2.6.37.6-0.9-desktop x86_64. The two possibilities are 1. The current transaction has exceeded its time to complete its execution BUT MOST LIKELY to be an out of Memory situation where the transaction taking place has gobbled up huge RAM resources in Cache Buffers...See the Image attached Reproducible: Always Steps to Reproduce: 1.I can faithfully reproduce the Segment Fault - Signal 11 2. 3. Actual Results: In the image attached you can see that out of 4GIG of RAM the Kernel has allocated 3.1GIG just to cache buffers and I think they are not being flushed correctly, if at all..I would look at the values for Flush of Dirty cache Buffers in the Kernel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.