I have a Vaio pro13 with av SSD disk; dual booting with Win8. At last I managed to install and boot with ubuntu 12 and 13 with Linux 13.13, 64 bits. But I have a very slow boot with Ubuntu; about 2 minutes. The problem was the same with ubuntu 12 and 13. And I have among others this message: NCQ disabled due to excessive errors.
I can see the problems start at 31.821757 (from dmesg):

ata1.00: exception Emask 0x0 SAct 0x1ff SErr 0x0 action 0x6 frozen
[ 31.821763] ata1.00: failed command: READ FPDMA QUEUED
[ 31.821769] ata1.00: cmd 60/08:00:f0:77:3d/00:00:15:00:00/40 tag 0 ncq 4096 in
[ 31.821769] res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 31.821772] ata1.00: status: { DRDY }
[ 31.821774] ata1.00: failed command: READ FPDMA QUEUED

And so at 32.155757:

ata1.00: device reported invalid CHS sector 0
[ 32.155769] ata1: EH complete
[ 62.780539] ata1.00: exception Emask 0x0 SAct 0x1e1 SErr 0x0 action 0x6 frozen
[ 62.780545] ata1.00: failed command: READ FPDMA QUEUED
[ 62.780551] ata1.00: cmd 60/08:00:f0:0f:4f/00:00:14:00:00/40 tag 0 ncq 4096 in
[ 62.780551] res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 62.780554] ata1.00: status: { DRDY }
[ 62.780556] ata1.00: failed command: READ FPDMA QUEUED

It is the same until:

94.137352] ata1.00: device reported invalid CHS sector 0
[ 94.137361] ata1: EH complete
[ 129.735288] ata1.00: NCQ disabled due to excessive errors
[ 129.735294] ata1.00: exception Emask 0x0 SAct 0x7fffffc3 SErr 0x0 action 0x6 frozen
[ 129.735298] ata1.00: failed command: READ FPDMA QUEUED
[ 129.735303] ata1.00: cmd 60/08:00:08:22:d1/00:00:10:00:00/40 tag 0 ncq 4096 in
[ 129.735303] res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 129.735306] ata1.00: status: { DRDY }

At the end of dmesg:

[ 130.069249] ata1.00: device reported invalid CHS sector 0
[ 130.069258] sd 0:0:0:0: [sda]
[ 130.069260] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 130.069262] sd 0:0:0:0: [sda]
[ 130.069264] Sense Key : Aborted Command [current] [descriptor]
[ 130.069267] Descriptor sense data with sense descriptors (in hex):
[ 130.069269] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 130.069278] 00 00 00 00

.....

130.070184] ata1: EH complete
[ 130.071011] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
[ 130.151868] random: init urandom read with 93 bits of entropy available
[ 130.181183] init: plymouth-upstart-bridge main process (193) terminated with status 1

I think there must be some problems with the SSD Disk and Linux. Any clues? Could another kernel or a kernel with other options be a solution? And in that case compile a new kernel?

Nope. My AntiX 13.2 boots in under 10 seconds on my 64gig SSD on my M&A companion 9" screen Netbook.

Search "Ubuntu SSD boot time" to see what I mean.

Then search for "Ubuntu SSD slow boot"

Maybe you will find some useful info on what to do about your issue.

The clue is here:
NCQ disabled due to excessive errors.
I found the solution here:

http://bernaerts.dyndns.org/linux/74...ntu-tweaks-ssd

"6. If you get some System Freeze

In case your system is showing some type of freeze, it may come from the fact that your SSD disk is not compatible with Linux NCQ (SATA Native Command Queueing), which is enabled by default.

This should not be the case with modern SSD, but it happens with some old generation or no-name ones.

To disable NCQ,you need to add the kernel parameter libata.force=noncq.

# sudo nano /etc/default/grub

/etc/default/grub

...
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash libata.force=noncq"
...
Once modified, propagate it to grub database :

# sudo update-grub

After next reboot, these freezes should be part of the past.

Your computer should now be more responsive and your SSD life expectancy should have increased quite a bit.

Hope it helps".

Strange nobody in this forum was aware of the problem?
But now my Ubuntu boots as fast as my Win8 on the same computer. Nice!