** Changed in: linux (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856603
Title:
fstrim on nvme / AMD CPU fails and produces kernel error me
(I can confirm that the new kernel fixes the original problem.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856603
Title:
fstrim on nvme / AMD CPU fails and produces kernel error messages
To man
Thank you all for your help, especially @connork, who stepped me through
building the custom kernel and shepherded this bug report through its
early days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
This bug was fixed in the package linux - 4.15.0-88.88
---
linux (4.15.0-88.88) bionic; urgency=medium
* bionic/linux: 4.15.0-88.88 -proposed tracker (LP: #1862824)
* Segmentation fault (kernel oops) with memory-hotplug in
ubuntu_kernel_selftests on Bionic kernel (LP: #186231
This bug was fixed in the package linux - 5.3.0-40.32
---
linux (5.3.0-40.32) eoan; urgency=medium
* eoan/linux: 5.3.0-40.32 -proposed tracker (LP: #1861214)
* No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered' after
modprobe sof (LP: #1860248)
- ASoC:
Thank you. I've been using the patch since late December with no issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856603
Title:
fstrim on nvme / AMD CPU fails and produces kernel error message
@Seth. Fair enough. I'm happy to consider the bug verified if you have
no further issues.
Thanks for reporting the bug!
** Tags removed: verification-needed-bionic verification-needed-eoan
** Tags added: verification-done-bionic verification-done-eoan
--
You received this bug notification becau
Thanks. I read that but I'm 1) on eoan, and 2) already running a custom
kernel 5.3.10+ that has this fix. 1) should be an easy substitute, but
I'm really nervous about trying to shoehorn instructions from the
section following the one you quoted into a system that's already pretty
customized (and r
Hi Seth,
The second half of the instructions explain how to go about enabling the
proposed pocket. Here is the relevant text for convenience:
---
Or you can modify the software sources manually by adding the following line to
/etc/apt/sources.list:
deb http://archive
I'm not quite sure how to go about testing this proposed kernel. The
instructions assume a GUI which I don't have. Could you point me to
steps to install the proposed kernel via CLI?
Unless the request to test this is intended for someone else, in which
case please disregard.
--
You received thi
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a
https://lists.ubuntu.com/archives/kernel-team/2020-January/106863.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856603
Title:
fstrim on nvme / AMD CPU fails and produces kernel error messages
It looks like the version of this routine is Xenial is not impacted
since it hasn't received this refactor patch which constrains the
allocation to 16 bytes: 03b5929ebb20 ("nvme: rewrite discard support").
I will remove the Xenial nomination.
** Description changed:
+ [Impact]
+
+ Discard reques
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: fstrim (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: fstrim (Ubuntu Disco)
Impor
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: fstrim (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Inval
Update: I built a 5.3.10 kernel with the patch suggested in the
infradead link (patch located at
http://git.infradead.org/nvme.git/patch/530436c45ef2e446c12538a400e465929a0b3ade?hp=400b6a7b13a3fd71cff087139ce45dd1e5fff444)
and the errors went away; fstrim is working properly:
seth@elemental:~$ sud
18 matches
Mail list logo
