Bug 195042 - 10.1 regression: background dhcp client, wlan, lagg, default route page fault
Summary: 10.1 regression: background dhcp client, wlan, lagg, default route page fault
Status: Closed DUPLICATE of bug 195074
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: 10.1-STABLE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-wireless (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-15 17:14 UTC by Nikolai Lifanov
Modified: 2016-05-17 17:41 UTC (History)
1 user (show)

See Also:

Attachments
core summary for the crash (186.92 KB, text/plain)
2014-11-15 17:14 UTC, Nikolai Lifanov 		no flags Details
core crash summary: 10.2-BETA1 (171.67 KB, text/plain)
2015-07-12 17:23 UTC, Nikolai Lifanov 		no flags Details
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 Nikolai Lifanov 2014-11-15 17:14:21 UTC 
Created attachment 149447 [details]
core summary for the crash

This seems to be the case with at least 10.1-RC3, 10.1-RC4, and 10.1-RELEASE, but not 10.0: if lagg comes up with a wlan interface and dhcp client is backgrounded, I get a panic when bringing up the default route interface.
This doesn't happen when lagg attaches to a wired interface (timing, probably) or when I run dhcp client synchronously.
Crash summary is attached.
Comment 1 Marcus von Appen freebsd_committer freebsd_triage 2015-02-18 11:54:21 UTC 
Updated 10.1-BETA and 10.1-RC versioned bugs to 10.1-STABLE.
Comment 2 Glen Barber freebsd_committer freebsd_triage 2015-07-07 16:03:08 UTC 
Is this still an issue on 10.2-PRERELEASE?
Comment 3 Nikolai Lifanov 2015-07-12 17:23:57 UTC 
Created attachment 158659 [details]
core crash summary: 10.2-BETA1

I confirmed that this is still an issue in 10.2-BETA1.
Comment 4 Andriy Voskoboinyk freebsd_committer freebsd_triage 2016-05-17 17:41:00 UTC 
The same problem as in PR 195074; fixed in r288990 but not MFCed to 10-STABLE yet.

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