All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <jroedel@suse.de>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: David Airlie <airlied@linux.ie>,
	bugzilla-daemon@bugzilla.kernel.org,
	Matthew Wilcox <willy@infradead.org>,
	linux-mm@kvack.org, Huang Rui <ray.huang@amd.com>,
	Qian Cai <cai@lca.pw>,
	dri-devel@lists.freedesktop.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Petr Vandrovec <petr@vandrovec.name>,
	Christian Koenig <christian.koenig@amd.com>
Subject: Re: [Bug 204407] New: Bad page state in process Xorg
Date: Fri, 16 Aug 2019 14:52:07 +0200	[thread overview]
Message-ID: <20190816125207.GA23865@suse.de> (raw)
In-Reply-To: <6a45a9b1-81ad-72c4-8f06-5d2cd87278ef@suse.cz>

On Fri, Aug 16, 2019 at 02:47:53PM +0200, Vlastimil Babka wrote:
> On 8/15/19 9:13 PM, Petr Vandrovec wrote:
> > [   18.110985] DMAR: [DMA Write] Request device [07:00.1] fault addr 
> > fffe0000 [fault reason 02] Present bit in context entry is clear
> 
> Worth reporting as well, not nice regression.

Is that a regression between 5.3-rc3 and 5.3-rc4 or is it already broken
since -rc1? The 5.3-rc5 kernel will contains some VT-d fixes that are
worth a try here too. If you can test latest linus/master branch that
would be great, otherwise -rc5 is fine too.


Regards,

	Joerg
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <jroedel@suse.de>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Petr Vandrovec <petr@vandrovec.name>,
	Matthew Wilcox <willy@infradead.org>, Qian Cai <cai@lca.pw>,
	Andrew Morton <akpm@linux-foundation.org>,
	bugzilla-daemon@bugzilla.kernel.org,
	Christian Koenig <christian.koenig@amd.com>,
	Huang Rui <ray.huang@amd.com>, David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel@ffwll.ch>,
	dri-devel@lists.freedesktop.org, linux-mm@kvack.org
Subject: Re: [Bug 204407] New: Bad page state in process Xorg
Date: Fri, 16 Aug 2019 14:52:07 +0200	[thread overview]
Message-ID: <20190816125207.GA23865@suse.de> (raw)
In-Reply-To: <6a45a9b1-81ad-72c4-8f06-5d2cd87278ef@suse.cz>

On Fri, Aug 16, 2019 at 02:47:53PM +0200, Vlastimil Babka wrote:
> On 8/15/19 9:13 PM, Petr Vandrovec wrote:
> > [   18.110985] DMAR: [DMA Write] Request device [07:00.1] fault addr 
> > fffe0000 [fault reason 02] Present bit in context entry is clear
> 
> Worth reporting as well, not nice regression.

Is that a regression between 5.3-rc3 and 5.3-rc4 or is it already broken
since -rc1? The 5.3-rc5 kernel will contains some VT-d fixes that are
worth a try here too. If you can test latest linus/master branch that
would be great, otherwise -rc5 is fine too.


Regards,

	Joerg


  reply	other threads:[~2019-08-16 12:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-204407-27@https.bugzilla.kernel.org/>
2019-08-02 20:23 ` [Bug 204407] New: Bad page state in process Xorg Andrew Morton
2019-08-02 20:23   ` Andrew Morton
2019-08-02 20:33   ` Matthew Wilcox
2019-08-02 20:33     ` Matthew Wilcox
2019-08-02 21:17     ` Qian Cai
2019-08-02 21:17       ` Qian Cai
2019-08-02 22:59       ` Matthew Wilcox
2019-08-02 22:59         ` Matthew Wilcox
2019-08-02 23:29         ` Petr Vandrovec
2019-08-15 14:32           ` Vlastimil Babka
2019-08-15 14:32             ` Vlastimil Babka
2019-08-15 19:13             ` Petr Vandrovec
2019-08-15 19:13               ` Petr Vandrovec
2019-08-16 12:47               ` Vlastimil Babka
2019-08-16 12:47                 ` Vlastimil Babka
2019-08-16 12:52                 ` Joerg Roedel [this message]
2019-08-16 12:52                   ` Joerg Roedel
2019-08-17  0:20                 ` Petr Vandrovec
2019-08-17  0:20                   ` Petr Vandrovec
2019-08-19 14:44                   ` Vlastimil Babka
2019-08-19 14:44                     ` Vlastimil Babka
2019-08-02 21:25   ` Petr Vandrovec

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=20190816125207.GA23865@suse.de \
    --to=jroedel@suse.de \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cai@lca.pw \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-mm@kvack.org \
    --cc=petr@vandrovec.name \
    --cc=ray.huang@amd.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.