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

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
Subject: Re: kern/41918: pppoe BROKEN: panic:kernel diagnostic assertion "!cpu_softintr_p()" ... subr_kmem.c
From: christos%zoulas.com@localhost (Christos Zoulas)
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

Follow-Ups:
- Re: kern/41918: pppoe BROKEN: panic:kernel diagnostic assertion "!cpu_softintr_p()" ... subr_kmem.c
  - From: David Young

References:
- Re: kern/41918: pppoe BROKEN: panic:kernel diagnostic assertion "!cpu_softintr_p()" ... subr_kmem.c
  - From: David Young

Prev by Date: PR/41925 CVS commit: src/distrib/utils/sysinst
Next by Date: Re: kern/41918: pppoe BROKEN: panic:kernel diagnostic assertion "!cpu_softintr_p()" ... subr_kmem.c
Previous by Thread: Re: kern/41918: pppoe BROKEN: panic:kernel diagnostic assertion "!cpu_softintr_p()" ... subr_kmem.c
Next by Thread: Re: kern/41918: pppoe BROKEN: panic:kernel diagnostic assertion "!cpu_softintr_p()" ... subr_kmem.c
Indexes:

Home | Main Index | Thread Index | Old Index