[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I just want to say that after 2 years I remembered I had an SSD with different brand tham Samsung, a Kingston one. I installed it on my razer and it worked perfectly for days, I did several SSD stress tests and no errors. The error is defintely with Samsung AND linux. And it's not a faulty SSD because it happens on both of my samsung SSDs. It does not happen on Windows, neither Qubes, with any SSD. I tested the latest Ubuntu 21.04 and the problem still happens on Samsung SSDs right on the installation screen. Anyways I'm not even using this computer anymore, I bought a Dell XPS 13, but the error persists and it's either Samsung's or Linux fault. Probably Samsung since other brands work ok with Samsung. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915747] [NEW] notebook lid open wont awake linux
Public bug reported: If I leave the notebook closed for too much time and open it, it will not wake up and I have to force reboot by pressing power. However if I simply close and open at the same minute it works. This kernel fixes the athk11 wifi, it works now but I think it might be the cause of this bug. One time I opened and the screen wouldn't power so I closed and did nothing. After some hours I noticed the notebook was hot and then I opened and ubuntu was open but with wifi service off. Dell XPS 9310 Ubuntu 20.04 5.10.0-1013-oem ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1013-oem 5.10.0-1013.14 ProcVersionSignature: Ubuntu 5.10.0-1013.14-oem 5.10.6 Uname: Linux 5.10.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 15 15:22:18 2021 InstallationDate: Installed on 2021-02-08 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915747 Title: notebook lid open wont awake linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1915747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
Any news on this driver? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879633 Title: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1879633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907724] [NEW] bluetooth wont find anything on Dell XPS 13 9310
Public bug reported: Just installed Ubuntu 20.04 on my brand new XPS 13. Bluetooth is active and it wont find anything. There is one time where it found "Audio Device" and "Unknown" but I can't even click, but in majority of times it wont find anything. I tried `bluetoothctl` with `power on`, `scan on` and etc, but it won't find anything. I don't even know which bluetooth device my Dell uses, because it won't appear on lspci or lsusb: lz@xps13:~$ lspci :00:00.0 Host bridge: Intel Corporation Device 9a14 (rev 01) :00:02.0 VGA compatible controller: Intel Corporation Device 9a49 (rev 01) :00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01) :00:06.0 System peripheral: Intel Corporation Device 09ab :00:07.0 PCI bridge: Intel Corporation Device 9a23 (rev 01) :00:07.2 PCI bridge: Intel Corporation Device 9a27 (rev 01) :00:0a.0 Signal processing controller: Intel Corporation Device 9a0d (rev 01) :00:0d.0 USB controller: Intel Corporation Device 9a13 (rev 01) :00:0d.2 USB controller: Intel Corporation Device 9a1b (rev 01) :00:0d.3 USB controller: Intel Corporation Device 9a1d (rev 01) :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller :00:12.0 Serial controller: Intel Corporation Device a0fc (rev 20) :00:14.0 USB controller: Intel Corporation Device a0ed (rev 20) :00:14.2 RAM memory: Intel Corporation Device a0ef (rev 20) :00:15.0 Serial bus controller [0c80]: Intel Corporation Device a0e8 (rev 20) :00:15.1 Serial bus controller [0c80]: Intel Corporation Device a0e9 (rev 20) :00:16.0 Communication controller: Intel Corporation Device a0e0 (rev 20) :00:19.0 Serial bus controller [0c80]: Intel Corporation Device a0c5 (rev 20) :00:19.1 Serial bus controller [0c80]: Intel Corporation Device a0c6 (rev 20) :00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) :00:1d.0 PCI bridge: Intel Corporation Device a0b3 (rev 20) :00:1e.0 Communication controller: Intel Corporation Device a0a8 (rev 20) :00:1f.0 ISA bridge: Intel Corporation Device a082 (rev 20) :00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20) :00:1f.4 SMBus: Intel Corporation Device a0a3 (rev 20) :00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a0a4 (rev 20) :55:00.0 Network controller: Qualcomm Device 1101 (rev 01) :56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card Reader (rev 01) 1:e0:06.0 PCI bridge: Intel Corporation Device 9a09 (rev 01) 1:e1:00.0 Non-Volatile memory controller: Toshiba Corporation Device 011a lz@xps13:~$ lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 0c45:672a Microdia Integrated_Webcam_HD Bus 003 Device 007: ID 22b8:2e25 Motorola PCS XT1650 Bus 003 Device 002: ID 27c6:533c Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I'm on `5.10.0-051000rc6-lowlatency` because the one that comes with ubuntu 20.04 has problems with sleep and other things. How do I know which bluetooth device I'm using? PS: I also have no wifi yet, seems like the driver for `Network controller: Qualcomm Device 1101 (rev 01)` is not ready yet. I thought that's where the bluetooth comes from, but I doubt because there's no driver for it yet. I don't know. I tried ubuntu 20.10 but I get error on installation, tried many times. But I guess the problem is more kernel related. [bluetooth]# list Controller 00:00:00:00:5A:AD xps13 [default] ** Affects: ubuntu Importance: Undecided Status: New ** Tags: bluetooth dell driver xps13 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907724 Title: bluetooth wont find anything on Dell XPS 13 9310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1907724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I also had this problem of it working for a year, then I update it and it stops working. Then I roll back the kernel and it won't work again Enviado via ProtonMail móvel Mensagem Original Ativo 7 de mar de 2020 10:17, Ramon Fontes escreveu: > I have a Dell Inspiron 14 5000 Series-5480. The most strange thing is > that I bought my laptop about 1 year ago and I've installed Ubuntu > 18.04.1 with kernel 4.15.0-65-xxx (default installation) and everything > worked as expected. However, the same problem happened with any other > kernel version (including 4.17.0-041700-generic). > > Then, after having some problems with my system I've installed Ubuntu > 18.04.4. The kernel version installed with the system was 5.3 and after > observing the same problem with the disk I've tried to install 4.15.0-65 and > the problem has not been solved (I don't remember exactly which kernel > version I had in the first time (e.g. what was the xxx)). Finally, I've found > that 4.17.0-041700-generic works and I don't know why. It didn't work with > Ubuntu 18.04.1 and it works with 18.04.4. This is really strange and I need > to use most recent kernel versions, because I need to use some features I've > implemented for v5.5-rc1. > > [1] > https://github.com/torvalds/linux/commit/b5764696ac409523414f70421c13b7e7a9309454#diff-21081ef83e1374560c2e244926168e49 > [2] > https://github.com/torvalds/linux/commit/7dfd8ac327301f302b03072066c66eb32578e940#diff-21081ef83e1374560c2e244926168e49 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1746340 > > Title: > Samsung SSD corruption (fsck needed) > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Ubuntu 4.13.0-21.24-generic 4.13.13 > > I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu > 17.04, which gave me this error after 2 weeks of usage. After that, I > installed 16.04 and used it for MONTHS without any problems, until it > produced the same error this week. I think it has to do with the ubuntu > updates, because I did one recently and one today, just before this problem. > Could be a coincidence though. > > I notice the error when I try to save something on disk and it says me > that the disk is in read-only mode: > > lz@lz:/var/log$ touch something > touch: cannot touch 'something': Read-only file system > > lz@lz:/var/log$ cat syslog > Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): > ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming > directory block 0 > > lz@lz:/var/log$ dmesg > [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.377374] Aborting journal on device nvme0n1p2-8. > [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only > [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" > operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" > capability=12 capname="net_admin" > > Rebooting the ubuntu will give me a black terminal where I can run > fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of > orphaned inodes. The majority of time it boots back to the Ubuntu > working good, but some times it boots to a broken ubuntu (no images, > lots of things broken). I have to reinstall ubuntu then. > > Every time I reinstall my Ubuntu, I have to try lots of times until it > installs without an Input/Output error. When it installs, I can use it > for some hours without having the problem, but if I run the software > updates, it ALWAYS crashes and enters in read-only mode, specifically > in the part that is installing kernel updates. > > I noticed that Ubuntu installs
Re: [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Ramon, which hardware is yours? Razer? Enviado via ProtonMail móvel Mensagem Original Ativo 6 de mar de 2020 16:34, Ramon Fontes escreveu: > BTW, pcie_aspm=off and nvme_core.default_ps_max_latency_us=5500 didn't > work. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1746340 > > Title: > Samsung SSD corruption (fsck needed) > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Ubuntu 4.13.0-21.24-generic 4.13.13 > > I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu > 17.04, which gave me this error after 2 weeks of usage. After that, I > installed 16.04 and used it for MONTHS without any problems, until it > produced the same error this week. I think it has to do with the ubuntu > updates, because I did one recently and one today, just before this problem. > Could be a coincidence though. > > I notice the error when I try to save something on disk and it says me > that the disk is in read-only mode: > > lz@lz:/var/log$ touch something > touch: cannot touch 'something': Read-only file system > > lz@lz:/var/log$ cat syslog > Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): > ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming > directory block 0 > > lz@lz:/var/log$ dmesg > [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.377374] Aborting journal on device nvme0n1p2-8. > [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only > [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode > #26607929: comm updatedb.mlocat: checksumming directory block 0 > [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" > operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" > capability=12 capname="net_admin" > > Rebooting the ubuntu will give me a black terminal where I can run > fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of > orphaned inodes. The majority of time it boots back to the Ubuntu > working good, but some times it boots to a broken ubuntu (no images, > lots of things broken). I have to reinstall ubuntu then. > > Every time I reinstall my Ubuntu, I have to try lots of times until it > installs without an Input/Output error. When it installs, I can use it > for some hours without having the problem, but if I run the software > updates, it ALWAYS crashes and enters in read-only mode, specifically > in the part that is installing kernel updates. > > I noticed that Ubuntu installs updates automatically when they're for > security reasons. Could this be the reason my Ubuntu worked for months > without the problem, but then an update was applied and it broke? > > I thought that this bug was happening: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried > different nvme_core.default_ps_max_latency_us= combinations, all them > gave errors. I just changed to 0 and I had no error while using ubuntu > (however I didn't test for a long time) but I still had the error > after trying to update my ubuntu. > > My Samsung 512gb SSD is: > > SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q > > on a Razer Blade Stealth. > > I also asked this on ask ubuntu, without success: > https://askubuntu.com/questions/998471/razer-blade-stealth-disk- > corruption-fsck-needed-probably-samsung-ssd-bug-afte > > Please help me, as I need this computer to work on lots of things :c > --- > ApportVersion: 2.20.7-0ubuntu3.7 > Architecture: amd64 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC0: lz 1088 F pulseaudio > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 17.10 > InstallationDate: Installed on 2018-01-30 (0 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) >
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Juan, which hardware you're on? Razer? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi Kai-Heng Feng, please note that after I installed Qubes, I never ever had the problem again. It may be useful in the debug process, and maybe the way Xen, PCIe and Linux work together in Qubes can give a hint on what's happening. Thank you for all your help to this day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
non nvme SSDs are pretty slow, like 8 times slower. Stick with NVME and if nothing works install Qubes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
The other 2 good brands I know are Corsair and WD Black. Don't buy Samsung, the majority of people with this problem have Samsung -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hu trong lu. I indeed bought a new SSD because I thought mine was faulty. However I bought one of the same brand (Samsung). I didn't have the idea of buying another brand. Anyways, the brand new SSD also has the problem. For my case it definitely is not a hardware problem. With Linux the problem happens every day, sometimes more than once per day. With Windows the error never happened and with Qubes I'm running for more than 2 months without any problems. So it's not hardware, definitely is something wrong with Linux kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi trong luu, I didn't test it, but I think that it depends on the way VMware virtualizes access to the disk. There may be multiple ways, one of which will work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi trong luu, for me the error happened every day, which is why I ended up using Qubes. It's the only way that I could find except for Windows You can try older kernels but it didn't work for me. Remember that downloading older ubuntus will still give you a recent kernel, you have to downgrade by yourself. However ni Ubuntu or Debian kernels fixed the problem for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi tronglx, I didn't try Arch but I THINK I tried Manjaro which is based on it. If I did it didn't work. I remember trying lots of linux and all of them failed. Qubes OS works because it doesn't use linux kernels directly because it uses Xen microkernel, so somehow it excludes the bug. You can install Arch as a Qubes VM, there's a script for it, you just run it and then it generates an image that you can install. They also provide Ubuntu, Kali and others. Since this bug is rare I don't think they'll try to fix, the guy that was helping here gave up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi tronglx, the only way I found was to install Qubes OS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi Juan, what computer you are in? If you really want to use your computer with linux the only way that it solved for me was to use Qubes OS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi, I didn't find the root of the problem, **BUT**... Using Qubes OS I was able to run for more than 7 days without any problems! It normally would occur in the first hour of usage. I guess Qubes's Xen drivers proxy the pcie requests and therefore the failing NVME/PCIE drivers aren't used. So it at least shines a light in the problem. Maybe someone with better understanding of how Xen works can reason about which drivers are being used and which are not and discover the root of the problem! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi Kai-Heng Feng, I just installed kernel 5.1.1 and the error still happens -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I tried the Ubuntu 19.04 installer and I couldn't even install it because of IO errors. Does the installer of Ubuntu 19.04 uses the new kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi Kai-Heng Feng, do you have any news on this problem? It'd be great to know. Than you so much! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Just tried Ubuntu 19 today and the problem persists (can't even install ubuntu because it gives io error) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Any news on this problem? Im still having it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Ok Christian, thanks for the info. You can try the kernel for now, and I also read that using ubuntu with brtfs system instead of ext4 also solves the problem, you could try -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi Ole Christian. First, did you have any problems in the ubuntu installation? In mine I had to try to install several times until it installed without any disk errors. Also, you can try this kernel https://people.canonical.com/~khfeng/pm961 -disable-aspm/ with this kernel parameter "nvme- core.default_ps_max_latency_us=1500". This is what worked for me, but it's not a definitive solution, I still get the error in some situations (much more rare than before though). You can read our discussion to understand it better. I guess someone is working on this bug for a definitive solution... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Fabian, did you have any problems installing ubuntu? Mine would give disk errors about 7/10 times I tried to install. I had to try many times until no error appeared. I'd like to try btrfs but I don't have the time to do it right now. I also had problems with apt, but when upgrading the system. It'd always give the error in the initramfs update, or something like that. I'll try to install a fresh ubuntu 18.04 soon too, as Janne suggested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
It's worth saying that the ASPM patch + 1500 kernel parameter worked for me for over a month without giving me one single error. After update to 18.04 now I see the error every 2 or 3 days. Actually, in the middle of the update process to 18.04 it gave the error right on the initramfs update, which is where it always gives the error. This is sad, it was working perfectly except inside the VMs but it was very stable :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi hariprasad. If possible, you could try our patched kernel which disables ASPM: https://people.canonical.com/~khfeng/pm961-disable- aspm/. It worked for me but only when I added the nvme- core.default_ps_max_latency_us=1500 kernel parameter. Maybe you can try some day. We're still investigating the issue. When Kai Heng send me the patch I can try it and see what changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Could you send me the patch (and should I use the aspm patch together with it?) Another information that you might find useful: I've been using for 30 days without any problems on the main machine (only one incident inside the virtual machine), so today I decided to finally conclude all the missing updates that I've been waiting to do since the problems arised. It updated more than 1000 packages, and as before it gave the Read Only error while updating initram. It seems that it ALWAYS happens when updating initram. Here's the output I was able to save: https://pastebin.com/raw/PaSQwRJN So after 30 days without any problems it happens while doing this. It's gotta explain something, because it's very unusual, and I've always had problems with initram before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi hariprasad. nvme-core.default_ps_max_latency_us=1500 and ASPM disabling by kernel patching worked for me, at least for the main machine (my virtual machines inside this main machine still give the error after some time). I've been using the patch for almost a month without incidents. I had the problem inside a virtual machine after some days, but it didn't happen again yet (I'm using VMs but not for too much time like in the last time the problem happened). I'm going to try to disable TRIM but it's going to take days for me to test if the VMs give any errors. Should sudo rm /etc/cron.weekly/fstrim be enough? Have you experienced problems installing ubuntu into your SSD? My ubuntu installation gives disk error in 8/10 tries. That is, I need to reinstall ubuntu 8 times in average for the installation to end without any problems. I didn't try to install ubuntu with the kernel patch because it's a lot of work to create a live CD instalation with a patched kernel, but maybe I'll do it some day. I also need to try virtualbox in place of virt-manager as kaihengfeng suggested. Problem is that I need to leave things open for days to notice these errors, so it's going to take time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I've tested the new kernel with this parameter for 10 days and the error didn't happen, which is a record. So I decided to open a VM yesterday and it handled good for like 12 hours, they I went to sleep and grabbed the computer again and the error had happened inside and outside the VM. I don't know if it was caused by the VM itself but for those 10 days I tested, it worked great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Should I take nvme.io_queue_depth=64 out? I didn't experience the problem again yet, just right after the first boot with the new kernel. However I still experience the error inside the VMs. I'm adding nvme-core.default_ps_max_latency_us=1500 now. Is this an user of Razer Blade Stealth? Would be good to talk to him to see if he experiences the problems inside VMs, which is very annoying as I do everything in them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I just compiled the kernel and it presented the error just minutes after the first boot. A reminder: my kernel parameters are still like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash button.lid_init_state=open nvme.io_queue_depth=64" Here's the output you wanted: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 02) Subsystem: Razer USA Ltd. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1a58:6752] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. HD Graphics 620 [1a58:6752] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Razer USA Ltd. Sunrise Point-LP USB 3.0 xHCI Controller [1a58:6752] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21) Subsystem: Razer USA Ltd. Sunrise Point-LP Serial IO I2C Controller [1a58:6752] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Razer USA Ltd. Sunrise Point-LP CSME HECI [1a58:6752] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #3, Speed 8GT/s, Width x1, ASPM L1, Exit Latency L0s <1us, L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt-
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Should I also add the other quirk you made which made the problem happen fewer times? https://lkml.org/lkml/2018/2/15/347 I'm using the 4.15-23 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Could you provide the diff file? I need to compile with other modifications. Or better yet, is there a command to disable aspm in boot? Thank you so much -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hello. Thank you for your continued support! I was unable to test the older kernel yet as I'm using this PC constantly and cannot lose or have it unusable for too much time, as when the system gets corrupted I have to spend hours trying to install it again without errors. Here's the output: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 02) Subsystem: Razer USA Ltd. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1a58:6752] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. HD Graphics 620 [1a58:6752] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Razer USA Ltd. Sunrise Point-LP USB 3.0 xHCI Controller [1a58:6752] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21) Subsystem: Razer USA Ltd. Sunrise Point-LP Serial IO I2C Controller [1a58:6752] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Razer USA Ltd. Sunrise Point-LP CSME HECI [1a58:6752] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #3, Speed 8GT/s, Width x1, ASPM L1, Exit Latency L0s <1us, L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM-
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi, I'm back, sorry for the delay. I'll test it soon again. I tried and the error happened in the middle of the update and broke my ubuntu. I'll reinstall and try again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I didn't need but suddenly I installed some updates and it broke. However I don't think the kernel got upgraded with that update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I did not try to install with disable APST. I tried to put a custom kernel in the live CD but it wouldn't boot. My current ubuntu was installed with trial and error until it installed without any errors. The installation process is not so important for me, I can try 5 or 7 times before getting it right. I'm mainly concerned about usage after. So this is what happened: before any quirks, I was having the error every 2 hours. After your kernel quirk, I started having the error every 2 days on main machine and on average every day on the virtual machines. After the NVME queue_depth parameter it looks like it's taking 5 days, but the virtual machines continue giving the errors 1 time per day on average. So I should try this new kernel? I suppose it already has the quirk you created. I'll install it soon. Not now because I need to backup things, because if the error happens during the kernel installation then the whole ubuntu is going to get wrecked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
On the epoch when I was having the error every 2 hours I installed windows and used for some days without any problems, so I guess not. I also tried an old debian and installation went ok (on ubuntu it fails 80% of the time. I have to try many until I get a good installation) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
And it just happened again. It's common to happend again right after I rebooted ans fscked from a previous one. Then it calms down for some days -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Ok, the error just happened now in the main machine. Took much more days to happen. I picked my computer while it were sleeping but opened, and moved the mouse and saw a black screen with nothing on it. Then pressed power and soething appeared: /.../libvirt read only file system and then it turned off. Libvirt was running at the time so I think it was just an error saying that libvirt was trying to write to the disk. Don't know if it's related. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I'm trying since you wrote. No problems yet on the host machine, but the virtual machine already presented the error twice today (not related to high disk usage) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I tried this parameter and the computer got stuck at the loading screen. Had to enter recovery mode and remove the parameter to make it boot again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Would you mind posting the diff? I'm using custom kernel modifications (not related to disk and tested without them) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I just noted that almost always when I do docker rm $(docker ps -a -q) to remove all docker containers inside my VM, the error happens. Maybe high disk usage causes this? The errors on my computer are taking time to happen, but ih the VMs it happens every day. I'm 100% thankful for what you've done. If you know something, I can pay, these errors are making very hard for me to work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
No. The times I've read dmesg there was nothing like this, neither as an error popup. I'll grep D0 and D3 the next time though -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I do it a lot. However the errors don't happen right afetr waking from suspend. They take some time. Before the NVME quirk I tried to see if suspend/resume influenced in the error. I experienced botting the PC and leaving it open until the error ocurred, proving the suspend wasn't causing it. However now with the NVME quirk the computer takes a lot of time to show the error, so I always en dup closing it. However I think there was one time the error happened right after turning the PC on, though I'm not 100% sure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
The error just happened again inside the VM, and upon VM reboot it said that something was trying to access outside the disk hd0 or hd1, don't remember. Then I noted that the host machine had the error too. This already happened before and I mentioned in commet #75 Somehow the virtual machine errors and the host machine errors are related. However, the error happens even without virtual machine usage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Without NVME_QUIRK_PCI_RESET_RESUME the bug happens every 2 hours. With it, the bug happens every 2 days or more (I think there was a time i've run 5 to 8 days without an error) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Ok so I didn't know exactly what to do. I was using my machine and even though I didn't get any errors I rebooted, entered ubuntu live image and did fsck on /dev/nvme0n1p1 and /dev/nvme0n1p2, no errors showed up Then I continued using my machine and the error appeared. I rebooted into the live machine and did fsck /dev/nvme0n1p2 and fsck /dev/nvme0n1p1 here are the outputs: https://pastebin.com/jpz5SwrR https://pastebin.com/xNMQPuVi (in the nvme0n1p1 I got dirty bit, don't know what is this, and in nvme0n1p2 the output looks the same as when I've run the fsck from the SSD) The error persists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Sorry I didn't test it yet. I had to travel and use the computer so I did a fsck on onvme0n1p2 only, to get it working. I thought fsck /dev/nvme0n1p2 was the same a fscking the rootfs. I do it every time the error happens. I didn't understand exactly what you meant. Also I think NVME_QUIRK_NO_DEEPEST_PS had no effect when added. I'd however try to make it work with it first, and if everything goes ok I'd take it off to see if it continues. If I need to do it before the error happens, I can just run my live ubuntu and do it. Thank you for your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
The next time it happen I will post the full dmesg. But even my first message (#1): Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 cites EXT-4 errors. It's always been like that, nothing changed. I need to fsck the rootfs now or when the error happens again? And how should I do it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
After 2 days with the new kernel, it happened again. Seems like around every 2 days it happens. Maybe some rare nvme write that you didn't cover in the quirks? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Ok, I'm compiling it now on my other PC. Meanwhile, the error happened twice in the same day. That's odd, it usually took at least 2 days to manifest again. Could it be that something chanded on my PC? Anyways, here's the error: 4609.325351] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1447: inode #26610978: comm updatedb.mlocat: checksumming directory block 0 [ 4609.327443] Aborting journal on device nvme0n1p2-8. [ 4609.329533] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [ 4609.357281] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1447: inode #26739117: comm updatedb.mlocat: checksumming directory block 0 [ 4609.627350] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1447: inode #5901277: comm updatedb.mlocat: checksumming directory block 0 [ 4795.596378] perf: interrupt took too long (2563 > 2500), lowering kernel.perf_event_max_sample_rate to 78000 [ 4911.346846] audit: type=1400 audit(1519876882.781:29): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=4149 comm="cupsd" capability=12 capname="net_admin" I'll test the new compiler kernel in some hours -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Well, the error happened again, and I wasn't even running any VMs Maybe there's a rare case in which your diff correction didn't get applied? :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Yes, the fix totally works. The only time when I had a real nvme error on the main machine was that one I reported. Don't know why, though, but it looks like that the VM gone terribly wrong. But these VMs are just plain ubuntus with docker, visual studio code and git. Nothing fancy, don't know why I keep getting ext4 problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Just to remember, inside the VM the error looks like this: [26547.754916] EXT4-fs error (device sda1): htree_dirblock_to_tree:976: inode #31777: comm gvfsd-trash: Directory block failed checksum [26547.756301] Aborting journal on device sda1-8. [26547.757724] EXT4-fs (sda1): Remounting filesystem read-only [26547.762207] EXT4-fs error (device sda1): ext4_journal_check_start:60: Detected aborted journal [26631.771204] EXT4-fs error (device sda1): htree_dirblock_to_tree:976: inode #302034: comm gvfsd-trash: Directory block failed checksum when outside there's no problem 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/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Nope, sorry, I rebooted after copying the dmesg. I thought that since there is [68668.595459] EXT4-fs (nvme0n1p2): Remounting filesystem read-only in what I copied, it was enough because there is where the error started. Gonna cat the entire file the next time, but I'm afraid it'll only happend if I force my CPU too much like I did (actually this is good, because the nvme took a very long time to enter in read only mody, it's a very good progress) Meanwhile, I think that the average of read only errors inside the VMs is like 0.8/day. I always test the main machine when these errors happen and it's always fine. The only time when it gone wrong was this one that I reported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
here's a print screen: https://imgur.com/a/ZEBAP -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
So... the error happened :( I don't know if it's related but I was compiling QT 5 inside a virtual machine and gone to sleep. When I woke up there was an error in the compilation about not being able to allocate virtual memory. The vm was unusable (I pressed things and they won't work) then I rebooted the VM and in the ubuntu initialization there was something about trying to write outside disk hd1. I did fsck then and the machine kept printing lots of lines indefintely about disk writes (wouldn't stop). Tried to print but couldn't save. Now, in the main machine, I did touch a and the error Read Only filesystem appeared. Then looks at dmesg: [62526.097648] CPU3: Package temperature above threshold, cpu clock throttled (total events = 734393) [62526.097650] CPU2: Package temperature above threshold, cpu clock throttled (total events = 734389) [62526.097654] CPU0: Package temperature above threshold, cpu clock throttled (total events = 734421) [62526.098643] CPU0: Core temperature/speed normal [62526.098644] CPU2: Core temperature/speed normal [62526.098644] CPU3: Package temperature/speed normal [62526.098645] CPU1: Package temperature/speed normal [62526.098646] CPU2: Package temperature/speed normal [62526.098647] CPU0: Package temperature/speed normal [62826.083664] CPU0: Core temperature/speed normal [62826.083665] CPU2: Core temperature/speed normal [62826.083666] CPU3: Package temperature/speed normal [62826.083667] CPU1: Package temperature/speed normal [62826.083667] CPU2: Package temperature/speed normal [62826.083669] CPU0: Package temperature/speed normal [63109.039660] CPU3: Core temperature above threshold, cpu clock throttled (total events = 122579) [63109.039661] CPU1: Core temperature above threshold, cpu clock throttled (total events = 122586) [63109.043637] CPU3: Core temperature/speed normal [63109.043637] CPU1: Core temperature/speed normal [63141.298625] CPU2: Core temperature above threshold, cpu clock throttled (total events = 685839) [63141.298626] CPU0: Core temperature above threshold, cpu clock throttled (total events = 685861) [63141.298628] CPU1: Package temperature above threshold, cpu clock throttled (total events = 752070) [63141.298628] CPU3: Package temperature above threshold, cpu clock throttled (total events = 752043) [63141.298630] CPU0: Package temperature above threshold, cpu clock throttled (total events = 752073) [63141.298633] CPU2: Package temperature above threshold, cpu clock throttled (total events = 752042) [63141.311665] CPU0: Core temperature/speed normal [63141.311666] CPU2: Core temperature/speed normal [63141.311667] CPU1: Package temperature/speed normal [63141.311667] CPU3: Package temperature/speed normal [63141.311668] CPU2: Package temperature/speed normal [63141.311669] CPU0: Package temperature/speed normal [63441.300764] CPU2: Core temperature/speed normal [63441.300765] CPU0: Core temperature/speed normal [63441.300766] CPU3: Package temperature/speed normal [63441.300766] CPU1: Package temperature/speed normal [63441.300767] CPU0: Package temperature/speed normal [63441.300768] CPU2: Package temperature/speed normal [63742.088404] CPU0: Core temperature above threshold, cpu clock throttled (total events = 702907) [63742.088405] CPU1: Package temperature above threshold, cpu clock throttled (total events = 773051) [63742.088406] CPU3: Package temperature above threshold, cpu clock throttled (total events = 773025) [63742.088407] CPU2: Core temperature above threshold, cpu clock throttled (total events = 702884) [63742.088408] CPU2: Package temperature above threshold, cpu clock throttled (total events = 773023) [63742.088412] CPU0: Package temperature above threshold, cpu clock throttled (total events = 773055) [63742.089411] CPU2: Core temperature/speed normal [63742.089412] CPU0: Core temperature/speed normal [63742.089412] CPU3: Package temperature/speed normal [63742.089413] CPU1: Package temperature/speed normal [63742.089413] CPU0: Package temperature/speed normal [63742.089414] CPU2: Package temperature/speed normal [64044.223423] CPU0: Core temperature above threshold, cpu clock throttled (total events = 712002) [64044.223424] CPU2: Core temperature above threshold, cpu clock throttled (total events = 711979) [64044.223425] CPU1: Package temperature above threshold, cpu clock throttled (total events = 783486) [64044.223426] CPU3: Package temperature above threshold, cpu clock throttled (total events = 783460) [64044.223428] CPU2: Package temperature above threshold, cpu clock throttled (total events = 783459) [64044.223431] CPU0: Package temperature above threshold, cpu clock throttled (total events = 783491) [64044.235444] CPU2: Core temperature/speed normal [64044.235444] CPU3: Package temperature/speed normal [64044.235445] CPU1: Package temperature/speed normal [64044.235446] CPU0: Core temperature/speed normal [64044.235447] CPU0: Package temperature/speed normal [64044.235448] CPU2: Package
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
The kernel is still good. The error happened again in the virtual machine, here's dmesg: [ 6730.708866] EXT4-fs error (device sda1): htree_dirblock_to_tree:976: inode #418562: comm updatedb.mlocat: Directory block failed checksum [ 6730.710121] Aborting journal on device sda1-8. [ 6730.711514] EXT4-fs (sda1): Remounting filesystem read-only [ 6730.713087] EXT4-fs error (device sda1): ext4_journal_check_start:60: Detected aborted journal [ 7030.415582] audit: type=1400 audit(1519269087.344:26): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=2851 comm="cupsd" capability=12 capname="net_admin" [67539.479651] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: [67539.479670] clocksource: 'kvm-clock' wd_now: 55b3d2da2f60 wd_last: 269f11d4c146 mask: [67539.479673] clocksource: 'tsc' cs_now: 422f92c80a6a cs_last: 422e9dc07f56 mask: what do you think? My disk is /dev/sda1 on the virtual machine, so no NVME... I'm using KVM spice -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Since you wrote the last message I recompiled the kernel and reinstalled. Tested again, the problem ocurred in about 1 hour. Then I took the kernel parameter off and started to test and I've been running for more than 24 hours without errors. However, the error ocurred inside a virtual machine. But the disk in the machine is named /dev/sda1, so it's not using NVME drivers or anything like that. How is it possible for the error to occur inside the virtual machine but not on the main machine? Could this be due to another completely unrelated problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I added nvme_core.default_ps_max_latency_us=0 because you said in an older comment. Is it necessary or can I take it off? I'm compiling my own because I want to learn and also test new kernels as they are released, specially now with specte and meltdown (it's going to take time for it to reach mainline and even more time for it to reach the live installer). Also it's a good pratice for security reasons. I don't see what I did wrong, my kernel should work exactly as yours. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Here's what I did: git clone bionic_git_url... cd ubuntu-bionic git checkout patch -p1 < nvme_reset.diff #(from your diff file) #gave an error about last line but I checked manually and it was ok (I guess was because of the number in the end: https://pastebin.com/j4Tz1fDa sudo apt-get build-dep linux-image-$(uname -r) fakeroot debian/rules clean fakeroot debian/rules binary-headers binary-generic binary-perarch after a long time, I copied linux-headers-4.15.0-9_4.15.0-9.10_all.deb linux-headers-4.15.0-9-generic_4.15.0-9.10_amd64.deb linux-image-4.15.0-9-generic_4.15.0-9.10_amd64.deb linux-image-extra-4.15.0-9-generic_4.15.0-9.10_amd64.deb and installed on my fresh ubuntu 17.10.1 install on the razer blade stealth by doing sudo dpkg -i *.deb then I added nvme_..._us=0 to grub and did sudo update-grub rebooted and used for a while (confirmed using uname-r that the new kernel was running). In the first time I did all this, the problem ocurred while installing updates. In the second time I tried, the error ocurred when tried to install virt-manager. Since the kernel worked perfectly except for that, I can only assume that your diff didn't go through. But if I do git checkout and then apply a diff to that tag, then I can simply cd to this folder and compile and I'll be using the diff, right? Thank you for your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I installed ubuntu again, installed my compiled kernel, disabled updates. When installing a package (virt-manager), the error ocurred again. This package messes with kernel (kvm things) but I used before on your kernels and everything was fine (I didn't try to install while in your kernel though) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I download a fresh 4.15.0-9 kernel, applied the diff and compiled just as in the page you sent. I then formatted, installed ubuntu 17.10.1, booted and enabled nvme_..._us=0, rebooted. Then I started installing updates. The error ocurred in the middle of it. I've never tried to install updates on the kernels you made me test. Could it be that it's breaking something? :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I compiled a kernel myself apllying the patcch and using make deb-pkg and got these files: linux-headers-4.15.4_4.15.4-4_amd64.deb linux-image-4.15.4_4.15.4-4_amd64.deb linux-image-4.15.4-dbg_4.15.4-4_amd64.deb linux-libc-dev_4.15.4-4_amd64.deb but you don't have image...dbg neither libc, and you have image-extra and headers...generic. What's the difference? Will mine work? If not, how do I get your 4 files exactly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
but v4.16-rc1 doesn't have "NVME_QUIRK_PCI_RESET_RESUME = (1 << 7)" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
When there will be a kernel with this patch included? What about the live image? It's going to take months for a live installation image to have this patch. Is it possible for me to use this kernel in a live image myself? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Everything is ok with this new kernel. No erros. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Ok, just installed it. Gonna monitor it to see if any errors come up -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I've been running for days without any problem (it'd happen before like 30 minutes after installation). So can you release the source? Will it be on mainline? Also, how to use this kernel with the live image? Because it's painful to install ubuntu with this problems, I get I/O error in 90% of my tries. I have to try for hours until it installs good. Thank you so much! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Nevermind I installed libssl1.1 by adding the bionic rep, however right before I could reinstall the kernel the system entered in read-only mode. I'm gonna try to enter and install the new kernel in some way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I think I got it: http://pastebin.com/raw/squFVnGi I'm counting with the idea that this 4.13.0-34 is the new one, not the old one I had. I hope it is. Just booted and PCIe wireless is working. uname-r gives 4.13.0-34-generic. Going to leave the system rest for a while to see if something happens, not going to download torrent again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I just installed your new kernel on the old SSD and changed the nvme_core_..._us to 0 seems that a dependency is missing on the kernel: oblems prevent configuration of linux-headers-4.13.0-34-generic: linux-headers-4.13.0-34-generic depends on libssl1.1 (>= 1.1.0); however: Package libssl1.1 is not installed. dpkg: error processing package linux-headers-4.13.0-34-generic (--install): dependency problems - leaving unconfigured Setting up linux-image-4.13.0-34-generic (4.13.0-34.37~lp1746340) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-34-generic /boot/vmlinuz-4.13.0-34-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.13.0-34-generic /boot/vmlinuz-4.13.0-34-generic update-initramfs: Generating /boot/initrd.img-4.13.0-34-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.13.0-34-generic /boot/vmlinuz-4.13.0-34-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.13.0-34-generic /boot/vmlinuz-4.13.0-34-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.13.0-34-generic /boot/vmlinuz-4.13.0-34-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.15.0+ Found initrd image: /boot/initrd.img-4.15.0+ Found linux image: /boot/vmlinuz-4.14.0-17-generic Found initrd image: /boot/initrd.img-4.14.0-17-generic Found linux image: /boot/vmlinuz-4.13.0-34-generic Found initrd image: /boot/initrd.img-4.13.0-34-generic Found linux image: /boot/vmlinuz-4.13.0-32-generic Found initrd image: /boot/initrd.img-4.13.0-32-generic Found linux image: /boot/vmlinuz-4.13.0-21-generic Found initrd image: /boot/initrd.img-4.13.0-21-generic Adding boot menu entry for EFI firmware configuration done Setting up linux-image-extra-4.13.0-34-generic (4.13.0-34.37~lp1746340) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-34-generic /boot/vmlinuz-4.13.0-34-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.13.0-34-generic /boot/vmlinuz-4.13.0-34-generic update-initramfs: Generating /boot/initrd.img-4.13.0-34-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.13.0-34-generic /boot/vmlinuz-4.13.0-34-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.13.0-34-generic /boot/vmlinuz-4.13.0-34-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.13.0-34-generic /boot/vmlinuz-4.13.0-34-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.15.0+ Found initrd image: /boot/initrd.img-4.15.0+ Found linux image: /boot/vmlinuz-4.14.0-17-generic Found initrd image: /boot/initrd.img-4.14.0-17-generic Found linux image: /boot/vmlinuz-4.13.0-34-generic Found initrd image: /boot/initrd.img-4.13.0-34-generic Found linux image: /boot/vmlinuz-4.13.0-32-generic Found initrd image: /boot/initrd.img-4.13.0-32-generic Found linux image: /boot/vmlinuz-4.13.0-21-generic Found initrd image: /boot/initrd.img-4.13.0-21-generic Adding boot menu entry for EFI firmware configuration done Errors were encountered while processing: linux-headers-4.13.0-34-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
You mean I need to boot with the parameter on your new kernel? I'm gonna try it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Is it possible to boot the live installation media with the kernel parameter? I'm having problems installing the ubuntu into the new SSD, always get I/O errors... I'm gonna also try the new kernel on the old SSD though -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Very important update: I bought a brand new Samsung 960 EVO, and I can't even install Ubuntu: I get I/O error in the installation -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I rebooted and I was still at 4.15. I then activated grub to select a kernel version, and I chose 4.14 which is yours. I then boot to a cpu_fifo_underun and nothing boots -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
initramf [drm: intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Just after running sudo dpkg -i *.deb, and before rebooting, the error happened. Since the new kernel isn't running yet, I guess this current kernel still had the problem? That's strange because I've been running for more than 24 hours, downloading lots of torrents and had no problems. I'm going to reboot now to test the new kernel Here's the output: sudo dpkg -i *.deb [sudo] password for lz: Selecting previously unselected package linux-headers-4.14.0-17. (Reading database ... 215114 files and directories currently installed.) Preparing to unpack linux-headers-4.14.0-17_4.14.0-17.20~lp1746340_all.deb ... Unpacking linux-headers-4.14.0-17 (4.14.0-17.20~lp1746340) ... Selecting previously unselected package linux-headers-4.14.0-17-generic. Preparing to unpack linux-headers-4.14.0-17-generic_4.14.0-17.20~lp1746340_amd64.deb ... Unpacking linux-headers-4.14.0-17-generic (4.14.0-17.20~lp1746340) ... Selecting previously unselected package linux-image-4.14.0-17-generic. Preparing to unpack linux-image-4.14.0-17-generic_4.14.0-17.20~lp1746340_amd64.deb ... Examining /etc/kernel/preinst.d/ Done. Unpacking linux-image-4.14.0-17-generic (4.14.0-17.20~lp1746340) ... Selecting previously unselected package linux-image-extra-4.14.0-17-generic. Preparing to unpack linux-image-extra-4.14.0-17-generic_4.14.0-17.20~lp1746340_amd64.deb ... Unpacking linux-image-extra-4.14.0-17-generic (4.14.0-17.20~lp1746340) ... Setting up linux-headers-4.14.0-17 (4.14.0-17.20~lp1746340) ... Setting up linux-headers-4.14.0-17-generic (4.14.0-17.20~lp1746340) ... Setting up linux-image-4.14.0-17-generic (4.14.0-17.20~lp1746340) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.14.0-17-generic /boot/vmlinuz-4.14.0-17-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.14.0-17-generic /boot/vmlinuz-4.14.0-17-generic update-initramfs: Generating /boot/initrd.img-4.14.0-17-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.14.0-17-generic /boot/vmlinuz-4.14.0-17-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.14.0-17-generic /boot/vmlinuz-4.14.0-17-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.14.0-17-generic /boot/vmlinuz-4.14.0-17-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-4.15.0+ Found initrd image: /boot/initrd.img-4.15.0+ Found linux image: /boot/vmlinuz-4.14.0-17-generic Found initrd image: /boot/initrd.img-4.14.0-17-generic Found linux image: /boot/vmlinuz-4.13.0-32-generic Found initrd image: /boot/initrd.img-4.13.0-32-generic Found linux image: /boot/vmlinuz-4.13.0-21-generic Found initrd image: /boot/initrd.img-4.13.0-21-generic Adding boot menu entry for EFI firmware configuration done Setting up linux-image-extra-4.14.0-17-generic (4.14.0-17.20~lp1746340) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.14.0-17-generic /boot/vmlinuz-4.14.0-17-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.14.0-17-generic /boot/vmlinuz-4.14.0-17-generic update-initramfs: Generating /boot/initrd.img-4.14.0-17-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.14.0-17-generic /boot/vmlinuz-4.14.0-17-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.14.0-17-generic /boot/vmlinuz-4.14.0-17-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.14.0-17-generic /boot/vmlinuz-4.14.0-17-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-4.15.0+ Found initrd image: /boot/initrd.img-4.15.0+ Found linux image: /boot/vmlinuz-4.14.0-17-generic Found initrd image: /boot/initrd.img-4.14.0-17-generic Found linux image: /boot/vmlinuz-4.13.0-32-generic Found initrd image: /boot/initrd.img-4.13.0-32-generic Found linux image: /boot/vmlinuz-4.13.0-21-generic Found initrd image: /boot/initrd.img-4.13.0-21-generic Adding boot menu entry for EFI firmware configuration done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
The new kernel has been running for almost a day and no problems happened (however I still have no PCIe wireless and no i915 firmware so I can't open things like kdenlive) What does this fix of yours do and is it possible to make it work with everything? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I added an USB wireless receiver to use internet to download things so I can see if something happens. I installed more system updates through the ubuntu software updates. Is this ok? The kernel will still be yours, rigtht? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
After installing everything, I rebooted to use the new kernel. I then installed updates on the machine to see if the problem would happen (easier way to make it happen is on the moment I try to update). After the update, wireless stopped working. Restarted many times and still not working. Could it be that the update triggered the error and the so called pcie reset of this kernel made the wireless go wrong? I'm gonna still use this kernel to see if the read only filesystem happens though -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I downloaded again and it seems that this time it wasn't corrupted. Output: Preparing to unpack linux-headers-4.15.0+_4.15.0+-2_amd64.deb ... Unpacking linux-headers-4.15.0+ (4.15.0+-2) over (4.15.0+-2) ... Preparing to unpack linux-image-4.15.0+_4.15.0+-2_amd64(1).deb ... Unpacking linux-image-4.15.0+ (4.15.0+-2) over (4.15.0+-2) ... Preparing to unpack linux-image-4.15.0+-dbg_4.15.0+-2_amd64(1).deb ... Unpacking linux-image-4.15.0+-dbg (4.15.0+-2) ... Preparing to unpack linux-libc-dev_4.15.0+-2_amd64.deb ... Unpacking linux-libc-dev (4.15.0+-2) over (4.15.0+-2) ... Setting up linux-headers-4.15.0+ (4.15.0+-2) ... Setting up linux-image-4.15.0+ (4.15.0+-2) ... update-initramfs: Generating /boot/initrd.img-4.15.0+ W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_27.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_39.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver9_29.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_ver9_33.bin for module i915 Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-4.15.0+ Found initrd image: /boot/initrd.img-4.15.0+ Found linux image: /boot/vmlinuz-4.13.0-21-generic Found initrd image: /boot/initrd.img-4.13.0-21-generic Adding boot menu entry for EFI firmware configuration done Setting up linux-image-4.15.0+-dbg (4.15.0+-2) ... Setting up linux-libc-dev (4.15.0+-2) ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Thanks. What's a 'PCI reset for NVMe device after resume'? Here's the output of running sudo dpkg -i *.deb on the 4 files: Selecting previously unselected package linux-headers-4.15.0+. (Reading database ... 137951 files and directories currently installed.) Preparing to unpack linux-headers-4.15.0+_4.15.0+-2_amd64.deb ... Unpacking linux-headers-4.15.0+ (4.15.0+-2) ... Selecting previously unselected package linux-image-4.15.0+. Preparing to unpack linux-image-4.15.0+_4.15.0+-2_amd64.deb ... Unpacking linux-image-4.15.0+ (4.15.0+-2) ... Selecting previously unselected package linux-image-4.15.0+-dbg. Preparing to unpack linux-image-4.15.0+-dbg_4.15.0+-2_amd64.deb ... Unpacking linux-image-4.15.0+-dbg (4.15.0+-2) ... dpkg-deb (subprocess): decompressing archive member: lzma error: compressed data is corrupt dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing archive linux-image-4.15.0+-dbg_4.15.0+-2_amd64.deb (--install): cannot copy extracted data for './usr/lib/debug/lib/modules/4.15.0+/kernel/drivers/iio/pressure/zpa2326.ko' to '/usr/lib/debug/lib/modules/4.15.0+/kernel/drivers/iio/pressure/zpa2326.ko.dpkg-new': unexpected end of file or stream Selecting previously unselected package linux-libc-dev. Preparing to unpack linux-libc-dev_4.15.0+-2_amd64.deb ... Unpacking linux-libc-dev (4.15.0+-2) ... Setting up linux-headers-4.15.0+ (4.15.0+-2) ... Setting up linux-image-4.15.0+ (4.15.0+-2) ... update-initramfs: Generating /boot/initrd.img-4.15.0+ W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_27.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_39.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver9_29.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_ver9_33.bin for module i915 Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-4.15.0+ Found initrd image: /boot/initrd.img-4.15.0+ Found linux image: /boot/vmlinuz-4.13.0-21-generic Found initrd image: /boot/initrd.img-4.13.0-21-generic Adding boot menu entry for EFI firmware configuration done Setting up linux-libc-dev (4.15.0+-2) ... Errors were encountered while processing: linux-image-4.15.0+-dbg_4.15.0+-2_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Initially I noted that it'd happen after opening the lid of the notebook, so yes. But now after I install Ubuntu it immediately starts looking for software updates and that's when the problem happens for the first time, when I haven't even had time to close the notebook to suspend it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I found a guy with same problem as mine and had a Razer Blade Stealth, but he didn't post anything more after that. And he was in a thread with you. I also found some people with this same problem on the same SSD. Together with the fact that I had no problem on windows (ore than 24hrs of usage by now) I think it can be fixed in the kernel. I had no luck updating my SSD's firmware as it's OEM and Samsung's updater won't work for it. Do you have any idea? I don't have money to buy a new SSD, and I really need to work. I'd be so grateful if you could help with a solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1620396] Re: Installer crashed. Using Samsung 950 Pro NVMe SSD
This problem were always present when I tried to install Ubuntu on my Razer Blade Stealth, but sometimes the installation wouldn't crash and I could use it normally.I have a Samsung 950 Pro NVMe SSD too. Any updates on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620396 Title: Installer crashed. Using Samsung 950 Pro NVMe SSD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1620396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I searched and found nothing. So, even with APST disabled my ssd will fail on linux. What should I do? Does it work normally for other people when they disable it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I forgot to mention that I reinstalled windows and everything is fine. Even did a benchmark test on the SSD and I'm downloading lots of files to test -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
On debian (4.9) I didn't notice the issue but I didn't use much. HOWEVER, when I do apt-get upgrade on debian I do get the issue. It just updated the kernel file, didn't run the new kernel (a boot would have to happen). On v4.15 I didn't change the nvme_core.default_ps_max_latency_us=0, I guess. I did before upgrading to v4.15, I guess. But I can try again. This is all very strange -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Problem persists with 4.15.0-041500-generic, just happened -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I just installed 4.15.0-041500-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi! I managed to install ubuntu again, these are the outputs you asked for the ms tie of 0 milliseconds: NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S33UNX0J324060 mn : SAMSUNG MZVLW512HMJP-0 fr : CXY7501Q rab : 2 ieee: 002538 cmic: 0 mdts: 0 cntlid : 2 ver : 10200 rtd3r : 186a0 rtd3e : 4c4b40 oaes: 0 oacs: 0x17 acl : 7 aerl: 3 frmw: 0x16 lpa : 0x3 elpe: 63 npss: 4 avscc : 0x1 apsta : 0x1 wctemp : 341 cctemp : 344 mtfa: 0 hmpre : 0 hmmin : 0 tnvmcap : 512110190592 unvmcap : 0 rpmbs : 0 sqes: 0x66 cqes: 0x44 nn : 1 oncs: 0x1f fuses : 0 fna : 0 vwc : 0x1 awun: 255 awupf : 0 nvscc : 1 acwu: 0 sgls: 0 subnqn : ps0 : mp:7.60W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps1 : mp:6.00W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps2 : mp:5.10W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- get-feature:0xc (Autonomous Power State Transition), Current value: Autonomous Power State Transition Enable (APSTE): Disabled Auto PST Entries. Entry[ 0] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 1] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 2] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 3] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 4] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 5] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 6] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 7] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 8] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 9] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[10] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[11] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[12] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[13] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[14] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[15] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[16] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[17] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[18] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[19] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 .
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi. I've been trying to install Windows 10 in order to try to update my SSD firmware, but I'm getting an error: https://imgur.com/a/BM0gG could it be that my SSD has a real hardware problem? I tried many different pen drives, in different USB ports, but I always get the same error. I'm trying to install Ubuntu to get the output of nvme_core.default_ps_max_latency_us=0 but the installation always fails -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Thank you for your answer. I'm desperated. I just installed debian therefore I'm not going to able to do it right now, but I have output from the last time I was using Ubuntu. I tried nvme_core.default_ps_max_latency_us=5500 and it didn't work. Then I've put it to 0, which didn't work too. Well, with 0 it didn't generate errors while using, but while trying to update my machine, which always happens too, so I don't know anymore. I remember seeing ATSP Disabled at the output, but the error always happens when I try to update my software... Shouldn't this bug be already fixed? Or not in my kernel? I could pay to get to the bottom of this, because I need my computer so much right now and this bug is happening every day and I can't continue my work! The last kernel I had on ubuntu was 4.13.0-26-generic, now I'm on debian and I have 4.9.0-4. sudo nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 S33UNX0J324060 SAMSUNG MZVLW512HMJP-0 1 25,30 GB / 512,11 GB 512 B + 0 B CXY7501Q NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S33UNX0J324060 mn : SAMSUNG MZVLW512HMJP-0 fr : CXY7501Q rab : 2 ieee : 002538 cmic : 0 mdts : 0 cntlid : 2 ver : 10200 rtd3r : 186a0 rtd3e : 4c4b40 oaes : 0 oacs : 0x17 acl : 7 aerl : 3 frmw : 0x16 lpa : 0x3 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 341 cctemp : 344 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 512110190592 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0 vwc : 0x1 awun : 255 awupf : 0 nvscc : 1 acwu : 0 sgls : 0 subnqn : ps 0 : mp:7.60W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:6.00W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:5.10W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1746340/+attachment/5045896/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1746340/+attachment/5045895/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1746340/+attachment/5045893/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
