Artful verification: I was able to successfully run the above stress-ng
commmand w/o any errors on the console.
** 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.
arm64: Unfair rwlock can stall the system
Status in linux package in Ubuntu:
Status in linux source package in Artful:
There is a long-standing upstream bug with the ARM64 specific implementation
of RW locks. The implementation can starve writers under lock contention
leading to RCU stalls, driver timeouts and general system instability.
$ stress-ng --kill 0 -t 300 -v
You'll see the console fill with messages like:
[ 2534.423119] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 2534.428606] 192-...: (1 ticks this GP) idle=b6e/140000000000000/0
[ 2534.437029] (detected by 0, t=15005 jiffies, g=1479, c=1478, q=473)
[ 2714.623691] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 2714.629181] 192-...: (1 ticks this GP) idle=b6e/140000000000000/0
[ 2714.637692] (detected by 116, t=60058 jiffies, g=1479, c=1478,
[ 2747.216955] watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
[ 2775.399061] watchdog: BUG: soft lockup - CPU#13 stuck for 123s!
The proposed fix for this comprises clean cherry-picks from the v4.15 merge
window. The code modified for this fix is restricted to x86 & arm64, as they
are the only Ubuntu architectures that define ARCH_USE_QUEUED_LOCKS. Fix
verified on a 228 CPU arm64 (ThunderX2) server and regression tested on a
128-cpu x86 system using stress-ng and locktorture.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~kernel-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp