Soft Lockup in shrink_dentry_list+0x4e/0xe0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
In Progress
|
Undecided
|
Dave Chiluk | ||
Utopic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
BUG: soft lockup - CPU#1 stuck for 23s! [test.sh:1928]
Kernel panic - not syncing: softlockup: hung tasks
CPU: 1 PID: 1928 Comm: test.sh Tainted: G W 3.13.0-24-generic #47-Ubuntu
Hardware name: NEC Mercury CPU Module [NQ2250-
000000000000419b ffff88017fc43e28 ffffffff81715ac4 ffffffff81a5ee64
ffff88017fc43ea0 ffffffff8170ecc5 0000000000000008 ffff88017fc43eb0
ffff88017fc43e50 0000000000000086 00000000a954a952 0000000000000007
Call Trace:
<IRQ> [<ffffffff81715
[<ffffffff8170e
[<ffffffff8110d
[<ffffffff8108e
[<ffffffff8110c
[<ffffffff8108e
[<ffffffff81043
[<ffffffff81728
[<ffffffff81727
<EOI> [<ffffffff8171d
[<ffffffff811d0
[<ffffffff811d1
[<ffffffff81224
[<ffffffff81068
[<ffffffff8109e
[<ffffffff81069
[<ffffffff81069
[<ffffffff8106a
[<ffffffff81068
[<ffffffff81726
Some machines are able to reliably reproduce this soft lockup using the following script.
"
#!/bin/bash
mkdir -p testdir
cd testdir
while true; do if ! (exec >xx1 2>xx2 ; rm -f xx*; host www.google.com); then echo failed; fi ; done &
while true; do ls -lR /proc >& /dev/null; done &
while true; do lsof > /dev/null; done &
while true; do ls -H >& /dev/null; done &
wait
"
The following changes to dcache have been tested to resolve the issue.
https:/
even though the original stack trace differs, but still ends in shrink_dentry_list.
affects: | linux-meta (Ubuntu) → linux (Ubuntu) |
Changed in linux (Ubuntu Trusty): | |
assignee: | nobody → Dave Chiluk (chiluk) |
status: | New → In Progress |
Changed in linux (Ubuntu Utopic): | |
status: | Incomplete → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1354157
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.