You have been subscribed to a public bug: Steps to Reproduce:
$ sudo cat /proc/kallsyms | grep pid_max c000000001308794 D pid_max $ echo x > /proc/sysrq-trigger xmon> bd c000000001308794 xmon> x As soon as pid_max got accessed, machine should automatically enter into xmon. But that is not happening. Machine detail: $ uname -a Linux tul163-u1704-qemu 4.10.0-13-generic #15 SMP Wed Mar 22 06:35:20 EDT 2017 ppc64le ppc64le ppc64le GNU/Linux $ cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.04 DISTRIB_CODENAME=zesty DISTRIB_DESCRIPTION="Ubuntu Zesty Zapus (development branch)" This patch solves the issue: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=c21a493a2b44650707d06741601894 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-152886 severity-high targetmilestone-inin1704 -- Ubuntu 17.04: xmon: data-breakpoint not working https://bugs.launchpad.net/bugs/1675772 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
