public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug record/30073] [intel Efficient-core] FAIL: gdb.btrace/exception.exp: flat (pattern 1)
Date: Thu, 16 Feb 2023 16:00:07 +0000 [thread overview]
Message-ID: <bug-30073-4717-oCQchDt3f8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30073-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30073
--- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Markus Metzger from comment #9)
> It looks like a kernel issue to me. I'm discussing it with Intel kernel
> developers. This might take a bit of time.
Ack. FTR, I'm running into this with:
- openSUSE Leap 15.4 using kernel version 5.14.21, and
- openSUSE Tumbleweed using kernel version 6.1.10.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-02-16 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 9:26 [Bug record/30073] New: " vries at gcc dot gnu.org
2023-02-03 9:26 ` [Bug record/30073] " vries at gcc dot gnu.org
2023-02-03 9:28 ` vries at gcc dot gnu.org
2023-02-06 12:30 ` vries at gcc dot gnu.org
2023-02-13 18:10 ` vries at gcc dot gnu.org
2023-02-14 11:01 ` vries at gcc dot gnu.org
2023-02-16 11:16 ` markus.t.metzger at intel dot com
2023-02-16 13:32 ` vries at gcc dot gnu.org
2023-02-16 13:54 ` markus.t.metzger at intel dot com
2023-02-16 14:28 ` vries at gcc dot gnu.org
2023-02-16 14:52 ` markus.t.metzger at intel dot com
2023-02-16 16:00 ` vries at gcc dot gnu.org [this message]
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=bug-30073-4717-oCQchDt3f8@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).