From: "Theodore Ts'o" <tytso@mit.edu>
To: Drew Abbott <abbotta4@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: Page BUGs
Date: Fri, 16 Apr 2021 16:32:49 -0400 [thread overview]
Message-ID: <YHn0cYYXcZI1xPV6@mit.edu> (raw)
In-Reply-To: <CALY-g87oRuOGPiOEyFHFgc-TjbTvUEvrRZbGRbf19+MqcderGg@mail.gmail.com>
I'd suggest you take a look at:
https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html
and after following the self-service debugging steps, follow up by
send a report with the information suggested in the above guide.
Cheers,
- Ted
On Fri, Apr 16, 2021 at 01:54:21PM -0400, Drew Abbott wrote:
> Hello,
>
> I have been troubleshooting problems with the vanilla and lts linux kernels
> for a couple of weeks now and was referred to this mailing list from
> MAINTAINERS for
> problems with mm.h; apologies if this is the wrong place to ask. I have
> 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] https://paste.linux.community/view/raw/86e25348
>
prev parent reply other threads:[~2021-04-16 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 17:54 Drew Abbott
2021-04-16 20:32 ` Theodore Ts'o [this message]
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=YHn0cYYXcZI1xPV6@mit.edu \
--to=tytso@mit.edu \
--cc=abbotta4@gmail.com \
--cc=linux-mm@kvack.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