Public bug reported:

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

** Tags added: architecture-ppc64le bugnameltc-152886 severity-high
targetmilestone-inin1704

** Changed in: ubuntu
     Assignee: (unassigned) => Taco Screen team (taco-screen-team)

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1675772

Title:
  Ubuntu 17.04: xmon: data-breakpoint not working

Status in linux package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to