I'm also at 4.16.7-1. Grub (grub-install -v) reports version 2.02. I switch from the "1" parameter to "y" as Simon posted but it made no difference. Removing the option allows it to boot normally though. I just installed the RAID controller a couple weeks ago - migrated away from the md driver and since I did that blkid reports my main drive as being /dev/sdc and not sda. I use UUID mounting ( and grub.cfg entries ) so it wasn't an issue until the update. Doesn't seem to matter either if I remove the boot cmd line arg though. I am a C/C++ developer, but not really a kernel dev and have never spent any time understanding the low level bootstrap stuffs, but I may try to dive into it if for nothing more than for academic purposes. In the interim, any other ideas are welcome. Many thanks! On Mon, May 7, 2018 at 7:19 PM Simon Perry via arch-general < arch-general@xxxxxxxxxxxxx> wrote: > On 2018-05-08 09:21, Randy DuCharme via arch-general wrote: > > Greetings, > > > > Just updated my system (pacman -Syu) and was dumped into an emergency > > shell > > on reboot. Seems my boot command line option (scsi_mod.use_blk_mq=1) > > was > > no longer acceptable. LOL. I haven't seen anything that indicated > > this > > was deprecated or obsolete. > > > > System is fairly simple. Asus CrosshairV - Formula Z + FX9590. Main > > disk > > is a 2T Barracuda and a handfull of WD Raptors on an LSI-9260. System > > comes up fine removing the boot option. > > > > Thanks in advance! > > I use scsi_mod.use_blk_mq=y and dm_mod.use_blk_mq=y and had no problems > booting 4.16.7-1. > > Cheers. > > -- > Simon Perry > -- Randall DuCharme (Radio *AD5GB*) Powered entirely by Open Source software.
