-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NUC10i7FNK - nvme abort error on 33700 with kernel 5.8 #2121
Comments
Can you try to update the NUC BIOS Firmware, and try again please. |
Hi @miguelinux I updated from FNCML357.0039 to FNCML357.0045 but the error remains. Even worse... my working kernel is now gone from the boot menu... |
@miguelinux I can confirm this issue on my "SB-ROCKET-NVMe4-1TB" as well. |
To fix the issue I tried to add the kernel-lts bundle. After multiple |
I can at least confirm that version 33700 with kernel 5.8 works flawlessly on my Threadripper machine with Gigabyte GP-ASM2NE6100TTTD SSDs |
Hello, i can confirm that i started experiencing issues since i upgraded the system. I think it might be related with that specific Linux kernel they AFAIK have been working on nvme devices recently. Not sure about the specific error as i just glanced over it but it went like i was doing something, then system froze and inside terminal it started printing "Input/Output" error then on dmesg I've seen some errors regarding fs and blocks like read_inode or something like that, it usually goes to the error state after 5 min of working on random stuff like browsing internet/coding etc. |
Ah yes APST feature. I was googling for a bit online to know a little bit more about the issues, it looks like there is some bug with power management of the nvme devices? something like that. https://wiki.archlinux.org/index.php/Solid_state_drive/NVMe#Samsung_drive_errors_on_Linux_4.10 Arch linux has some mention and the effect of this bug seems to produce the same errors, but i've tried to set that param and it still happens, really not sure what is causing it, maybe i should use different values on |
This one seems to be resolved with 5.8.11-988.native on 33760 |
Issue remains :-/ |
I have similar issues with an Intel NUC10i5FNK. It boots normally, commands work fine but then trying to install a package using "sudo swupd bundle-add docker-compose" it locks up at copying files at 50%, this is the last bit of output: Error: failed to rename staged 8b3c83c5a076c81d106c422eb10178b168f63e7fbac184f1e0c462483de73d78 to final: Input/output error Error: Failed to install required files After that, every command results into "dmesg: command not found" and I need to reboot. After a reboot it is normal again until trying to install the package again. My drive is a "Kingston A2000 1000GB M.2 SSD", fsck does not show any errors, memtest86 also does not show any errors. Update: I've decided to use a different distro which runs without issues. |
Facing this issue. Environment
What was the activity?
What was observed?OS hangs and slowly deteriorates to forceful manual reboot state. Other observations
If community has any feedback (like specific version to revert) then do let me know. |
Clear Linux kernel-lts is working normally. I had this issue with kernel-native. During fresh installation chose kernel-lts as the default. |
What was observed?Performing some major I/O operations (fstrim, search files) results in performance degradation until the NVMe controller resets:
What seemed to solve the problem SO FAR
https://wiki.archlinux.org/index.php/Solid_state_drive/NVMe
Other observations
|
Now on 5.8.14-991.native with NVME and Clear Linux OS 33820 is working normally. Let me monitor for few days. |
Oops! The machine hung once this morning. I powered off forcefully and turned it on with LTS2019 kernel and it is working normally. |
I updated a system to 33930 this morning and am still seeing this issue as a reproducible system crash. bundle-adding just about any bundle will crash the entire system when the nvme storage fails. I don't think I can use the LTS kernel as the NUC I am on has an Intel wired ethernet adapter that is too new / not supported by the LTS kernel, and using a different ethernet adapter is simply not an option. Frustratingly enough, bundle-adding storage-utils to get the nvme command failed repeatedly at 50% installing files for dozens of attempts this morning, but eventually I got it installed. I'm currently running the kernel parameters listed above to try to work around the show-stoppingly broken nvme support, along with the set-feature command to try to disable the autonomous power state "feature". This is a really frustrating problem, mostly because from reading around, other distributions don't have this issue. |
I have the same issue on my laptop XPS 15 9500 with kernel 5.9.6-998.native. |
Hello again, i've been recently checking out the new kernel updates and day has come, i think the issue at least for me is fixed on Haven't noticed issues so far. |
Thanks, @Polish-Civil for the update. Would be trying the native kernel soon. |
This is to confirm that with Google Chrome running on 5.9.9-1001.native kernel is working fine. Also, the Gnome suspend or sleep mode works fine. |
Hello. This seems to be still an issue on later kernels. I am using 5.19 and have that issue from 5.19.1 to the now recent, and used by me, 5.19.11 from ubuntu 22.04 mainline. nvme nvme0: Abort status: 0x0 I have these issues after I changed from a AMD 2400G with an AM3 AGESA (on X370 chipset) before 1.0.0.6 to a AMD 5600G on a AM3 with AGESA 1.2.0.7 (on A520 chipset). NVME drive is the same. I also get an error message at bootup from the NVME: The NVME drive never breached the high temp count and shows zero errors and very little wear on SMART tests, since I use this drive for a simple "daily use" multimedia system. When the "nvme nvme0: Abort status: 0x0" / "nvme nvme0: I/O 14 QID 2 timeout, aborting" errors occur, the system hangs for a while, no I/O operations get processed for up to 30 seconds. Since this entry is from 2020 and still an issue in late 2022, is there a global fix or a planned fix for the user or planned to kernel changes? Thank you for any reply. |
Since this is the tracker for the Clear Linux distribution, it might be better to report the issue with the Ubuntu kernel to the Ubuntu bug reporting forum.... |
I totally get why my report is out of place. I really do. And since I consider myself more of a user than a tech savy person I also understand the reluctance to consider my comment a real issue. This bug is still open, if I am reading it right. The same issue on vmware/open-vm-tools#579 , also unsolved. The same issue on #2121 , also unsolved. And there is my issue on ubuntu. Three different kernels, linux brands, same issue. I thought bringing the people together who actually have the tech knowledge to get behind this issue might be helpful (but that's just me). |
Posted it on https://bugs.launchpad.net/launchpad/+bug/1991291 fyi |
Hi there,
every time I boot version 33700 with kernel 5.8.8-984 on my NUC10i7FNK I get nvme abort errors and the system freezes completely.
SSD: Intel SSDPEKNW020T8
There are no problems with kernel 5.7.19-982.native
Steps to reproduce:
sudo swupd diagnose
The text was updated successfully, but these errors were encountered: