All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Günter Waller" <g.wal@web.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Tejun Heo <tj@kernel.org>, linux-ide@vger.kernel.org
Subject: Re: Samsung 840 EVO
Date: Mon, 04 May 2015 18:19:45 +0200	[thread overview]
Message-ID: <55479C21.8020608@web.de> (raw)
In-Reply-To: <yq16188tl8v.fsf@sermon.lab.mkp.net>

[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]

Hi Martin,
here you are - the second command, however, did not seem to produce
anything useful.
But beware: this is the old firmware, EXT0BB6Q, i.e. the one with the
performance issues (not seen on my machine yet), not the one that causes
the problems with fstrim - named EXT0DB6Q.
As I mentioned I shy away from upgrading at this point, not knowing
whether my Linux system runs fstrim somewhere behind my back. I am not
that deeply involved in the inner workings of the kernel as you guys.
This is my bread and butter machine, I'd rather not expose it to risk if
I can help it.
Cheers
Günter


Am 04.05.2015 um 17:28 schrieb Martin K. Petersen:
>>>>>> "Günter" == Günter Waller <g.wal@web.de> writes:
> 
> Günter> the subject Samsung SSD is having performance issues with "old
> Günter> data" which Samsung now addresses with a new firmware.
> 
> I wonder if they enabled the same botched queued discard that they did
> in 850 Pro?
> 
> If someone has an 840 Evo with the new firmware it would be helpful for
> us to receive the output of:
> 
> # hdparm -I /dev/sdN
> # smartctl -l gplog,0x13 /dev/sdN
> 
> I think I might have an 840 in the lab. Will head down and update it
> later this week unless somebody beats me to providing the information
> above.
> 

[-- Attachment #2: 840evo.txt --]
[-- Type: text/plain, Size: 3616 bytes --]

hdparm -I /dev/sda
/dev/sda:

ATA device, with non-removable media
	Model Number:       Samsung SSD 840 EVO 250GB               
	Serial Number:      S1DBNSBF767383T     
	Firmware Revision:  EXT0BB6Q
	Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
	Used: unknown (minor revision code 0x0039) 
	Supported: 9 8 7 6 5 
	Likely used: 9
Configuration:
	Logical		max	current
	cylinders	16383	16383
	heads		16	16
	sectors/track	63	63
	--
	CHS current addressable sectors:   16514064
	LBA    user addressable sectors:  268435455
	LBA48  user addressable sectors:  488397168
	Logical  Sector size:                   512 bytes
	Physical Sector size:                   512 bytes
	Logical Sector-0 offset:                  0 bytes
	device size with M = 1024*1024:      238475 MBytes
	device size with M = 1000*1000:      250059 MBytes (250 GB)
	cache/buffer size  = unknown
	Nominal Media Rotation Rate: Solid State Device
Capabilities:
	LBA, IORDY(can be disabled)
	Queue depth: 32
	Standby timer values: spec'd by Standard, no device specific minimum
	R/W multiple sector transfer: Max = 1	Current = 1
	DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
	     Cycle time: min=120ns recommended=120ns
	PIO: pio0 pio1 pio2 pio3 pio4 
	     Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
	Enabled	Supported:
	   *	SMART feature set
	    	Security Mode feature set
	   *	Power Management feature set
	   *	Write cache
	   *	Look-ahead
	   *	Host Protected Area feature set
	   *	WRITE_BUFFER command
	   *	READ_BUFFER command
	   *	NOP cmd
	   *	DOWNLOAD_MICROCODE
	    	SET_MAX security extension
	   *	48-bit Address feature set
	   *	Device Configuration Overlay feature set
	   *	Mandatory FLUSH_CACHE
	   *	FLUSH_CACHE_EXT
	   *	SMART error logging
	   *	SMART self-test
	   *	General Purpose Logging feature set
	   *	WRITE_{DMA|MULTIPLE}_FUA_EXT
	   *	64-bit World wide name
	    	Write-Read-Verify feature set
	   *	WRITE_UNCORRECTABLE_EXT command
	   *	{READ,WRITE}_DMA_EXT_GPL commands
	   *	Segmented DOWNLOAD_MICROCODE
	   *	Gen1 signaling speed (1.5Gb/s)
	   *	Gen2 signaling speed (3.0Gb/s)
	   *	Gen3 signaling speed (6.0Gb/s)
	   *	Native Command Queueing (NCQ)
	   *	Phy event counters
	   *	READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
	   *	DMA Setup Auto-Activate optimization
	    	Device-initiated interface power management
	   *	Asynchronous notification (eg. media change)
	   *	Software settings preservation
	   *	SMART Command Transport (SCT) feature set
	   *	SCT Write Same (AC2)
	   *	SCT Error Recovery Control (AC3)
	   *	SCT Features Control (AC4)
	   *	SCT Data Tables (AC5)
	   *	reserved 69[4]
	   *	DOWNLOAD MICROCODE DMA command
	   *	SET MAX SETPASSWORD/UNLOCK DMA commands
	   *	WRITE BUFFER DMA command
	   *	READ BUFFER DMA command
	   *	Data Set Management TRIM supported (limit 8 blocks)
Security: 
	Master password revision code = 65534
		supported
	not	enabled
	not	locked
		frozen
	not	expired: security count
		supported: enhanced erase
	2min for SECURITY ERASE UNIT. 8min for ENHANCED SECURITY ERASE UNIT. 
Logical Unit WWN Device Identifier: 50025388a05d2afa
	NAA		: 5
	IEEE OUI	: 002538
	Unique ID	: 8a05d2afa
Checksum: correct

*************************************************************
smartctl -l gplog,0x13 /dev/sda
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-51-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

General Purpose Log 0x13 does not exist (override with '-T permissive' option)

  parent reply	other threads:[~2015-05-04 16:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04 12:38 Samsung 840 EVO Günter Waller
2015-05-04 15:28 ` Martin K. Petersen
2015-05-04 15:49   ` Sven Köhler
2015-05-04 16:21     ` Martin K. Petersen
2015-05-04 16:27       ` Sven Köhler
2015-05-04 16:35         ` Martin K. Petersen
2015-05-04 16:19   ` Günter Waller [this message]
2015-05-04 16:24     ` Martin K. Petersen
2015-05-04 16:37       ` Günter Waller
2015-05-04 16:47         ` Martin K. Petersen
2015-05-04 15:45 ` Sven Köhler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55479C21.8020608@web.de \
    --to=g.wal@web.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.