Date: Sun, 24 Apr 2022 04:11:43 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl>, freebsd-hackers@freebsd.org Subject: Re: kernel crash making a vlan on a wlan Message-ID: <113d6d4d-eb23-30b1-a9e7-5a82a46604f8@grosbein.net> In-Reply-To: <28c9ea32-b913-c153-005b-a62d6a7a6f4e@plan-b.pwste.edu.pl> References: <f08424d6-e209-928b-9927-3cc6c0aabb22@hesiod.org> <421d0c0d-4109-3370-9147-85168051deed@freebsd.org> <9ea3536e-b501-3684-850e-65f95fddf2e7@freebsd.org> <28c9ea32-b913-c153-005b-a62d6a7a6f4e@plan-b.pwste.edu.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
24.04.2022 3:28, Marek Zarychta wrote: > W dniu 23.04.2022 o 22:11, Craig Leres pisze: >> >> On 4/23/22 11:12, Craig Leres wrote: >>> I am able to reproduce the crash with 13.1-RC4. >> >> I'm also able to reproduce the crash on 12.3-RELEASE-p5. It seems wlan0 is part of the recipe, I tried vlans_em0="vlan0" first but was not able to induce a crash. >> >> Craig >> > > I am curious what is this WiFi hardware that supports 802.1q tagging over the air? Could you please reveal this? > > That's rather not a bug when you are shooting yourself in the foot. Kernel panic due to ifconfig command is always a bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?113d6d4d-eb23-30b1-a9e7-5a82a46604f8>