From: Paul Larson <plars@austin.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: New failures in nightly LTP test
Date: 09 Sep 2002 14:22:55 -0500 [thread overview]
Message-ID: <1031599375.30394.43.camel@plars.austin.ibm.com> (raw)
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
reply other threads:[~2002-09-09 19:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1031599375.30394.43.camel@plars.austin.ibm.com \
--to=plars@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®