Bug 216731 - [patch] if_lagg.c: Boot hang due to LOR in lagg initialization
Summary: [patch] if_lagg.c: Boot hang due to LOR in lagg initialization
Status: Closed DUPLICATE of bug 194109
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 11.0-RELEASE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-net (Nobody)
URL:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2017-02-02 16:26 UTC by J.R. Oldroyd
Modified: 2017-02-15 17:38 UTC (History)
1 user (show)

See Also:

Attachments
Patch to drop and re-aquire lock (621 bytes, patch)
2017-02-02 16:26 UTC, J.R. Oldroyd 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description J.R. Oldroyd 2017-02-02 16:26:11 UTC 
Created attachment 179534 [details]
Patch to drop and re-aquire lock

Discussed in freebsd-wireless, here: https://lists.freebsd.org/pipermail/freebsd-wireless/2016-December/007391.html

FreeBSD 11.0 occasionally hangs during boot due to a LOR between if_lagg.c and if_re.c.  The attached patch drops one of the locks in if_lagg.c before calling the lower driver's initialization, then re-acquires the lock after.
Comment 1 Alan Somers freebsd_committer freebsd_triage 2017-02-03 17:06:23 UTC 
Can you still reproduce the problem on FreeBSD/head after r309177?
Comment 2 J.R. Oldroyd 2017-02-04 18:22:03 UTC 
I have removed my patch and applied the r309177 patch and am running with that now.

Since the deadlock hang was intermittent, I will need to test a while to know if this resolves the problem.  I'll post back in a week or two.
Comment 3 J.R. Oldroyd 2017-02-15 17:28:26 UTC 
Well, it's been 10 days now, with many reboots of the system in question over this time.  No hangs to report.

That would suggest that the patch in r309177 also resolves this problem.
Comment 4 Alan Somers freebsd_committer freebsd_triage 2017-02-15 17:38:24 UTC 
Glad to hear it, fbsd@opal.com

*** This bug has been marked as a duplicate of bug 194109 ***