From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751922AbdIUPKr (ORCPT ); Thu, 21 Sep 2017 11:10:47 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:36278 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751890AbdIUPKp (ORCPT ); Thu, 21 Sep 2017 11:10:45 -0400 Date: Thu, 21 Sep 2017 17:10:40 +0200 From: Sebastian Andrzej Siewior To: Vinod Adhikary Cc: Joerg Roedel , iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] iommu/amd: Use raw_cpu_ptr() instead of get_cpu_ptr() for ->flush_queue Message-ID: <20170921151040.szekdgibvojrdzhf@linutronix.de> References: <20170906103459.oi2nn7jondjqdo5m@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.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