[ SOLVED ] Samsung Evo SSD Kernel Bug

[Duckeenie]

Oh yeah...I do have the 850. I'm getting too old for this!

[Wirezfree]

O.K,
You have 850EVO, not 840EVO
I believe the issue is 840EVO
But reading more, it's even more confusing, it might be just certain sizes of 840EVO...arghhhhhh..

[Duckeenie]

Just tested mine, I'm using the 4.2 kernel.






I guess that looks pretty stable for this drive?

[Wirezfree]

Hi,

My bad,,,
I mixed up my SSD's, I have 840Pro and a 840EVO, picture above is PRO,
This is the EVO, and kind of looks like what I had seen with some other tools, with the spikes.
I need to investigate further...

[rokytnji]

Alrighty then.

[Duckeenie]

or this

Code: [Select]

arry@misohorny1:~$ dpkg --list | grep linux-image
ii  linux-image-3.13.0-24-generic              3.13.0-24.47                            i386         Linux kernel image for version 3.13.0 on 32 bit x86 SMP
ii  linux-image-extra-3.13.0-24-generic        3.13.0-24.47                            i386         Linux kernel extra modules for version 3.13.0 on 32 bit x86 SMP
ii  linux-image-linuxlite-4.0.0                0010                                    i386         Linux kernel binary image for version 4.0.0-linuxlite
ii  linux-image-linuxlite-4.1.0                0010                                    i386         Linux kernel binary image for version 4.1.0-linuxlite
ii  linux-image-linuxlite-4.2.0                0010                                    i386         Linux kernel binary image for version 4.2.0-linuxlite

Maybe you missed the news here
https://www.linuxliteos.com/forums/installing-software/linux-lite-kernel/

Perhaps you could develop a little empathy and consider the LL target demographic before you make such sarcastic posts in the future.

[Duckeenie]

Thanks for your input Wirezfree.

 I have an Evo 840 and was indeed a little worried after reading some of those threads but seeing the results from your benchmark gives me a more confidence to play around with LL again. Who knows I might even find time to play some Dizzy games

[Wirezfree]

Hi,


No, LL is based on Ubuntu 14.04 LTS with Kernel 3.13
You can update the Kernel, but but not sure where that leaves you with LTS.?

I have some Samsung SSD's...
I started reading some of those threads,
It started a slanging match... It's Samsung, it's the kernel it only affects Window, No it's Linux.........

From what I understand:
- A mixture of performance/access issues and data loss
- Samsung identified a Kernel Bug, that was patched in Kernel 3.15
- Then a firmware issue was discovered in certain 840/850 drives, that's not fixed I believe.?
- Certain Samsung drives are blacklisted now for trimming from Kernel >= 4.0.5

I have disabled daily trimming, now just weekly

This drive is over 18 months old, powered on for 11 months 14 days, it looks O.K to me.

[rokytnji]

or this

Code: [Select]

arry@misohorny1:~$ dpkg --list | grep linux-image
ii  linux-image-3.13.0-24-generic              3.13.0-24.47                            i386         Linux kernel image for version 3.13.0 on 32 bit x86 SMP
ii  linux-image-extra-3.13.0-24-generic        3.13.0-24.47                            i386         Linux kernel extra modules for version 3.13.0 on 32 bit x86 SMP
ii  linux-image-linuxlite-4.0.0                0010                                    i386         Linux kernel binary image for version 4.0.0-linuxlite
ii  linux-image-linuxlite-4.1.0                0010                                    i386         Linux kernel binary image for version 4.1.0-linuxlite
ii  linux-image-linuxlite-4.2.0                0010                                    i386         Linux kernel binary image for version 4.2.0-linuxlite

Maybe you missed the news here
https://www.linuxliteos.com/forums/installing-software/linux-lite-kernel/

[rokytnji]

that LL uses an older kernel

Like this?

Code: [Select]

harry@misohorny1:~$ inxi -MFxz
System:    Host: misohorny1 Kernel: 4.2.0-linuxlite i686 (32 bit gcc: 4.8.4)
           Desktop: Xfce 4.11.8 (Gtk 2.24.23) Distro: Ubuntu 14.04 trusty
Machine:   System: Dell product: OptiPlex 755
           Mobo: Dell model: 0GM819 Bios: Dell v: A11 date: 08/04/2008
CPU:       Dual core Intel Core2 Duo E6550 (-MCP-) cache: 4096 KB
           flags: (lm nx pae sse sse2 sse3 ssse3 vmx) bmips: 9310
           clock speeds: max: 2333 MHz 1: 2000 MHz 2: 2000 MHz
Graphics:  Card: Intel 82Q35 Express Integrated Graphics Controller
           bus-ID: 00:02.0
           Display Server: X.Org 1.15.1 drivers: intel (unloaded: fbdev,vesa)
           Resolution: [email protected]
           GLX Renderer: Mesa DRI Intel Q35 x86/MMX/SSE2
           GLX Version: 1.4 Mesa 10.1.3 Direct Rendering: Yes
Audio:     Card Intel 82801I (ICH9 Family) HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture v: k4.2.0-linuxlite
Network:   Card-1: Intel 82566DM-2 Gigabit Network Connection
           driver: e1000e v: 3.2.5-k port: ecc0 bus-ID: 00:19.0
           IF: eth0 state: down mac: <filter>
           Card-2: D-Link System DWA-140 RangeBooster N Adapter(rev.B2) [Ralink RT3072]
           driver: rt2800usb v: 2.3.0 usb-ID: 002-003
           IF: wlan1 state: N/A speed: N/A duplex: N/A mac: N/A
Drives:    HDD Total Size: 2000.4GB (0.7% used)
           ID-1: /dev/sda model: WDC_WD2003FYPS size: 2000.4GB
Partition: ID-1: / size: 15G used: 5.7G (42%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 71G used: 4.5G (7%) fs: ext4 dev: /dev/sda2
           ID-3: swap-1 size: 4.19GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 39.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 171 Uptime: 39 min Memory: 602.0/3897.5MB
           Init: Upstart runlevel: 2 Gcc sys: 4.8.4
           Client: Shell (bash 4.3.111) inxi: 2.2.28
harry@misohorny1:~$ cat /etc/llver
Linux Lite 2.6


[Duckeenie]

I recall reading a few months ago about the Linux Kernel bug that was causing issues with the aforementioned drives. Forgive me if this is a naive question but given that LL uses an older kernel I was wondering if the issue will have been patched out at this point or whether it's a case of waiting for a newer kernel?