From: Mark Wielaard <mark@klomp.org>
To: frysk@sourceware.org
Subject: Kernel 2.6.19-1.2911.fc6
Date: Thu, 15 Feb 2007 10:24:00 -0000 [thread overview]
Message-ID: <1171535064.3613.40.camel@dijkstra.wildebeest.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
I saw a new kernel for FC6, so I did a quick install and test on my
x86_64 (SMP) box. With 2.6.19-1.2911.fc6 we have the following failures
in frysk-imports/tests
FAIL: frysk3491/x-state
According to http://sourceware.org/bugzilla/show_bug.cgi?id=3491:
"So the kernel test needs adjusting, and a lot more comments, and the
correspnding testTerm might need a re-think."
FAIL: frysk3595/detach-multi-thread
http://sourceware.org/bugzilla/show_bug.cgi?id=3595 says RESOLVED/FIXED,
but if it is then the fix never made it to the upstream Fedora kernel.
FAIL: frysk3997/ptrace_step_sig
Pushed upstream as
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=227693
which says:
Happens on vanilla 2.6.18.6 from kernel.org, too
Does not happen on 2.6.16.35
Since we confirmed it also on 2.6.19 this seems to be a long term regression.
Note that it might be less severe than it looks since this is only when
stepping through a SIGTRAP handler, but there are real programs that
install those themselves and don't like them being reset by a
ptrace-step (and it makes debugging a pain!)
There is also a spurious kernel message seen:
Message from syslogd@dijkstra at Thu Feb 15 11:00:39 2007 ...
dijkstra kernel: invalid opcode: 0000 [1] SMP
PASS: process/single_exec
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-02-15 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 10:24 Mark Wielaard [this message]
2007-02-15 10:29 ` Roland McGrath
2007-02-15 10:33 ` Mark Wielaard
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=1171535064.3613.40.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).