Howdy, I recently had some off-time and decided to look into why some of my drives where completely failing to show up after v4.8-rc3, some with odd DMA errors. Turned out to be vmapped stacks! Once CONFIG_VMAP_STACK got enabled by default in x86_64 (by commit e37e43a), to be more precise. I turned it off, and everything is back in working order. I don't have a standard setup, so probably nobody else has run into the same issue yet -- but if you want to replicate it: Get (or make) an ATA locked drive, boot with or hot-swap said locked drive on a v4.9 kernel with CONFIG_VMAP_STACK set to Y. On my systems (tested on two systems), the drive fails to get sensed correctly and no SCSI nodes get created. This means no way to unlock drives with hdparm (or in my case, via the kernel). I will try to dig into this issue a bit more next weekend, I just wanted to bring it up in case it hasn't been already. Cheers, G -- gamaral -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
