Hi piquadrat
Re-reading your second post you say that in the locked state it responds to a very limited set of ATA
commands. I also see you are getting a lot of DMA errors. So try libata.dma=0 and see if anything
changes.
From what I could find there is no way to prevent libata from probing the drive.
Just to be clear, if you boot into Microcore with the drive unlocked, does it do the same thing?
If the drive is unlocked none of the DMA errors are present. Log looks ok, boot is fast. The code placed in my previous message comes exactly from booting in such 'normal' conditions. As you can see, the drive is recognized as Intel SSDSA2CW08 with id: ata5.00. If the drive is locked all logs are filled with exceptions and I can't even tell when exactly during boot process they started but I assume that right there because the only thing that changed was that Intel ssd disk's security status.
If it's that important you could try and see what happens if you recompile the kernel, changing current
CONFIG_ATA_VERBOSE_ERROR=y
I could try but I'm affraid it would not help. I can silence those errors even right now with 'loglevel=0' bootcode but that 25-30seconds probe pause remains. At least after some time ata driver stops for querying drive so I suspect that there is some kind of timer used during the probing. But can I set it somewhere?
I've found some scsi related bootcodes (at least my intel ssd drive seems to be categorized as scsi):
scsi_mod.scan=none / async / sync
but it seems they are not implemented in tiny/microcore according to the documentation. Will try them anyway.