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
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
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 stacktrac
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 n
I'll try to come up with something for ncpfs.
Trivial lock replacement will open deadlock possibility when someone reads to
page which is also mmaped from the same filesystem (like grep likes to do). BKL
with its automated release on sleep helped (or papered over) a lot here.
Petr
"Arnd Bergma
I'll try to come up with something for ncpfs.
Trivial lock replacement will open deadlock possibility when someone reads to
page which is also mmaped from the same filesystem (like grep likes to do). BKL
with its automated release on sleep helped (or papered over) a lot here.
Petr
"Arnd Bergma
