[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
Hi Chris, Can another track be opened for Vivid to provide the same fix there or is it preferable to just open a new bug or even necessary? Thanks. -- 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Bug description: SRU Justification: [Impact] Users of LE Power8 hardware might not be able to use XMON properly. [Test Case] # echo x /proc/sysrq-trigger This should put us in the xmon debugger without errors. [Fix] 3b8a3c01096925a824ed3272601082289d9c23a5 can be cleanly cherry-picked to 3.13/3.16. It only adds cpu_to_be32 macros which shouldn't change the behavior of BE mode CPUs. -- == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+subscriptions -- 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
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
This bug was fixed in the package linux - 3.16.0-29.39 --- linux (3.16.0-29.39) utopic; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1402822 [ AceLan Kao ] * SAUCE: Add use_native_backlight quirk for HP ProBook 6570b - LP: #1359010 [ Andy Whitcroft ] * Revert SAUCE: (no-up) arm64: optimized copy_to_user and copy_from_user assembly code - LP: #1398596 * [Config] updateconfigs to balance CONFIG_SCOM_DEBUGFS [ Paolo Pisati ] * [Config] armhf: VIRTIO_[BALLOON|MMIO]=y [ Upstream Kernel Changes ] * Revert arm64: Make default dma_ops to be noncoherent - LP: #1386490 * Revert percpu: free percpu allocation info for uniprocessor system - LP: #1401079 * ath3k: Add support of MCI 13d3:3408 bt device - LP: #1395465 * x86: kvm: use alternatives for VMCALL vs. VMMCALL if kernel text is read-only - LP: #1379340 * cpufreq: Allow stop CPU callback to be used by all cpufreq drivers - LP: #1397928 * cpufreq: powernv: Set the pstate of the last hotplugged out cpu in policy-cpus to minimum - LP: #1397928 * cpufreq: powernv: Set the cpus to nominal frequency during reboot/kexec - LP: #1397928 * xen-netfront: Remove BUGs on paged skb data which crosses a page boundary - LP: #1275879 * ACPI / blacklist: blacklist Win8 OSI for Dell Vostro 3546 - LP: #1383589 * iwlwifi: add device / firmware to fw-error-dump file - LP: #1399440 * iwlwifi: rename iwl_mvm_fw_error_next_data - LP: #1399440 * iwlwifi: pcie: add firmware monitor capabilities - LP: #1399440 * iwlwifi: remove wrong comment about alignment in iwl-fw-error-dump.h - LP: #1399440 * iwlwifi: mvm: don't collect logs in the interrupt thread - LP: #1399440 * iwlwifi: mvm: kill iwl_mvm_fw_error_rxf_dump - LP: #1399440 * iwlwifi: mvm: update layout of firmware error dump - LP: #1399440 * powerpc/pseries: Fix endiannes issue in RTAS call from xmon - LP: #1396235 * mmc: sdhci-pci-o2micro: Fix Dell E5440 issue - LP: #1346067 * mfd: rtsx: Fix PM suspend for 5227 5249 - LP: #1359052 * samsung-laptop: Add broken-acpi-video quirk for NC210/NC110 - LP: #1401079 * acer-wmi: Add acpi_backlight=video quirk for the Acer KAV80 - LP: #1401079 * pinctrl: baytrail: show output gpio state correctly on Intel Baytrail - LP: #1401079 * ALSA: hda - Add dock support for Thinkpad T440 (17aa:2212) - LP: #1401079 * ALSA: hda - Add ultra dock support for Thinkpad X240. - LP: #1401079 * rbd: Fix error recovery in rbd_obj_read_sync() - LP: #1401079 * ds3000: fix LNB supply voltage on Tevii S480 on initialization - LP: #1401079 * powerpc: do_notify_resume can be called with bad thread_info flags argument - LP: #1401079 * powerpc/powernv: Properly fix LPC debugfs endianness - LP: #1401079 * irqchip: armada-370-xp: Fix MSI interrupt handling - LP: #1401079 * irqchip: armada-370-xp: Fix MPIC interrupt handling - LP: #1401079 * USB: kobil_sct: fix non-atomic allocation in write path - LP: #1401079 * USB: opticon: fix non-atomic allocation in write path - LP: #1401079 * regulator: max77693: Fix use of uninitialized regulator config - LP: #1401079 * USB: cdc-acm: add device id for GW Instek AFG-2225 - LP: #1401079 * usb: Do not allow usb_alloc_streams on unconfigured devices - LP: #1401079 * usb-storage: handle a skipped data phase - LP: #1401079 * uas: Add US_FL_NO_ATA_1X quirk for 1 more Seagate model - LP: #1401079 * xhci: Disable streams on Asmedia 1042 xhci controllers - LP: #1401079 * uas: Add NO_ATA_1X for VIA VL711 devices - LP: #1401079 * USB: core: add device-qualifier quirk - LP: #1401079 * USB: quirks: enable device-qualifier quirk for Elan Touchscreen - LP: #1401079 * USB: quirks: enable device-qualifier quirk for another Elan touchscreen - LP: #1401079 * USB: quirks: enable device-qualifier quirk for yet another Elan touchscreen - LP: #1401079 * xhci: no switching back on non-ULT Haswell - LP: #1401079 * uas: Add US_FL_NO_ATA_1X quirk for 2 more Seagate models - LP: #1401079 * of: Fix overflow bug in string property parsing functions - LP: #1401079 * spi: fsl-dspi: Fix CTAR selection - LP: #1401079 * Btrfs: fix kfree on list_head in btrfs_lookup_csums_range error cleanup - LP: #1401079 * ALSA: usb-audio: Fix device_del() sysfs warnings at disconnect - LP: #1401079 * iio: as3935: allocate correct iio_device size - LP: #1401079 * staging:iio:ade7758: Fix NULL pointer deref when enabling buffer - LP: #1401079 * staging:iio:ade7758: Fix check if channels are enabled in prenable - LP: #1401079 * staging:iio:ade7758: Remove raw from channel name - LP: #1401079 * USB: cdc-acm: only raise DTR on transitions from B0 - LP: #1401079 * fix breakage in o2net_send_tcp_msg() - LP: #1401079 * phy:
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
This bug was fixed in the package linux - 3.13.0-44.73 --- linux (3.13.0-44.73) trusty; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1402872 [ AceLan Kao ] * SAUCE: Add use_native_backlight quirk for HP ProBook 6570b - LP: #1359010 [ Andy Whitcroft ] * Revert SAUCE: (no-up) arm64: optimized copy_to_user and copy_from_user assembly code - LP: #1398596 * [Config] updateconfigs to balance CONFIG_SCOM_DEBUGFS [ Upstream Kernel Changes ] * iwlwifi: mvm: fix merge damage - LP: #1393317 * iwlwifi: remove IWL_UCODE_TLV_FLAGS_SCHED_SCAN flag - LP: #1393317 * iwlwifi: mvm: disable scheduled scan to prevent firmware crash - LP: #1393317 * iwlwifi: mvm: enable scheduled scan on newest firmware - LP: #1393317 * x86: kvm: use alternatives for VMCALL vs. VMMCALL if kernel text is read-only - LP: #1379340 * phylib: introduce PHY_INTERFACE_MODE_XGMII for 10G PHY - LP: #1381084 * of: make of_get_phy_mode parse 'phy-connection-type' - LP: #1381084 * xen-netfront: Remove BUGs on paged skb data which crosses a page boundary - LP: #1275879 * ACPI / blacklist: blacklist Win8 OSI for Dell Vostro 3546 - LP: #1383589 * powerpc/pseries: Fix endiannes issue in RTAS call from xmon - LP: #1396235 * mmc: sdhci-pci-o2micro: Fix Dell E5440 issue - LP: #1346067 * mfd: rtsx: Fix PM suspend for 5227 5249 - LP: #1359052 * drivers:scsi:storvsc: Fix a bug in handling ring buffer failures that may result in I/O freeze - LP: #1400289 * arm64: optimized copy_to_user and copy_from_user assembly code - LP: #1400349 * net:socket: set msg_namelen to 0 if msg_name is passed as NULL in msghdr struct from userland. - LP: #1335478 * drm/radeon: initialize sadb to NULL in the audio code - LP: #1402714 * powerpc/vphn: NUMA node code expects big-endian - LP: #1401150 * ALSA: usb-audio: Fix device_del() sysfs warnings at disconnect - LP: #1402853 * ALSA: hda - Add mute LED pin quirk for HP 15 touchsmart - LP: #1334950, #1402853 * rcu: Make callers awaken grace-period kthread - LP: #1402853 * rcu: Use rcu_gp_kthread_wake() to wake up grace period kthreads - LP: #1402853 * net: sctp: fix NULL pointer dereference in af-from_addr_param on malformed packet - LP: #1402853 * KVM: x86: Don't report guest userspace emulation error to userspace - LP: #1402853 * [media] ttusb-dec: buffer overflow in ioctl - LP: #1402853 * arm64: __clear_user: handle exceptions on strb - LP: #1402853 * ARM: pxa: fix hang on startup with DEBUG_LL - LP: #1402853 * samsung-laptop: Add broken-acpi-video quirk for NC210/NC110 - LP: #1402853 * acer-wmi: Add Aspire 5741 to video_vendor_dmi_table - LP: #1402853 * acer-wmi: Add acpi_backlight=video quirk for the Acer KAV80 - LP: #1402853 * rbd: Fix error recovery in rbd_obj_read_sync() - LP: #1402853 * [media] ds3000: fix LNB supply voltage on Tevii S480 on initialization - LP: #1402853 * powerpc: do_notify_resume can be called with bad thread_info flags argument - LP: #1402853 * USB: kobil_sct: fix non-atomic allocation in write path - LP: #1402853 * USB: opticon: fix non-atomic allocation in write path - LP: #1402853 * regulator: max77693: Fix use of uninitialized regulator config - LP: #1402853 * USB: cdc-acm: add device id for GW Instek AFG-2225 - LP: #1402853 * usb: Do not allow usb_alloc_streams on unconfigured devices - LP: #1402853 * usb-storage: handle a skipped data phase - LP: #1402853 * xhci: Switch only Intel Lynx Point-LP ports to EHCI on shutdown. - LP: #1402853 * xhci: no switching back on non-ULT Haswell - LP: #1402853 * of: Fix overflow bug in string property parsing functions - LP: #1402853 * spi: fsl-dspi: Fix CTAR selection - LP: #1402853 * Btrfs: fix kfree on list_head in btrfs_lookup_csums_range error cleanup - LP: #1402853 * staging:iio:ade7758: Fix NULL pointer deref when enabling buffer - LP: #1402853 * staging:iio:ade7758: Fix check if channels are enabled in prenable - LP: #1402853 * staging:iio:ade7758: Remove raw from channel name - LP: #1402853 * USB: cdc-acm: only raise DTR on transitions from B0 - LP: #1402853 * serial: Fix divide-by-zero fault in uart_get_divisor() - LP: #1402853 * tty: Fix high cpu load if tty is unreleaseable - LP: #1402853 * tty: Prevent read/write wait queue active! log flooding - LP: #1402853 * tty/vt: don't set font mappings on vc not supporting this - LP: #1402853 * spi: pxa2xx: toggle clocks on suspend if not disabled by runtime PM - LP: #1402853 * sysfs: driver core: Fix glue dir race condition by gdp_mutex - LP: #1402853 * i2c: at91: don't account as iowait - LP: #1402853 * nfsd: don't try to reuse an expired DRC entry off the list - LP: #1402853 * nfsd: don't halt
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
Verified this with 3.16.0-29-generic ppc64le. ** Tags removed: verification-needed-utopic ** Tags added: verification-done-utopic -- 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: SRU Justification: [Impact] Users of LE Power8 hardware might not be able to use XMON properly. [Test Case] # echo x /proc/sysrq-trigger This should put us in the xmon debugger without errors. [Fix] 3b8a3c01096925a824ed3272601082289d9c23a5 can be cleanly cherry-picked to 3.13/3.16. It only adds cpu_to_be32 macros which shouldn't change the behavior of BE mode CPUs. -- == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+subscriptions -- 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
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
Verified this with 3.13.0-44-generic ppc64le. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: SRU Justification: [Impact] Users of LE Power8 hardware might not be able to use XMON properly. [Test Case] # echo x /proc/sysrq-trigger This should put us in the xmon debugger without errors. [Fix] 3b8a3c01096925a824ed3272601082289d9c23a5 can be cleanly cherry-picked to 3.13/3.16. It only adds cpu_to_be32 macros which shouldn't change the behavior of BE mode CPUs. -- == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+subscriptions -- 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
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty ** Tags added: verification-needed-utopic -- 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: SRU Justification: [Impact] Users of LE Power8 hardware might not be able to use XMON properly. [Test Case] # echo x /proc/sysrq-trigger This should put us in the xmon debugger without errors. [Fix] 3b8a3c01096925a824ed3272601082289d9c23a5 can be cleanly cherry-picked to 3.13/3.16. It only adds cpu_to_be32 macros which shouldn't change the behavior of BE mode CPUs. -- == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+subscriptions -- 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
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- utopic' to 'verification-done-utopic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: SRU Justification: [Impact] Users of LE Power8 hardware might not be able to use XMON properly. [Test Case] # echo x /proc/sysrq-trigger This should put us in the xmon debugger without errors. [Fix] 3b8a3c01096925a824ed3272601082289d9c23a5 can be cleanly cherry-picked to 3.13/3.16. It only adds cpu_to_be32 macros which shouldn't change the behavior of BE mode CPUs. -- == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+subscriptions -- 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
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-trusty -- 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: SRU Justification: [Impact] Users of LE Power8 hardware might not be able to use XMON properly. [Test Case] # echo x /proc/sysrq-trigger This should put us in the xmon debugger without errors. [Fix] 3b8a3c01096925a824ed3272601082289d9c23a5 can be cleanly cherry-picked to 3.13/3.16. It only adds cpu_to_be32 macros which shouldn't change the behavior of BE mode CPUs. -- == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+subscriptions -- 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
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-utopic -- 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: SRU Justification: [Impact] Users of LE Power8 hardware might not be able to use XMON properly. [Test Case] # echo x /proc/sysrq-trigger This should put us in the xmon debugger without errors. [Fix] 3b8a3c01096925a824ed3272601082289d9c23a5 can be cleanly cherry-picked to 3.13/3.16. It only adds cpu_to_be32 macros which shouldn't change the behavior of BE mode CPUs. -- == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+subscriptions -- 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
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1504 -- 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: SRU Justification: [Impact] Users of LE Power8 hardware might not be able to use XMON properly. [Test Case] # echo x /proc/sysrq-trigger This should put us in the xmon debugger without errors. [Fix] 3b8a3c01096925a824ed3272601082289d9c23a5 can be cleanly cherry-picked to 3.13/3.16. It only adds cpu_to_be32 macros which shouldn't change the behavior of BE mode CPUs. -- == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+subscriptions -- 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
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
** Branch linked: lp:ubuntu/trusty-proposed/linux-keystone -- 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: SRU Justification: [Impact] Users of LE Power8 hardware might not be able to use XMON properly. [Test Case] # echo x /proc/sysrq-trigger This should put us in the xmon debugger without errors. [Fix] 3b8a3c01096925a824ed3272601082289d9c23a5 can be cleanly cherry-picked to 3.13/3.16. It only adds cpu_to_be32 macros which shouldn't change the behavior of BE mode CPUs. -- == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+subscriptions -- 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
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
** Changed in: linux (Ubuntu Trusty) Status: In Progress = Fix Committed ** Changed in: linux (Ubuntu Utopic) Status: In Progress = Fix Committed -- 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: SRU Justification: [Impact] Users of LE Power8 hardware might not be able to use XMON properly. [Test Case] # echo x /proc/sysrq-trigger This should put us in the xmon debugger without errors. [Fix] 3b8a3c01096925a824ed3272601082289d9c23a5 can be cleanly cherry-picked to 3.13/3.16. It only adds cpu_to_be32 macros which shouldn't change the behavior of BE mode CPUs. -- == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+subscriptions -- 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
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
$ git tag --contains 3b8a3c01096925a824ed3272601082289d9c23a5 v3.18-rc7 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New = Fix Released ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = Chris J Arges (arges) ** Changed in: linux (Ubuntu Utopic) Assignee: (unassigned) = Chris J Arges (arges) ** Changed in: linux (Ubuntu Trusty) Status: New = In Progress ** Changed in: linux (Ubuntu Utopic) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Utopic) Status: New = In Progress ** Description changed: + SRU Justification: + [Impact] + Users of LE Power8 hardware might not be able to use XMON properly. + + [Test Case] + # echo x /proc/sysrq-trigger + This should put us in the xmon debugger without errors. + + [Fix] + 3b8a3c01096925a824ed3272601082289d9c23a5 can be cleanly cherry-picked to 3.13/3.16. It only adds cpu_to_be32 macros which shouldn't change the behavior of BE mode CPUs. + + -- + == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- - Kernel fails to invoke xmon, instead print following messages + Kernel fails to invoke xmon, instead print following messages - # echo x /proc/sysrq-trigger - [ 47.600133] SysRq : Entering xmon - cpu 0xf: Vector: 0 at [c000e8603b80] - pc: c05610c0: write_sysrq_trigger+0x120/0x260 - lr: c05610c0: write_sysrq_trigger+0x120/0x260 - sp: c000e8603ce0 -msr: 80009033 - current = 0xc000ef4a - paca= 0xc7df3480 softe: 0irq_happened: 0x00 - pid = 2303, comm = bash - [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 - cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] - pc: 0ee27cc4 - lr: 0ee27c44 - sp: fc7b4b0 -msr: 80001000 -dar: 1000 - dsisr: 4200 - current = 0xc000ef4a - paca= 0xc7df3480 softe: 0irq_happened: 0x00 - pid = 2303, comm = bash - cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop - xmon: WARNING: bad recursive fault on cpu 0xf + # echo x /proc/sysrq-trigger + [ 47.600133] SysRq : Entering xmon + cpu 0xf: Vector: 0 at [c000e8603b80] + pc: c05610c0: write_sysrq_trigger+0x120/0x260 + lr: c05610c0: write_sysrq_trigger+0x120/0x260 + sp: c000e8603ce0 + msr: 80009033 + current = 0xc000ef4a + paca= 0xc7df3480 softe: 0irq_happened: 0x00 + pid = 2303, comm = bash + [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 + cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] + pc: 0ee27cc4 + lr: 0ee27c44 + sp: fc7b4b0 + msr: 80001000 + dar: 1000 + dsisr: 4200 + current = 0xc000ef4a + paca= 0xc7df3480 softe: 0irq_happened: 0x00 + pid = 2303, comm = bash + cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop + xmon: WARNING: bad recursive fault on cpu 0xf - - ---uname output--- N/A - - Machine Type = powervm le - + + Machine Type = powervm le + ---System Hang--- - System is hung - + System is hung + ---Debugger--- A debugger is not configured - + ---Steps to Reproduce--- - see problem description - + see problem description + Stack trace output: - no - + no + Oops output: - see problem description - + see problem description + System Dump Info: - The system is not configured to capture a system dump. - - This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ + The system is not configured to capture a system dump. + + This patch has been sent upstream: +
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
Patch is upstream: 3b8a3c010969 (powerpc/pseries: Fix endiannes issue in RTAS call from xmon). The patch is also marked for -stable. -- 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+subscriptions -- 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
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
** 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in “linux” package in Ubuntu: New Bug description: == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+subscriptions -- 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
[Kernel-packages] [Bug 1396235] Re: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM)
** Tags added: kernel-da-key -- 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/1396235 Title: Ubuntu - unable to use XMON debugger (running ppc64le on PowerVM) Status in “linux” package in Ubuntu: New Bug description: == Comment: #0 - Laurent Dufour laurent.duf...@fr.ibm.com - 2014-11-25 10:13:17 == ---Problem Description--- Kernel fails to invoke xmon, instead print following messages # echo x /proc/sysrq-trigger [ 47.600133] SysRq : Entering xmon cpu 0xf: Vector: 0 at [c000e8603b80] pc: c05610c0: write_sysrq_trigger+0x120/0x260 lr: c05610c0: write_sysrq_trigger+0x120/0x260 sp: c000e8603ce0 msr: 80009033 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash [ 47.607247] Bad kernel stack pointer fc7b4b0 at ee27cc4 cpu 0xf: Vector: 300 (Data Access) at [c7f37d40] pc: 0ee27cc4 lr: 0ee27c44 sp: fc7b4b0 msr: 80001000 dar: 1000 dsisr: 4200 current = 0xc000ef4a paca= 0xc7df3480 softe: 0irq_happened: 0x00 pid = 2303, comm = bash cpu 0xf: Exception 300 (Data Access) in xmon, returning to main loop xmon: WARNING: bad recursive fault on cpu 0xf ---uname output--- N/A Machine Type = powervm le ---System Hang--- System is hung ---Debugger--- A debugger is not configured ---Steps to Reproduce--- see problem description Stack trace output: no Oops output: see problem description System Dump Info: The system is not configured to capture a system dump. This patch has been sent upstream: http://patchwork.ozlabs.org/patch/413744/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396235/+subscriptions -- 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
