From: Udo van den Heuvel <udovdh@xs4all.nl>
To: unlisted-recipients:; (no To-header on input)
Cc: "linux-mm@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 5.4+: PAGE FAULT crashes the system multiple times per 24h
Date: Tue, 11 Feb 2020 18:04:37 +0100 [thread overview]
Message-ID: <2689744f-f981-84f6-eee3-8416d3dc3b22@xs4all.nl> (raw)
In-Reply-To: <CAEJqkgjq3pd8kJSBpv4moOjdjgXiwPS6HgoD81rVAL0X-SAGew@mail.gmail.com>
On 10-02-2020 18:01, Gabriel C wrote:
> But try to boot a kernel with only what you need to boot when hunting bugs.
> As an example, if such a kernel works then you know for sure one of
> the option or a combination causes bugs.
These options are reasonable and necessary; so far things worked OK.
So why would they start being an issue?
And how can I even proceed when the kernel cannot find a rootfs anymore
while bisecting?
5.5.2 also has the page fault issue.
So why Linus does call 5.5.x 'stable' is beyond me.
How can I continue and find the root cause for the page fault hang?
> The force parameter is used to try to enable ACPI on HW has is OFF by
> default, you don't need that.
I booted 5.5.3 without acpi=force and dmesg output with `acpi` in it
looks similar.
So acpi=force wil be removed from future kernel commandlines.
>> We want to use discard on our ssd's.
>
> Use mount options?
Not enough to make it work for LUKS.
>> elevator=mq-deadline
>> We want a different scheduler for ssd versus hdd.
>
> If you really want that you should use udev rules for SSD/NVME/HDD/USB etc.
/etc/rc.d/rc.local is easier.
Look at the overhead of a service file.
Same as the overhead of NetworkManager versus a few kilobytes of
network-scripts.
But Fedora thinks otherwise....
Kind regards,
Udo
next prev parent reply other threads:[~2020-02-11 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 14:39 5.4+: PAGE FAULT crashes the system multiple times per 24h Udo van den Heuvel
2020-02-10 16:04 ` Gabriel C
2020-02-10 16:24 ` Udo van den Heuvel
2020-02-10 17:01 ` Gabriel C
2020-02-11 2:56 ` Udo van den Heuvel
2020-02-11 17:04 ` Udo van den Heuvel [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-09 8:39 Udo van den Heuvel
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=2689744f-f981-84f6-eee3-8416d3dc3b22@xs4all.nl \
--to=udovdh@xs4all.nl \
--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).