From: Randy Dunlap <rdunlap@infradead.org>
To: Drew Abbott <abbotta4@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Page BUGs
Date: Fri, 16 Apr 2021 10:31:12 -0700 [thread overview]
Message-ID: <e39e346d-6d4c-f265-67ca-736d51f16266@infradead.org> (raw)
In-Reply-To: <48806d4c-743a-8c63-fd86-04babb149744@infradead.org>
On 4/16/21 10:29 AM, Randy Dunlap wrote:
> 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@linux-foundation.org>
> L: linux-mm@kvack.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@kvack.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
That was on Firefox.
Opera can display it successfully.
--
~Randy
next prev parent reply other threads:[~2021-04-16 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 17:20 Page BUGs Drew Abbott
2021-04-16 17:29 ` Randy Dunlap
2021-04-16 17:31 ` Randy Dunlap [this message]
2021-04-16 17:44 ` Drew Abbott
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=e39e346d-6d4c-f265-67ca-736d51f16266@infradead.org \
--to=rdunlap@infradead.org \
--cc=abbotta4@gmail.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).