[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48806d4c-743a-8c63-fd86-04babb149744@infradead.org>
Date: Fri, 16 Apr 2021 10:29:25 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Drew Abbott <abbotta4@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: Page BUGs
On 4/16/21 10:20 AM, Drew Abbott wrote:
> Hello,
>
> I have been troubleshooting problems with the vanilla and lts linux kernels
> for a couple of weeks now and saw this mailing list in MAINTAINERS for
> problems with mm.h; apologies if this is the wrong place to ask. I have
MAINTAINERS file says:
MEMORY MANAGEMENT
M: Andrew Morton <akpm@...ux-foundation.org>
L: linux-mm@...ck.org
S: Maintained
W: http://www.linux-mm.org
T: quilt https://ozlabs.org/~akpm/mmotm/
T: quilt https://ozlabs.org/~akpm/mmots/
T: git git://github.com/hnaz/linux-mm.git
F: include/linux/gfp.h
F: include/linux/memory_hotplug.h
F: include/linux/mm.h
F: include/linux/mmzone.h
F: include/linux/pagewalk.h
F: include/linux/vmalloc.h
F: mm/
so linux-mm@...ck.org would be better IMO.
> been experiencing many freezes and panics with this hardware:
> https://pcpartpicker.com/user/Abbott/saved/#view=wXdgt6
> Originally[0], many of the traces referred to cpu idling funcs that seem to
> be addressed already[1][2], but now all of the traces refer to problems
> with paging[3][4][5][6]. I normally mount a mergerfs filesystem at boot
> that I thought was causing the panics[7], but I have since removed that
> entry from fstab and can still see paging bugs without that fs (or any
> other FUSE fs) mounted[7].
> What can I do to keep my computer from freezing and panicking?
>
> Thank you,
> Drew Abbott
>
> [0] https://bbs.archlinux.org/viewtopic.php?id=259571
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=212087
> [2] https://bugzilla.kernel.org/show_bug.cgi?id=212543
> [3] https://imgur.com/HT4F7p7
> [4] https://imgur.com/pTb4Miu
> [5] https://imgur.com/pTb4Miu
> [6] https://imgur.com/JVueE3m
> [7] http://0x0.st/-ATM.log
[7] tells me:
SyntaxError: JSON.parse: unexpected non-whitespace character after JSON data at line 1 column 16 of the JSON data
--
~Randy
Powered by blists - more mailing lists