From: Andy Fiddaman <illumos@fiddaman.net>
To: developer@lists.illumos.org
Subject: Review - 16615 ena assertion failure in ena_tx_intr_work()
Date: Thu, 20 Jun 2024 17:12:16 +0000 [thread overview]
Message-ID: <20240620171216.GA20998@reaper.citrus-it.net> (raw)
Please can you review the following change? A fix for a panic we've
started seeing in AWS.
16615 ena assertion failure in ena_tx_intr_work()
https://www.illumos.org/issues/16615
https://code.illumos.org/c/illumos-gate/+/3553
Thanks,
Andy
reply other threads:[~2024-06-20 17:12 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=20240620171216.GA20998@reaper.citrus-it.net \
--to=illumos@fiddaman.net \
--cc=developer@lists.illumos.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 NNTP newsgroup(s).