I'm on Ubuntu 20.04, and after updating to the HWE 5.8 kernel recently I
have also been suffering my nvme drive becoming read only after a period
of time. I have now switched back to the 5.4 kernel and not suffered the
issue again.
I am on a single disk system so had to run dmesg --follow remotely
@kairhengfeng Yes this is a regression after the upgrade from 5.4 to
5.8. After the upgrade I had it multiple times and now I have switched
back to 5.4 my machine is stable again.
I do not think I can run `lspci -vv` *after* the issue happens, as my
NVMe drive goes read-only, so all commands fail
Note for me it is happening quite rapidly (sometimes after 5-10 minutes)
of high disk load. Eg the first times it happened when apt was running
update-grub and then when pip3 install was running. Then to capture the
logs above i started a `find /` and `find ~` at the same time and this
was enough t
FYI I have captured the `sudo lspci -vv` output on the kernel 5.8
*before* the issue here https://pastebin.ubuntu.com/p/GtZyTWzKTd/ it is
subtly different to the 5.4 kernel (which has not had the issue) in case
that mattered.
I was also able to reproduce the issue again by causing high disk I/O,
s
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Changed in: music-app
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1648250
T
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
As this bug is to do with bluetooth (possibly media-hub as well) and
unlikely to be due to the music-app's code, I'm going to mark it is
invalid for the music-app.
** Changed in: music-app
Status: New => In
I have been using the kernel stated in the previous comment for 9 days
now and have not had the same freeze and resume (note this doesn't mean
it has totally gone as it was random before but I am quite confident it
has), therefore I am tagging this bug with 'kernel-fixed-upstream'.
However while t
Public bug reported:
Description:Ubuntu 14.10
Release:14.10
Linux andy-Pangolin-Performance 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4
12:06:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
This has happened a few times, the UI freezes and no input works for
~30s and then something resets/
Thanks for the instructions, I have managed to install the later kernel
version and will report back if I have any freezes on this as well.
Linux andy-Pangolin-Performance 3.18.0-031800rc7-generic #201411302035
SMP Mon Dec 1 01:36:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
--
You received this b
@kaihengfeng
I have found that running the command "fio --name=basic
--directory=/path/to/empty/directory --size=1G --rw=randrw --numjobs=4
--loops=5" runs fine on linux-image-5.4.0-59-generic but when trying
with linux-image-5.8.0-36-generic it would freeze the system in the
"Laying out IO file"
OK, so using https://people.canonical.com/~kernel/info/kernel-version-
map.html that states that Ubuntu kernel 5.8.0-36.40~20.04.1 matches
mainline version 5.8.18. I have installed 5.8.18 and it fails ! So it is
not the Ubuntu patches.
Ubuntu Kernels:
linux-image-5.4.0-59-generic: PASS
linux-image
So bisecting between 5.8.18 (bad) and 5.11-rc3 (good).
The following results with the mainline kernel
v5.11-rc3/ PASS
v5.9.12/PASS
v5.9.10/PASS
v5.9.9/ MISSING
v5.9.8/ FAIL (could not boot long enough for full test)
v5.9.
And the bisect between 5.4.78 (good) and 5.8.18 (bad).
The following results with the mainline kernel
v5.8.18/FAIL
v5.8.4/ FAIL
v5.8-rc5/ FAIL
v5.8-rc1/ FAIL
v5.7.19/PASS
v5.7.18/PASS
v5.7.16/
@kaihengfeng
So v5.7 was fine and after many reboots it has been found that this
commit below introduced the issue.
Do I also need to find when the issue was resolved ? (between v5.8-rc1
and v5.9.10) or is this information enough ?
54b2fcee1db041a83b52b51752dade6090cf952f is the first bad commi
@kaihengfeng Thanks for the quick response! bug 1908555 linked there
only lists groovy as a target series, I hope that this will also be
applied to the focal HWE kernel :-)
Also I am happy to test any kernel in a -proposed channel or PPA to
confirm it fixes the issue if that helps :-)
--
You re
Thanks! I'll take a look :-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1910866
Title:
nvme drive fails after some time
Status in linux package in Ubuntu:
Confirmed
Bug descripti
@Marcelo So far it looks good :-) It passes the "fio" command test when
A/B testing between a known bad kernel and this new kernel. I will
continue running it on this machine over the weekend to ensure longer
usage doesn't have any remaining issues - but looks like it resolves the
issue so far :-D
@Kleber I have installed the focal hwe kernel from proposed (as seen
below). So far when A/B testing this kernel it is working correctly :-)
I will continue running this kernel and report any issues I have.
Also note that I have been continuously running the test kernel (from
comment 22) since las
18 matches
Mail list logo
