[lkml]   [2002]   [Sep]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectNew failures in nightly LTP test
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,
[PATCH] pci bus resources, transparent bridges

The ending changeset was:
ChangeSet@1.641, 2002-09-08 20:04:56-07:00,
[PATCH] Re: pinpointed: PANIC caused by dequeue_signal() in current

Any ideas on what may be causing this?

Paul Larson

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.085 / U:0.524 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site