The nightly LTP test against the 2.5 kernel bk tree last night turned up
some test failures we don't normally see. These failures did not show
up in the run from the previous night.
execve06 0 INFO : Test FAILED
getpgid01 0 INFO : getpgid01 FAILED
mprotect03 1 FAIL : child returned unexpected status
All three are showing warnings that look like this before the failure:
mprotect03 0 WARN : signal() failed for signal 41. error:22
Invalid argument.
mprotect03 0 WARN : signal() failed for signal 51. error:22
Invalid argument.
The beginning changeset was:
ChangeSet@1.632, 2002-09-08 08:23:34-07:00, ink@jurassic.park.msu.ru
[PATCH] pci bus resources, transparent bridges
The ending changeset was:
ChangeSet@1.641, 2002-09-08 20:04:56-07:00, mingo@elte.hu
[PATCH] Re: pinpointed: PANIC caused by dequeue_signal() in current
Linus
Any ideas on what may be causing this?
Thanks,
Paul Larson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Sep 15 2002 - 22:00:18 EST