Date: Tue, 03 May 2022 23:52:03 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 263707] iwlwifi crashed and would not recover after network fail-over Message-ID: <bug-263707-21060-z1BwikLxqz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-263707-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-263707-21060@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263707 --- Comment #4 from rkoberman@gmail.com --- A this point I am unsure whether to open a new ticket or change the subject= on this one. My initial idea of the cause (and hte subject) was wrong. The fail-over triggered the problem, but otherwise had nothing to do with it. The real problem was the driver crashing when I enabled IPv6 with a static address on the interface. Once I removed the static address, ran rtsold and set the interface to accept_rtadv, it came up correctly and I had IPv6 connectivity to the FreeB= SD package build systems web pages to access build reports. (Other things, too, but that and google are the only ones I tested.) I have no idea why a static address would cause the iwlwifi driver to crash, but it did... repeatedly. I will admit that i may have had a configuration error from editing rc.conf to switch from an HE tunnel to native access but= I still don't see why that would cause the driver to fail. I will probably try going back to a static address in a while, but I need the system stable for today. As I already have the logs of the crashes in this ticket, I tempted to keep= it with a new subject, but that might create confusion. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263707-21060-z1BwikLxqz>