[Expired for linux (Ubuntu Bionic) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762450
Removing the scsi_mod.use_blk_mq=1 from /etc/default/grub and the
mentioned udev rule file, and regenerating initial ramdisk + reboot
seems to do the trick, now everything works with default (cfq) I/O
scheduler.
Before this comment, and the problem:
# cat /sys/block/sda/queue/scheduler
[bfq]
Ok, I will investigate as soon as I have time. By the way, I am
wondering if using BFQ as I/O scheduler can be the problem, ie:
# cat /etc/udev/rules.d/60-schedulers.rules
## set noop scheduler for non-rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="0",
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
[22596.884250] sysrq: SysRq : This sysrq operation is disabled.
I got this, if I try to trigger those sysreq events by echoing t/m into
that procfs file. I'm anyway curious how sysreq stuffs can be
enabled/disabled, since I seldom use ALT-SYSREQ- combos as well, and
many of them just reports
I can't answer what is happening here. But can you obtain more information
using SysRq-t
and SysRq-m as described at
https://akari.osdn.jp/capturing-kernel-messages.html#Tips5 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
