From: Petr Vandrovec <petr@vandrovec.name>
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: Thu, 15 Aug 2019 12:13:21 -0700 [thread overview]
Message-ID: <0287aace-fec1-d2d1-370f-657e80477717@vandrovec.name> (raw)
In-Reply-To: <45258da8-2ce7-68c2-1ba0-84f6c0e634b1@suse.cz>
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 stacktraces of allocation and first
> freeing (assuming this is a double free).
Unfortunately -rc4 does not find any my SATA disks due to some
misunderstanding between AHCI driver and HPT642L adapter (there is no
device 07:00.1, HPT is single-function device at 07:00.0):
[ 18.003015] scsi host6: ahci
[ 18.006605] DMAR: DRHD: handling fault status reg 2
[ 18.006619] DMAR: [DMA Write] Request device [07:00.1] fault addr
fffe0000 [fault reason 02] Present bit in context entry is clear
[ 18.076616] DMAR: DRHD: handling fault status reg 102
[ 18.085910] DMAR: [DMA Write] Request device [07:00.1] fault addr
fffa0000 [fault reason 02] Present bit in context entry is clear
[ 18.100989] DMAR: DRHD: handling fault status reg 202
[ 18.110985] DMAR: [DMA Write] Request device [07:00.1] fault addr
fffe0000 [fault reason 02] Present bit in context entry is clear
With iommu=off disks are visible, but USB keyboard (and other USB
devices) does not work:
[ 18.174802] ehci-pci 0000:00:1a.0: swiotlb buffer is full (sz: 8
bytes), total 0 (slots), used 0 (slots)
[ 18.174804] ehci-pci 0000:00:1a.0: overflow 0x0000000ffdc75ae8+8 of
DMA mask ffffffff bus mask 0
[ 18.174815] WARNING: CPU: 2 PID: 508 at kernel/dma/direct.c:35
report_addr+0x2e/0x50
[ 18.174816] Modules linked in:
[ 18.174818] CPU: 2 PID: 508 Comm: kworker/2:1 Tainted: G
T 5.3.0-rc4-64-00058-gd717b092e0b2 #77
[ 18.174819] Hardware name: Dell Inc. Precision T3610/09M8Y8, BIOS A16
02/05/2018
[ 18.174822] Workqueue: usb_hub_wq hub_event
I'll try to find -rc4 configuration that has enabled debugging and can boot.
Petr
next prev parent reply other threads:[~2019-08-15 19:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-204407-27@https.bugzilla.kernel.org/>
2019-08-02 20:23 ` Andrew Morton
2019-08-02 20:33 ` Matthew Wilcox
2019-08-02 21:17 ` Qian Cai
2019-08-02 22:59 ` Matthew Wilcox
2019-08-02 23:29 ` Petr Vandrovec
2019-08-15 14:32 ` Vlastimil Babka
2019-08-15 19:13 ` Petr Vandrovec [this message]
2019-08-16 12:47 ` Vlastimil Babka
2019-08-16 12:52 ` Joerg Roedel
2019-08-17 0:20 ` Petr Vandrovec
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=0287aace-fec1-d2d1-370f-657e80477717@vandrovec.name \
--to=petr@vandrovec.name \
--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=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox