Re: [Bug 204407] New: Bad page state in process Xorg

On 8/17/19 2:20 AM, Petr Vandrovec wrote: > Vlastimil Babka wrote on 8/16/2019 5:47 AM: >> On 8/15/19 9:13 PM, Petr Vandrovec wrote: >>> With iommu=off disks are visible, but USB keyboard (and other USB >>> devices) does not work: >> >> I've been told iommu=soft might help. > > Thanks. I've

Re: [Bug 204407] New: Bad page state in process Xorg

Vlastimil Babka wrote on 8/16/2019 5:47 AM: On 8/15/19 9:13 PM, Petr Vandrovec wrote: With iommu=off disks are visible, but USB keyboard (and other USB devices) does not work: I've been told iommu=soft might help. Thanks. I've rebuilt kernel without IOMMU. Unfortunately I was not able to

Re: [Bug 204407] New: Bad page state in process Xorg

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 > > fffe [fault reason 02] Present bit in context entry is clear > > Worth reporting as well, not nice

Re: [Bug 204407] New: Bad page state in process Xorg

Vlastimil Babka wrote on 8/15/2019 7:32 AM: Does the issue still happen with rc4? Could you apply the 3 attached patches (work in progress), configure-enable CONFIG_DEBUG_PAGEALLOC and CONFIG_PAGE_OWNER and boot kernel with debug_pagealloc=on page_owner=on parameters? That should print 

Re: [Bug 204407] New: Bad page state in process Xorg

On 8/15/19 9:13 PM, Petr Vandrovec wrote: > Vlastimil Babka wrote on 8/15/2019 7:32 AM: >> >> Does the issue still happen with rc4? Could you apply the 3 attached >> patches (work in progress), configure-enable CONFIG_DEBUG_PAGEALLOC and >> CONFIG_PAGE_OWNER and boot kernel with debug_pagealloc=on 

Re: [Bug 204407] New: Bad page state in process Xorg

On 8/3/19 1:29 AM, Petr Vandrovec wrote: > On Fri, Aug 2, 2019, 3:59 PM Matthew Wilcox > wrote: > > That doesn't help because we call reset_page_owner() in the free > page path. > > We could turn on tracing because we call trace_mm_page_free() in this >

Re: [Bug 204407] New: Bad page state in process Xorg

On Fri, Aug 2, 2019, 3:59 PM Matthew Wilcox wrote: > That doesn't help because we call reset_page_owner() in the free page path. > > We could turn on tracing because we call trace_mm_page_free() in this > path. That requires the reporter to be able to reproduce the problem, > and it's not clear

Re: [Bug 204407] New: Bad page state in process Xorg

Andrew Morton wrote on 8/2/2019 1:23 PM: (switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Thu, 01 Aug 2019 22:34:16 + bugzilla-dae...@bugzilla.kernel.org wrote: [259701.549382] Code: 10 e9 67 ff ff ff 0f 1f 44 00 00 48 8b 15 b1 6c 0c 00

Re: [Bug 204407] New: Bad page state in process Xorg

On Fri, Aug 02, 2019 at 05:17:30PM -0400, Qian Cai wrote: > On Fri, 2019-08-02 at 13:33 -0700, Matthew Wilcox wrote: > > It occurs to me that when a page is freed, we could record some useful bits > > of information in the page from the stack trace to help debug double-free  > > situations.  Even

Re: [Bug 204407] New: Bad page state in process Xorg

On Fri, 2019-08-02 at 13:33 -0700, Matthew Wilcox wrote: > On Fri, Aug 02, 2019 at 01:23:06PM -0700, Andrew Morton wrote: > > > [259701.387365] BUG: Bad page state in process Xorg  pfn:2a300 > > > [259701.393593] page:eaa8c000 refcount:0 mapcount:-128 > > > mapping:

Re: [Bug 204407] New: Bad page state in process Xorg

On Fri, Aug 02, 2019 at 01:23:06PM -0700, Andrew Morton wrote: > > [259701.387365] BUG: Bad page state in process Xorg pfn:2a300 > > [259701.393593] page:eaa8c000 refcount:0 mapcount:-128 > > mapping: index:0x0 mapcount -128 is PAGE_MAPCOUNT_RESERVE, aka PageBuddy. I

Re: [Bug 204407] New: Bad page state in process Xorg

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Thu, 01 Aug 2019 22:34:16 + bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204407 > > Bug ID: 204407 >Summary: Bad page