From: Mark Wielaard <mark@klomp.org>
To: frysk <frysk@sourceware.org>
Subject: 2.6.24.3-12.fc8 kernel on x86 breaks frysk test suite
Date: Mon, 10 Mar 2008 10:55:00 -0000 [thread overview]
Message-ID: <1205146503.3356.16.camel@dijkstra.wildebeest.org> (raw)
Hi,
Be careful upgrading your fedora kernel, at least on x86.
The way the frysk test suite does a teardown seems to play havoc with
the new kernel leading to strange kill messages and TestRunner just
completely stopping.
With 2.6.24.3-12.fc8 on x86 a make check almost always fails (x86_64
seems fine though). Downgrading to 2.6.23.15-137.fc8 makes make check
(at least in frysk-core) completely clean again. With the newer kernel
tests fail (and the TestRunner gets killed!) somewhat randomly. It is
easily reproducible through something like:
./TestRunner -r 100 frysk.proc.TestTaskTerminateObserver
Which makes things a little worse by throwing in some kills of its own.
And it always fails within a couple of rounds with as output:
frysk.sys.Errno$Einval: tkill: Invalid argument (task 0)
I filed it as bug #5902. It is somewhat nasty in that it isn't very
predictable where/when it breaks things. And I spend some time trying to
bisect patches till it occurred to me that it might have been the kernel
upgrade.
Cheers,
Mark
reply other threads:[~2008-03-10 10:55 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=1205146503.3356.16.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).