Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible problem with samsung SSDs that might be affecting razer's notebooks #10

Closed
lucaszanella opened this issue Jan 21, 2018 · 35 comments

Comments

Projects
None yet
5 participants
@lucaszanella
Copy link
Contributor

commented Jan 21, 2018

I've had corruption problems and downraded to ubuntu 16.04 which worked well until I applied some updates. It looks like there's a bug in samsung SSDs that starts with ubuntu 17.04 tat might be the cause of this, as I figured out and posted here:

https://askubuntu.com/questions/998471/razer-blade-stealth-disk-corruption-fsck-needed-probably-samsung-ssd-bug-afte

(probable fix also linked in my post)

Probably a good thing to list in this repository.

@rolandguelle

This comment has been minimized.

Copy link
Owner

commented Jan 28, 2018

I don't have this problem, but sounds interesting & useful.

What I don't understand, what fix this issue?

The kernel parameter:

  • nvme_core.default_ps_max_latency_us=5500

or updating the firmware?

@lucaszanella

This comment has been minimized.

Copy link
Contributor Author

commented Jan 28, 2018

@rolandguelle

This comment has been minimized.

Copy link
Owner

commented Jan 30, 2018

OK, I keep this issue open. Maybe we find more infos in the future.

@rolandguelle

This comment has been minimized.

Copy link
Owner

commented May 7, 2018

I had problems with installing a fresh 18.04 on my machine, where I first guess I run into the same issue. But using this kernel parameters make it worse. Start the installation mode direct in Grub solves the problem.

@samr28

This comment has been minimized.

Copy link

commented Jun 17, 2018

I had a few problems similar to this when I was running KDE neon 5.12 (ubuntu 16.04). In my case, I would often have the system go into read only mode and I would get an error every time that I opened a file or program. Then I would reboot the system and fsck would fix it. This didn't happen too often but it did happen quite a few times.

Then later I had a much more serious issue where the system went into read only mode but then when I booted back up, I couldn't get into fsck or neon. I did some tests and tried to fix it with the help of the people on the ubuntu irc but had no success. I ended up just reinstalling but instead, going with kubuntu which is based on 18.04. Since then I have had one fsck read only mode issue. So I'm hoping that it was something solved with ubuntu related to the m.2 ssds. I remember that one of the people on the ubuntu irc said that there was a bug that seemed to be similar to what I experienced and the bug was fixed after 16.04 (not sure when). So hopefully I don't have any of these problems with 18.04.

Razer blade stealth late 2017 512GB ssd.

@jheise

This comment has been minimized.

Copy link

commented Aug 6, 2018

I've been running into this issue since upgrading to ubuntu 18.04, i'm fairly certain i saw it sporadically on 16.10, 17.04, and 17.10, maybe 6 to 10 times total for all of those. Since the 18.04 upgrade its been much more frequent, easily once every two weeks, often more. I'm running on a fresh install of 18.04, no kernel changes or firmware upgrades to ssd.

@lucaszanella

This comment has been minimized.

Copy link
Contributor Author

commented Aug 6, 2018

Hi @jheise. A guy in ubuntu launchpad bug forum has been helping me with this for months. We made a lot of progress. I'm using now a patched kernel which won't show this problem ever except in 2 situations:

1 - when I do sudo apt upgrade, in the last step, the initramfs upgrade, it gives the error
2 - it still gives the error very rarely inside my virtual machines (but the main machine still runs intact)

You can follow our progress here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340

I can guide you into patching and compiling this new kernel (it's very easy, less than 5 commands needed I guess).

Also, @samr28, do you have any updates?

Thank you much for your inputs, it's rare to find razer blade stealth users with ubuntu to help with this problem.

@lucaszanella

This comment has been minimized.

Copy link
Contributor Author

commented Aug 6, 2018

@jheise I ust say that when I had these problems I would encounter them 2 times a day. It was impossible to use. Maybe I was using some software which you weren't, and therefore I triggered more the source of these errors. Anyways, my case was much worse. Didn't you have any problems installing ubuntu? I always have to try like 8 times to get the installation to go without any errors. It's very critical to me. Please tell me your razer setup :)

@samr28

This comment has been minimized.

Copy link

commented Aug 6, 2018

@lucaszanella Yeah I actually have been having the same problems and I totally forgot about this thread. I tried the microcode updates but that didn't seem to solve the problem for me. Also I'm on 18.04 now and the issue seems to be occurring more often as @jheise said.

@lucaszanella

This comment has been minimized.

Copy link
Contributor Author

commented Aug 6, 2018

@jheise I applied this patch https://launchpadlibrarian.net/374634454/0001-ASPM-quirk-for-SM-PM-EVO-961.patch to the 4.15.0-23-generic ubuntu kernel (bionic) and added the following kernel parameter: nvme-core.default_ps_max_latency_us=1500

I've been using the notebook with this patch for more than one month and only had the problem in the two situations I listed. You can use the notebook for almost anything with this patch with very few or no problems at all

@jheise

This comment has been minimized.

Copy link

commented Aug 6, 2018

@lucaszanella Awesome! Starting to read through the backlog.

@samr28

This comment has been minimized.

Copy link

commented Aug 6, 2018

I installed the kernel linked in this comment: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/comments/134. I'll let you guys know if I run into the issue again or if it solves it.

@jheise

This comment has been minimized.

Copy link

commented Aug 7, 2018

I've also installed the above kernel, rebooted and waiting to see how it goes.

@jheise

This comment has been minimized.

Copy link

commented Aug 7, 2018

Prior to patching, has anyone had an issue where the hard drive doesnt show up in the bios? One a few occasions i've had to reboot several time until drive shows up again.

@lucaszanella

This comment has been minimized.

Copy link
Contributor Author

commented Aug 7, 2018

@jheise

This comment has been minimized.

Copy link

commented Aug 8, 2018

Running kernel Linux alita 4.18.0-3-generic #4 SMP Wed Aug 1 00:12:23 CST 2018 x86_64 x86_64 x86_64 GNU/Linux I've seen crashes twice after suspend

@lucaszanella

This comment has been minimized.

Copy link
Contributor Author

commented Aug 9, 2018

Did you add the kernel parameter too? In my comments you can see that im using 1500. Unfortunately I'm not at my computer right now but you should find it easily.

I'm supposing you're using the ASPM patched kernel. There are multiple ones we tested.

@jheise

This comment has been minimized.

Copy link

commented Aug 9, 2018

So in /etc/default/grub I have the following
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash button.lid_init_state=open nvme-core.default_ps_max_latency_us=1500"

but checking /proc/cmdline i see this
BOOT_IMAGE=/boot/vmlinuz-4.18.0-3-generic root=UUID=5d60876c-02ce-4657-8a2f-31bc42f32cbd ro quiet splash button.lid_init_state=open vt.handoff=1

@lucaszanella

This comment has been minimized.

Copy link
Contributor Author

commented Aug 11, 2018

Just to be sure, did you install this one: https://people.canonical.com/~khfeng/pm961-disable-aspm/? This is the one that worked for me (but I did not install this, I compiled my own with the patch that generated this). And this is the parameter: nvme-core.default_ps_max_latency_us=1500

My computer has been working for more than 30 days without problems

@jheise

This comment has been minimized.

Copy link

commented Aug 16, 2018

I installed https://people.canonical.com/~khfeng/quirk-no-commclk/ no change in performance. Afterwards i installed the latest 4.18.0-3 kernel, that had an uptime of a day and then froze after resume. I then had to reboot twice because my drive was not showing up. At this point i'm contemplating replacing the drive.

@samr28

This comment has been minimized.

Copy link

commented Sep 24, 2018

It sounds like this has kernel has fixed the issue. How do we go about getting it merged into the official kernel?

@lucaszanella

This comment has been minimized.

Copy link
Contributor Author

commented Sep 24, 2018

@samr28

This comment has been minimized.

Copy link

commented Sep 24, 2018

My system has been stable for about a month now but I haven't been updating packages. Is it possible that you accidentally updated the kernel when updating the system?

@lucaszanella

This comment has been minimized.

Copy link
Contributor Author

commented Sep 24, 2018

@samr28

This comment has been minimized.

Copy link

commented Oct 2, 2018

I've been running 4.18.0-3-generic for the past week and so far I haven't run into any issues with the SSD. The only weird thing that I run into is that when it boots into ubuntu, the xserver doesn't start. So I just have to switch terminals and run startx.

Also I'm getting really terrible battery life not (less than 3 hours) for some reason. #29

@rolandguelle

This comment has been minimized.

Copy link
Owner

commented Oct 2, 2018

Have you tried booting Live Ubuntu 18.04 from USB with the xserver problem?
Ubuntu switched back from Wayland to X with 18.04, maybe some of your start scripts or gdm, lightdm are broken.

@rolandguelle

This comment has been minimized.

Copy link
Owner

commented Oct 2, 2018

@samr28 solves 4.18.0-3 the SSD problem without any other tweaks / workarounds?
Could we close the issue with the (upcoming) Ubuntu 18.10?

@samr28

This comment has been minimized.

Copy link

commented Oct 2, 2018

@rolandguelle I've been running fine on the 4.18.0-3 kernel so far but I wouldn't conclude that its fixed. I haven't tried the "download a bunch of emails" (to write a bunch of things to the drive) test. I've also been restarting every week or so which in the past seemed to prolong the self destruct timer.

I'll try the live boot tonight and see if the xserver starts up properly.

@lucaszanella

This comment has been minimized.

Copy link
Contributor Author

commented Oct 2, 2018

I think the issue should still be left open. I'll try the new ubuntu releases soon when I get the chance to. However, I'm still experiencing problems with the current patched kernel, and these are the patches that go to these new kernels. It's way more stable though

@rolandguelle

This comment has been minimized.

Copy link
Owner

commented Oct 21, 2018

If this issue still exists in Ubuntu 18.10, please reopen this issue.

@lucaszanella

This comment has been minimized.

Copy link
Contributor Author

commented Apr 19, 2019

Just tested on ubuntu 19 which was lunched today. Couldn't even install because it had a problem in disk while installing

@sabiou

This comment has been minimized.

Copy link

commented May 19, 2019

I'm actually facing this issues since two weeks.. I'm running Ubuntu 18.10 on a Lenovo Thinkpad T570

@lucaszanella

This comment has been minimized.

Copy link
Contributor Author

commented May 19, 2019

@sabiou

This comment has been minimized.

Copy link

commented May 19, 2019

Okay @lucaszanella thanks I will do it asap

@lucaszanella

This comment has been minimized.

Copy link
Contributor Author

commented May 19, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.