It looks like CONFIG_BLK_DEV_RAM was built in going as back as far as Trusty (14.04). Was there a prior release where you did not experience this bug?
It looks like CONFIG_BLK_DEV_RAM was built in going as back as far as Trusty (14.04). Was there a prior release where you did not experience this bug?