Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I am seeing hundreds of these errors in syslog and dmesg:
add_thread_group: pid 1456781 partially shared with pid 1456769
proc_migrate: migrate to process 1456781 returned -22
The jobs that were started via tcsh-ll are all sleeping. The pids in the
log do not exist in /proc .
Is this a known problem? What might have caused this?
From: John Byrne <john.byrne@hp...> - 2005-04-20 18:43:00
Indraneel Majumdar wrote:
> I am seeing hundreds of these errors in syslog and dmesg:
> add_thread_group: pid 1456781 partially shared with pid 1456769
> proc_migrate: migrate to process 1456781 returned -22
> The jobs that were started via tcsh-ll are all sleeping. The pids in the
> log do not exist in /proc .
> Is this a known problem? What might have caused this?
There are various reasons SSI cannot migrate processes and have printks
so we can get diagnostics from the field. While we can move threaded
processes created by the pthread_create() call, the linux clone call is
capable of such weird and wonderful semantics, that the effort in trying
to handle them all is prohibitive; so we try to handle 99% of the cases.
What you are seeing is probably the result of some program that tries
clever things with clone() and not a bug. Maybe not, but probably.
The problem with these messages is that they are useless and annoying.
They are WARNING level messages, so syslog cannot filter them without
turning off truly important messages and they do not include the command
name so that some useful information is provided.
I will lower these messages and our other to the DEBUG level which can
be filtered easily by syslog without losing more valuable messages. I
will also add the command name to the messages.