[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)
*** This bug is a duplicate of bug 1338706 *** https://bugs.launchpad.net/bugs/1338706 Here's an edited summary of the reply I got from the please contact our firmware engineers at xxx@xxx address; turns out there's no engineers there either, but at least we finally have a sane non-formletter reply which *for the first time* states that Samsung is aware of the issue and is working on a fix at the firmware level. Good news for everyone: We are just the SSD tech support. We are not the FW engineers. They are in Korea and have been aware of the issue since it first started being reported online. The latest stable Linux Kernal 4.0.5 successfully blacklists the affected drive(s) from queued TRIM. Linux can still use Sequential TRIM, so you’re not losing out on anything. We see that you are well aware that Marc Carino and Martin K. Petersen are in contact with Samsung on how to resolve the issue since it started. All we can say to users at this moment is that Linux is the only operating system that has this issue with the Queued TRIM. Linux is open source and can be modified by anyone, as such we do not support the OS. We recommend updating to the new kernel, as we have seen that other users have done so and it alleviated their issue(s). -- 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/1449005 Title: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q) Status in fstrim package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in fstrim source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in fstrim source package in Utopic: Invalid Status in linux source package in Utopic: Fix Committed Status in fstrim source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Bug description: Hi, after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the fstream command doesn't work anymore. Besides, there are a lot of file system errors and bad sectors reports. The problem is certainly caused by Samsung's firmware but I reported it as a bug because in Windows TRIM works normally after the upgrade. I have attached an image uploaded by a user who is experiencing the same problem. If you execute the command sudo fstrim / the console gets stuck. If you add that command in rc.local the boot is compromised. I really hope this problem could be solved. Thanks === break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)
*** This bug is a duplicate of bug 1338706 *** https://bugs.launchpad.net/bugs/1338706 Success! By not mentioning triggering keywords, the support person wasn't offered the normal form-letter reply, and had to actually read what I said. As a result, they replied with the direct email to their firmware department and asked me to send the technical report to them. I've now done so. Maybe we'll see a solution to this after all. -- 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/1449005 Title: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q) Status in fstrim package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in fstrim source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in fstrim source package in Utopic: Invalid Status in linux source package in Utopic: Fix Committed Status in fstrim source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Bug description: Hi, after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the fstream command doesn't work anymore. Besides, there are a lot of file system errors and bad sectors reports. The problem is certainly caused by Samsung's firmware but I reported it as a bug because in Windows TRIM works normally after the upgrade. I have attached an image uploaded by a user who is experiencing the same problem. If you execute the command sudo fstrim / the console gets stuck. If you add that command in rc.local the boot is compromised. I really hope this problem could be solved. Thanks === break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)
*** This bug is a duplicate of bug 1338706 *** https://bugs.launchpad.net/bugs/1338706 Got that braindead form-reply again, yet again blaming SAMSUNG'S FAULT on Linux: --- Thank you for contacting Samsung Support regarding your concerns and inquiries. We apologize for any inconvenience this may be causing you. Linux is the only operating system that has this issue with the Queued TRIM. Linux is open source and can be modified by anyone, as such we do not support the OS. We have seen with other customers that updating your kernel version to 4.0.5 addresses the issue. Thank you again for contacting Samsung Support and have a good day. DM CS20204 --- Time to re-send the message with *zero* mention of the word TRIM, because maybe they've got a trigger for the support-monkeys to auto- suggest using this response when queued trim is mentioned. -- 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/1449005 Title: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q) Status in fstrim package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in fstrim source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in fstrim source package in Utopic: Invalid Status in linux source package in Utopic: Fix Committed Status in fstrim source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Bug description: Hi, after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the fstream command doesn't work anymore. Besides, there are a lot of file system errors and bad sectors reports. The problem is certainly caused by Samsung's firmware but I reported it as a bug because in Windows TRIM works normally after the upgrade. I have attached an image uploaded by a user who is experiencing the same problem. If you execute the command sudo fstrim / the console gets stuck. If you add that command in rc.local the boot is compromised. I really hope this problem could be solved. Thanks === break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)
*** This bug is a duplicate of bug 1338706 *** https://bugs.launchpad.net/bugs/1338706 My final attempt at contacting Samsung's braindead support monkeys, this time without any mention of the word trim, and I decided to lie and say that I'm a hardware controller manufacturer who discovered the flaw to hopefully get the monkey to take notice. Let's see the support monkeys screw this up again - I am SURE they will, as they've repeatedly done so for *every one of us* who has tried contacting them. And if/when that happens, I'll do one last effort and take this up with the two guys above who have direct contacts at Samsung, who can bypass the monkey brigade. --- I am working on programming a new hardware RAID controller, and one of my test disks is a Samsung 850 PRO 500gb which shipped with firmware EXM02B6Q from the factory. During my testing, I probe all the drives and discovered that your firmware revision includes SATA 3.2 spec features, but that they are not properly implemented. The drive sets ATA IDENTIFY's word 77, bit 6 to 1 (true), which means RECEIVE/SEND FPDMA QUEUED supported. But the firmware does NOT actually support RECV/SEND FPDMA QUEUED, and just wrongly claims that it does. If you try to retrieve log 13h the drive errors out, but the spec says that if RECV/SEND FPDMA is supported then log 13h MUST also be supported. So this is a case of Samsung's firmware department ticking a flag for all the shiny SATA 3.2 features, and not actually making sure they implemented them all. The false advertisement of ATA IDENTIFY word 77 bit 6, without actually supporting that new feature, means that the drive is severely broken in multiple ways. Two possible solutions to this situation: 1) A firmware update which sets ATA IDENTIFY's word 77, bit 6 to 0 (FALSE!) instead, to PROPERLY show that the drive does NOT support SATA 3.2 FPDMA QUEUED features. 2) Alternatively, a firmware update which implements FPDMA QUEUED, log 13h, etc, so that the drive actually supports what it *claims* it does. Of these two, #1 is the easiest and makes the most sense. Either way, there's a problem in the firmware and it needs a fix. Thank you for your time, Richard -- 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/1449005 Title: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q) Status in fstrim package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in fstrim source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in fstrim source package in Utopic: Invalid Status in linux source package in Utopic: Fix Committed Status in fstrim source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Bug description: Hi, after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the fstream command doesn't work anymore. Besides, there are a lot of file system errors and bad sectors reports. The problem is certainly caused by Samsung's firmware but I reported it as a bug because in Windows TRIM works normally after the upgrade. I have attached an image uploaded by a user who is experiencing the same problem. If you execute the command sudo fstrim / the console gets stuck. If you add that command in rc.local the boot is compromised. I really hope this problem could be solved. Thanks === break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)
*** This bug is a duplicate of bug 1338706 *** https://bugs.launchpad.net/bugs/1338706 I have now sent a second email to Samsung's support, this time being much more detailed about *exactly* why their drive is broken. If they keep coming back with their retarded form-reply again, I will just keep sending it, and will be talking to the two guys mentioned earlier who have direct contacts at Samsung. Here is the new email (to save time, I copied heavily from my previous post here on this thread so readers will recognize lots of segments): --- My Samsung 850 PRO 500gb drive came shipped with firmware EXM02B6Q from the factory. This firmware revision includes SATA 3.2 spec features, but they are not properly implemented. The drive sets ATA IDENTIFY's word 77, bit 6 to 1 (true), which means RECEIVE/SEND FPDMA QUEUED supported. But the firmware does NOT actually support RECV/SEND FPDMA QUEUED, and just wrongly claims that it does. If you try to retrieve log 13h the drive errors out, but the spec says that if RECV/SEND FPDMA is supported then log 13h MUST also be supported. So this is a case of Samsung's firmware department ticking a flag for all the shiny SATA 3.2 features, and not actually making sure they implemented them all. A secondary problem of you incorrectly setting ATA IDENTIFY's word 77, bit 6 to 1 (true) is that FPDMA QUEUED TRIM *must* ALSO be supported if you do that. But the drive does not support queued trim. So the false advertisement of ATA IDENTIFY word 77 bit 6, without actually supporting that new feature, means that the drive is severely broken in multiple ways. Two possible solutions to this situation: 1) A firmware update which sets ATA IDENTIFY's word 77, bit 6 to 0 (FALSE!) instead, to PROPERLY show that the drive does NOT support SATA 3.2 FPDMA QUEUED features. 2) Alternatively, a firmware update which implements FPDMA QUEUED, log 13h, FPDMA QUEUED TRIM, etc, so that the drive actually supports what it *claims* it does. Of these two, #1 is the easiest and makes the most sense. Either way, there's a problem in the firmware and it needs a fix. Thank you for your time, Mark --- -- 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/1449005 Title: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q) Status in fstrim package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in fstrim source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in fstrim source package in Utopic: Invalid Status in linux source package in Utopic: Fix Committed Status in fstrim source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Bug description: Hi, after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the fstream command doesn't work anymore. Besides, there are a lot of file system errors and bad sectors reports. The problem is certainly caused by Samsung's firmware but I reported it as a bug because in Windows TRIM works normally after the upgrade. I have attached an image uploaded by a user who is experiencing the same problem. If you execute the command sudo fstrim / the console gets stuck. If you add that command in rc.local the boot is compromised. I really hope this problem could be solved. Thanks === break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12
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 Samsung:
https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/comments/55
You can also check prior comments by me and others in that thread, to
see more information.
--
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 xfermode (err_mask=0x40) on upstream kernels = 3.12
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Utopic:
Fix Committed
Status in linux source package in Vivid:
Fix Committed
Status in linux source package in Wily:
Invalid
Bug description:
[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.
#!/bin/bash
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
for i in {0..10} ; do
cp -r linux linux$i
done
rm -rf linux*
echo sudo fstrim requires your password
sudo fstrim ./
[Regression Potential]
* There is very little regression potential as this change simply
prevents NCQ trim from being used on Samsung 8** drives.
[Other Info]
* Commit is upstream.
* Greatly increasing the timeout for the drives seems to relieve the timeout
errors. This may be due to trimming large numbers of sectors with single
commands. It may be prudent for future upstream to break up large trims into
multiple requests on smaller regions.
===Original Bug description ==
Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-30-generic 3.13.0-30.55
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: user 2131 F pulseaudio
CurrentDesktop: Unity
Date: Mon Jul 7 20:01:28 2014
HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35
InstallationDate: Installed on 2014-06-22 (14 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic
root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.13.0-30-generic N/A
linux-backports-modules-3.13.0-30-generic N/A
linux-firmware 1.127.4
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0901
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3N78-EM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)
Turns out this I support Queued TRIM! issue is a year old and affected the entire previous generation too: Discovered by kernel devs in the 840 Pro and 840 Evo: https://bugzilla.kernel.org/show_bug.cgi?id=72341 and also discussed here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706 Here is another brand (WD) doing the same thing in late 2013: http://lists.infradead.org/pipermail/linux-arm- kernel/2013-October/203508.html The bottom line is: Samsung SSDs firmware have been updated to SATA 3.2 spec, which includes Queued TRIM, and they advertise that they support it, but in reality the firmware doesn't process those queued trims properly and seems to eat random blocks instead, thus destroying random data. From what I understand from the first link (see comment 48), these drives set ATA IDENTIFY's word 77, bit 6 to 1, which means RECEIVE/SEND FPDMA QUEUED supported. That FPDMA QUEUED is the thing used to send a queued TRIM. The firmware does not actually support RECV/SEND FPDMA QUEUED, and just wrongly claims that it does. If you try to retrieve log 13h the drive errors out, but the spec says that if RECV/SEND FPDMA is supported then log 13h MUST also be supported. So this is a clear case of Samsung's firmware department ticking a flag for all the shiny SATA 3.2 features, and not actually making sure they implemented them all. Very, very shoddy. Since this problem affects all modern Samsung SSDs, it's really up to Samsung to fix their firmware. It's NOT up to the operating systems to blacklist misbehaving drives. Are we really gonna have to wait until Windows does Queued TRIM and millions of people lose data, for them to react to their broken firmware? It has proven futile to talk to Samsung via their regular support contact form. This bug report needs to come from someone with better access to intelligent humans at Samsung (they must exist, right?). I know of only two people with direct access to Samsung firmware people: - Marc Carino marc.ce [at] gmail.com , who wrote in kernel.org bug #72341 on 2014-05, that he was reaching out to Samsung's firmware department about the problem. - Martin K. Petersen from Oracle martin.petersen [at] oracle.com , who wrote on the kernel mailing list on 2015-05-04 about contacting Samsung. ** 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1449005 Title: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q) Status in fstrim package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in fstrim source package in Trusty: Invalid Status in linux source package in Trusty: Confirmed Status in fstrim source package in Utopic: Invalid Status in linux source package in Utopic: Confirmed Status in fstrim source package in Vivid: Invalid Status in linux source package in Vivid: Confirmed Bug description: Hi, after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the fstream command doesn't work anymore. Besides, there are a lot of file system errors and bad sectors reports. The problem is certainly caused by Samsung's firmware but I reported it as a bug because in Windows TRIM works normally after the upgrade. I have attached an image uploaded by a user who is experiencing the same problem. If you execute the command sudo fstrim / the console gets stuck. If you add that command in rc.local the boot is compromised. I really hope this problem could be solved. Thanks === break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)
Followup: My email to Samsung clearly and succinctly stated that there is a bug in their firmware, where it wrongly reports I support NCQ TRIM! but it really doesn't, and that they introduced the bug recently. I said nothing about Linux. Their mentally retarded response: Dear Customer, Thank you for contacting Samsung Support regarding your concerns and inquiries. We apologize for any inconvenience this may be causing you. Since Linux is open source, Samsung does not support the OS. All we can tell you is that you can disable Queued TRIM in Linux. Linux will then start using Sequential Trim, which is similar to how Windows does TRIM. Newer versions of Linux kernels blacklist the drive so that Queued TRIM automatically is disabled. Thank you again for contacting Samsung Support and have a good day. DM CS20204 In other words: Our product is broken, so just tell the OS not to use the broken feature and hey presto you're a winner! Now stop bugging us with your Loonixes and stuff. Can we try to get press attention on this? Random corruption caused by regular TRIM operation is almost as serious as the 840 Evo's data retention issue. -- 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/1449005 Title: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q) Status in fstrim package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in fstrim source package in Trusty: Invalid Status in linux source package in Trusty: Confirmed Status in fstrim source package in Utopic: Invalid Status in linux source package in Utopic: Confirmed Status in fstrim source package in Vivid: Invalid Status in linux source package in Vivid: Confirmed Bug description: Hi, after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the fstream command doesn't work anymore. Besides, there are a lot of file system errors and bad sectors reports. The problem is certainly caused by Samsung's firmware but I reported it as a bug because in Windows TRIM works normally after the upgrade. I have attached an image uploaded by a user who is experiencing the same problem. If you execute the command sudo fstrim / the console gets stuck. If you add that command in rc.local the boot is compromised. I really hope this problem could be solved. Thanks === break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)
The exact same bug also affects the 850 PRO: http://www.spinics.net/lists/linux-ide/msg50342.html Originally, they came with EXM01B6Q, which reports I do NOT support NCQ TRIM!. Then, samsung released EXM02B6Q, which wrongly reports I SUPPORT NCQ TRIM!, but of course they don't; the data corrupts if you try. Samsung then pulled EXM02B6Q from their website for a DIFFERENT issue: The firmware update bricked many devices. But the problem is that new 850 PROs from the factory come with the new, buggy firmware preinstalled. And Samsung are not yet aware that their NCQ TRIM is buggy. I have contacted Samsung via their regular tech support form and pointed out the NCQ TRIM bug and hopefully they will fix it. I also know that Martin K. Petersen from Oracle has contacts at Samsung and is talking to them to get it resolved in their firmware, see here: http://permalink.gmane.org/gmane.linux.ide/59802 (Full thread: http://comments.gmane.org/gmane.linux.ide/59791) I hope Samsung will get on this swiftly, and at least release an intermediary firmware which disables NCQ TRIM until they're ready to re- add it. -- 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/1449005 Title: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q) Status in fstrim package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in fstrim source package in Trusty: Invalid Status in linux source package in Trusty: Confirmed Status in fstrim source package in Utopic: Invalid Status in linux source package in Utopic: Confirmed Status in fstrim source package in Vivid: Invalid Status in linux source package in Vivid: Confirmed Bug description: Hi, after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the fstream command doesn't work anymore. Besides, there are a lot of file system errors and bad sectors reports. The problem is certainly caused by Samsung's firmware but I reported it as a bug because in Windows TRIM works normally after the upgrade. I have attached an image uploaded by a user who is experiencing the same problem. If you execute the command sudo fstrim / the console gets stuck. If you add that command in rc.local the boot is compromised. I really hope this problem could be solved. Thanks === break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210361] Re: [Samsung NP540U3C-A01UB] Incorrect battery/power status and missing /proc/acpi/battery
Hello, I have the same problem with Samsung NP530. Could I do something that could help you to resovle this 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/1210361 Title: [Samsung NP540U3C-A01UB] Incorrect battery/power status and missing /proc/acpi/battery Status in “linux” package in Ubuntu: Incomplete Bug description: Hi after the last Ubuntu upgrade, I am having these power related problems: 1) the initial battery/power indicator does not change when the laptop is plugged/unplugged. If the laptop was on battery, the indicator continues to show it after I plug it in, and vice versa. 2) Sleep never works when the lid is closed, however it can be invoked using /etc/acpi/sleep.sh or selecting suspend from the menu. 3) /proc/acpi/battery got disappeared I am attaching the following: - version.log - dmesg | grep ACPI - dmidecode - lshw - lscpu -vnvn - /proc/acpi when plugged - /proc/acpi when on battery - uname -a Ubuntu is my primary OS so I will appreciate any suggestions for resolving this issue. Thanks in advance! --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: memo 2111 F pulseaudio /dev/snd/pcmC0D0p: memo 2111 F...m pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=acb42b41-ef8d-4cc3-9746-06868ce9e5d3 InstallationDate: Installed on 2012-11-09 (272 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=e5741332-e4ea-46e4-84e9-b72b1cadc742 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-27 (104 days ago) UserGroups: adm cdrom debian-tor dip fuse lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 11/15/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P05ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP540U3C-A01UB dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP05ABH:bd11/15/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP540U3C-A01UB:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2904 F pulseaudio CasperVersion: 1.336 DistroRelease: Ubuntu 13.10 LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130825) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash -- ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 RelatedPackageVersions: linux-restricted-modules-3.11.0-3-generic N/A linux-backports-modules-3.11.0-3-generic N/A linux-firmware1.113 Tags: saucy Uname: Linux 3.11.0-3-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/15/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P05ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP540U3C-A01UB dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP05ABH:bd11/15/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP540U3C-A01UB:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug
