[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-09-25 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-09-25 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-07-27 Thread Andrew Cloke
** Changed in: linux (Ubuntu) Status: Triaged => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-07-16 Thread Manoj Iyer
processor : 0 BogoMIPS: 200.00 Features: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x43 CPU architecture: 8 CPU variant : 0x1 CPU part: 0x0a1 CPU revision: 1 -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-07-11 Thread Manoj Iyer
** Attachment added: "stress-ng disk test on CRB with CONFIG_ARM64_SW_TTBR0_PAN disabled." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754053/+attachment/5162584/+files/seuss-disk.test -- You received this bug notification because you are a member of Kernel Packages, which is

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-07-11 Thread Manoj Iyer
If CONFIG_ARM64_SW_TTBR0_PAN is disabled in the kernel we dont see these random crashes anymore. I ran /usr/lib/plainbox-provider- checkbox/bin/disk_stress_ng and /usr/lib/plainbox-provider- checkbox/bin/memory_stress_ng tests on CRB (seuss) the last couple of days and did not see any crash.

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-07-11 Thread Manoj Iyer
** Changed in: linux (Ubuntu) Status: Won't Fix => Triaged ** Changed in: linux (Ubuntu Bionic) Status: Won't Fix => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-06-12 Thread Manoj Iyer
Collected more data points on this issue. 1. Tried offline CPUs. We found that the crash typically was on CPU:40, so offlined CPU40 and repeated the test. The test seemed to make progress but panicked on a different CPU. I tried to offline several more CPU, but the crash seems to move on to other

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-04-09 Thread Manoj Iyer
-- pre-req for apt-add-repository -- $ sudo apt-get install -y python-software-properties -- Install cert -- $ sudo apt-add-repository -y ppa:hardware-certification/public $ sudo apt-get update $ sudo apt-get install -y canonical-certification-server Edit this file for iperf3:        

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-04-05 Thread Manoj Iyer
-- linux mainline -- The current mainline kernel (4.16 04-01-2018) from http://kernel.ubuntu.com/~kernel-ppa/mainline/ was installed and tested using stress-ng sda. Again softlockups causing system to be unstable. ** Attachment added: "trace from 4.16 kernel."

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-04-05 Thread Manoj Iyer
Based on all the testing with different kernels I suspect this might be a HW/FW issue, and we might want to seek guidance from Cavium on how to effectively address this issue on Seuss. Please note that the issue is not reproduced on a similar CRB system, and occurs *only on* Seuss. Where there any

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-04-05 Thread Manoj Iyer
-- linux-hwe -- Reproduced with linux-hwe on xenial running stress-ng sda. We either see soft lockups or we see the kernel oopsing on random fs/jbd2/ code, which I believe is a side effect of lockups. ** Attachment added: "trace from 4.13 kernel."

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-03-30 Thread dann frazier
These observations were on a system in our lab called "seuss". My suggestions for next steps would be: 1) Determine how reliable this failure is. a) Deploy xenial/hwe on seuss, and downgrade the kernel to the version in the crash log (4.13.0-36-generic #40~16.04.1-Ubuntu). b) Run the

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-03-30 Thread dann frazier
** Description changed: Seen on a Cavium CRB1S a couple of times while running the - com.canonical.certification::disk/disk_stress_ng_sda kernel from the + com.canonical.certification::disk/disk_stress_ng_sda testcase from the canonical-certification-server test suite: [ 1823.116031]

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

2018-03-07 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Artful) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** 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.