[SOLVED] SSD and boot problem

cesura · 2012-03-31 21:37:31

I recently bought a new 30GB Corsair SSD, and it runs wonderfully. However, the device takes a considerably long time to initialize on boot (~30-45 seconds).

Here's a snippet of the relevant dmesg output:

[   23.360042] ata5: lost interrupt (Status 0x58)
[   23.363366] ata5: drained 65536 bytes to clear DRQ
[   23.447633] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[   23.447673] scsi 4:0:0:0: CDB: cdb[0]=0x12: 12 00 00 00 60 00
[   23.447683] ata5.00: cmd a0/01:00:00:60:00/00:00:00:00:00/a0 tag 0 dma 96 in
[   23.447684]          res 40/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[   23.447754] ata5.00: status: { DRDY }
[   23.447810] ata5: soft resetting link
[   23.653843] ata5.00: configured for UDMA/33
[   23.654431] ata5: EH complete
[   23.654435] scsi scan: 96 byte inquiry failed.  Consider BLIST_INQUIRY_36 for this device
[   23.657130] scsi 4:0:0:0: CD-ROM            TOSHIBA  DVD-ROM SD-R1312 1011 PQ: 0 ANSI: 5
[   54.373360] ata5: lost interrupt (Status 0x58)
[   54.376674] ata5: drained 65536 bytes to clear DRQ
[   54.465937] ata5.00: limiting speed to UDMA/25:PIO4
[   54.465941] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[   54.465985] sr 4:0:0:0: CDB: cdb[0]=0x5a: 5a 00 2a 00 00 00 00 00 80 00
[   54.465996] ata5.00: cmd a0/01:00:00:80:00/00:00:00:00:00/a0 tag 0 dma 16512 in
[   54.465997]          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[   54.466085] ata5.00: status: { DRDY }
[   54.466144] ata5: soft resetting link

I haven't encountered this problem with any other drive I've put in there, so I'm guessing it must be SSD-related. Has anyone else experienced something similar, and could you point me in the right direction? Thanks.

Last edited by cesura (2012-04-01 00:05:28)

falconindy · 2012-03-31 23:09:15

Consider RMA'ing the drive.

cesura · 2012-03-31 23:22:00

falconindy wrote:

Consider RMA'ing the drive.

Do you think it's defective/worth replacing? It's more of an annoyance than anything, and the drive has no other visible issues other than on initialization.

graysky · 2012-03-31 23:31:39

falconindy wrote:

Consider RMA'ing the drive.

+1

falconindy · 2012-03-31 23:49:06

itsbrad212 wrote:

falconindy wrote:
Consider RMA'ing the drive.
Do you think it's defective/worth replacing? It's more of an annoyance than anything, and the drive has no other visible issues other than on initialization.

Yes, I do. Healthy drives don't timeout on simple DMA initialization requests.

cesura · 2012-04-01 00:05:16

I seemed to have fixed the issue by adding:

libata.dma=0

to the end of the kernel line in my grub config.

falconindy · 2012-04-01 00:22:02

Huh, interesting. Sounds like a kernel bug then. There's a nice list of quirky devices in drivers/ata/libata-core.c which are problematic in various ways. You likely need an entry with the model name and the ATA_HORKAGE_NODMA attribute.

Arch Linux

#1 2012-03-31 21:37:31

[SOLVED] SSD and boot problem

#2 2012-03-31 23:09:15

Re: [SOLVED] SSD and boot problem

#3 2012-03-31 23:22:00

Re: [SOLVED] SSD and boot problem

#4 2012-03-31 23:31:39

Re: [SOLVED] SSD and boot problem

#5 2012-03-31 23:49:06

Re: [SOLVED] SSD and boot problem

#6 2012-04-01 00:05:16

Re: [SOLVED] SSD and boot problem

#7 2012-04-01 00:22:02

Re: [SOLVED] SSD and boot problem

Board footer