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
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
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:
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`,
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
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
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:
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
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
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:
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
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.
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
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
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
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
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
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
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
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)
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
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:
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.
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-
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'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,
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
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
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
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
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
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
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
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.
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:
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.
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:
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
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
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
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
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.
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
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
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
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
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.
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
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.
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
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
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
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.
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):
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
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
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
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
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:
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
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]
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.
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
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
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)
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
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
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
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
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:
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
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
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
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
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
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
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
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:
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.
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
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
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
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
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
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
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
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
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
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
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.
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.
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.
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
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:
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
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
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,
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,
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:
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
1 - 100 of 116 matches
Mail list logo
