[This bugreport is somehow incomplete, since I cant access the box in question right now and just report from memory. Will post more info later.] In the last few days, I have observed twice on my office computer a sudden complete failure. While in KDE, within seconds, random programs crash. The first time, X froze (hard reset required.) The second time, I was able to switch to the text console. Syslog showed random processes crashing (also kdeinit, and login when I tried to log in on the text console), with a segv in ld-2.10. Trying CTRL-ALT-DEL for a reboot led to an oops. This is new, the box was stable for nearly a year. Barring sudden hardware failure, what could be the problem? Could it be related to the update to glibc-2.10.1-r1 ??? 90% stable amd64 system with current stable gcc. Intel Core2 with corresponding march flag. Splitedbug, MAKEOPTS="-j3", some ebuilds from sunrise. VMware modules. Some googling gave me the following links - are they related? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/455266 http://sourceware.org/ml/libc-help/2009-05/msg00070.html
Need a `emerge --info` output, and preferably also backtrace[1] [1] http://www.gentoo.org/proj/en/qa/backtraces.xml As you may have guessed, the provided information is not enough.
Just from looking at the symptoms, have you run memtest for a few hours? Sounds like a hardware failure to me
Reopening with additional info from the logs. Memtest will run tomorrow. Core dumps are not available yet, I will have them when it happens again. This is what the syslog gives: Jan 28 14:45:12 grenadine kernel: [91899.283913] console-kit-dae[3271] general protection ip:7f9e45f91fdb sp:7fffbc010260 error:0 in libglib-2.0.so.0.2000.5[7f9e45f56000+e1000] Jan 28 14:45:19 grenadine kernel: [91906.188445] dbus-daemon[5257] general protection ip:7fd02e9df993 sp:7fffe5647f60 error:0 in libc-2.10.1.so[7fd02e96c000+14f000] Jan 28 14:45:31 grenadine kernel: [91918.357008] kdeinit4[17947]: segfault at 7f3ab75e73d2 ip 00007f3ab8f933bc sp 00007fff78554620 error 4 in ld-2.10.1.so[7f3ab8f8a000+1d000] Jan 28 14:45:32 grenadine kernel: [91918.382815] kdeinit4[17948]: segfault at 7fcaeb02e3d2 ip 00007fcaec9da3bc sp 00007fffeaacd310 error 4 in ld-2.10.1.so[7fcaec9d1000+1d000] Jan 28 14:45:33 grenadine kernel: [91919.460550] plasma-desktop[17950]: segfault at 7f5c3084e3d2 ip 00007f5c31fa63bc sp 00007fffd7ed69e0 error 4 in ld-2.10.1.so[7f5c31f9d000+1d000] Jan 28 14:45:55 grenadine kernel: [91942.103064] uhci_hcd 0000:00:1a.1: release dev 2 ep81-INT, period 8, phase 4, 93 us Jan 28 14:45:55 grenadine kernel: [91942.115428] [drm] Resetting GPU Jan 28 14:46:58 grenadine kernel: [92004.413286] login[5204]: segfault at 8 ip 00007f50902e985e sp 00007fff2aa91130 error 4 in ld-2.10.1.so[7f50902df000+1d000] Jan 28 14:47:06 grenadine kernel: [92013.322605] login[17952]: segfault at 8 ip 00007f84033ce85e sp 00007fff25d89eb0 error 4 in ld-2.10.1.so[7f84033c4000+1d000] Jan 28 14:47:10 grenadine shutdown[17954]: shutting down for system reboot Jan 28 14:47:10 grenadine kernel: [92017.311702] kdeinit4[17957]: segfault at 7f11e82fe3d2 ip 00007f11e9caa3bc sp 00007ffff77fdb20 error 4 in ld-2.10.1.so[7f11e9ca1000+1d000]
Created attachment 218010 [details] output of emerge --info
memtest86+ found no problems so far
Problem seems to have disappeared. Cosmic radiation? :) Resolving as NEEDINFO
