All,

Could you check out the Lenovo tip with firmware for Intel SSD published here on our support site?

Please see if this helps...

Thanks!

Mark

Hello,

I've tried the latest firmware and it seems things have improved a little bit, but they are still not solved.  The indexing tasks which I refered to in my first post were able to run for longer than before.  The system also slowed down like before, however, it recovered without a crash.  This was OK until about 10 minutes into the indexing, when it started to really slow down, and it finally started showing some errors in the kernel log.  I will paste them here, I hope it's not too much clutter.

--- first time it slowed down a lot:

ata2.00: exception Emask 0x0 SAct 0x7ff SErr 0x0 action 0x6 frozen
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/00:00:3f:08:21/04:00:0d:00:00/40 tag 0 ncq 524288 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/20:08:3f:0c:21/00:00:0d:00:00/40 tag 1 ncq 16384 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/20:10:ff:b1:44/00:00:0a:00:00/40 tag 2 ncq 16384 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/08:18:bf:00:00/00:00:10:00:00/40 tag 3 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/20:20:77:01:00/00:00:10:00:00/40 tag 4 ncq 16384 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/18:28:c7:01:00/00:00:10:00:00/40 tag 5 ncq 12288 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/08:30:e7:01:00/00:00:10:00:00/40 tag 6 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/08:38:a7:01:01/00:00:10:00:00/40 tag 7 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/08:40:3f:00:00/00:00:00:00:00/40 tag 8 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/08:48:87:00:00/00:00:00:00:00/40 tag 9 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/08:50:47:00:00/00:00:10:00:00/40 tag 10 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2: hard resetting link
ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata2.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
ata2.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
ata2.00: configured for UDMA/133
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2: EH complete

----- next time it slowed down:

ata2.00: exception Emask 0x0 SAct 0x1ff SErr 0x0 action 0x6 frozen
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/20:00:3f:bd:46/00:00:0a:00:00/40 tag 0 ncq 16384 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/18:08:d7:01:00/00:00:10:00:00/40 tag 1 ncq 12288 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/08:10:a7:01:01/00:00:10:00:00/40 tag 2 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/08:18:3f:00:00/00:00:00:00:00/40 tag 3 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/08:20:77:00:00/00:00:00:00:00/40 tag 4 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/08:28:7f:00:00/00:00:0d:00:00/40 tag 5 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/08:30:bf:00:00/00:00:10:00:00/40 tag 6 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/18:38:77:01:00/00:00:10:00:00/40 tag 7 ncq 12288 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2.00: failed command: WRITE FPDMA QUEUED
ata2.00: cmd 61/10:40:c7:01:00/00:00:10:00:00/40 tag 8 ncq 8192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2: hard resetting link
ata2: link is slow to respond, please be patient (ready=0)
ata2: COMRESET failed (errno=-16)
ata2: hard resetting link
ata2: link is slow to respond, please be patient (ready=0)
ata2: COMRESET failed (errno=-16)
ata2: limiting SATA link speed to 3.0 Gbps
ata2: hard resetting link
ata2: COMRESET failed (errno=-16)
ata2: reset failed, giving up
ata2.00: disabled
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2.00: device reported invalid CHS sector 0
ata2: EH complete
sd 1:0:0:0: [sdb] Unhandled error code
sd 1:0:0:0: [sdb] Unhandled error code
sd 1:0:0:0: [sdb]
sd 1:0:0:0: [sdb]
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 1:0:0:0: [sdb] CDB:
sd 1:0:0:0: [sdb] CDB:
Write(10): 2a 00
Write(10): 2a 00 10 00 01 77 00 00 18 00
10<3>end_request: I/O error, dev sdb, sector 268435831
Buffer I/O error on device sdb1, logical block 33554471
lost page write due to I/O error on sdb1
00 01 c7 00 00 10 00
end_request: I/O error, dev sdb, sector 268435911
Buffer I/O error on device sdb1, logical block 33554472
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 33554481
Buffer I/O error on device sdb1, logical block 33554473
lost page write due to I/O error on sdb1
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 33554482
lost page write due to I/O error on sdb1
sd 1:0:0:0: [sdb] Unhandled error code
sd 1:0:0:0: [sdb]
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 1:0:0:0: [sdb] CDB:
sd 1:0:0:0: [sdb] Unhandled error code
sd 1:0:0:0: [sdb] Unhandled error code
sd 1:0:0:0: [sdb]
sd 1:0:0:0: [sdb]
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 1:0:0:0: [sdb] CDB:
sd 1:0:0:0: [sdb] CDB:
Write(10)
Write(10)
:
:
2a
2a
00
00
00
0d
00
00
00
00
77
7f
00
00
00
00
08
08
00

00
end_request: I/O error, dev sdb, sector 119
end_request: I/O error, dev sdb, sector 218103935
Buffer I/O error on device sdb1, logical block 7
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 27262984
lost page write due to I/O error on sdb1
sd 1:0:0:0: [sdb] Unhandled error code
sd 1:0:0:0: [sdb]
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 1:0:0:0: [sdb] CDB:
Write(10): 2a 00 10 00 00 bf
Write(10): 2a 00 00 00 00 3f 00 00 08 00
end_request: I/O error, dev sdb, sector 63
Buffer I/O error on device sdb1, logical block 0
lost page write due to I/O error on sdb1
00 00 08 00
end_request: I/O error, dev sdb, sector 268435647
sd 1:0:0:0: [sdb] Unhandled error code
sd 1:0:0:0: [sdb]
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 1:0:0:0: [sdb] CDB:
Buffer I/O error on device sdb1, logical block 33554448
lost page write due to I/O error on sdb1
Write(10): 2a 00 10 01 01 a7 00 00 08 00
end_request: I/O error, dev sdb, sector 268501415
sd 1:0:0:0: [sdb] Unhandled error code
sd 1:0:0:0: [sdb]
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 1:0:0:0: [sdb] CDB:
Write(10): 2a 00 10 00 01 d7 00 00 18 00
end_request: I/O error, dev sdb, sector 268435927
sd 1:0:0:0: [sdb] Unhandled error code
sd 1:0:0:0: [sdb]
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 1:0:0:0: [sdb] CDB:
Write(10): 2a 00 0a 46 bd 3f 00 00 20 00
end_request: I/O error, dev sdb, sector 172408127
Aborting journal on device sdb1-8.
EXT4-fs (sdb1): delayed block allocation failed for inode 8388779 at logical offset 0 with max blocks 1 with error -30
EXT4-fs (sdb1): This should not happen!! Data will be lost

sd 1:0:0:0: [sdb] Unhandled error code
sd 1:0:0:0: [sdb]
EXT4-fs error (device sdb1) in ext4_da_writepages:2399: Journal has aborted
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 1:0:0:0: [sdb] CDB:
EXT4-fs (sdb1): previous I/O error to superblock detected
Write(10): 2a 00 0a 44 00 3f 00 00 08 00
end_request: I/O error, dev sdb, sector 172228671
JBD2: Error -5 detected when updating journal superblock for sdb1-8.
sd 1:0:0:0: [sdb] Unhandled error code
sd 1:0:0:0: [sdb]
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 1:0:0:0: [sdb] CDB:
Write(10): 2a 00 00 00 00 3f 00 00 08 00
EXT4-fs (sdb1): Remounting filesystem read-only
journal commit I/O error
EXT4-fs (sdb1): ext4_da_writepages: jbd2_start: 1024 pages, ino 8388779; err -30
sd 1:0:0:0: [sdb] Unhandled error code
sd 1:0:0:0: [sdb]
Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 1:0:0:0: [sdb] CDB:
Read(10): 28 00 10 01 01 a7 00 00 08 00
blk_update_request: 1 callbacks suppressed
end_request: I/O error, dev sdb, sector 268501415

And finally:
Message from syslogd@... at Feb 20 08:54:38 ...

kernel:journal commit I/O error

So in the end it was remounted as R/O.

This is not such a big issue for me anymore because I use a Samsung 830 drive as my main drive and only use the intel 520 in the ultrabay to store my virtualbox images.  I just wanted to post on here in case it helps the Lenovo/Intel guys with anything.

Mark,

I ran the update tool on Win8 earlier today - as I already used the bootable firmware update it did not do anything.

I am still able to reliably reproduce the system hang in Ubuntu 12.10 using Oracle 11g and PostgreSQL 9.1. It takes less than 60 seconds to completely crash the system. My log file looks about the same as madi's, containing

res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }

and lots of

ata2: COMRESET failed (errno=-16)

Would be great if you could give us some more pointers.

PS: Can I have the on site service replace the SSD with a different one?

Hmm.

Thanks for the feedback - let me share this with our engineers and get back to you shortly on next steps / suggestions.  If we engage service, I want to make sure we have a definitive fix.

Mark

Hi,

I have the same problem with a Lenovo W530 / 240GB SSD drive running XUbuntu 12.04.

The problem occurs when I sync my Dropbox account. It makes the computer freeze after 5 to 15 minutes. When I switch to the console, I get error messages saying:

ata1: COMRESET failed (errno=-16)
end_request: I/O error, dev sda, sector 373370472

I got a replacement disk from Lenovo, but I still have the same issues. Both disk have the latest firmware (LF1i).

I don't seem to have the same problems running Windows 8 even when I synced my Dropbox accound and did other disk intensive tasks.

All help is appreciated!

Sincerely,

Mathias Bjerke

Hi,

I installed a OCZ SSD drive, and that solved all my problems. The computer have been stable the last week.

Sincerely,

Mathias Bjerke

I just wanted to thank everyone for discussing this issue. It helped with my purchase decision of a Samsung 840 instead of an Intel Drive this time around. I'm afraid of the SF controller, and due to disk encryption all of my data is incompressible so the SF controller wouldn't help me anyway.