Can any one check if Queued TRIM issue is resolved in EXM03B6Q firmware
(available as of October 2016) for 850 Pro?
I'm not expecting Queued TRIM to work properly, but may be it is not advertised
as supported any more?
--
You received this bug notification because you are a member of Ubuntu
Bug
@evan
No, you are seeing a different or new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
set xfermode (err
Does this result in anyone not being able to suspend?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
set xfermode
Hi Chris,
I filed the bug, sorry I don't know how to subscribe you to it ...
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530459
all the best, John
On 1 January 2016 at 05:02, Christopher M. Penalver
wrote:
> JohnShep, as this report is closed, if you are having an issue, you will want
JohnShep, as this report is closed, if you are having an issue, you will want
to file a new report via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on this, please see https://wiki.ubuntu.com/ReportingBugs.
--
You received this bug notification because you are
I think it is still there in a fresh Wily install
uname -a
Linux john-Aspire-X3812 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
dmesg | grep ata4
[ 6846.008190] ata4: hard resetting link
[ 6846.328019] ata4: SATA link up 3.0 Gbps (SStatus 123 S
@Dave Chiluk
No, I didn't. I have no that configuration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
set xfermo
@Andrei Demin,
Have you opened a separate case for Samsung drives + RAID 0 + trim =
corruption? If so what is that bug number?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung
Yes, it's a different issue. Algolia weren't even using queues TRIM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
Or this patch fixes another trim bug... Then i'm sorry.
"The queued TRIM issue with Samsung drives remains open but it has nothing
whatsoever to do with the Algolia bug."
http://techreport.com/news/28724/samsung-docs-detail-linux-trim-bug-and-fix
--
You received this bug notification because yo
This patch from Samsung fixes trim bug in kernel.
1.
http://techreport.com/news/28674/samsung-says-data-eating-trim-bug-is-a-linux-kernel-problem
2. http://www.spinics.net/lists/raid/msg49440.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
On 08/12/2015 03:59 AM, Andrei Demin wrote:
> Seems Samsung fixed this bug in kernel
> (https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f3f5da624e0a891c34d8cd513c57f1d9b0c7dadc)
> and blacklist is no longer needed. Maybe we should remove blacklist and
> apply this patch i
Seems Samsung fixed this bug in kernel
(https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f3f5da624e0a891c34d8cd513c57f1d9b0c7dadc)
and blacklist is no longer needed. Maybe we should remove blacklist and
apply this patch instead?
--
You received this bug notification beca
Having same problem on kernel 3.19.0-25-generic/Ubuntu 15.04 and no
solution so far. :((
[0.553706] ata5: SATA max UDMA/133 abar m2048@0xf3216000 port 0xf3216300
irq 26
[0.872359] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[0.873019] ata5.00: failed to get NCQ Send/Recv Lo
@fabiocasi
As far as I understand updated ubuntu kernels are available in mint as I think
they pull from the same archives. Why don't you try enabling proposed and
checking since you are clearly running mint. Also per comment 75
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706/com
Hi All,
then the kernel 3.13 has the fix, but what about the 3.16 used as default
kernel in Linux MINT 17.2 "Rafaela" ???
Will be available a 3.16-xxx that fix th bug??
In the meantime is better to don't do fstrim???
--
You received this bug notification because you are a member of Ubuntu
Bugs
This bug was fixed in the package linux - 3.19.0-22.22
---
linux (3.19.0-22.22) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1465755
[ Tai Nguyen ]
* SAUCE: power: reset: Add syscon reboot device node for APM X-Gene
platform
- LP: #1463211
[
This bug was fixed in the package linux - 3.13.0-57.95
---
linux (3.13.0-57.95) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1466592
[ Brad Figg ]
* Merged back Ubuntu-3.13.0-55.94 regression fix for security release
linux (3.13.0-56.93) trusty;
This bug was fixed in the package linux - 3.16.0-43.58
---
linux (3.16.0-43.58) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1466792
[ Brad Figg ]
* Merged back Ubuntu-3.16.0-41.57 regression fix for security release
linux (3.16.0-42.56) utopic;
This bug was fixed in the package linux - 3.19.0-22.22
---
linux (3.19.0-22.22) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1465755
[ Tai Nguyen ]
* SAUCE: power: reset: Add syscon reboot device node for APM X-Gene
platform
- LP: #1463211
[
This bug was fixed in the package linux - 3.13.0-57.95
---
linux (3.13.0-57.95) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1466592
[ Brad Figg ]
* Merged back Ubuntu-3.13.0-55.94 regression fix for security release
linux (3.13.0-56.93) trusty;
This bug was fixed in the package linux - 3.16.0-43.58
---
linux (3.16.0-43.58) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1466792
[ Brad Figg ]
* Merged back Ubuntu-3.16.0-41.57 regression fix for security release
linux (3.16.0-42.56) utopic;
You need to check you firmware version:
> sudo hdparm -i /dev/sda | grep FwRev
Model=Samsung SSD 840 EVO 250GB, FwRev=EXT0DB6Q, SerialNo=x
If you have the latest rev EXT0DB6Q, then you need the fixed kernel
mentioned above.
--
You received this bug notification because you are a member of U
Hi All,
In my Linux Mint 17.1
if I do:
sudo smartctl -a /dev/sda | grep SATA\ Version
I receive:
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
I don't understand if this means that I'M NOT affected to this Bug.
Can I do :
fstrim -v / >> $LOG
without risk??
--
You received this bug
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask
@IoannisVranos, thanks for the link, but I'm already on the latest firmware
version for this drive (DXT09B0Q).
Maybe this drive simply does not support getting NCQ Log Emask...
[1.439428] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
--
You received this bug notification because you ar
Trusty LTS Kernel 3.13.0-57 works for me too for a Samsung SSD 840 Pro.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Trusty LTS Vivid Kernel 3.19.0-22.22 works for me too for a Samsung SSD
840 Pro.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x
@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 Ubuntu
Bugs, which is subscribed to
So, I already use the proposed (3.19.0-22-generic) kernel on Vivid
Vervet, I installed it days ago. The discard mount option and the fstrim
command are works now, without any problem. Please do not drop the path,
but move this kernel to the stable repository.
--
You received this bug notification
"If the problem is solved, change the tag 'verification-needed-trusty' to
'verification-done-trusty'.
If verification is not done by 5 working days from today, this fix will be
dropped from the source code, and this bug will be closed."
I really do not understand those sentences... wha
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
I've updated to the latest kernel via Vivid Proposed (linux-image-
extra-3.19.0-22-generic 3.19.0-22.22) which per commit log should fix
the error, but I still see it:
$ dmesg | grep ata
[0.00] BIOS-e820: [mem 0xc8f9e000-0xc8ff] ACPI data
[0.00] ACPI: SSDT 0x0
In the meantime instead of modifying your boot command line you could
test the 3.13 ppa that contains the fix that will eventually make it
into the updated kernel.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706/comments/34
--
You received this bug notification because you are a mem
@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.
I
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
set xfe
You can modify single ata channels too like I do, it works fine:
/etc/default/grub
GRUB_CMDLINE_LINUX="libata.force=10:noncq,9:noncq"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Sa
@Cyberbob, I'm in the same situation:
SSD 840 EVO and Linux Mint 17.1 Mate Edition...
*If you upgrade your 840 firmware you will need to **rebuild a custom*
*kernel with the proper ATA HORKAGE, as I do since the upgrade,*
*or you will need to use libata.force=noncq (**which I discourage)**.*
*Do
@Cyberbob, I'm in the same situation:
SSD 840 EVO and Linux Mint 17.1 Mate Edition...
If you upgrade your 840 firmware you will need to rebuild a custom
kernel with the proper ATA HORKAGE, as I do since the upgrade,
or you will need to use libata.force=noncq (which I discourage).
Don't know if a
Hi All
First of all thanks for your job!
I have an SSD 840 EVO firmware DXT06B0Q (NOT yet update cause this
problem!!)
I'm using linux MINT 17.1 64bit with Kernel 3.13.0-37
Have I to upgrado to kernel 3.19 or will be available an official Kernel
update for the 3.13.** default on Mint 17.1 OR Wil
Does someone know which kernel version introduced the "queued trim"? My
3.2 kernel seems to be not affected by this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD
This bug was fixed in the package linux - 3.19.0-22.22
---
linux (3.19.0-22.22) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1465755
[ Tai Nguyen ]
* SAUCE: power: reset: Add syscon reboot device node for APM X-Gene
platform
- LP: #1463211
[
** Changed in: linux (Ubuntu Wily)
Status: Invalid => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 fail
There are problems with the 850 Pro as well, see, e.g.:
http://ubuntuforums.org/showthread.php?t=2282808&p=13305283
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 fail
Through, script in OP doesn't work correctly.
fstrim: ./: FITRIM ioctl failed: input/output error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send
Samsung SSD 850 Pro, EXM02B6Q, Trusty with 3.13.0-55. There is no errors
in dmesg, multiple fstrim operatins runs just fine. Strange.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Sam
@chiluk: yes, i did before adding libata.force=noncq to my kernel
command line.
another article on SSDs from this manufacturer has further information:
https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/
--
You received this bug notification because you are a member of Ubuntu
Bu
@gimpsmart your e-mail is well written, but I don't believe it applies
to the EXT0DB6Q for the 840 EVO.
We no longer receive the "failed to get NCQ Send/Recv Log Emask 0x1"
errors with this level of firmware which implies that the log has been
correctly implemented. Samsung may simply need to re-
I have reached out to Samsung again to hopefully get this falsely
advertised feature fixed at the firmware level, since the firmware is at
fault for advertising FPDMA QUEUED support (which is what QUEUED TRIM
uses), even though it doesn't support it at all.
Read this post for the letter I sent to
The fix is in kernel 4.0.5 and I can confirm it fixes the problem. Been
running the latest firmware on my EVO 840 SSD for a few days now and
everything looks good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
@loannis, How do you know you have data loss, and how do you know that
Ubuntu/Linux is the reason for that data loss?
None of the error message I've seen posted to the cases related to
Samsung SSDs imply that linux is causing data loss when running trim.
--
You received this bug notification bec
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
The command is
fstrim-all
in *buntus 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
set xfermode (err_mas
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 yo
@loannis,
That is correct it will be in the -21 build of the vivid kernel, . We
have 3 week kernel integration and test cycles. There will be an
automated message posted here when the kernel that contains the fix is
pushed to the -proposed archives.
It should be noted that most of the Ubuntu Ke
I should say that whenever upgrading firmware on a drive please make
sure you have recent backups of your data, especially considering the
nature of this issue.
It's very possible that the electron leakage in the NAND may have
already corrupted your data, and the new firmware may not be able to
re
** Changed in: linux (Ubuntu Wily)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed
http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/log/?h=master-next
Seems this one has been commited after the -20 build :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a mem
** Description changed:
[Impact]
* Users with Samsung 8** SSD drives see miscellaneous errors and
warning messages in the logs depending on the firmware level of the
drive while booting or after running trim.
[Test Case]
* Run this script, and then check logs for errors.
#
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: linux (Ubuntu Utopic)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: linux (Ubuntu Vivid)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: linux (Ubuntu W
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Vivid)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Utopic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Wily)
Importan
** Description changed:
[Impact]
- * Users with Samsung 8** SSD drives see miscellaneous errors and
+ * Users with Samsung 8** SSD drives see miscellaneous errors and
warning messages in the logs depending on the firmware level of the
drive while booting or after running trim.
[Tes
** Description changed:
+ [Impact]
+
+ * Users with Samsung 8** SSD drives see miscellaneous errors and
+ warning messages in the logs depending on the firmware level of the
+ drive while booting or after running trim.
+
+ [Test Case]
+
+ * Run this script, and then check logs for errors.
+ #
** Changed in: linux (Ubuntu)
Milestone: None => trusty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
I've integrated the 9a9324d396967 NO NCQ Trim fix into this ppa.
https://launchpad.net/~chiluk/+archive/ubuntu/samsungncqtrim
Please test it and report back here either way. I'll remove the ppa
when the fix hits the kernels in -updates.
--
You received this bug notification because you are a m
So after some additional testing it looks like NCQ Trim on the Samsung
8** drives still has "issues".
It looks like it mostly works, but once the drive gets saturated with a
large trim *(i.e. deleting 5 kernel trees, and then fstrimming), the
kernel starts to hit timeouts. Increasing the timeout
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0
I'm running 3.13.0-53-generic from ubuntu, with the latest EXT0DB6Q, on
a q87 motherboard connected to sata 3 connectors, and am not seeing the
original issue.
[1.108155] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[1.110025] ata2.00: supports DRM functions and may not be fully
I am running the EXT0DB6Q firmware on my 840 EVO + 3.13.0-53 , and think
this issue may have cleared up somewhat.
The first time I ran
chiluk@beastly:/etc/cron.weekly$ sudo fstrim /home
I got.
^[OQfstrim: /home: FITRIM ioctl failed: Input/output error
The Log showed
[164782.716062] ata2.00: ex
** Attachment added: "dmesg subset (relevant disc is ata2)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706/+attachment/4381943/+files/2015-04-23-dmesg-850pro-sata-errors-lp.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm on Ubuntu 12.04 with kernel 3.13.0-49-generic and experiencing the
same problem with a freshly bought Samsung SSD 850 Pro and can confirm
what already has been stated at
https://bugzilla.kernel.org/show_bug.cgi?id=72341.
- Enabled NCQ and TRIM (=queued TRIM) causes errors and a fallback after
I have the same on Ubuntu 14.04 and 3.17.8
Mar 12 20:36:21 icanseeyou kernel: [2.344273] scsi host1: ahci
Mar 12 20:36:21 icanseeyou kernel: [2.344352] scsi host2: ahci
Mar 12 20:36:21 icanseeyou kernel: [2.33] scsi host3: ahci
Mar 12 20:36:21 icanseeyou kernel: [2.344532] scsi
By the way, for testing Trim support, just get this script below, and
run it, it's a lot simpler to use, instead of all the reading and doing
from the link binjarac (coppensmeister) provided...
wget -O /tmp/test_trim.sh
"https://sites.google.com/site/lightrush/random-1/checkiftrimonext4isenabledan
It would really be great if Canonical, or the developers could contact
Samsung, if anyone knows how?
I wonder if Samsung is even aware of this situation, or if they really
care. I'd hate to think we're going to have to sit around and wait on
this, because this has been going in their SSDs already
During a fresh install today (14.04.1 on Samsung 850 Pro) I also hit this bug.
I noticed the same issue on a 13.04 install on a Samsung 840 Pro (after fw
upgrade) that I am running for quite some time now.
Allthough running fstrim manually is still working, I found this litte test
which seems to
Does anyone have any contact information the end-user can contact
Samsung over this matter, and I don't mean supp...@samsung.com that
email address is pointless...
The queued trim support is broke on the SSD's from Samsung and the fix
is going to have to come from them, but I'm wondering if they'r
This has been reported on the Kernel Bug Tracker;
https://bugzilla.kernel.org/show_bug.cgi?id=72341
According to them queued trim support is broke on the drive.
I also experienced this on an 840 Pro and now I have the same issue on
an 850 Pro.
It's my understanding we have to wait on a fix from
tilo kremer, thank you for your comment. So your problem and hardware may be
tracked, could you please file a new report with Ubuntu by executing the
following in a terminal while booted into the default Ubuntu kernel (not a
mainline one) via:
ubuntu-bug linux
For more on this, please read the
see https://bugzilla.kernel.org/show_bug.cgi?id=72341
** Bug watch added: Linux Kernel Bug Tracker #72341
http://bugzilla.kernel.org/show_bug.cgi?id=72341
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
The updated firmware does not solve this for me, the message is still there:
3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 x86_64 x86_64
x86_64 GNU/Linux
ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
--
You received this bug notification because you are a member of Ubuntu
B
I have solved the problem with an update to the Firmware.
I have followed the instructions at this page (as Samsung tools only works from
Windows/DOS):
https://www.content-space.de/dokuwiki/blog/2012/updating_a_samsung_ssd_840_firmware_with_linux
I am happily running a 3.13 kernel version:
Linux
Augusto Bortoluzzi, could you please test 3.18-rc3 and advise to the
results?
If reproducible, the next step is to fully commit bisect from kernel
3.12 to 3.13 in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis
Dear Sirs,
I have the same drive model, Mint 17 gives me the same error, so does Windows
7, well not exactly the same error but it is not able to sync at sata 3 speeds
and goes down to sata 1 ( same happens in linux ) would this be the same issue?
--
You received this bug notification because y
I have tried with a 3.17 kernel and still got the same error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
set x
I am getting the same error. I have tried as well a Live USB of Ubuntu
14.10 Beta, which fails to detect the drive (I can't risk installing the
whole system as this is my "production" computer).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I am also getting these errors with mint17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
set xfermode (err_mask=0
When I use dmesg I see the following lines:
allard@ubuntu-laptop-allard:~$ dmesg | grep ata1
[1.196018] ata1: SATA max UDMA/133 abar m2048@0xc2617000 port 0xc2617100
irq 42
[1.515247] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[1.515449] ata1.00: supports DRM functions and
Please could you confirm this bug to official LKML
https://lkml.org/lkml/2014/7/16/724
so maybe someone could notice it or could address it to the right person. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
This really scared the hell out of me. My first SDD and now it's going
to die I thought. Thanks for pointing out it was a bug. Tested on Ubuntu
14.04.1 32/64. On both cases it shows the error many times. Some days it
repeats the error endlessly.
--
You received this bug notification because you a
I reported the problem to linux-kernel ML:
https://lkml.org/lkml/2014/7/16/724
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1
98 matches
Mail list logo