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

[christos%zoulas.com@localhost (Christos Zoulas)]

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

From: christos%zoulas.com@localhost (Christos Zoulas)
To: 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 15:29:07 -0400

 On Aug 23,  5:45pm, dyoung%pobox.com@localhost (David Young) wrote:
 -- Subject: Re: kern/41918: pppoe BROKEN: panic:kernel diagnostic assertion "
 
 |  I don't know if it is related, but iwn(4) and pppoe(4) are both doing
 |  "funny" things with IFF_UP.  It is inexcusable in the case of iwn(4),
 |  which should modify IFF_RUNNING, instead.  I don't understand how/why
 |  pppoe(4) messes with IFF_UP, yet, but it probably should not.
 |  
 
 What's funny about it? It just clears it on error like all the other
 wireless drivers do. Can you please explain what you mean?
 
 christos