When it happened to me back then (2022) I'm pretty sure I did a "down" followed by a "delete" and then the "destroy". Have not tried to recreate since then.
On Wed, Oct 4, 2023 at 10:31 AM Alexander Bluhm <alexander.bl...@gmx.net> wrote: > On Wed, Oct 04, 2023 at 10:08:01AM -0400, Sonic wrote: > > See the post: > > "Uninterruptible D State after ifconfig wg0 destroy" Oct. 31, 2022 in the > > Bugs archive. > > I have a test regress/sys/net/wg that configures a wg(4), sends > some traffic, and destroys it. I have never seen this bug. There > must be something special to trigger it. > > If it happns again, could you send an 'ps axlww | grep ifconifg' > output? Then we see the wait channel where it hangs in the kernel. > > $ ps axlww > UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME > COMMAND > > The WCHAN string can be found in the kernel sources and gives hints. > More sophisticated would be to break into ddb and show the kernel > stack trace of the ifconfig process. If you want to do that, I can > give some advice. But I recommend a serial console for that. > > Any idea what you did specially to trigger the problem? > > bluhm >
