From owner-freebsd-current Mon Jul 8 16:29:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2A9037B400 for ; Mon, 8 Jul 2002 16:29:28 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FC0E43E31 for ; Mon, 8 Jul 2002 16:29:28 -0700 (PDT) (envelope-from abjenkins@attbi.com) Received: from foo ([24.60.235.125]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020708232928.SVHT8262.rwcrmhc52.attbi.com@foo>; Mon, 8 Jul 2002 23:29:28 +0000 Content-Type: text/plain; charset="iso-8859-1" From: Anthony Jenkins To: Josef Karthauser Subject: Re: KSE M-III status & junior hacker project. Date: Mon, 8 Jul 2002 19:28:50 -0400 User-Agent: KMail/1.4.1 Cc: current@FreeBSD.ORG References: <20020707.123406.26740511.imp@village.org> <20020708180829.GE16325@genius.tao.org.uk> In-Reply-To: <20020708180829.GE16325@genius.tao.org.uk> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200207081928.50162.abjenkins@attbi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday 2002-July-08 14:08, Josef Karthauser wrote: >=20 > On a new kernel I appear to be getting dumps now (along with the crashe= s > ;). Actually it's pretty stable, but there are random crashes occuring, > usually I come back to the machine when I've not used it for a new hour= s > and find it in rebooted and in the kernel debugging due to those "pcm m= ay > sleep locked" type things. I've been looking at the pcm code and I can see where it locks, then allo= cates=20 memory with the M_WAITOK flag thing. I'm wondering if there's a standard= =20 procedure for fixing these... would I just nail down the malloc to a=20 non-sleepable one? Also the lock could be freed before it's unlocked... = is=20 this okay? I'm guessing it is... =09mtx_assert(mtx, MA_OWNED); =09mtx_destroy(mtx); Every time I load my sound driver, top(1) shows the irq10 entry to be loc= ked=20 in "*Giant" state, and if I unload it and do a kldstat it's instant panic= =2E I finally shelled out Radio Shack's ridiculous amount for a null modem ca= ble=20 and can do remote debugging now, but I can't remember the URL for that re= cent=20 series of articles on getting started with CURRENT debugging...anyone? TIA, Anthony > Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message