From: Sebastian Andrzej Siewior <bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
To: Vinod Adhikary <vinadhy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] iommu/amd: Use raw_cpu_ptr() instead of get_cpu_ptr() for ->flush_queue
Date: Thu, 21 Sep 2017 17:10:40 +0200 [thread overview]
Message-ID: <20170921151040.szekdgibvojrdzhf@linutronix.de> (raw)
In-Reply-To: <CABp9dQUcXTAX9ggX+TAMHE2oH0SF8bcu47E=UYG9fgJdKBXEVg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 2017-09-11 22:22:11 [-0400], Vinod Adhikary wrote:
> Dear all,
Hi,
> Thank you for the great community support and support from Sebastian to
> provide me this patch. I wanted to send this email to inform you and
> perhaps get some information on how I could keep myself updated on updates
> in regards to linux-rt. I apologize if I'm spamming you with this email.
There is a rt-users mailing list, see
https://wiki.linuxfoundation.org/realtime/communication/mailinglists
> I noticed `Bug: Scheduling while atomic` on ahci after building 4.9 rt and
> reported the issue on oftc channel. Sebastian quickly helped me get a patch
> and my `journalctl -f` was clean without any such messages. Yesterday I
> decided to build 4.11 without the patch but I saw a whole bunch of similar
> bug logs not just on ahci but on my nic card as well among a few others.
> There were a few instances where I had to hard shutdown my machine. I
> patched 4.11 with Sebastian's patch again and so far it's been okay for
> about 24 hours and going.
It sounds like the same issue. I taking this for v4.11 RT and v4.9 will
pick it at some point.
> My concern is, how I can provide more information to resolve this issue,
> perhaps in the next release. Please let me know how I can be of help.
usually providing a backtrace like you did to the rt-usrs list is
enough.
> Thank you
Sebastian
next prev parent reply other threads:[~2017-09-21 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 10:34 [PATCH] iommu/amd: Use raw_cpu_ptr() instead of get_cpu_ptr() for ->flush_queue Sebastian Andrzej Siewior
[not found] ` <20170906103459.oi2nn7jondjqdo5m-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2017-09-12 2:22 ` Vinod Adhikary
[not found] ` <CABp9dQUcXTAX9ggX+TAMHE2oH0SF8bcu47E=UYG9fgJdKBXEVg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-21 15:10 ` Sebastian Andrzej Siewior [this message]
2017-09-19 9:41 ` Joerg Roedel
2017-09-21 15:21 ` [PATCH v2] iommu/iova: Use raw_cpu_ptr() instead of get_cpu_ptr() for ->fq Sebastian Andrzej Siewior
2017-11-02 17:33 ` Sebastian Andrzej Siewior
[not found] ` <20171102173349.btd3b2xfklcfopmz-E0PNVn5OA6ohrxcnuTQ+TQ@public.gmane.org>
2017-11-06 15:43 ` Alex Williamson
[not found] ` <20171106084334.639512ea-1yVPhWWZRC1BDLzU/O5InQ@public.gmane.org>
2017-11-06 16:45 ` Robin Murphy
[not found] ` <5653117e-7708-de28-f349-ffe5ebf4481d-5wv7dgnIgG8@public.gmane.org>
2017-11-06 20:07 ` Alex Williamson
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=20170921151040.szekdgibvojrdzhf@linutronix.de \
--to=bigeasy-hfztesqfncyowbw4kg4ksq@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vinadhy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).