Errors:

Thu 21 Feb 2008 05:54:17 AM PST|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
Thu 21 Feb 2008 05:54:17 AM PST||Rescheduling CPU: start failed
Thu 21 Feb 2008 05:54:17 AM PST|SETI@home|Unexpected state 7 for task 11dc06af.32510.17250.3.7.192_0
Thu 21 Feb 2008 05:54:18 AM PST|SETI@home|Computation for task 11dc06af.32510.17250.3.7.192_0 finished
Thu 21 Feb 2008 05:55:17 AM PST|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
Thu 21 Feb 2008 05:55:17 AM PST|SETI@home|Reason: To fetch work
Thu 21 Feb 2008 05:55:17 AM PST|SETI@home|Requesting 864 seconds of new work, and reporting 1 completed tasks
Thu 21 Feb 2008 05:55:22 AM PST|SETI@home|Scheduler request succeeded
Thu 21 Feb 2008 05:55:24 AM PST|SETI@home|Started download of file 29no06af.5932.16432.11.7.167
Thu 21 Feb 2008 05:55:27 AM PST|SETI@home|Finished download of file 29no06af.5932.16432.11.7.167
Thu 21 Feb 2008 05:55:27 AM PST|SETI@home|Throughput 365487 bytes/sec
Thu 21 Feb 2008 05:55:28 AM PST||Rescheduling CPU: files downloaded
Thu 21 Feb 2008 05:55:28 AM PST|SETI@home|Can't create shared memory: system shmget
Thu 21 Feb 2008 05:55:28 AM PST|SETI@home|Unrecoverable error for result 29no06af.5932.16432.11.7.167_0 (Couldn't start or resume: -144)
Thu 21 Feb 2008 05:55:28 AM PST|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
Thu 21 Feb 2008 05:55:28 AM PST||Rescheduling CPU: start failed

I didn't find previous questions about the errors "Rescheduling CPU: start failed" & "Unexpected state 7 for task" anywhere. The shmget error has been discussed quite a bit, but only in the context of MacOS. Shouldn't Linux be looking for uswusp/swap partition? I have a feeling this is a n00b question, directly caused by my first kernel build, but I am stumped. No other apps seem to be having trouble allocating memory, so I don't know where to start looking. Thanks for any clues.

---

Make sure this line is somewhere in your /etc/fstab file:
tmpfs /dev/shm tmpfs defaults 0 0

Then, try this as root:
mount /dev/shm

If it fails, then go back to stock kernel or rebuild with shared memory support.

Make sure this line is somewhere in your /etc/fstab file:
tmpfs /dev/shm tmpfs defaults 0 0

Then, try this as root:
mount /dev/shm

If it fails, then go back to stock kernel or rebuild with shared memory support.

Thank you. In just a minute I'll see whether editing fstab does the trick ...

---

Make sure this line is somewhere in your /etc/fstab file:
tmpfs /dev/shm tmpfs defaults 0 0

Then, try this as root:
mount /dev/shm

If it fails, then go back to stock kernel or rebuild with shared memory support.

I'm not sure. I forgot to mention that after 49 pings to the SETI server, they shut me out for 24 hours, so I'll have to wait until tomorrow to be absolutely certain. But, /dev/shm mounted OK, so I'm hopeful. Thanks!

---

problem solved; close thread

I don't want to bore you with a lot of details, but I will say it's a wonder I was able to compile that kernel at all without libcorelinux. Ha! No wonder I didn't find a lot of records of this problem.

---