Bug #178
closed
possible recursive locking detected in nc
Added by Wilfried Klaebe over 10 years ago.
Updated about 7 years ago.
Description
A self-compiled vanilla Linux 3.12.0 (with only a non-relevant patch), containing batman-adv 2013.4.0, network coding enabled, running in an environment with several batman-adv nodes in range, threw the attached message.
Another user's Arch linux kernel paniced completely. Digital photo of panic message available on request.
Files
Hi,
Thanks for reporting this!
I tried to recreate this issue in my virtual setup with five (smp) nodes running Arch Linux on a 3.12.1 kernel:
N1 ---- N2 ---- N3
\ /\ /
\- N3 -/ \- N4 -/
All nodes have batman-adv with NC enabled and lockup_detector compiled in:
root@n1 ~ # zgrep -E "LOCKUP_DETECTOR|BATMAN_ADV_NC" /proc/config.gz
CONFIG_BATMAN_ADV_NC=y
CONFIG_LOCKUP_DETECTOR=y
CONFIG_HARDLOCKUP_DETECTOR=y
So can you please try if this issue persists in kernel version 3.12.1-ARCH and, if so, give some information about topology and version information on the other nodes? When did the panic (and/or) lockdep issue show up and was the network under load or not?
Thanks again,
Martin
- Status changed from New to Closed
closing due to inactivity. Feel free to re-open if the problem shows up again
- Has duplicate Bug #186: 3.14: Possible recursive lock with nc enabled added
- Status changed from Closed to Rejected
Also available in: Atom
PDF