[Bug 1710690] Re: Ubuntu16.04.3: System running network stress crashes with Alignment exception

2018-01-22 Thread Manoj Iyer
Closing the bug based on IBM's comments. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: ubuntu-power-systems Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1710690] Re: Ubuntu16.04.3: System running network stress crashes with Alignment exception

2017-12-04 Thread Manoj Iyer
** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1710690] Re: Ubuntu16.04.3: System running network stress crashes with Alignment exception

2017-11-06 Thread Manoj Iyer
** Changed in: linux (Ubuntu) Status: Triaged => Incomplete ** Changed in: ubuntu-power-systems Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710690

[Bug 1710690] Re: Ubuntu16.04.3: System running network stress crashes with Alignment exception

2017-09-11 Thread Frank Heimes
** Changed in: ubuntu-power-systems Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710690 Title: Ubuntu16.04.3: System running network stress crashes with Alignment

[Bug 1710690] Re: Ubuntu16.04.3: System running network stress crashes with Alignment exception

2017-09-06 Thread Joseph Salisbury
I built a Zesty test kernel with commit 1ae948fa4f00f3a2823e7cb19a3049ef27dd6947 from linux-next. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1710690/ Can you test this kernel and see if it resolves this bug? -- You received this bug notification because you

[Bug 1710690] Re: Ubuntu16.04.3: System running network stress crashes with Alignment exception

2017-09-05 Thread Joseph Salisbury
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710690 Title: Ubuntu16.04.3: System running network stress crashes with Alignment

[Bug 1710690] Re: Ubuntu16.04.3: System running network stress crashes with Alignment exception

2017-08-21 Thread Manoj Iyer
** Tags added: triage-g -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710690 Title: Ubuntu16.04.3: System running network stress crashes with Alignment exception To manage notifications about

[Bug 1710690] Re: Ubuntu16.04.3: System running network stress crashes with Alignment exception

2017-08-16 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 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

[Bug 1710690] Re: Ubuntu16.04.3: System running network stress crashes with Alignment exception

2017-08-16 Thread Andrew Cloke
** Changed in: ubuntu-power-systems Assignee: Canonical Server Team (canonical-server) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710690

[Bug 1710690] Re: Ubuntu16.04.3: System running network stress crashes with Alignment exception

2017-08-14 Thread Frank Heimes
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Server Team (canonical-server) ** Changed in: ubuntu-power-systems Importance: Undecided => High -- You received this bug