subject:"\[Kernel\-packages\] \[Bug 1746225\] Re\: \[P9, Power NV\]\[WSP\]\[Ubuntu 1804\] \: \"Kernel access of bad area \" when grouping different pmu events using perf fuzzer . \(perf\:\)"

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-04-04 Thread Frank Heimes

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

-- 
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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
  and results in a call trace shown in the bug.  It is due to grouping of 
  different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1

  Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
  v4.15-rc5.

  
  == Fix ==
  commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
  Author: Ravi Bangoria 
  Date:   Thu Nov 30 14:03:22 2017 +0530

  powerpc/perf: Fix oops when grouping different pmu events

  
  == Regression Potential ==
  Low.  This fix is specific to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13

  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048
  [78592.995985] NUMA
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 

  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028
  [78592.996642] GPR12:  c7a8d480  

  [78592.996642] GPR16:    

  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        

  [78592.997664]        

  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780]
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-04-03 Thread Launchpad Bug Tracker

This bug was fixed in the package linux - 4.13.0-38.43

---
linux (4.13.0-38.43) artful; urgency=medium

  * linux: 4.13.0-38.43 -proposed tracker (LP: #1755762)

  * Servers going OOM after updating kernel from 4.10 to 4.13 (LP: #1748408)
- i40e: Fix memory leak related filter programming status
- i40e: Add programming descriptors to cleaned_count

  * [SRU] Lenovo E41 Mic mute hotkey is not responding (LP: #1753347)
- platform/x86: ideapad-laptop: Increase timeout to wait for EC answer

  * fails to dump with latest kpti fixes (LP: #1750021)
- kdump: write correct address of mem_section into vmcoreinfo

  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines
- ALSA: hda - Fix a wrong FIXUP for alc289 on Dell machines

  * CIFS SMB2/SMB3 does not work for domain based DFS (LP: #1747572)
- CIFS: make IPC a regular tcon
- CIFS: use tcon_ipc instead of use_ipc parameter of SMB2_ioctl
- CIFS: dump IPC tcon in debug proc file

  * i2c-thunderx: erroneous error message "unhandled state: 0" (LP: #1754076)
- i2c: octeon: Prevent error message on bus error

  * hisi_sas: Add disk LED support (LP: #1752695)
- scsi: hisi_sas: directly attached disk LED feature for v2 hw

  * EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs
entries with KNL SNC2/SNC4 mode) (LP: #1743856)
- EDAC, sb_edac: Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode

  * [regression] Colour banding and artefacts appear system-wide on an Asus
Zenbook UX303LA with Intel HD 4400 graphics (LP: #1749420)
- drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA

  * DVB Card with SAA7146 chipset not working (LP: #1742316)
- vmalloc: fix __GFP_HIGHMEM usage for vmalloc_32 on 32b systems

  * [Asus UX360UA] battery status in unity-panel is not changing when battery is
being charged (LP: #1661876) // AC adapter status not detected on Asus
ZenBook UX410UAK (LP: #1745032)
- ACPI / battery: Add quirk for Asus UX360UA and UX410UAK

  * ASUS UX305LA - Battery state not detected correctly (LP: #1482390)
- ACPI / battery: Add quirk for Asus GL502VSK and UX305LA

  * support thunderx2 vendor pmu events (LP: #1747523)
- perf pmu: Extract function to get JSON alias map
- perf pmu: Pass pmu as a parameter to get_cpuid_str()
- perf tools arm64: Add support for get_cpuid_str function.
- perf pmu: Add helper function is_pmu_core to detect PMU CORE devices
- perf vendor events arm64: Add ThunderX2 implementation defined pmu core
  events
- perf pmu: Add check for valid cpuid in perf_pmu__find_map()

  * lpfc.ko module doesn't work (LP: #1746970)
- scsi: lpfc: Fix loop mode target discovery

  * Ubuntu 17.10 crashes on vmalloc.c (LP: #1739498)
- powerpc/mm/book3s64: Make KERN_IO_START a variable
- powerpc/mm/slb: Move comment next to the code it's referring to
- powerpc/mm/hash64: Make vmalloc 56T on hash

  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p

  * CVE-2017-17807
- KEYS: add missing permission check for request_key() destination

  * [Artful SRU] Fix capsule update regression (LP: #1746019)
- efi/capsule-loader: Reinstate virtual capsule mapping

  * [Artful/Bionic] [Config] enable EDAC_GHES for ARM64 (LP: #1747746)
- Ubuntu: [Config] enable EDAC_GHES for ARM64

  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd

  * Cherry pick c96f5471ce7d for delayacct fix (LP: #1747769)
- delayacct: Account blkio completion on the correct task

  * Error in CPU frequency reporting when nominal and min pstates are same
(cpufreq) (LP: #1746174)
- cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin

  * retpoline abi files are empty on i386 (LP: #1751021)
- [Packaging] retpoline-extract -- instantiate retpoline files for i386
- [Packaging] final-checks -- sanity checking ABI contents
- [Packaging] final-checks -- check for empty retpoline files

  * [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping
different pmu events using perf fuzzer . (perf:) (LP: #1746225)
- powerpc/perf: Fix oops when grouping different pmu events

  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware

  * Ubuntu16.04.03: ISAv3 initialize MMU registers before setting partition
table (LP: #1736145)
- powerpc/64s: Initialize ISAv3 MMU registers before setting partition table

  * powerpc/powernv: Flush console before platform error reboot (LP: #1735159)
-

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-03-26 Thread Manoj Iyer

** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

-- 
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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
  and results in a call trace shown in the bug.  It is due to grouping of 
  different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1

  Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
  v4.15-rc5.

  
  == Fix ==
  commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
  Author: Ravi Bangoria 
  Date:   Thu Nov 30 14:03:22 2017 +0530

  powerpc/perf: Fix oops when grouping different pmu events

  
  == Regression Potential ==
  Low.  This fix is specific to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13

  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048
  [78592.995985] NUMA
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 

  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028
  [78592.996642] GPR12:  c7a8d480  

  [78592.996642] GPR16:    

  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        

  [78592.997664]        

  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780]
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-03-19 Thread Stefan Bader

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-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

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-artful

-- 
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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
  and results in a call trace shown in the bug.  It is due to grouping of 
  different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1

  Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
  v4.15-rc5.

  
  == Fix ==
  commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
  Author: Ravi Bangoria 
  Date:   Thu Nov 30 14:03:22 2017 +0530

  powerpc/perf: Fix oops when grouping different pmu events

  
  == Regression Potential ==
  Low.  This fix is specific to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13

  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048
  [78592.995985] NUMA
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 

  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028
  [78592.996642] GPR12:  c7a8d480  

  [78592.996642] GPR16:    

  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038]

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-03-05 Thread Manoj Iyer

** Changed in: ubuntu-power-systems
   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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
  and results in a call trace shown in the bug.  It is due to grouping of 
  different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1

  Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
  v4.15-rc5.

  
  == Fix ==
  commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
  Author: Ravi Bangoria 
  Date:   Thu Nov 30 14:03:22 2017 +0530

  powerpc/perf: Fix oops when grouping different pmu events

  
  == Regression Potential ==
  Low.  This fix is specific to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13

  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048
  [78592.995985] NUMA
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 

  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028
  [78592.996642] GPR12:  c7a8d480  

  [78592.996642] GPR16:    

  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        

  [78592.997664]        

  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780]
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-03-01 Thread Kleber Sacilotto de Souza

** Changed in: linux (Ubuntu Artful)
   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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
  and results in a call trace shown in the bug.  It is due to grouping of 
  different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1

  Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
  v4.15-rc5.

  
  == Fix ==
  commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
  Author: Ravi Bangoria 
  Date:   Thu Nov 30 14:03:22 2017 +0530

  powerpc/perf: Fix oops when grouping different pmu events

  
  == Regression Potential ==
  Low.  This fix is specific to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13

  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048
  [78592.995985] NUMA
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 

  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028
  [78592.996642] GPR12:  c7a8d480  

  [78592.996642] GPR16:    

  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        

  [78592.997664]        

  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780]
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-02-27 Thread Joseph Salisbury

** Changed in: linux (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
  and results in a call trace shown in the bug.  It is due to grouping of 
  different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1

  Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
  v4.15-rc5.

  
  == Fix ==
  commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
  Author: Ravi Bangoria 
  Date:   Thu Nov 30 14:03:22 2017 +0530

  powerpc/perf: Fix oops when grouping different pmu events

  
  == Regression Potential ==
  Low.  This fix is specific to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13

  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048
  [78592.995985] NUMA
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 

  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028
  [78592.996642] GPR12:  c7a8d480  

  [78592.996642] GPR16:    

  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        

  [78592.997664]        

  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780]
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to other

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-02-26 Thread Manoj Iyer

This should be available in Bionic now. The patch was applied to bionic
earlier this month. And, in Artful in a couple of weeks.

-- 
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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
  and results in a call trace shown in the bug.  It is due to grouping of 
  different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1

  Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
  v4.15-rc5.

  
  == Fix ==
  commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
  Author: Ravi Bangoria 
  Date:   Thu Nov 30 14:03:22 2017 +0530

  powerpc/perf: Fix oops when grouping different pmu events

  
  == Regression Potential ==
  Low.  This fix is specific to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13

  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048
  [78592.995985] NUMA
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 

  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028
  [78592.996642] GPR12:  c7a8d480  

  [78592.996642] GPR16:    

  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        

  [78592.997664]        

  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780]
  [78594.008932] Sending

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-02-13 Thread Frank Heimes

According to comment #5 the SRU request was already submitted and is in 
progress.
So it usually will go out with the next SRU cycle, but that might be held up a 
bit due to  Spectre/Meltdown activities.

-- 
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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
  and results in a call trace shown in the bug.  It is due to grouping of 
  different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1

  Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
  v4.15-rc5.

  
  == Fix ==
  commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
  Author: Ravi Bangoria 
  Date:   Thu Nov 30 14:03:22 2017 +0530

  powerpc/perf: Fix oops when grouping different pmu events

  
  == Regression Potential ==
  Low.  This fix is specific to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13

  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048
  [78592.995985] NUMA
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 

  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028
  [78592.996642] GPR12:  c7a8d480  

  [78592.996642] GPR16:    

  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        

  [78592.997664]        

  [78592.997733] ---[ end trace

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-02-03 Thread Seth Forshee

** Changed in: linux (Ubuntu Bionic)
   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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
  and results in a call trace shown in the bug.  It is due to grouping of 
  different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1

  Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
  v4.15-rc5.

  
  == Fix ==
  commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
  Author: Ravi Bangoria 
  Date:   Thu Nov 30 14:03:22 2017 +0530

  powerpc/perf: Fix oops when grouping different pmu events

  
  == Regression Potential ==
  Low.  This fix is specific to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13

  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048
  [78592.995985] NUMA
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 

  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028
  [78592.996642] GPR12:  c7a8d480  

  [78592.996642] GPR16:    

  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        

  [78592.997664]        

  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780]
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-02-02 Thread Joseph Salisbury

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089902.html

** Description changed:

+ == SRU Justification ==
+ Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
+ and results in a call trace shown in the bug.  It is due to grouping of 
+ different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1
+ 
+ Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
+ v4.15-rc5.
+ 
+ 
+ == Fix ==
+ commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
+ Author: Ravi Bangoria 
+ Date:   Thu Nov 30 14:03:22 2017 +0530
+ 
+ powerpc/perf: Fix oops when grouping different pmu events
+ 
+ 
+ == Regression Potential ==
+ Low.  This fix is specific to powerpc.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.
  
  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13
  
- 
  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
- [78592.995982] SMP NR_CPUS=2048 
- [78592.995985] NUMA 
+ [78592.995982] SMP NR_CPUS=2048
+ [78592.995985] NUMA
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
- [78592.996642] CFAR: c00e9b18 SOFTE: 1 
- [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 
 
- [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10 
- [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028 
- [78592.996642] GPR12:  c7a8d480  
 
- [78592.996642] GPR16:    
 
- [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98 
- [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0 
- [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190 
+ [78592.996642] CFAR: c00e9b18 SOFTE: 1
+ [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 

+ [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10
+ [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028
+ [78592.996642] GPR12:  c7a8d480  

+ [78592.996642] GPR16:    

+ [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98
+ [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0
+ [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-01-31 Thread Joseph Salisbury

I built a test kernel with commit 5aa04b3eb6fca.  The test kernel can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1746225

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

-- 
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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13


  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048 
  [78592.995985] NUMA 
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1 
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 
 
  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10 
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028 
  [78592.996642] GPR12:  c7a8d480  
 
  [78592.996642] GPR16:    
 
  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98 
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0 
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190 
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        
 
  [78592.997664]        
 
  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780] 
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to other CPUs
  [78594.01029

  Steps to reproduce :
  

  #! /bin/bash
  set -x
  git clone https://github.com/deater/perf_event_tests.git
  cd perf_event_tests/include
  mkdir asm
  cd asm
  wget http://9.114.13.132/repo/shriya/perf_regs.h
  cd ../../lib
  make
  sleep 10
  cd ../fuzzer
  make
  sleep 10

  echo 0 > /proc/sys/kernel/nmi_watchdog
  echo 2 > /proc/sys/kernel/perf_event_paranoid
  echo 10 > /proc/sys/kernel/perf_event_max_sample_rate
  ./perf_fuzzer -r 1492143527

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-01-31 Thread Frank Heimes

** Changed in: ubuntu-power-systems
   Status: New => In Progress

-- 
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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13


  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048 
  [78592.995985] NUMA 
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1 
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 
 
  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10 
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028 
  [78592.996642] GPR12:  c7a8d480  
 
  [78592.996642] GPR16:    
 
  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98 
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0 
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190 
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        
 
  [78592.997664]        
 
  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780] 
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to other CPUs
  [78594.01029

  Steps to reproduce :
  

  #! /bin/bash
  set -x
  git clone https://github.com/deater/perf_event_tests.git
  cd perf_event_tests/include
  mkdir asm
  cd asm
  wget http://9.114.13.132/repo/shriya/perf_regs.h
  cd ../../lib
  make
  sleep 10
  cd ../fuzzer
  make
  sleep 10

  echo 0 > /proc/sys/kernel/nmi_watchdog
  echo 2 > /proc/sys/kernel/perf_event_paranoid
  echo 10 > /proc/sys/kernel/perf_event_max_sample_rate
  ./perf_fuzzer -r 1492143527

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746225/+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 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-01-31 Thread Joseph Salisbury

** Changed in: linux (Ubuntu)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Joseph Salisbury (jsalisbury)

** Also affects: linux (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Critical
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

** Changed in: linux (Ubuntu Artful)
   Status: New => In Progress

** Changed in: linux (Ubuntu Artful)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

-- 
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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13


  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048 
  [78592.995985] NUMA 
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1 
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 
 
  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10 
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028 
  [78592.996642] GPR12:  c7a8d480  
 
  [78592.996642] GPR16:    
 
  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98 
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0 
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190 
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        
 
  [78592.997664]        
 
  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780] 
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to other CPUs
  [78594.01029

  Steps to reproduce :
  

  #! /bin/bash
  set -x
  git clone https://github.com/deater/perf_event_tests.git
  cd perf_event_tests/include
  mkdir asm
  cd asm
  wget http://9.114.13.132/repo/shriya/perf_regs.h
  cd ../../lib
  make

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

2018-01-30 Thread Joseph Salisbury

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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 this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15


** Tags added: kernel-da-key

** Changed in: kernel-package (Ubuntu)
   Importance: Undecided => Critical

** Package changed: kernel-package (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/1746225

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13


  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048 
  [78592.995985] NUMA 
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1 
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 
 
  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10 
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028 
  [78592.996642] GPR12:  c7a8d480  
 
  [78592.996642] GPR16:    
 
  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98 
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0 
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190 
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        
 
  [78592.997664]        
 
  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780] 
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to other CPUs
  [78594.01029

  Steps to reproduce :
  

  #! /bin/bash
  set -x
  git clone https://github.com/deater/perf_event_tests.git
  cd perf_event_tests/include
  mkdir asm
  cd asm
  wget

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

15 matches

Site Navigation

Mail list logo

Footer information