Bug 706637

Created attachment 500214 [details]
File: backtrace

Thanks for your report.

consolehelper-gtk aborted because it failed to create a thread; this is most likely caused by memory exhaustion, but there might be a different cause.

The "hddtemp -q /dev/sda" command should have sent an error message to its standard error output before aborting in consolehelper-gtk.  Is the output of the command recorded?  If not, are you able to reproduce this crash and arrange for recording the output?

I assume this is related to the problems I've been having waking the computer from suspend. During this crash, I had to try and wake it 3-4 times before it finally stayed running. At the end, the KDE crash reporter had popped up about a kded4 crash. I wasn't able to file the report because the debug information wasn't complete enough. I assume consolehelper-gtk crashed due to things happening around that. Here is the part of /var/log/messages from around that time (when the system was waking up and then decided immediately to go back into suspend):

May 22 06:09:51 politemadness avahi-daemon[1306]: Registering new address record for 10.1.1.6 on eth0.IPv4.
May 22 06:09:51 politemadness dhclient[10978]: bound to 10.1.1.6 -- renewal in 841475056 seconds.
May 22 06:09:53 politemadness ntpd[1728]: Listen normally on 73 eth0 10.1.1.6 UDP 123
May 22 06:09:53 politemadness NetworkManager[1293]: <info> (eth0): device state change: 7 -> 8 (reason 0)
May 22 06:09:53 politemadness NetworkManager[1293]: <info> Policy set 'System eth0' (eth0) as default for IPv4 routing and DNS.
May 22 06:09:53 politemadness NetworkManager[1293]: <info> Activation (eth0) successful, device activated.
May 22 06:09:53 politemadness dnsmasq[2624]: reading /etc/resolv.conf
May 22 06:09:53 politemadness dnsmasq[2624]: using nameserver 10.1.1.1#53
May 22 06:09:53 politemadness NetworkManager[1293]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
May 22 06:09:53 politemadness avahi-daemon[1306]: Registering new address record for fe80::6ef0:49ff:fe48:3e0 on eth0.*.
May 22 06:09:55 politemadness ntpd[1728]: Listen normally on 74 eth0 fe80::6ef0:49ff:fe48:3e0 UDP 123
May 22 06:09:56 politemadness ntpd[1728]: 0.0.0.0 0628 08 no_sys_peer
May 22 06:10:03 politemadness dbus: [system] Rejected send message, 9 matched rules; type="method_call", sender=":1.5872" (uid=579 pid=7926 comm="/usr/bin/plasma-desktop) interface="org.freedesktop.NetworkManager" member="Sleep" error name="(unset)" requested_reply=0 destination="org.freedesktop.NetworkManager" (uid=0 pid=1293 comm="NetworkManager))
May 22 06:10:08 politemadness ntpd[1728]: 0.0.0.0 0613 03 spike_detect +1.013708 s
May 22 06:10:34 politemadness NetworkManager[1293]: <info> sleep requested (sleeping: no  enabled: yes)
May 22 06:10:34 politemadness NetworkManager[1293]: <info> sleeping or disabling...
May 22 06:10:34 politemadness NetworkManager[1293]: <info> (eth0): now unmanaged
May 22 06:10:34 politemadness NetworkManager[1293]: <info> (eth0): device state change: 8 -> 1 (reason 37)
May 22 06:10:34 politemadness NetworkManager[1293]: <info> (eth0): deactivating device (reason: 37).
May 22 06:10:34 politemadness NetworkManager[1293]: <info> (eth0): canceled DHCP transaction, DHCP client pid 10978
May 22 06:10:34 politemadness avahi-daemon[1306]: Withdrawing address record for 10.1.1.6 on eth0.
May 22 06:10:34 politemadness avahi-daemon[1306]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.1.1.6.
May 22 06:10:34 politemadness avahi-daemon[1306]: Interface eth0.IPv4 no longer relevant for mDNS.
May 22 06:10:35 politemadness NetworkManager[1293]: <info> (eth0): cleaning up...
May 22 06:10:35 politemadness NetworkManager[1293]: <info> (eth0): taking down device.
May 22 06:10:35 politemadness avahi-daemon[1306]: Withdrawing address record for fe80::6ef0:49ff:fe48:3e0 on eth0.
May 22 06:10:35 politemadness NetworkManager[1293]: <info> (eth0): carrier now OFF (device state 1)
May 22 06:10:37 politemadness ntpd[1728]: Deleting interface #74 eth0, fe80::6ef0:49ff:fe48:3e0#123, interface stats: received=0, sent=0, dropped=0, active_time=42 secs
May 22 06:10:37 politemadness ntpd[1728]: Deleting interface #73 eth0, 10.1.1.6#123, interface stats: received=24, sent=24, dropped=0, active_time=44 secs
May 22 06:10:37 politemadness ntpd[1728]: 192.189.54.17 interface 10.1.1.6 -> (null)
May 22 06:10:37 politemadness ntpd[1728]: 203.82.209.217 interface 10.1.1.6 -> (null)
May 22 06:10:37 politemadness ntpd[1728]: 118.107.60.254 interface 10.1.1.6 -> (null)
May 22 06:10:37 politemadness ntpd[1728]: 192.189.54.33 interface 10.1.1.6 -> (null)
May 22 06:10:46 politemadness abrt[12146]: saved core dump of pid 12013 (/usr/bin/consolehelper-gtk) to /var/spool/abrt/ccpp-1306008643-12013.new/coredump (9433088 bytes)
May 22 06:10:46 politemadness abrtd: Directory 'ccpp-1306008643-12013' creation detected
May 22 06:10:51 politemadness abrtd: can't set uid 500: Resource temporarily unavailable
May 22 06:10:53 politemadness abrtd: New crash /var/spool/abrt/ccpp-1306008643-12013, processing
May 22 06:10:53 politemadness abrtd: RunApp('/var/spool/abrt/ccpp-1306008643-12013','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
May 22 06:11:00 politemadness kernel: [1413450.134553] PM: Syncing filesystems ... done.
May 22 06:11:21 politemadness rtkit-daemon[3138]: The canary thread is apparently starving. Taking action.
May 22 06:11:21 politemadness rtkit-daemon[3138]: Demoting known real-time threads.
May 22 06:11:21 politemadness rtkit-daemon[3138]: Successfully demoted thread 891 of process 891 (/usr/bin/pulseaudio).
May 22 06:11:21 politemadness rtkit-daemon[3138]: Demoted 1 threads.
May 22 06:11:21 politemadness kernel: [1413454.655146] Freezing user space processes ... (elapsed 0.36 seconds) done.
May 22 06:11:21 politemadness kernel: [1413455.020298] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
May 22 06:11:21 politemadness kernel: [1413455.031311] Suspending console(s) (use no_console_suspend to debug)


Today, I had to try and wake the computer twice and abrt popped up with a crash in this (but again, the debug information wasn't complete)

Package:    	kdelibs-6:4.6.3-4.fc14.1
Latest Crash:	Tue 24 May 2011 06:38:09 
Command:    	/usr/bin/kded4 --nocrashhandler
Reason:     	Process /usr/bin/kded4 was killed by signal 11 (SIGSEGV)
Comment:    	None
Bug Reports:	

BFD: Warning: /var/spool/abrt/ccpp-1306183087-10874/coredump is truncated: expected core file size >= 58871808, found: 65536.
[New Thread 10874]
[New Thread 11175]
[New Thread 11172]
Failed to read a valid object file image from memory.
Core was generated by `/usr/bin/kded4 --nocrashhandler'.
Program terminated with signal 11, Segmentation fault.
#0  0x007e5424 in ?? ()

/var/log/pm-suspend.log only seems to have the latest suspend, so there are no clues there as to why it seems to be failing to wake up all the time.

I have had recent problems with suspend which I could try and log better (if I knew what I needed to set to get better debug information), but I'm not sure how I could reproduce this specific consolehelper-gtk crash since it has only happened this one time.

Thanks for the information.

> May 22 06:10:51 politemadness abrtd: can't set uid 500: Resource temporarily
unavailable

is very likely the same cause, i.e. hitting the "max user processes" limit.  In such a case it is be expected behavior for consolehelper-gtk to abort with SIGABRT.

The limit is set by e.g. (ulimit -u) or perhaps in /etc/security/limits.conf.  Please check the value of this limit (in the environment that starts hddtemp), and compare it with the number of threads running under your UID (e.g. by running (ps -e u m n | awk '$1 == 500 && $2 == "-"'|wc -l)) to see if the limit is high enough.

When I set (ulimit -u) low enough, I can reproduce a crash at the same location in consolehelper-gtk, so it is very likely the "max user processes" limit has in fact been reached.

It is possible that I'm wrong and the crash is caused by a different problem; if you can log the standard error output of hddtemp (running hddtemp causes consolehelper-gtk to run), and it reports something else than "Resource temporarily unavailable", please reopen this bug report.