LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (http://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Multiple KDE application crashes (signal 11, SIGSEV) in MEPIS and Kubuntu (http://www.linuxquestions.org/questions/linux-newbie-8/multiple-kde-application-crashes-signal-11-sigsev-in-mepis-and-kubuntu-656421/)

adasiak 07-17-2008 12:51 PM

Multiple KDE application crashes (signal 11, SIGSEV) in MEPIS and Kubuntu
 
(This may belong under Hardware, but I won't assume.)

I'm getting repeated application crashes for (it seems) just about everything I run in KDE, on MEPIS 7.0: "[This application] caused the signal 11 (SIGSEV)." It has happened for kmix, korgac, ksmserver, kicker, artsd, kpackage, kiouiserver, klipper, kded, knotify, adept, and guidance-power-manager.py.

In the desperate hope that I could get a desktop that functioned for more than a few minutes, I installed Kubuntu 8.04 (Hardy). (I am now triple-booting MEPIS, Kubuntu, and Windows XP.) But the crashes are there, too. This makes me think it's related to the hardware.

I recently had new processor, graphics card, motherboard, RAM, and power supply installed. For some reason (I think because MEPIS wouldn't recognize my ethernet port), I re-installed MEPIS, found the kernel/driver patch (see here), and got it working -- sort of. Soon, apps started failing; even X re-started (and still does).

Nothing seems to be crashing at the terminal login (tty0), though I don't run a lot of apps there. But running command-line apps (like apt-get) through Konsole does (or can) cause a crash.

The output of lspci (from MEPIS, not Kubuntu) is:
Code:

00:00.0 Host bridge: Intel Corporation Unknown device 29c0 (rev 02)
00:01.0 PCI bridge: Intel Corporation Unknown device 29c1 (rev 02)
00:03.0 Communication controller: Intel Corporation Unknown device 29c4 (rev 02)
00:19.0 Ethernet controller: Intel Corporation Unknown device 294c (rev 02)
00:1a.0 USB Controller: Intel Corporation Unknown device 2937 (rev 02)
00:1a.1 USB Controller: Intel Corporation Unknown device 2938 (rev 02)
00:1a.2 USB Controller: Intel Corporation Unknown device 2939 (rev 02)
00:1a.7 USB Controller: Intel Corporation Unknown device 293c (rev 02)
00:1b.0 Audio device: Intel Corporation Unknown device 293e (rev 02)
00:1c.0 PCI bridge: Intel Corporation Unknown device 2940 (rev 02)
00:1c.1 PCI bridge: Intel Corporation Unknown device 2942 (rev 02)
00:1c.2 PCI bridge: Intel Corporation Unknown device 2944 (rev 02)
00:1c.3 PCI bridge: Intel Corporation Unknown device 2946 (rev 02)
00:1c.4 PCI bridge: Intel Corporation Unknown device 2948 (rev 02)
00:1d.0 USB Controller: Intel Corporation Unknown device 2934 (rev 02)
00:1d.1 USB Controller: Intel Corporation Unknown device 2935 (rev 02)
00:1d.2 USB Controller: Intel Corporation Unknown device 2936 (rev 02)
00:1d.7 USB Controller: Intel Corporation Unknown device 293a (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation Unknown device 2912 (rev 02)
00:1f.2 IDE interface: Intel Corporation Unknown device 2920 (rev 02)
00:1f.3 SMBus: Intel Corporation Unknown device 2930 (rev 02)
00:1f.5 IDE interface: Intel Corporation Unknown device 2926 (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 71c1 (rev 9e)
01:00.1 Display controller: ATI Technologies Inc Unknown device 71e1 (rev 9e)
03:00.0 IDE interface: Marvell Technology Group Ltd. Unknown device 6101 (rev b2)
07:01.0 Mass storage controller: Promise Technology, Inc. 20269 (rev 02)
07:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)

I'll be grateful for any suggestions about where to start checking.

pusrob 07-18-2008 06:20 AM

Well, I think you need to check your RAM first. I had a problem not long time ago, when my RAM was detected correctly during system startup, but when I booted an OS, they kept crashing. Than I checked my RAM with Memtest, and it showed, that there were many read-write errors. I replaced the bad RAM module, and everything is fine since then.
The conclusion is: your RAM can be bad, even when the basic system check (by BIOS) during startup says that its good.


All times are GMT -5. The time now is 09:44 PM.