It is indeed very odd. dmesg | grep dyndbg [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-041200rc5-generic root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash nvme_core.default_ps_max_latency_us=0 nvme_core.dyndbg=+p vt.handoff=7 [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-041200rc5-generic root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash nvme_core.default_ps_max_latency_us=0 nvme_core.dyndbg=+p vt.handoff=7
seems to indicate, that I DID actually set the kernel parameter. Is there some way to check whether dynamic debug is ACTUALLY enabled? Given that the system seems to quietly ignore "nvme_core.default_ps_max_latency_us=0", maybe it also ignores "nvme_core.dyndbg=+p". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699004 Title: APST gets enabled against explicit kernel option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699004/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
