This bug was fixed in the package linux - 3.11.0-15.23
---
linux (3.11.0-15.23) saucy; urgency=low
[Brad Figg]
* Release Tracking Bug
- LP: #1259259
[ Tim Gardner ]
* [Config] Build-in ohci-pci
- LP: #1244176
linux (3.11.0-15.22) saucy; urgency=low
[Brad Figg]
Added Tag ; Verification-done-saucy based on comment #17
** Tags removed: verification-needed-saucy
** Tags added: verification-done-saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239800
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-
saucy' to 'verification-done-saucy'.
If verification is not done by 5 working days from
I can verify that I was unable to reproduce this bug with the latest
proposed kernel on a highbank.
ubuntu@hb07-15:~$ cat /etc/issue
Ubuntu 13.10 \n \l
ubuntu@hb07-15:~$ uname -a
Linux hb07-15 3.11.0-15-generic #22-Ubuntu SMP Mon Dec 2 23:36:39 UTC 2013
armv7l armv7l armv7l GNU/Linux
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239800
Title:
Soft lockup when running bonnie++ only at 1600 mt/s
To manage
** Description changed:
+ SRU Justification:
+
+ Impact: running a test like bonnie++ makes the system instable and prone
+ to hangs.
+
+ Fix: apply the attached patches and recompile a kernel.
+
+ Test case: leave bonnie running in a loop for 24hrs.
+
+ --
+
When bonnie++ was run in a
** Patch added:
0002-ARM-7855-1-Add-check-for-Cortex-A15-errata-798181-EC.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239800/+attachment/3901317/+files/0002-ARM-7855-1-Add-check-for-Cortex-A15-errata-798181-EC.patch
--
You received this bug notification because you are a
Patch 0001 in #13 is a prerequisite for patch 0002 in #14, that actually
solves the problem: both of them are already in Linus tree.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239800
Title:
** Patch added:
0001-ARM-tlb-don-t-perform-inner-shareable-invalidation-f.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239800/+attachment/3901316/+files/0001-ARM-tlb-don-t-perform-inner-shareable-invalidation-f.patch
--
You received this bug notification because you are a
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239800
Title:
Soft lockup when running bonnie++ only at 1600 mt/s
To manage notifications about this bug go to:
Kernel 3.11.0-5.11 has been deleted from ports.ubuntu.com. Is there
another way to get hold of this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239800
Title:
Soft lockup when running bonnie++
When this occured, was there any symptoms other than the self detected
stall. Did the machine continue and recover.
@Pardeep -- all versions are in the launchpad librarian under the source
listing page for the linux package.
--
You received this bug notification because you are a member of
@Pardeep, a direct link to the 3.11.0-5.11 kernel is:
https://launchpad.net/ubuntu/+source/linux/3.11.0-5.11
The .deb files can be found by clicking the arch under Builds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The node was unresponsive and could not be recovered.
It needed a hard reset to continue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239800
Title:
Soft lockup when running bonnie++ only at 1600
Are you unable to reprduce this bug if you boot back into: 3.11.0-5.11 ?
If that is the case, we should be able to perform a bisect to identify
the commit that introduced this.
It might also be worthwhile to test the latest mainline kernel, which can be
downloaded from:
apport information
** Tags added: apport-collected
** Description changed:
When bonnie++ was run in a loop, the system exhibits a hang behavior with
rcu_sched: self-detected stall on CPU
The time to error can be inconsistent. One time it took 7 hours and the next
time more than 2 days.
As this bug repots a hang behavior apport log collection tool cannot be
run at the time of the hang. However, I tried to run this after a
reboot, but the python script crashed. Please let me know if you need
additional info.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
17 matches
Mail list logo
