Re: port-amd64/55661: pppoe renegotiation timeout causing pani

[s ymgch <s.ymgch228%gmail.com@localhost>]

The following reply was made to PR port-amd64/55661; it has been noted by GNATS.

From: s ymgch <s.ymgch228%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost, roy%marples.name@localhost
Cc: port-amd64-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
	netbsd-bugs%netbsd.org@localhost
Subject: Re: port-amd64/55661: pppoe renegotiation timeout causing pani
Date: Thu, 26 Nov 2020 16:17:10 +0900

 Hi,
 
 I committed some fixes around pppoe(4). And these may have fixed the panic.
 Can you check?
 
 -- yamaguchi
 
 On Thu, Sep 24, 2020 at 12:00 PM Roy Marples <roy%marples.name@localhost> wrote:
 >
 > The following reply was made to PR port-amd64/55661; it has been noted by GNATS.
 >
 > From: Roy Marples <roy%marples.name@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc:
 > Subject: Re: port-amd64/55661: pppoe renegotiation timeout causing pani
 > Date: Thu, 24 Sep 2020 03:56:03 +0100
 >
 >  I can reliably reproduce this on NetBSD-9.99.73 without an ISP.
 >
 >  I have setup a pppoe(4) interface with LINK0 and enabled PPPOE server in the kernel.
 >  I have a VM that in turn is a pppoe client for the above.
 >  Upon shutting down the VM, the NetBSD host panics.
 >
 >  Slightly blurred backtrace here:
 >  https://photos.app.goo.gl/6KRiUe3ifdhRDgy19
 >
 >  Riastradh | sppp_keepalive needs to defer if_down to workqueue
 >  Riastradh | not fully fixed, please reopen and share stack trace with yamaguchi-san
 >
 >  Roy
 >