This bug was fixed in the package linux - 3.13.0-58.97
---
linux (3.13.0-58.97) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1472453
[ Upstream Kernel Changes ]
* vm: Fix incomplete backport of VM_FAULT_SIGSEGV handling support
- LP: #1471892
This bug was fixed in the package linux - 3.16.0-44.59
---
linux (3.16.0-44.59) utopic; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1472030
[ Iyappan Subramanian ]
* SAUCE: (no-up) drivers: net: xgene: fix: Out of order descriptor bytes
read
- LP:
This bug was fixed in the package linux - 3.13.0-58.97
---
linux (3.13.0-58.97) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1472453
[ Upstream Kernel Changes ]
* vm: Fix incomplete backport of VM_FAULT_SIGSEGV handling support
- LP: #1471892
This bug was fixed in the package linux - 3.16.0-44.59
---
linux (3.16.0-44.59) utopic; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1472030
[ Iyappan Subramanian ]
* SAUCE: (no-up) drivers: net: xgene: fix: Out of order descriptor bytes
read
- LP:
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
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
ubuntu@am2:~$ iperf -c 10.228.0.2 -P 8 -t 120
Client connecting to 10.228.0.2, TCP port 5001
TCP window size: 85.0 KByte (default)
[ 10] local 10.228.66.98 port 59722 connected
ubuntu@ms10-40-mcdivittA3:~$ uname -a
Linux ms10-40-mcdivittA3 3.16.0-44-generic #59-Ubuntu SMP Tue Jul 7 02:18:58
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@ms10-40-mcdivittA3:~$
ubuntu@ms10-40-mcdivittA3:~$
ubuntu@ms10-40-mcdivittA3:~$
ubuntu@ms10-40-mcdivittA3:~$ iperf -c
** Changed in: linux (Ubuntu Utopic)
Status: In Progress = Fix Committed
** Changed in: linux (Ubuntu Trusty)
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.
** Description changed:
- This crash was submitted upstream and a fix was already present, but it
- didn't land until the 3.19 kernel. This bug is to track getting that fix
- into trusty and utopic.
+ [Impact]
+ System panics every few hours under constant network load
- Unable to handle
After testing with the proposed backport[1], I was able to run the iperf
test overnight on a trusty kernel w/o any crashes.
[1]http://kernel.ubuntu.com/git/ming/ubuntu-utopic.git/commit/?h=arm64
-net-backportid=d46456e3ed9153e743f2add6e01d06c56eb2ceb7
** Changed in: linux (Ubuntu Trusty)
Finally I figured out one approach to reproduce it quickly, see the
attachment log.
** Attachment added: crash log in trusty
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1425576/+attachment/4416913/+files/dmesg-trusty.log
--
You received this bug notification because you are a
** Attachment added: crash log in utopic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1425576/+attachment/4416914/+files/dmesg-utopic.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
And the patches in below links can fix the above crashs(#14, #15)
http://kernel.ubuntu.com/git/ming/ubuntu-trusty.git/commit/?h=apm-enet-
fixid=a19b2c0bdd12e59a482717664312b18407284ee5
http://kernel.ubuntu.com/git/ming/ubuntu-utopic.git/commit/?h=arm64-net-
I can't confirm that this is 100% the same issue since the backtrace
isn't identical, but I was able to hit the following panic on trusty's
3.13 just by running iperf to another system for a few hours:
[ 2613.269450] BUG: Bad page state in process iperf pfn:41d5c57
[ 2613.275172]
From the original report, the issue happened since 3.17, so close it on trysty
because we can't reproduce it
on trusty too.
I've seen this with mainline since somewhere in v3.17 and on several
hardware boards stress testing KVM by running workloads in VMs.
** Changed in:
I have not been able to find a reliable way to reproduce this issue, but
the fix did not cause any issues in my testing.
--
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/1425576
Title:
That test kernel should have upstream commit: 0b46b8a, which is the
following commit in Utopic:
commit e16bd2b7e29c5434505929deda4c6bb4436104d3
Author: Sonny Rao sonny...@chromium.org
Date: Sun Nov 23 23:02:44 2014 -0800
clocksource: arch_timer: Fix code to use physical timers when
Hmm, right commit ecf6ba83, the fix for this bug, is in mainline as of
3.19 final, so Vivid should already have the fix for both bugs.
Maybe I'll build a Utopic test kernel using the master-next branch.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I built a Utopic test kernel from the master-next branch, with a cherry-
pick of commit ecf6ba83d.
It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1425576/
Can you test this kernel to see if it resolves the bug and does not
exhibit bug 1426043 ?
--
You received this bug
One final issue is the kernel version you used to test this fix contains
a bug that prevents it from booting on arm64 systems. The fix is in the
utopic-stable branch to be pulled into the next SRU cycle. The fix was
pushed into the latest trusty kernel for a one-off release,
3.13.0-46.76. You can
I just looked at your packages and noticed they are for amd64, this
issue is an xgene (arm64) platform bug. If you give me the a point to
the git tree I can build the packages myself and test. Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Sorry for building amd64. I no have arm64 packages available with a
cherry pick of commit ecf6ba83d. They can be downloaded from the same
location:
http://kernel.ubuntu.com/~jsalisbury/lp1425576/
If you also need my git tree, I'll move it to a public spot on
zinc(kernel.ubuntu.com). But it's
Commit ecf6ba83d wasn't cc'd to stable. I built a Utopic test kernel
with a cherry pick of the commit. It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1425576/
Can you test this kernel to see if it resolves the bug? If it does, we
can send a request to the upstream stable
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
Here is a direct link to the upstream submission of the crash:
http://www.spinics.net/lists/arm-kernel/msg399023.html
The upstream commit that fixes it is:
commit ecf6ba83d76e0c78e89401750dc527008e14faa2
Author: Iyappan Subramanian isubramanian@xxx
Date: Thu Jan 29 14:38:23 2015 -0800
26 matches
Mail list logo
