Closing this per above comment. Thanks. It still seems eventually that
MTRR might be drop-able, but won't just leave this open waiting for
future.
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
It is my impression that specifying "mtrr_gran_size/mtrr_chunk_size" when
"mtrr_cleanup: can not find optimal value" is still useful on some systems.
The latest system where I helped identifying good values (according to
https://github.com/tomreyn/linux_mtrr_size_fix) was a
Gigabyte
OK, 7 years after the original report, this issue still seems relevant
on Ubuntu 20.04.
So how to know if a machine needs mtrr_cleanup at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1163587
>From my latest testing, we do currently support machines that don't have
PAT support (really old 32 bit x86). So this can be revisited at some
future point when we go 64 bit only for x86.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
My testing could not find any difference in boot time using systemd's
tools.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1163587
Title:
mtrr_cleanup: can not find optimal value, perhaps no longer
It seems MTRR support is being deprecated now -
http://lkml.iu.edu/hypermail/linux/kernel/1508.3/04830.html, commit
2baa891e42d84159b693eadd44f6fe1486285bdc.
Perhaps disabling MTRR (as opposed to just mtrr_cleanup) might be
considered for xenial? I believe it may affect boot time when the
Is there a good way to identify a machine that is helped by having this
on? I'm curious as to what kind of hardware requires mtrr_cleanup to
perform well.
The 128 GB RAM Machine, did result in some RAM lost, but it wasn't
significant considering it has 128 GB of RAM (around 128 MB loss if
This was enabled because many machines do not have spance for an MTRR
for the AGP Gart space. Without one we are unable to switch the
graphics display memory into Write Combining mode with a serious
performance hit. The errors in your case seem to be benign as I assume
you have sufficient space
Marked it as kernel-bug-exists-upstream, but I should point out that it
could be fixed by simply disabling mtrr_cleanup in the kernel build
(so it might be an Ubuntu config choice?).
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.9 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
If this bug is fixed in the
10 matches
Mail list logo
