Re: kern/41918: pppoe BROKEN: panic:kernel diagnostic assertion "!cpu_softintr_p()" ... subr_kmem.c

[Martin Husemann <martin%duskware.de@localhost>]

The following reply was made to PR kern/41918; it has been noted by GNATS.

From: Martin Husemann <martin%duskware.de@localhost>
To: David Young <dyoung%pobox.com@localhost>, Christos Zoulas 
<christos%zoulas.com@localhost>,
        gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost,
        gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
        kardel%pip.acrys.com@localhost
Cc: 
Subject: Re: kern/41918: pppoe BROKEN: panic:kernel diagnostic assertion 
"!cpu_softintr_p()" ... subr_kmem.c
Date: Sun, 23 Aug 2009 20:10:25 +0200

 On Sun, Aug 23, 2009 at 12:44:23PM -0500, David Young wrote:
 > which should modify IFF_RUNNING, instead.  I don't understand how/why
 > pppoe(4) messes with IFF_UP, yet, but it probably should not.
 
 Hysterical raisinins mostly. This part was originally done for ISDN 
connections.
 It prevented routing further packets down the interface while the connection
 was being established (which might take quite some time) - preventing a
 sure imediate quueue overflow and packet loss, basically causing retransmits
 and often have the (expensive) ISDN connection's idle timeout fire before
 the retry.
 
 I agree it is ugly, I'm open to suggestions how to do it differently, but
 we should probably disuss that outside of gnats separately.
 
 Martin