@munbi, have you installed the latest firmware available for your SSD?
You can find it here:
http://www.samsung.com/global/business/semiconductor/minisite/SSD/global/html/support/downloads.html
--
You received this bug notification because you are a member of Kernel
Packages, which is
*** This bug is a duplicate of bug 1338706 ***
https://bugs.launchpad.net/bugs/1338706
@CJ, this bug is duplicate of bug #1338706.
The title of it, is:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set
xfermode (err_mask=0x40) on upstream kernels = 3.12.
So I presume
@Cyberbob, there is a fix coming for *buntus 14.04 (Trusty), as you can
see at the beginning of this page (Fix Committed).
When the message becomes Fix Released, the updated kernel will be
avaible to all *buntus 14.04.
I do not remember if Linux Mint uses the official Ubuntu repositories.
If
Also, for data loss to occur, you must have something like 60-70 GB of
data on the filesystem.
Data loss does not occur, if you have just clean installed some *buntu.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The command is
fstrim-all
in *buntus 14.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
set
If you have not disabled NCQ in /etc/default/grub, if you run
fstrim -av
manually 3-4 times, one after the other, you will get data loss.
It has happened to me with *buntus 14.04.2, 14.10, 15.04.
If you disable NCQ in grub, everything is fine.
--
You received this bug notification because
Does the last kernel update (kernel 3.19.0-20.20) contain the fix?
I saw no reference to any Samsung SSD, at its changelog.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
The issue still exists in some form.
Usually if one or more USB error messages appear, and you wait, they
disappear now, and the boot proceeds ok.
Sometimes however, like if you press a keyboard button before they
disappear, the issue remains.
--
You received this bug notification because you
I think the issue with USB error messages, error -110, was fixed with
the last kernel update (kernel 3.19.0-18.18).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1437492
Title:
boot
I have the sane bug, error -110 USB error messages, and when I reboot,
the computer's UEFI initialisation during boot, at the USB device stage,
is very slow.
The problem gets fixed temporarily, if you unplug the computer from the
power socket (or turn off the power switch, at the back of the
Or it may be some systemd bug.
It is definitely an *buntu 15.04 issue.
As I said, the workaround is to remove the computer's power cord from
the power socket, until the motherboard loses all its power.
--
You received this bug notification because you are a member of Kernel
Packages, which is
My post with all my typos fixed:
I have the same bug, error -110 USB error messages, and when I reboot,
the computer's UEFI initialisation during boot, at the USB device stage,
is very slow.
The problem gets fixed temporarily, if you unplug the computer from the
power socket (or turn off the
I have the sane bug= I have the same bug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1437492
Title:
boot stalls on USB detection errors
Status in linux package in Ubuntu:
13 matches
Mail list logo
